Hey all,
Yesterday I did a fresh install of Windows 7 64 bit home on my pc.
Since then I have had 5 BSOD's. Some were random when I was afk from the pc, other times it has been while playing a game.
System_Service_Exception was one error
Interupt_Exception_Not_Handled was another
I also had the IRQL more or less equal one which i didn't take down fully but I gather it is one of the most common.
I have attached the dump files below and I hope someone can help me. I do not have a great deal of technological know how, but hoping it is something I can fix.
Thanks in advance
Yesterday I did a fresh install of Windows 7 64 bit home on my pc.
Since then I have had 5 BSOD's. Some were random when I was afk from the pc, other times it has been while playing a game.
System_Service_Exception was one error
Interupt_Exception_Not_Handled was another
I also had the IRQL more or less equal one which i didn't take down fully but I gather it is one of the most common.
I have attached the dump files below and I hope someone can help me. I do not have a great deal of technological know how, but hoping it is something I can fix.
Thanks in advance
Hi -
The zip file attachment is empty.
Please --> http://www.sevenforums.com/crashes-d...tructions.html
Attach resulting zip file to your next post.
Regards. . .
jcgriff2
.
The zip file attachment is empty.
Please --> http://www.sevenforums.com/crashes-d...tructions.html
Attach resulting zip file to your next post.
Regards. . .
jcgriff2
.
Weird they were in there a minute ago. I'll try again 
The dumps to to hardware issues, particularly corrupt memory.
I will post more information from the dumps; but to start with I suggest you download a copy of Memtest86+ - Advanced Memory Diagnostic Tool and burn the ISO to a CD using http://isorecorder.alexfeinman.com/W7. Boot from the CD, and leave it running for at least 7 passes. Please report back with your results.
I will post more information from the dumps; but to start with I suggest you download a copy of Memtest86+ - Advanced Memory Diagnostic Tool and burn the ISO to a CD using http://isorecorder.alexfeinman.com/W7. Boot from the CD, and leave it running for at least 7 passes. Please report back with your results.
Quote:
STOP 0x0000003D: INTERRUPT_EXCEPTION_NOT_HANDLED
(no information available as to the cause)
STOP 0x0000001A: MEMORY_MANAGEMENT
Usual causes: Device driver, memory, kernel
STOP 0x0000004A: IRQL_GT_ZERO_AT_SYSTEM_SERVICE
Usual causes: Device driver
STOP 0x0000004E: PFN_LIST_CORRUPT
Usual causes: Device driver, ?memory
(no information available as to the cause)
STOP 0x0000001A: MEMORY_MANAGEMENT
Usual causes: Device driver, memory, kernel
STOP 0x0000004A: IRQL_GT_ZERO_AT_SYSTEM_SERVICE
Usual causes: Device driver
STOP 0x0000004E: PFN_LIST_CORRUPT
Usual causes: Device driver, ?memory
Code:
Microsoft (R) Windows Debugger Version 6.11.0001.404 X86 Copyright (c) Microsoft Corporation. All rights reserved. Loading Dump File [C:\Users\Owner\AppData\Local\Temp\Temp3_Dump Files.zip\072910-13884-01.dmp] Mini Kernel Dump File: Only registers and stack trace are available Symbol search path is: SRV*c:\symbols*Symbol information Executable search path is: Windows 7 Kernel Version 7600 MP (2 procs) Free x64 Product: WinNt, suite: TerminalServer SingleUserTS Personal Built by: 7600.16385.amd64fre.win7_rtm.090713-1255 Machine Name: Kernel base = 0xfffff800`0284f000 PsLoadedModuleList = 0xfffff800`02a8ce50 Debug session time: Thu Jul 29 11:16:19.631 2010 (GMT-4) System Uptime: 0 days 1:12:48.160 Loading Kernel Symbols ............................................................... ................................................................ ........ Loading User Symbols Loading unloaded module list ........ ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* Use !analyze -v to get detailed debugging information. BugCheck 4E, {99, 3fdac, 0, 0} Probably caused by : memory_corruption ( nt!MiBadShareCount+4c ) Followup: MachineOwner --------- 1: kd> !analyze -v ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* PFN_LIST_CORRUPT (4e) Typically caused by drivers passing bad memory descriptor lists (ie: calling MmUnlockPages twice with the same list, etc). If a kernel debugger is available get the stack trace. Arguments: Arg1: 0000000000000099, A PTE or PFN is corrupt Arg2: 000000000003fdac, page frame number Arg3: 0000000000000000, current page state Arg4: 0000000000000000, 0 Debugging Details: ------------------ BUGCHECK_STR: 0x4E_99 CUSTOMER_CRASH_COUNT: 1 DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT PROCESS_NAME: rundll32.exe CURRENT_IRQL: 2 LAST_CONTROL_TRANSFER: from fffff8000294f32c to fffff800028c0f00 STACK_TEXT: fffff880`05e9a238 fffff800`0294f32c : 00000000`0000004e 00000000`00000099 00000000`0003fdac 00000000`00000000 : nt!KeBugCheckEx fffff880`05e9a240 fffff800`0291fb82 : 00000000`00000002 00000000`00000000 fffffa80`0010bed0 fffff800`02a76788 : nt!MiBadShareCount+0x4c fffff880`05e9a280 fffff800`0298023d : fffffa80`0010bed0 fffff880`05e9a3c0 00000000`00000080 00000000`0005da83 : nt! ?? ::FNODOBFM::`string'+0x11ae2 fffff880`05e9a2e0 fffff800`028743fe : 00000000`00000000 fffff880`05e9a3c0 ffffffff`ffffffff 00000000`000001c0 : nt!MiRemoveLowestPriorityStandbyPage+0x2ad fffff880`05e9a360 fffff800`028ece8e : fffff980`0d406000 00000000`024b6040 fffff880`00000000 00000000`00001000 : nt! ?? ::FNODOBFM::`string'+0x44fc3 fffff880`05e9a550 fffff800`028ecbf4 : fffffa80`02fa1330 00000000`024b6040 fffff880`05e9a690 00000000`00000000 : nt!CcMapAndCopyInToCache+0x20e fffff880`05e9a640 fffff880`01242f40 : fffff8a0`025a6168 fffff880`05e9a8c0 fffffa80`02bcf160 fffff880`05e9a800 : nt!CcCopyWrite+0x194 fffff880`05e9a6d0 fffff880`01247413 : fffffa80`02bcf160 fffffa80`033f8010 fffff880`05e9a801 fffff880`05e9a800 : Ntfs!NtfsCommonWrite+0xda0 fffff880`05e9a890 fffff880`010e023f : fffffa80`033f83b0 fffffa80`033f8010 fffffa80`01941420 00000000`00000001 : Ntfs!NtfsFsdWrite+0x1c3 fffff880`05e9a950 fffff880`010de6df : fffffa80`027d8c30 00000000`00000001 fffffa80`027d8c00 fffffa80`033f8010 : fltmgr!FltpLegacyProcessingAfterPreCallbacksCompleted+0x24f fffff880`05e9a9e0 fffff800`02bd4929 : 00000000`00000001 fffffa80`03bce5f0 00000000`00000001 fffffa80`033f8010 : fltmgr!FltpDispatch+0xcf fffff880`05e9aa40 fffff800`02bd56c3 : fffffa80`033f83f8 fffffa80`041eab00 fffffa80`03bce5f0 fffff880`009e7180 : nt!IopSynchronousServiceTail+0xf9 fffff880`05e9aab0 fffff800`028c0153 : 00000000`00000b01 00000000`000001d0 00000000`00000000 00000000`0029e568 : nt!NtWriteFile+0x7e2 fffff880`05e9abb0 00000000`77bdff3a : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13 00000000`001bde18 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x77bdff3a STACK_COMMAND: kb FOLLOWUP_IP: nt!MiBadShareCount+4c fffff800`0294f32c cc int 3 SYMBOL_STACK_INDEX: 1 SYMBOL_NAME: nt!MiBadShareCount+4c FOLLOWUP_NAME: MachineOwner MODULE_NAME: nt DEBUG_FLR_IMAGE_TIMESTAMP: 4a5bc600 IMAGE_NAME: memory_corruption FAILURE_BUCKET_ID: X64_0x4E_99_nt!MiBadShareCount+4c BUCKET_ID: X64_0x4E_99_nt!MiBadShareCount+4c Followup: MachineOwner --------- Microsoft (R) Windows Debugger Version 6.11.0001.404 X86 Copyright (c) Microsoft Corporation. All rights reserved. Loading Dump File [C:\Users\Owner\AppData\Local\Temp\Temp3_Dump Files.zip\072910-22573-01.dmp] Mini Kernel Dump File: Only registers and stack trace are available Symbol search path is: SRV*c:\symbols*Symbol information Executable search path is: Windows 7 Kernel Version 7600 MP (2 procs) Free x64 Product: WinNt, suite: TerminalServer SingleUserTS Personal Built by: 7600.16539.amd64fre.win7_gdr.100226-1909 Machine Name: Kernel base = 0xfffff800`02805000 PsLoadedModuleList = 0xfffff800`02a42e50 Debug session time: Thu Jul 29 14:56:49.418 2010 (GMT-4) System Uptime: 0 days 3:11:36.948 Loading Kernel Symbols ............................................................... ................................................................ .......... Loading User Symbols Loading unloaded module list ..... ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* Use !analyze -v to get detailed debugging information. BugCheck 1A, {41287, 42228030694d, 0, 0} Probably caused by : dxgmms1.sys ( dxgmms1!VIDMM_SEGMENT::SafeProbeAndLockPages+229 ) Followup: MachineOwner --------- 0: kd> !analyze -v ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* MEMORY_MANAGEMENT (1a) # Any other values for parameter 1 must be individually examined. Arguments: Arg1: 0000000000041287, The subtype of the bugcheck. Arg2: 000042228030694d Arg3: 0000000000000000 Arg4: 0000000000000000 Debugging Details: ------------------ BUGCHECK_STR: 0x1a_41287 CUSTOMER_CRASH_COUNT: 1 DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT PROCESS_NAME: csrss.exe CURRENT_IRQL: 0 TRAP_FRAME: fffff880009be3f0 -- (.trap 0xfffff880009be3f0) NOTE: The trap frame does not contain all registers. Some register values may be zeroed or incorrect. rax=000042228030694d rbx=0000000000000000 rcx=0000000000000002 rdx=0000000000000001 rsi=0000000000000000 rdi=0000000000000000 rip=fffff800028959c7 rsp=fffff880009be580 rbp=0000000000000000 r8=0000000000000001 r9=0000000000000002 r10=fffff6fb7da00000 r11=0000000000000000 r12=0000000000000000 r13=0000000000000000 r14=0000000000000000 r15=0000000000000000 iopl=0 nv up ei pl nz na po nc nt!MmProbeAndLockPages+0x597: fffff800`028959c7 488b00 mov rax,qword ptr [rax] ds:1000:00004222`8030694d=???????????????? Resetting default scope LAST_CONTROL_TRANSFER: from fffff80002821b6e to fffff80002875600 STACK_TEXT: fffff880`009be288 fffff800`02821b6e : 00000000`0000001a 00000000`00041287 00004222`8030694d 00000000`00000000 : nt!KeBugCheckEx fffff880`009be290 fffff800`028736ee : 00000000`00000000 ffffffff`ffffffff 7ff00000`00000000 fffff880`03c1e11a : nt! ?? ::FNODOBFM::`string'+0x42be5 fffff880`009be3f0 fffff800`028959c7 : 00000000`00000000 fffff800`02a01b40 00000000`00000000 fffff800`029a9646 : nt!KiPageFault+0x16e fffff880`009be580 fffff880`03c33a25 : fffffa80`01cab010 00000000`00000000 fffff8a0`00000002 00000000`00000002 : nt!MmProbeAndLockPages+0x597 fffff880`009be690 fffff880`03c2e026 : fffffa80`03912a60 fffff8a0`067743a0 00000000`00000038 00000000`00060000 : dxgmms1!VIDMM_SEGMENT::SafeProbeAndLockPages+0x229 fffff880`009be720 fffff880`03c2f0ea : fffffa80`03912a60 fffff8a0`067743a0 00000000`00000000 00000000`00060000 : dxgmms1!VIDMM_APERTURE_SEGMENT::LockAllocationRange+0x23e fffff880`009be7d0 fffff880`03c21af3 : fffffa80`0390cca0 fffff8a0`067743a0 fffffa80`03903000 fffff880`03c21600 : dxgmms1!VIDMM_MEMORY_SEGMENT::CommitResource+0x176 fffff880`009be8b0 fffff880`03c1e763 : 00000000`00000000 fffffa80`02ab1000 00000000`00000000 fffffa80`0264ab70 : dxgmms1!VIDMM_GLOBAL::PageInAllocations+0xbb fffff880`009be910 fffff880`03c3865d : 00000000`00000000 fffff8a0`011165b0 fffffa80`00000000 fffffa80`02a09510 : dxgmms1!VIDMM_GLOBAL::PrepareDmaBuffer+0xccf fffff880`009beae0 fffff880`03c38398 : fffff800`00b96080 fffff880`03c37d00 fffffa80`00000000 fffffa80`00000000 : dxgmms1!VidSchiSubmitRenderCommand+0x241 fffff880`009becd0 fffff880`03c37e96 : 00000000`00000000 fffffa80`03c5e950 00000000`00000080 fffffa80`038c9010 : dxgmms1!VidSchiSubmitQueueCommand+0x50 fffff880`009bed00 fffff800`02b1aa86 : 00000000`02db2c99 fffffa80`038ca060 fffffa80`01848b30 fffffa80`038ca060 : dxgmms1!VidSchiWorkerThread+0xd6 fffff880`009bed40 fffff800`02853b06 : fffff800`029efe80 fffffa80`038ca060 fffff800`029fdc40 fffff880`0126cbf0 : nt!PspSystemThreadStartup+0x5a fffff880`009bed80 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxStartSystemThread+0x16 STACK_COMMAND: kb FOLLOWUP_IP: dxgmms1!VIDMM_SEGMENT::SafeProbeAndLockPages+229 fffff880`03c33a25 4c8b1d8cd6fdff mov r11,qword ptr [dxgmms1!_imp_g_loggerInfo (fffff880`03c110b8)] SYMBOL_STACK_INDEX: 4 SYMBOL_NAME: dxgmms1!VIDMM_SEGMENT::SafeProbeAndLockPages+229 FOLLOWUP_NAME: MachineOwner MODULE_NAME: dxgmms1 IMAGE_NAME: dxgmms1.sys DEBUG_FLR_IMAGE_TIMESTAMP: 4a5bc578 FAILURE_BUCKET_ID: X64_0x1a_41287_dxgmms1!VIDMM_SEGMENT::SafeProbeAndLockPages+229 BUCKET_ID: X64_0x1a_41287_dxgmms1!VIDMM_SEGMENT::SafeProbeAndLockPages+229 Followup: MachineOwner --------- Microsoft (R) Windows Debugger Version 6.11.0001.404 X86 Copyright (c) Microsoft Corporation. All rights reserved. Loading Dump File [C:\Users\Owner\AppData\Local\Temp\Temp3_Dump Files.zip\072910-22869-01.dmp] Mini Kernel Dump File: Only registers and stack trace are available Symbol search path is: SRV*c:\symbols*Symbol information Executable search path is: Windows 7 Kernel Version 7600 MP (2 procs) Free x64 Product: WinNt, suite: TerminalServer SingleUserTS Personal Built by: 7600.16385.amd64fre.win7_rtm.090713-1255 Machine Name: Kernel base = 0xfffff800`0261d000 PsLoadedModuleList = 0xfffff800`0285ae50 Debug session time: Thu Jul 29 09:27:06.986 2010 (GMT-4) System Uptime: 0 days 1:58:02.184 Loading Kernel Symbols ............................................................... ................................................................ ....... Loading User Symbols Loading unloaded module list ....... ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* Use !analyze -v to get detailed debugging information. BugCheck 4A, {7fefe20184a, 2, 0, fffff880052b4ca0} Probably caused by : ntkrnlmp.exe ( nt!KiSystemServiceExit+245 ) Followup: MachineOwner --------- 1: kd> !analyze -v ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* IRQL_GT_ZERO_AT_SYSTEM_SERVICE (4a) Returning to usermode from a system call at an IRQL > PASSIVE_LEVEL. Arguments: Arg1: 000007fefe20184a, Address of system function (system call routine) Arg2: 0000000000000002, Current IRQL Arg3: 0000000000000000, 0 Arg4: fffff880052b4ca0, 0 Debugging Details: ------------------ PROCESS_NAME: LogonUI.exe BUGCHECK_STR: RAISED_IRQL_FAULT FAULTING_IP: +57bf952f01e0d81c 000007fe`fe20184a ?? ??? CUSTOMER_CRASH_COUNT: 1 DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT CURRENT_IRQL: 2 LAST_CONTROL_TRANSFER: from fffff8000268e469 to fffff8000268ef00 STACK_TEXT: fffff880`052b4a68 fffff800`0268e469 : 00000000`0000004a 000007fe`fe20184a 00000000`00000002 00000000`00000000 : nt!KeBugCheckEx fffff880`052b4a70 fffff800`0268e3a0 : fffffa80`03310060 fffff880`052b4ca0 00000000`001eec48 0000007f`ffffffff : nt!KiBugCheckDispatch+0x69 fffff880`052b4bb0 000007fe`fe20184a : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceExit+0x245 00000000`001eec28 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x7fe`fe20184a STACK_COMMAND: kb FOLLOWUP_IP: nt!KiSystemServiceExit+245 fffff800`0268e3a0 4883ec50 sub rsp,50h SYMBOL_STACK_INDEX: 2 SYMBOL_NAME: nt!KiSystemServiceExit+245 FOLLOWUP_NAME: MachineOwner MODULE_NAME: nt IMAGE_NAME: ntkrnlmp.exe DEBUG_FLR_IMAGE_TIMESTAMP: 4a5bc600 FAILURE_BUCKET_ID: X64_RAISED_IRQL_FAULT_LogonUI.exe_nt!KiSystemServiceExit+245 BUCKET_ID: X64_RAISED_IRQL_FAULT_LogonUI.exe_nt!KiSystemServiceExit+245 Followup: MachineOwner --------- Microsoft (R) Windows Debugger Version 6.11.0001.404 X86 Copyright (c) Microsoft Corporation. All rights reserved. Loading Dump File [C:\Users\Owner\AppData\Local\Temp\Temp3_Dump Files.zip\073010-16598-01.dmp] Mini Kernel Dump File: Only registers and stack trace are available Symbol search path is: SRV*c:\symbols*Symbol information Executable search path is: Windows 7 Kernel Version 7600 MP (2 procs) Free x64 Product: WinNt, suite: TerminalServer SingleUserTS Personal Built by: 7600.16539.amd64fre.win7_gdr.100226-1909 Machine Name: Kernel base = 0xfffff800`02804000 PsLoadedModuleList = 0xfffff800`02a41e50 Debug session time: Thu Jul 29 19:55:47.500 2010 (GMT-4) System Uptime: 0 days 4:58:14.029 Loading Kernel Symbols ............................................................... ................................................................ .......... Loading User Symbols Loading unloaded module list ........ ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* Use !analyze -v to get detailed debugging information. BugCheck 1A, {8887, fffffa80015c9660, fffffa8000bf9010, 705} Probably caused by : hardware_ram ( ZEROED_PAGE_CORRUPTED ) Followup: MachineOwner --------- 1: kd> !analyze -v ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* MEMORY_MANAGEMENT (1a) # Any other values for parameter 1 must be individually examined. Arguments: Arg1: 0000000000008887, The subtype of the bugcheck. Arg2: fffffa80015c9660 Arg3: fffffa8000bf9010 Arg4: 0000000000000705 Debugging Details: ------------------ BUGCHECK_STR: 0x1a_8887 CUSTOMER_CRASH_COUNT: 1 DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT PROCESS_NAME: explorer.exe CURRENT_IRQL: 2 STACK_TEXT: fffff880`05da17e8 fffff800`028957e4 : 00000000`0000001a 00000000`00008887 fffffa80`015c9660 fffffa80`00bf9010 : nt!KeBugCheckEx fffff880`05da17f0 fffff800`028a6457 : fffff8a0`05d5ba70 00000000`00000000 fffff6fb`05d5ba70 fffff8a0`05eb0900 : nt!MiUnlinkPageFromLockedList+0x2e4 fffff880`05da1880 fffff800`0289ac99 : 00000000`00000000 00000000`74322860 80000000`64896963 fffffa80`03fc8878 : nt!MiResolveTransitionFault+0x167 fffff880`05da1910 fffff800`0289049e : 00000000`00000000 000007fe`f36310d0 fffff683`ff79b188 fffffa80`03fc8878 : nt!MiResolveProtoPteFault+0x419 fffff880`05da19b0 fffff800`0288e623 : fffff880`05da1c00 000007fe`f36310d0 00000000`00000000 fffff960`00000000 : nt!MiDispatchFault+0x1de fffff880`05da1ac0 fffff800`028726ee : 00000000`00000008 00000000`000001a0 00000000`00000001 fffffa80`03f843b0 : nt!MmAccessFault+0x343 fffff880`05da1c20 000007fe`f36310d0 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiPageFault+0x16e 00000000`037cf758 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x7fe`f36310d0 STACK_COMMAND: kb SYMBOL_NAME: ZEROED_PAGE_CORRUPTED FOLLOWUP_NAME: MachineOwner MODULE_NAME: hardware IMAGE_NAME: hardware_ram DEBUG_FLR_IMAGE_TIMESTAMP: 0 FAILURE_BUCKET_ID: X64_0x1a_8887_ZEROED_PAGE_CORRUPTED BUCKET_ID: X64_0x1a_8887_ZEROED_PAGE_CORRUPTED Followup: MachineOwner --------- 1: kd> lmtsmn start end module name fffff880`00f7d000 fffff880`00fd4000 ACPI ACPI.sys Mon Jul 13 19:19:34 2009 (4A5BC106) fffff880`03aca000 fffff880`03b54000 afd afd.sys Mon Jul 13 19:21:40 2009 (4A5BC184) fffff880`00dda000 fffff880`00df0000 AgileVpn AgileVpn.sys Mon Jul 13 20:10:24 2009 (4A5BCCF0) fffff880`00dcf000 fffff880`00dda000 amdxata amdxata.sys Tue May 19 13:56:59 2009 (4A12F2EB) fffff880`00d9c000 fffff880`00da5000 atapi atapi.sys Mon Jul 13 19:19:47 2009 (4A5BC113) fffff880`00da5000 fffff880`00dcf000 ataport ataport.SYS Mon Jul 13 19:19:52 2009 (4A5BC118) fffff880`03c78000 fffff880`0428f000 atikmdag atikmdag.sys Mon Aug 17 23:05:47 2009 (4A8A1A8B) fffff880`018d2000 fffff880`018d9000 Beep Beep.SYS Mon Jul 13 20:00:13 2009 (4A5BCA8D) fffff880`0197e000 fffff880`0198f000 blbdrive blbdrive.sys Mon Jul 13 19:35:59 2009 (4A5BC4DF) fffff880`02993000 fffff880`029b1000 bowser bowser.sys Mon Jul 13 19:23:50 2009 (4A5BC206) fffff960`007d0000 fffff960`007f7000 cdd cdd.dll unavailable (00000000) fffff880`04400000 fffff880`0441d000 cdfs cdfs.sys Mon Jul 13 19:19:46 2009 (4A5BC112) fffff880`0189f000 fffff880`018c9000 cdrom cdrom.sys Mon Jul 13 19:19:54 2009 (4A5BC11A) fffff880`00c00000 fffff880`00cc0000 CI CI.dll Mon Jul 13 21:32:13 2009 (4A5BE01D) fffff880`01839000 fffff880`01869000 CLASSPNP CLASSPNP.SYS Mon Jul 13 19:19:58 2009 (4A5BC11E) fffff880`00d24000 fffff880`00d82000 CLFS CLFS.SYS Mon Jul 13 19:19:57 2009 (4A5BC11D) fffff880`010f8000 fffff880`0116b000 cng cng.sys Mon Jul 13 19:49:40 2009 (4A5BC814) fffff880`0181d000 fffff880`0182d000 CompositeBus CompositeBus.sys Mon Jul 13 20:00:33 2009 (4A5BCAA1) fffff880`039bd000 fffff880`039cb000 crashdmp crashdmp.sys Mon Jul 13 20:01:01 2009 (4A5BCABD) fffff880`03aa6000 fffff880`03ac4000 dfsc dfsc.sys Mon Jul 13 19:23:44 2009 (4A5BC200) fffff880`03a97000 fffff880`03aa6000 discache discache.sys Mon Jul 13 19:37:18 2009 (4A5BC52E) fffff880`01200000 fffff880`01216000 disk disk.sys Mon Jul 13 19:19:57 2009 (4A5BC11D) fffff880`04556000 fffff880`04578000 drmk drmk.sys Mon Jul 13 21:01:25 2009 (4A5BD8E5) fffff880`039d7000 fffff880`039e0000 dump_atapi dump_atapi.sys Mon Jul 13 19:19:47 2009 (4A5BC113) fffff880`039cb000 fffff880`039d7000 dump_dumpata dump_dumpata.sys Mon Jul 13 19:19:47 2009 (4A5BC113) fffff880`039e0000 fffff880`039f3000 dump_dumpfve dump_dumpfve.sys Mon Jul 13 19:21:51 2009 (4A5BC18F) fffff880`0457e000 fffff880`0458a000 Dxapi Dxapi.sys Mon Jul 13 19:38:28 2009 (4A5BC574) fffff880`0428f000 fffff880`04383000 dxgkrnl dxgkrnl.sys Thu Oct 01 21:00:14 2009 (4AC5509E) fffff880`04383000 fffff880`043c9000 dxgmms1 dxgmms1.sys Mon Jul 13 19:38:32 2009 (4A5BC578) fffff880`01086000 fffff880`0109a000 fileinfo fileinfo.sys Mon Jul 13 19:34:25 2009 (4A5BC481) fffff880`0103a000 fffff880`01086000 fltmgr fltmgr.sys Mon Jul 13 19:19:59 2009 (4A5BC11F) fffff880`013ee000 fffff880`013f8000 Fs_Rec Fs_Rec.sys unavailable (00000000) fffff880`01000000 fffff880`0103a000 fvevol fvevol.sys Fri Sep 25 22:34:26 2009 (4ABD7DB2) fffff880`01400000 fffff880`0144a000 fwpkclnt fwpkclnt.sys Mon Jul 13 19:21:08 2009 (4A5BC164) fffff880`03944000 fffff880`0394c000 gdrv gdrv.sys Sat Oct 13 03:22:00 2007 (47107218) fffff800`02de0000 fffff800`02e29000 hal hal.dll Mon Jul 13 21:27:36 2009 (4A5BDF08) fffff880`043c9000 fffff880`043ed000 HDAudBus HDAudBus.sys Mon Jul 13 20:06:13 2009 (4A5BCBF5) fffff880`044bd000 fffff880`04519000 HdAudio HdAudio.sys Mon Jul 13 20:06:59 2009 (4A5BCC23) fffff880`03800000 fffff880`03809000 hiber_atapi hiber_atapi.sys Mon Jul 13 19:19:47 2009 (4A5BC113) fffff880`039f3000 fffff880`039ff000 hiber_dumpata hiber_dumpata.sys Mon Jul 13 19:19:47 2009 (4A5BC113) fffff880`03809000 fffff880`0381c000 hiber_dumpfve hiber_dumpfve.sys Mon Jul 13 19:21:51 2009 (4A5BC18F) fffff880`04598000 fffff880`045b1000 HIDCLASS HIDCLASS.SYS Mon Jul 13 20:06:21 2009 (4A5BCBFD) fffff880`045b1000 fffff880`045b9080 HIDPARSE HIDPARSE.SYS Mon Jul 13 20:06:17 2009 (4A5BCBF9) fffff880`0458a000 fffff880`04598000 hidusb hidusb.sys Mon Jul 13 20:06:22 2009 (4A5BCBFE) fffff880`028cb000 fffff880`02993000 HTTP HTTP.sys Mon Jul 13 19:22:16 2009 (4A5BC1A8) fffff880`01464000 fffff880`0146d000 hwpolicy hwpolicy.sys Mon Jul 13 19:19:22 2009 (4A5BC0FA) fffff880`019b5000 fffff880`019cb000 intelppm intelppm.sys Mon Jul 13 19:19:25 2009 (4A5BC0FD) fffff880`04933000 fffff880`04942000 kbdclass kbdclass.sys Mon Jul 13 19:19:50 2009 (4A5BC116) fffff880`045bc000 fffff880`045ca000 kbdhid kbdhid.sys Mon Jul 13 20:00:20 2009 (4A5BCA94) fffff800`00bad000 fffff800`00bb7000 kdcom kdcom.dll Mon Jul 13 21:31:07 2009 (4A5BDFDB) fffff880`04953000 fffff880`04996000 ks ks.sys Mon Jul 13 20:00:31 2009 (4A5BCA9F) fffff880`013c3000 fffff880`013dd000 ksecdd ksecdd.sys Mon Jul 13 19:20:54 2009 (4A5BC156) fffff880`015d1000 fffff880`015fc000 ksecpkg ksecpkg.sys Fri Dec 11 01:03:32 2009 (4B21E0B4) fffff880`04578000 fffff880`0457d200 ksthunk ksthunk.sys Mon Jul 13 20:00:19 2009 (4A5BCA93) fffff880`04476000 fffff880`0448b000 lltdio lltdio.sys Mon Jul 13 20:08:50 2009 (4A5BCC92) fffff880`04453000 fffff880`04476000 luafv luafv.sys Mon Jul 13 19:26:13 2009 (4A5BC295) fffff880`00ccc000 fffff880`00d10000 mcupdate_GenuineIntel mcupdate_GenuineIntel.dll Mon Jul 13 21:29:10 2009 (4A5BDF66) fffff880`045d7000 fffff880`045e5000 monitor monitor.sys Mon Jul 13 19:38:52 2009 (4A5BC58C) fffff880`04942000 fffff880`04951000 mouclass mouclass.sys Mon Jul 13 19:19:50 2009 (4A5BC116) fffff880`045ca000 fffff880`045d7000 mouhid mouhid.sys Mon Jul 13 20:00:20 2009 (4A5BCA94) fffff880`00d82000 fffff880`00d9c000 mountmgr mountmgr.sys Mon Jul 13 19:19:54 2009 (4A5BC11A) fffff880`029b1000 fffff880`029c9000 mpsdrv mpsdrv.sys Mon Jul 13 20:08:25 2009 (4A5BCC79) fffff880`029c9000 fffff880`029f6000 mrxsmb mrxsmb.sys Sat Feb 27 02:52:19 2010 (4B88CF33) fffff880`02800000 fffff880`0284e000 mrxsmb10 mrxsmb10.sys Sat Feb 27 02:52:28 2010 (4B88CF3C) fffff880`0284e000 fffff880`02871000 mrxsmb20 mrxsmb20.sys Sat Feb 27 02:52:26 2010 (4B88CF3A) fffff880`01937000 fffff880`01942000 Msfs Msfs.SYS unavailable (00000000) fffff880`00fdd000 fffff880`00fe7000 msisadrv msisadrv.sys Mon Jul 13 19:19:26 2009 (4A5BC0FE) fffff880`0109a000 fffff880`010f8000 msrpc msrpc.sys unavailable (00000000) fffff880`03a8c000 fffff880`03a97000 mssmbios mssmbios.sys Mon Jul 13 19:31:10 2009 (4A5BC3BE) fffff880`01452000 fffff880`01464000 mup mup.sys Mon Jul 13 19:23:45 2009 (4A5BC201) fffff880`0147f000 fffff880`01571000 ndis ndis.sys Mon Jul 13 19:21:40 2009 (4A5BC184) fffff880`048a2000 fffff880`048ae000 ndistapi ndistapi.sys Mon Jul 13 20:10:00 2009 (4A5BCCD8) fffff880`048ae000 fffff880`048dd000 ndiswan ndiswan.sys Mon Jul 13 20:10:11 2009 (4A5BCCE3) fffff880`0485a000 fffff880`0486f000 NDProxy NDProxy.SYS Mon Jul 13 20:10:05 2009 (4A5BCCDD) fffff880`03bc8000 fffff880`03bd7000 netbios netbios.sys Mon Jul 13 20:09:26 2009 (4A5BCCB6) fffff880`03b54000 fffff880`03b99000 netbt netbt.sys Mon Jul 13 19:21:28 2009 (4A5BC178) fffff880`01571000 fffff880`015d1000 NETIO NETIO.SYS Mon Jul 13 19:21:46 2009 (4A5BC18A) fffff880`01942000 fffff880`01953000 Npfs Npfs.SYS Mon Jul 13 19:19:48 2009 (4A5BC114) fffff880`03a80000 fffff880`03a8c000 nsiproxy nsiproxy.sys Mon Jul 13 19:21:02 2009 (4A5BC15E) fffff800`02804000 fffff800`02de0000 nt ntkrnlmp.exe Sat Feb 27 02:55:23 2010 (4B88CFEB) fffff880`01220000 fffff880`013c3000 Ntfs Ntfs.sys Mon Jul 13 19:20:47 2009 (4A5BC14F) fffff880`018c9000 fffff880`018d2000 Null Null.SYS unavailable (00000000) fffff880`03ba2000 fffff880`03bc8000 pacer pacer.sys Mon Jul 13 20:09:41 2009 (4A5BCCC5) fffff880`01800000 fffff880`0181d000 parport parport.sys Mon Jul 13 20:00:40 2009 (4A5BCAA8) fffff880`00e40000 fffff880`00e55000 partmgr partmgr.sys Mon Jul 13 19:19:58 2009 (4A5BC11E) fffff880`00e00000 fffff880`00e33000 pci pci.sys Mon Jul 13 19:19:51 2009 (4A5BC117) fffff880`00fe7000 fffff880`00fee000 pciide pciide.sys Mon Jul 13 19:19:49 2009 (4A5BC115) fffff880`00fee000 fffff880`00ffe000 PCIIDEX PCIIDEX.SYS Mon Jul 13 19:19:48 2009 (4A5BC114) fffff880`013dd000 fffff880`013ee000 pcw pcw.sys Mon Jul 13 19:19:27 2009 (4A5BC0FF) fffff880`034d1000 fffff880`03577000 peauth peauth.sys Mon Jul 13 21:01:19 2009 (4A5BD8DF) fffff880`04519000 fffff880`04556000 portcls portcls.sys Mon Jul 13 20:06:27 2009 (4A5BCC03) fffff880`00d10000 fffff880`00d24000 PSHED PSHED.dll Mon Jul 13 21:32:23 2009 (4A5BE027) fffff880`0487e000 fffff880`048a2000 rasl2tp rasl2tp.sys Mon Jul 13 20:10:11 2009 (4A5BCCE3) fffff880`048dd000 fffff880`048f8000 raspppoe raspppoe.sys Mon Jul 13 20:10:17 2009 (4A5BCCE9) fffff880`048f8000 fffff880`04919000 raspptp raspptp.sys Mon Jul 13 20:10:18 2009 (4A5BCCEA) fffff880`04919000 fffff880`04933000 rassstp rassstp.sys Mon Jul 13 20:10:25 2009 (4A5BCCF1) fffff880`03a2f000 fffff880`03a80000 rdbss rdbss.sys Mon Jul 13 19:24:09 2009 (4A5BC219) fffff880`0191c000 fffff880`01925000 RDPCDD RDPCDD.sys Mon Jul 13 20:16:34 2009 (4A5BCE62) fffff880`01925000 fffff880`0192e000 rdpencdd rdpencdd.sys Mon Jul 13 20:16:34 2009 (4A5BCE62) fffff880`0192e000 fffff880`01937000 rdprefmp rdprefmp.sys Mon Jul 13 20:16:35 2009 (4A5BCE63) fffff880`011b7000 fffff880`011f1000 rdyboost rdyboost.sys Mon Jul 13 19:34:34 2009 (4A5BC48A) fffff880`0448b000 fffff880`044a3000 rspndr rspndr.sys Mon Jul 13 20:08:50 2009 (4A5BCC92) fffff880`019cb000 fffff880`019fd000 Rt64win7 Rt64win7.sys Thu Feb 26 04:04:13 2009 (49A65B0D) fffff880`03577000 fffff880`03582000 secdrv secdrv.SYS Wed Sep 13 09:18:38 2006 (4508052E) fffff880`03c67000 fffff880`03c73000 serenum serenum.sys Mon Jul 13 20:00:33 2009 (4A5BCAA1) fffff880`03bd7000 fffff880`03bf4000 serial serial.sys Mon Jul 13 20:00:40 2009 (4A5BCAA8) fffff880`0144a000 fffff880`01452000 spldr spldr.sys Mon May 11 12:56:27 2009 (4A0858BB) fffff880`0394c000 fffff880`039bd000 spsys spsys.sys Mon May 11 13:20:58 2009 (4A085E7A) fffff880`038ac000 fffff880`03944000 srv srv.sys Tue Dec 08 03:32:55 2009 (4B1E0F37) fffff880`03400000 fffff880`03469000 srv2 srv2.sys Mon Jul 13 19:25:02 2009 (4A5BC24E) fffff880`03582000 fffff880`035af000 srvnet srvnet.sys Tue Dec 08 03:32:26 2009 (4B1E0F1A) fffff880`04951000 fffff880`04952480 swenum swenum.sys Mon Jul 13 20:00:18 2009 (4A5BCA92) fffff880`01600000 fffff880`017fd000 tcpip tcpip.sys Mon Jul 13 19:25:34 2009 (4A5BC26E) fffff880`035af000 fffff880`035c1000 tcpipreg tcpipreg.sys Mon Jul 13 20:09:49 2009 (4A5BCCCD) fffff880`01971000 fffff880`0197e000 TDI TDI.SYS Mon Jul 13 19:21:18 2009 (4A5BC16E) fffff880`01953000 fffff880`01971000 tdx tdx.sys Mon Jul 13 19:21:15 2009 (4A5BC16B) fffff880`03a1b000 fffff880`03a2f000 termdd termdd.sys Mon Jul 13 20:16:36 2009 (4A5BCE64) fffff960`00410000 fffff960`0041a000 TSDDD TSDDD.dll unavailable (00000000) fffff880`0198f000 fffff880`019b5000 tunnel tunnel.sys Mon Jul 13 20:09:37 2009 (4A5BCCC1) fffff880`04996000 fffff880`049a8000 umbus umbus.sys Mon Jul 13 20:06:56 2009 (4A5BCC20) fffff880`045ba000 fffff880`045bbf00 USBD USBD.SYS Mon Jul 13 20:06:23 2009 (4A5BCBFF) fffff880`03c56000 fffff880`03c67000 usbehci usbehci.sys Mon Jul 13 20:06:30 2009 (4A5BCC06) fffff880`04800000 fffff880`0485a000 usbhub usbhub.sys Mon Jul 13 20:07:09 2009 (4A5BCC2D) fffff880`03c00000 fffff880`03c56000 USBPORT USBPORT.SYS Mon Jul 13 20:06:31 2009 (4A5BCC07) fffff880`043ed000 fffff880`043fa000 usbuhci usbuhci.sys Mon Jul 13 20:06:27 2009 (4A5BCC03) fffff880`00e33000 fffff880`00e40000 vdrvroot vdrvroot.sys Mon Jul 13 20:01:31 2009 (4A5BCADB) fffff880`018d9000 fffff880`018e7000 vga vga.sys Mon Jul 13 19:38:47 2009 (4A5BC587) fffff880`018e7000 fffff880`0190c000 VIDEOPRT VIDEOPRT.SYS Mon Jul 13 19:38:51 2009 (4A5BC58B) fffff880`00e55000 fffff880`00e6a000 volmgr volmgr.sys Mon Jul 13 19:19:57 2009 (4A5BC11D) fffff880`00e6a000 fffff880`00ec6000 volmgrx volmgrx.sys unavailable (00000000) fffff880`0116b000 fffff880`011b7000 volsnap volsnap.sys Mon Jul 13 19:20:08 2009 (4A5BC128) fffff880`03a00000 fffff880`03a1b000 wanarp wanarp.sys Mon Jul 13 20:10:21 2009 (4A5BCCED) fffff880`0190c000 fffff880`0191c000 watchdog watchdog.sys Mon Jul 13 19:37:35 2009 (4A5BC53F) fffff880`00eca000 fffff880`00f6e000 Wdf01000 Wdf01000.sys Mon Jul 13 19:22:07 2009 (4A5BC19F) fffff880`00f6e000 fffff880`00f7d000 WDFLDR WDFLDR.SYS Mon Jul 13 19:19:54 2009 (4A5BC11A) fffff880`03b99000 fffff880`03ba2000 wfplwf wfplwf.sys Mon Jul 13 20:09:26 2009 (4A5BCCB6) fffff960`000b0000 fffff960`003bf000 win32k win32k.sys unavailable (00000000) fffff880`00fd4000 fffff880`00fdd000 WMILIB WMILIB.SYS Mon Jul 13 19:19:51 2009 (4A5BC117) Unloaded modules: fffff880`0441d000 fffff880`0442b000 crashdmp.sys Timestamp: unavailable (00000000) Checksum: 00000000 fffff880`0442b000 fffff880`04437000 dump_ataport Timestamp: unavailable (00000000) Checksum: 00000000 fffff880`04437000 fffff880`04440000 dump_atapi.s Timestamp: unavailable (00000000) Checksum: 00000000 fffff880`04440000 fffff880`04453000 dump_dumpfve Timestamp: unavailable (00000000) Checksum: 00000000 fffff880`01869000 fffff880`01877000 crashdmp.sys Timestamp: unavailable (00000000) Checksum: 00000000 fffff880`01877000 fffff880`01883000 dump_ataport Timestamp: unavailable (00000000) Checksum: 00000000 fffff880`01883000 fffff880`0188c000 dump_atapi.s Timestamp: unavailable (00000000) Checksum: 00000000 fffff880`0188c000 fffff880`0189f000 dump_dumpfve Timestamp: unavailable (00000000) Checksum: 00000000
I found the following out of date drivers on your system. Win 7 does not like older drivers. The driver in red font is really out of date.
gdrv.sys Sat Oct 13 03:22:00 2007 - appears to be a driver for Gigabyte's Dynamic Energy Saver Advanced program. I suggest you uninstall this utility if you can.
Rt64win7.sys Thu Feb 26 04:04:13 2009 - Realtek 8101E/8168/8169 Network Driver Interface Specification 6.20 64-bit Driver Realtek. See there is an update for this driver.
Update drivers from the manufacturers' websites rather than using Windows Update or Device manager.
If Memtest checks back clean after 5+ passes, follow these instructions for enabling driver verifier: Using Driver Verifier to identify issues with Drivers
gdrv.sys Sat Oct 13 03:22:00 2007 - appears to be a driver for Gigabyte's Dynamic Energy Saver Advanced program. I suggest you uninstall this utility if you can.
Rt64win7.sys Thu Feb 26 04:04:13 2009 - Realtek 8101E/8168/8169 Network Driver Interface Specification 6.20 64-bit Driver Realtek. See there is an update for this driver.
Update drivers from the manufacturers' websites rather than using Windows Update or Device manager.
If Memtest checks back clean after 5+ passes, follow these instructions for enabling driver verifier: Using Driver Verifier to identify issues with Drivers
Quote:
Please follow these instructions in order to run it:
Using Driver Verifier is an iffy proposition. Most times it'll crash and it'll tell you what the driver is. But sometimes it'll crash and won't tell you the driver. Other times it'll crash before you can log in to Windows. If you can't get to Safe Mode, then you'll have to resort to offline editing of the registry to disable Driver Verifier.
So, I'd suggest that you first backup your stuff and then make sure you've got access to another computer so you can contact us if problems arise. Then make a System Restore point (so you can restore the system using the Vista/Windows 7 Startup Repair feature).
Then, here's the procedure:
- Go to Start and type in "verifier" (without the quotes) and press Enter
- Select "Create custom settings (for code developers)" and click "Next"
- Select "Select individual settings from a full list" and click "Next"
- Select everything EXCEPT FOR "Low Resource Simulation" and click "Next"
- Select "Select driver names from a list" and click "Next"
Then select all drivers NOT provided by Microsoft and click "Next"
- Select "Finish" on the next page.
Reboot the system and wait for it to crash to the Blue Screen. Continue to use your system normally, and if you know what causes the crash, do that repeatedly. The objective here is to get the system to crash because Driver Verifier is stressing the drivers out. If it doesn't crash for you, then let it run for at least 36 hours of continuous operation (an estimate on my part).
Reboot into Windows (after the crash) and turn off Driver Verifier by going back in and selecting "Delete existing settings" on the first page, then locate and zip up the memory dump file and upload it with your next post.
If you can't get into Windows because it crashes too soon, try it in Safe Mode.
If you can't get into Safe Mode, try using System Restore from your installation DVD to set the system back to the previous restore point that you created.
If that doesn't work, post back and we'll have to see about fixing the registry entry off-line.
More info on this at this link: Using Driver Verifier to identify issues with Windows drivers for advanced users
Using Driver Verifier is an iffy proposition. Most times it'll crash and it'll tell you what the driver is. But sometimes it'll crash and won't tell you the driver. Other times it'll crash before you can log in to Windows. If you can't get to Safe Mode, then you'll have to resort to offline editing of the registry to disable Driver Verifier.
So, I'd suggest that you first backup your stuff and then make sure you've got access to another computer so you can contact us if problems arise. Then make a System Restore point (so you can restore the system using the Vista/Windows 7 Startup Repair feature).
Then, here's the procedure:
- Go to Start and type in "verifier" (without the quotes) and press Enter
- Select "Create custom settings (for code developers)" and click "Next"
- Select "Select individual settings from a full list" and click "Next"
- Select everything EXCEPT FOR "Low Resource Simulation" and click "Next"
- Select "Select driver names from a list" and click "Next"
Then select all drivers NOT provided by Microsoft and click "Next"
- Select "Finish" on the next page.
Reboot the system and wait for it to crash to the Blue Screen. Continue to use your system normally, and if you know what causes the crash, do that repeatedly. The objective here is to get the system to crash because Driver Verifier is stressing the drivers out. If it doesn't crash for you, then let it run for at least 36 hours of continuous operation (an estimate on my part).
Reboot into Windows (after the crash) and turn off Driver Verifier by going back in and selecting "Delete existing settings" on the first page, then locate and zip up the memory dump file and upload it with your next post.
If you can't get into Windows because it crashes too soon, try it in Safe Mode.
If you can't get into Safe Mode, try using System Restore from your installation DVD to set the system back to the previous restore point that you created.
If that doesn't work, post back and we'll have to see about fixing the registry entry off-line.
More info on this at this link: Using Driver Verifier to identify issues with Windows drivers for advanced users
Cheers for the help, I'll try the memtest then post back here.
You are welcome, Watson. We are waiting for the results of Memtest. Don't forget about that obsolete driver; old drivers can and do cause crashes.
Memtest came back with no errors after I left it running all night. There are a couple of drivers I have found that need updating so I'm gonna do that now. Haven't had a blue screen for probably the longest stretch so far.
That is good to hear on both counts. If you have another blue screen, post the dump and enable Driver Verifier. Driver Verifier will cause BSOD's; it is supposed to.
Knew it wouldn't last 
latest dump file with error IRQL_Not_Less_Or_Equal
Will try the driver verifier now.
latest dump file with error IRQL_Not_Less_Or_Equal
Will try the driver verifier now.
Ok got a few blue screens on startup after running the verifier.
Don't think it said on the screen which drivers they were though. Was able to get in with safe mode+networking.
Attached are two more dump reports from the blue screens I got on restart with verifier.
Should I continue with the verifier? If not how do I cancel it. The guide was fairly vague about that bit.
Cheers again
Don't think it said on the screen which drivers they were though. Was able to get in with safe mode+networking.
Attached are two more dump reports from the blue screens I got on restart with verifier.
Should I continue with the verifier? If not how do I cancel it. The guide was fairly vague about that bit.
Cheers again
Ok I can no longer get in without safe mode. As soon as the desktop comes out I get a BSOD using the verifier.
I'm sorry to see that. Unfortunately this dump does not tell us very much.
I didn't see your other dump. I will look at it now.
Quote:
STOP 0x0000000A: IRQL_NOT_LESS_OR_EQUAL
Usual causes: Kernel mode driver, System Service, BIOS, Windows, Virus scanner, Backup tool, compatibility
Usual causes: Kernel mode driver, System Service, BIOS, Windows, Virus scanner, Backup tool, compatibility
Code:
******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* Use !analyze -v to get detailed debugging information. BugCheck A, {fffffa0002a05250, 2, 1, fffff80002893fe6} ***** Debugger could not find nt in module list, module list might be corrupt, error 0x80070057. Probably caused by : Unknown_Image ( ANALYSIS_INCONCLUSIVE ) Followup: MachineOwner 
�� Quote: Originally Posted by Watson 
Ok got a few blue screens on startup after running the verifier.
Don't think it said on the screen which drivers they were though. Was able to get in with safe mode+networking.
Attached are two more dump reports from the blue screens I got on restart with verifier.
Should I continue with the verifier? If not how do I cancel it. The guide was fairly vague about that bit.
Cheers again
Don't think it said on the screen which drivers they were though. Was able to get in with safe mode+networking.
Attached are two more dump reports from the blue screens I got on restart with verifier.
Should I continue with the verifier? If not how do I cancel it. The guide was fairly vague about that bit.
Cheers again
Both of these dumps blame DB3G.sys.
Code:
Microsoft (R) Windows Debugger Version 6.11.0001.404 X86 Copyright (c) Microsoft Corporation. All rights reserved. Loading Dump File [C:\Users\Owner\AppData\Local\Temp\Temp1_dump fles.zip\073110-22869-01.dmp] Mini Kernel Dump File: Only registers and stack trace are available Symbol search path is: SRV*c:\symbols*Symbol information Executable search path is: Windows 7 Kernel Version 7600 MP (2 procs) Free x64 Product: WinNt, suite: TerminalServer SingleUserTS Personal Built by: 7600.16539.amd64fre.win7_gdr.100226-1909 Machine Name: Kernel base = 0xfffff800`02863000 PsLoadedModuleList = 0xfffff800`02aa0e50 Debug session time: Sat Jul 31 13:11:17.651 2010 (GMT-4) System Uptime: 0 days 0:00:33.056 Loading Kernel Symbols ............................................................... ................................................................ ....... Loading User Symbols Loading unloaded module list .... ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* Use !analyze -v to get detailed debugging information. BugCheck C4, {f6, 474747470000011c, fffffa80049ab230, fffff880049a60f3} Unable to load image \SystemRoot\system32\drivers\DB3G.sys, Win32 error 0n2 *** WARNING: Unable to verify timestamp for DB3G.sys *** ERROR: Module load completed but symbols could not be loaded for DB3G.sys Probably caused by : DB3G.sys ( DB3G+20f3 ) Followup: MachineOwner --------- 0: kd> !analyze -v ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* DRIVER_VERIFIER_DETECTED_VIOLATION (c4) A device driver attempting to corrupt the system has been caught. This is because the driver was specified in the registry as being suspect (by the administrator) and the kernel has enabled substantial checking of this driver. If the driver attempts to corrupt the system, bugchecks 0xC4, 0xC1 and 0xA will be among the most commonly seen crashes. Arguments: Arg1: 00000000000000f6, Referencing user handle as KernelMode. Arg2: 474747470000011c, Handle value being referenced. Arg3: fffffa80049ab230, Address of the current process. Arg4: fffff880049a60f3, Address inside the driver that is performing the incorrect reference. Debugging Details: ------------------ BUGCHECK_STR: 0xc4_f6 CUSTOMER_CRASH_COUNT: 1 DEFAULT_BUCKET_ID: VERIFIER_ENABLED_VISTA_MINIDUMP PROCESS_NAME: razerhid.exe CURRENT_IRQL: 0 LAST_CONTROL_TRANSFER: from fffff80002d5d3dc to fffff800028d3600 STACK_TEXT: fffff880`06da0728 fffff800`02d5d3dc : 00000000`000000c4 00000000`000000f6 47474747`0000011c fffffa80`049ab230 : nt!KeBugCheckEx fffff880`06da0730 fffff800`02d72ae4 : fffffa80`049ab230 47474747`c0000022 fffffa80`00000000 fffff980`08e34ee0 : nt!VerifierBugCheckIfAppropriate+0x3c fffff880`06da0770 fffff800`02b2f580 : 0012019f`014fb200 fffff880`06da09a0 00000000`00000000 fffffa80`03fea500 : nt!VfCheckUserHandle+0x1b4 fffff880`06da0850 fffff800`02bab425 : fffffa80`00000000 fffffa80`00100000 00000000`00000000 fffff800`02bef600 : nt! ?? ::NNGAKEGL::`string'+0x20e1e fffff880`06da0920 fffff800`02d72878 : fffffa80`04982910 fffff980`08e5aee0 fffffa80`0409a0d8 fffff800`02bef6b7 : nt!ObReferenceObjectByHandle+0x25 fffff880`06da0970 fffff880`049a60f3 : fffff980`08e5aee0 00000000`00000002 fffffa80`03fea560 00000000`00000001 : nt!VerifierObReferenceObjectByHandle+0x48 fffff880`06da09c0 fffff980`08e5aee0 : 00000000`00000002 fffffa80`03fea560 00000000`00000001 fffff880`049a6fa8 : DB3G+0x20f3 fffff880`06da09c8 00000000`00000002 : fffffa80`03fea560 00000000`00000001 fffff880`049a6fa8 00000000`00000000 : 0xfffff980`08e5aee0 fffff880`06da09d0 fffffa80`03fea560 : 00000000`00000001 fffff880`049a6fa8 00000000`00000000 fffffa80`03fea560 : 0x2 fffff880`06da09d8 00000000`00000001 : fffff880`049a6fa8 00000000`00000000 fffffa80`03fea560 00000000`00000002 : 0xfffffa80`03fea560 fffff880`06da09e0 fffff880`049a6fa8 : 00000000`00000000 fffffa80`03fea560 00000000`00000002 00000000`049e8010 : 0x1 fffff880`06da09e8 00000000`00000000 : fffffa80`03fea560 00000000`00000002 00000000`049e8010 fffff800`02d75d86 : DB3G+0x2fa8 STACK_COMMAND: kb FOLLOWUP_IP: DB3G+20f3 fffff880`049a60f3 89842480000000 mov dword ptr [rsp+80h],eax SYMBOL_STACK_INDEX: 6 SYMBOL_NAME: DB3G+20f3 FOLLOWUP_NAME: MachineOwner MODULE_NAME: DB3G IMAGE_NAME: DB3G.sys DEBUG_FLR_IMAGE_TIMESTAMP: 436ef527 FAILURE_BUCKET_ID: X64_0xc4_f6_VRF_DB3G+20f3 BUCKET_ID: X64_0xc4_f6_VRF_DB3G+20f3 Followup: MachineOwner --------- Microsoft (R) Windows Debugger Version 6.11.0001.404 X86 Copyright (c) Microsoft Corporation. All rights reserved. Loading Dump File [C:\Users\Owner\AppData\Local\Temp\Temp1_dump fles.zip\073110-19500-01.dmp] Mini Kernel Dump File: Only registers and stack trace are available Symbol search path is: SRV*c:\symbols*Symbol information Executable search path is: Windows 7 Kernel Version 7600 MP (2 procs) Free x64 Product: WinNt, suite: TerminalServer SingleUserTS Personal Built by: 7600.16539.amd64fre.win7_gdr.100226-1909 Machine Name: Kernel base = 0xfffff800`0280d000 PsLoadedModuleList = 0xfffff800`02a4ae50 Debug session time: Sat Jul 31 13:00:26.384 2010 (GMT-4) System Uptime: 0 days 0:30:06.914 Loading Kernel Symbols ............................................................... ................................................................ ........ Loading User Symbols Loading unloaded module list .... ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* Use !analyze -v to get detailed debugging information. BugCheck C4, {f6, 737373730000011c, fffffa8003f59930, fffff88004a1b0f3} Unable to load image \SystemRoot\system32\drivers\DB3G.sys, Win32 error 0n2 *** WARNING: Unable to verify timestamp for DB3G.sys *** ERROR: Module load completed but symbols could not be loaded for DB3G.sys Probably caused by : DB3G.sys ( DB3G+20f3 ) Followup: MachineOwner --------- 1: kd> !analyze -v ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* DRIVER_VERIFIER_DETECTED_VIOLATION (c4) A device driver attempting to corrupt the system has been caught. This is because the driver was specified in the registry as being suspect (by the administrator) and the kernel has enabled substantial checking of this driver. If the driver attempts to corrupt the system, bugchecks 0xC4, 0xC1 and 0xA will be among the most commonly seen crashes. Arguments: Arg1: 00000000000000f6, Referencing user handle as KernelMode. Arg2: 737373730000011c, Handle value being referenced. Arg3: fffffa8003f59930, Address of the current process. Arg4: fffff88004a1b0f3, Address inside the driver that is performing the incorrect reference. Debugging Details: ------------------ BUGCHECK_STR: 0xc4_f6 CUSTOMER_CRASH_COUNT: 1 DEFAULT_BUCKET_ID: VERIFIER_ENABLED_VISTA_MINIDUMP PROCESS_NAME: razerhid.exe CURRENT_IRQL: 0 LAST_CONTROL_TRANSFER: from fffff80002d073dc to fffff8000287d600 STACK_TEXT: fffff880`06cc3728 fffff800`02d073dc : 00000000`000000c4 00000000`000000f6 73737373`0000011c fffffa80`03f59930 : nt!KeBugCheckEx fffff880`06cc3730 fffff800`02d1cae4 : fffffa80`03f59930 73737373`c0000022 fffffa80`00000000 fffff980`0fea2ee0 : nt!VerifierBugCheckIfAppropriate+0x3c fffff880`06cc3770 fffff800`02ad9580 : fffff800`029f7e80 fffff880`06cc39a0 00000000`00000000 fffffa80`018c8b00 : nt!VfCheckUserHandle+0x1b4 fffff880`06cc3850 fffff800`02b55425 : fffffa80`018c8b00 00000000`00100000 00000000`00000000 fffff800`02d13200 : nt! ?? ::NNGAKEGL::`string'+0x20e1e fffff880`06cc3920 fffff800`02d1c878 : fffffa80`03ca0e10 fffff980`10f2cee0 fffffa80`040210d8 fffff800`02b996b7 : nt!ObReferenceObjectByHandle+0x25 fffff880`06cc3970 fffff880`04a1b0f3 : fffff980`10f2cee0 00000000`00000002 fffffa80`018c8b00 00000000`00000001 : nt!VerifierObReferenceObjectByHandle+0x48 fffff880`06cc39c0 fffff980`10f2cee0 : 00000000`00000002 fffffa80`018c8b00 00000000`00000001 fffff880`04a1bfa8 : DB3G+0x20f3 fffff880`06cc39c8 00000000`00000002 : fffffa80`018c8b00 00000000`00000001 fffff880`04a1bfa8 00000000`00000000 : 0xfffff980`10f2cee0 fffff880`06cc39d0 fffffa80`018c8b00 : 00000000`00000001 fffff880`04a1bfa8 00000000`00000000 fffffa80`018c8b00 : 0x2 fffff880`06cc39d8 00000000`00000001 : fffff880`04a1bfa8 00000000`00000000 fffffa80`018c8b00 00000000`00000002 : 0xfffffa80`018c8b00 fffff880`06cc39e0 fffff880`04a1bfa8 : 00000000`00000000 fffffa80`018c8b00 00000000`00000002 00000000`02921f40 : 0x1 fffff880`06cc39e8 00000000`00000000 : fffffa80`018c8b00 00000000`00000002 00000000`02921f40 fffff800`02d1fd86 : DB3G+0x2fa8 STACK_COMMAND: kb FOLLOWUP_IP: DB3G+20f3 fffff880`04a1b0f3 89842480000000 mov dword ptr [rsp+80h],eax SYMBOL_STACK_INDEX: 6 SYMBOL_NAME: DB3G+20f3 FOLLOWUP_NAME: MachineOwner MODULE_NAME: DB3G IMAGE_NAME: DB3G.sys DEBUG_FLR_IMAGE_TIMESTAMP: 436ef527 FAILURE_BUCKET_ID: X64_0xc4_f6_VRF_DB3G+20f3 BUCKET_ID: X64_0xc4_f6_VRF_DB3G+20f3 Followup: MachineOwner ---------
Ok, I see why. this driver is way obsolete: DB3G.sys Mon Nov 07 01:33:11 2005
DB3G.sys -Diamondback USB Optical Mouse Driver - Diamondback USB Optical Mouse - Razer (Asia-Pacific) Pte Ltd. Razer Diamondback Driver v6.02
See if you can update the driver from the Razer website. You want a driver dated July 13, 2009 or later. If you can't get an updated driver, this mouse is not compatible with Win 7. You need to upgrade your mouse to one certified to be compatible.
Good job on updating your other drivers. I hope getting this driver resolved will solve the problem.
So my mouse is a problem. Ok I'll update the driver then see what happens. I was aware that my mouse driver was out of date. I have been using drivermax to find which of my drivers were out of date and downloading via it. Problem is it only allows 2 per day so I hadn't got round to it yet. I'd only done the major ones like graphics and other hardware. I had no idea a mouse/keyboard could cause any real issues so had kindof put them to the back of the queue. Some of the websites such as realtek's were a real pain in the arse to dl from and find the right updates.
Once again thaks for your help.
Once again thaks for your help.
You are very welcome. So you won't feel too alone, we have had several instances of the Razer mouse causing problems.
Just a note, we do not recommend using 3rd party driver update programs. It is far better to go to the manufacturers' websites yourself and search for the correct driver by model of your hardware. This way you are getting the latest driver and the chances of it it being corrupted are much less.
Just a note, we do not recommend using 3rd party driver update programs. It is far better to go to the manufacturers' websites yourself and search for the correct driver by model of your hardware. This way you are getting the latest driver and the chances of it it being corrupted are much less.
Random Blue screen today. Not one I've come across before.
Mouse driver updated. It was a driver that said gives the mouse compatability with windows 7.
Mouse driver updated. It was a driver that said gives the mouse compatability with windows 7.
The dump pointed to ntfs.sys, which is hard drive controller driver. I would suggest you to perform Disk Check and HD Diagnostic (download the HDD test from manufacture's site)
Code:
Microsoft (R) Windows Debugger Version 6.12.0002.633 X86 Copyright (c) Microsoft Corporation. All rights reserved. Loading Dump File [C:\Users\TUANTR~1\AppData\Local\Temp\Rar$DI00.478\080110-20202-01.dmp] Mini Kernel Dump File: Only registers and stack trace are available Symbol search path is: SRV*e:\symbols*http://msdl.microsoft.com/download/symbols Executable search path is: Windows 7 Kernel Version 7600 MP (2 procs) Free x64 Product: WinNt, suite: TerminalServer SingleUserTS Personal Built by: 7600.16539.amd64fre.win7_gdr.100226-1909 Machine Name: Kernel base = 0xfffff800`02859000 PsLoadedModuleList = 0xfffff800`02a96e50 Debug session time: Sun Aug 1 17:55:39.180 2010 (UTC + 7:00) System Uptime: 0 days 0:44:28.710 Loading Kernel Symbols ............................................................... ................................................................ ........ Loading User Symbols Loading unloaded module list ....... ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* Use !analyze -v to get detailed debugging information. BugCheck 24, {1904fb, fffff880024f3f58, fffff880024f37c0, fffff800028eea5f} Probably caused by : Ntfs.sys ( Ntfs! ?? ::FNODOBFM::`string'+2cc9 ) Followup: MachineOwner --------- Ok Thanks, I've schueduled a disk check and am downloading the diagnostics test from Seagate. I'll report back with my findings.
Glad you got you mouse updated. That eliminates that as a problem. Waiting for your hard drive test results.
Ok I ran a disk check. Unfortunately didn;t see the results as I was afk. Where can I find the results? I downloaded the seagate hard drive check. It passed all basic tests. It blue screened as I tried to start advanced tests.
Dump result from that one is below. I will try the advance tests again.
Dump result from that one is below. I will try the advance tests again.
Try to run the advanced test Seagate test again.
This dump is error code A pointing to memory corruption.
Lets see what the advanced hard drive test tells us.
I still see this driver in your dump.
DB3G.sys Mon Nov 07 01:33:11 2005 If you downloaded an updated driver, uninstall the old driver and install the updated one. Then reboot.
This dump is error code A pointing to memory corruption.
Code:
Microsoft (R) Windows Debugger Version 6.11.0001.404 X86 Copyright (c) Microsoft Corporation. All rights reserved. Loading Dump File [C:\Users\Owner\AppData\Local\Temp\Temp2_dump.zip\080110-29109-01.dmp] Mini Kernel Dump File: Only registers and stack trace are available Symbol search path is: SRV*c:\symbols*http://msdl.microsoft.com/download/symbols Executable search path is: Windows 7 Kernel Version 7600 MP (2 procs) Free x64 Product: WinNt, suite: TerminalServer SingleUserTS Personal Built by: 7600.16539.amd64fre.win7_gdr.100226-1909 Machine Name: Kernel base = 0xfffff800`0280f000 PsLoadedModuleList = 0xfffff800`02a4ce50 Debug session time: Sun Aug 1 12:04:06.993 2010 (GMT-4) System Uptime: 0 days 5:07:30.523 Loading Kernel Symbols ............................................................... ................................................................ ........ Loading User Symbols Loading unloaded module list ........ ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* Use !analyze -v to get detailed debugging information. BugCheck A, {42228030694d, 2, 0, fffff800028b1410} Probably caused by : memory_corruption ( nt!MiResolveTransitionFault+120 ) Followup: MachineOwner --------- 1: kd> !analyze -v ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* IRQL_NOT_LESS_OR_EQUAL (a) An attempt was made to access a pageable (or completely invalid) address at an interrupt request level (IRQL) that is too high. This is usually caused by drivers using improper addresses. If a kernel debugger is available get the stack backtrace. Arguments: Arg1: 000042228030694d, memory referenced Arg2: 0000000000000002, IRQL Arg3: 0000000000000000, bitfield : bit 0 : value 0 = read operation, 1 = write operation bit 3 : value 0 = not an execute operation, 1 = execute operation (only on chips which support this level of status) Arg4: fffff800028b1410, address which referenced memory Debugging Details: ------------------ READ_ADDRESS: GetPointerFromAddress: unable to read from fffff80002ab70e0 000042228030694d CURRENT_IRQL: 2 FAULTING_IP: nt!MiResolveTransitionFault+120 fffff800`028b1410 488b08 mov rcx,qword ptr [rax] CUSTOMER_CRASH_COUNT: 1 DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT BUGCHECK_STR: 0xA PROCESS_NAME: SearchIndexer. TRAP_FRAME: fffff880037ae6f0 -- (.trap 0xfffff880037ae6f0) NOTE: The trap frame does not contain all registers. Some register values may be zeroed or incorrect. rax=000042228030694d rbx=0000000000000000 rcx=0000000000000044 rdx=0000058000000000 rsi=0000000000000000 rdi=0000000000000000 rip=fffff800028b1410 rsp=fffff880037ae880 rbp=fffff8a002cbdcd0 r8=0000000000000000 r9=800000003fdaa882 r10=0000000000000000 r11=0000000000000000 r12=0000000000000000 r13=0000000000000000 r14=0000000000000000 r15=0000000000000000 iopl=0 nv up ei pl nz na po nc nt!MiResolveTransitionFault+0x120: fffff800`028b1410 488b08 mov rcx,qword ptr [rax] ds:00004222`8030694d=???????????????? Resetting default scope LAST_CONTROL_TRANSFER: from fffff8000287eb69 to fffff8000287f600 STACK_TEXT: fffff880`037ae5a8 fffff800`0287eb69 : 00000000`0000000a 00004222`8030694d 00000000`00000002 00000000`00000000 : nt!KeBugCheckEx fffff880`037ae5b0 fffff800`0287d7e0 : 00000000`00000000 80000000`3fdaa882 fffffa80`01be7b60 ffffffff`ffffffff : nt!KiBugCheckDispatch+0x69 fffff880`037ae6f0 fffff800`028b1410 : 9ee00000`3ffa5825 80000000`3ffa5921 fffffa80`00bfeef0 0000000f`ffffffff : nt!KiPageFault+0x260 fffff880`037ae880 fffff800`028a5c99 : 00000000`00000000 80000000`3fdaa882 fffffa80`01be7c20 fffffa80`04b79ec8 : nt!MiResolveTransitionFault+0x120 fffff880`037ae910 fffff800`0289b49e : 00000000`00000000 00000000`02e2b000 fffff680`00017158 fffffa80`04b79ec8 : nt!MiResolveProtoPteFault+0x419 fffff880`037ae9b0 fffff800`02899623 : ffffffff`ffffff00 00000000`02e2b000 00000000`00000000 00000000`00000000 : nt!MiDispatchFault+0x1de fffff880`037aeac0 fffff800`0287d6ee : 00000000`00000000 00000000`e23bbead fffff880`00000001 00000000`01c76d00 : nt!MmAccessFault+0x343 fffff880`037aec20 000007fe`f6e4f06e : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiPageFault+0x16e 00000000`03bbf430 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x7fe`f6e4f06e STACK_COMMAND: kb FOLLOWUP_IP: nt!MiResolveTransitionFault+120 fffff800`028b1410 488b08 mov rcx,qword ptr [rax] SYMBOL_STACK_INDEX: 3 SYMBOL_NAME: nt!MiResolveTransitionFault+120 FOLLOWUP_NAME: MachineOwner MODULE_NAME: nt DEBUG_FLR_IMAGE_TIMESTAMP: 4b88cfeb IMAGE_NAME: memory_corruption FAILURE_BUCKET_ID: X64_0xA_nt!MiResolveTransitionFault+120 BUCKET_ID: X64_0xA_nt!MiResolveTransitionFault+120 Followup: MachineOwner ---------
I still see this driver in your dump.
DB3G.sys Mon Nov 07 01:33:11 2005 If you downloaded an updated driver, uninstall the old driver and install the updated one. Then reboot.
Ok I removed the old mouse driver. Thanks for pointing that out Advanced tests are not available according to the tester. But viewing the website tells me that the tests that it is put through are fairly tough and that if something was wrong it would almost certainly of found it. So it looks like the blue screen was totally unrelated to me clicking on advance tests and coincidental.
Where can I view the results of my disk check from earlier?
Is it worth running the driver verifier as well seeing as the mouse issue has now been resolved?
Thanks again
Advanced tests are not available according to the tester. But viewing the website tells me that the tests that it is put through are fairly tough and that if something was wrong it would almost certainly of found it. So it looks like the blue screen was totally unrelated to me clicking on advance tests and coincidental. Where can I view the results of my disk check from earlier?
Is it worth running the driver verifier as well seeing as the mouse issue has now been resolved?
Thanks again
Let's see what your system does without driver verifier.
Check disk does not yield a saved report automatically. Below are the check disk commands.
Checks a disk and displays a status report.
The preferred command is shown below.
Attachment 88726
You can always run it again. I am pretty sure since your Drive passed the Seagate tester it is OK.
Check disk does not yield a saved report automatically. Below are the check disk commands.
Checks a disk and displays a status report.
Quote:
CHKDSK [volume[[path]filename]]] [/F] [/V] [/R] [/X] [/I] [/C] [/L[:size]] [/B]
volume Specifies the drive letter (followed by a colon),
mount point, or volume name.
filename FAT/FAT32 only: Specifies the files to check for fragmentation.
/F Fixes errors on the disk.
/V On FAT/FAT32: Displays the full path and name of every file
on the disk.
On NTFS: Displays cleanup messages if any.
/R Locates bad sectors and recovers readable information
(implies /F).
/L:size NTFS only: Changes the log file size to the specified number
of kilobytes. If size is not specified, displays current
size.
/X Forces the volume to dismount first if necessary.
All opened handles to the volume would then be invalid
(implies /F).
/I NTFS only: Performs a less vigorous check of index entries.
/C NTFS only: Skips checking of cycles within the folder
structure.
/B NTFS only: Re-evaluates bad clusters on the volume
(implies /R)
The /I or /C switch reduces the amount of time required to run Chkdsk by
skipping certain checks of the volume.
volume Specifies the drive letter (followed by a colon),
mount point, or volume name.
filename FAT/FAT32 only: Specifies the files to check for fragmentation.
/F Fixes errors on the disk.
/V On FAT/FAT32: Displays the full path and name of every file
on the disk.
On NTFS: Displays cleanup messages if any.
/R Locates bad sectors and recovers readable information
(implies /F).
/L:size NTFS only: Changes the log file size to the specified number
of kilobytes. If size is not specified, displays current
size.
/X Forces the volume to dismount first if necessary.
All opened handles to the volume would then be invalid
(implies /F).
/I NTFS only: Performs a less vigorous check of index entries.
/C NTFS only: Skips checking of cycles within the folder
structure.
/B NTFS only: Re-evaluates bad clusters on the volume
(implies /R)
The /I or /C switch reduces the amount of time required to run Chkdsk by
skipping certain checks of the volume.
Attachment 88726
You can always run it again. I am pretty sure since your Drive passed the Seagate tester it is OK.
Time for some Empire Total War 
I'll see if I get anymore.
Thanks
I'll see if I get anymore.Thanks
Let us know - and good job with the mouse driver.
Random one this afternoon while browsing the net.
Your .dmp file is still showing Memory Corruption as the cause of your crashes... Rerun memtest and post the results..
Code:
******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* Use !analyze -v to get detailed debugging information. BugCheck A, {42228030694d, 2, 0, fffff80002927a2f} Probably caused by : memory_corruption ( nt!MiIdentifyPfn+23f ) Followup: MachineOwner --------- 1: kd> !analyze -v ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* IRQL_NOT_LESS_OR_EQUAL (a) An attempt was made to access a pageable (or completely invalid) address at an interrupt request level (IRQL) that is too high. This is usually caused by drivers using improper addresses. If a kernel debugger is available get the stack backtrace. Arguments: Arg1: 000042228030694d, memory referenced Arg2: 0000000000000002, IRQL Arg3: 0000000000000000, bitfield : bit 0 : value 0 = read operation, 1 = write operation bit 3 : value 0 = not an execute operation, 1 = execute operation (only on chips which support this level of status) Arg4: fffff80002927a2f, address which referenced memory Debugging Details: ------------------ READ_ADDRESS: GetPointerFromAddress: unable to read from fffff80002aad0e0 000042228030694d CURRENT_IRQL: 2 FAULTING_IP: nt!MiIdentifyPfn+23f fffff800`02927a2f 4c8b7500 mov r14,qword ptr [rbp] CUSTOMER_CRASH_COUNT: 1 DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT BUGCHECK_STR: 0xA PROCESS_NAME: svchost.exe TRAP_FRAME: fffff8800260a4f0 -- (.trap 0xfffff8800260a4f0) NOTE: The trap frame does not contain all registers. Some register values may be zeroed or incorrect. rax=0000000000000011 rbx=0000000000000000 rcx=0a00000000000020 rdx=000000000003fdaa rsi=0000000000000000 rdi=0000000000000000 rip=fffff80002927a2f rsp=fffff8800260a680 rbp=000042228030694d r8=0000000000035fab r9=0000000000000001 r10=0000000000000042 r11=0000058000000000 r12=0000000000000000 r13=0000000000000000 r14=0000000000000000 r15=0000000000000000 iopl=0 nv up ei pl nz na po nc nt!MiIdentifyPfn+0x23f: fffff800`02927a2f 4c8b7500 mov r14,qword ptr [rbp] ss:0018:00004222`8030694d=???????????????? Resetting default scope LAST_CONTROL_TRANSFER: from fffff80002874b69 to fffff80002875600 STACK_TEXT: fffff880`0260a3a8 fffff800`02874b69 : 00000000`0000000a 00004222`8030694d 00000000`00000002 00000000`00000000 : nt!KeBugCheckEx fffff880`0260a3b0 fffff800`028737e0 : 00000000`42506650 22112205`1b06050c 00000000`00000000 00000000`00000000 : nt!KiBugCheckDispatch+0x69 fffff880`0260a4f0 fffff800`02927a2f : 00000000`00000000 02000000`00045c76 00000000`000018c0 fffff800`02b3d1af : nt!KiPageFault+0x260 fffff880`0260a680 fffff800`0292870b : 00000000`00000000 00000000`00000004 fffffa80`02c1a778 fffffa80`02c1a000 : nt!MiIdentifyPfn+0x23f fffff880`0260a720 fffff800`02c87c55 : fffffa80`02c1a000 fffff880`0260aca0 fffff880`0260a7f8 00000000`00000000 : nt!MmQueryPfnList+0xbb fffff880`0260a760 fffff800`02bccf18 : 00000000`00000006 00000000`00000000 fffffa80`02c1a000 fffff800`02805001 : nt!PfpPfnPrioRequest+0x115 fffff880`0260a7b0 fffff800`02b73fb3 : 00000000`00000000 fffff800`02805000 fffffa80`026a5000 00000000`00000001 : nt! ?? ::NNGAKEGL::`string'+0x4759d fffff880`0260a840 fffff800`02b75149 : 00000000`00f0bd88 00000000`00001101 00000000`00f0bde0 00000000`00f0bda8 : nt!ExpQuerySystemInformation+0x11c2 fffff880`0260abe0 fffff800`02874853 : fffffa80`04577b60 00000000`01a05030 00000000`00000001 00000000`03c215c0 : nt!NtQuerySystemInformation+0x4d fffff880`0260ac20 00000000`779500ba : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13 00000000`00f0bca8 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x779500ba STACK_COMMAND: kb FOLLOWUP_IP: nt!MiIdentifyPfn+23f fffff800`02927a2f 4c8b7500 mov r14,qword ptr [rbp] SYMBOL_STACK_INDEX: 3 SYMBOL_NAME: nt!MiIdentifyPfn+23f FOLLOWUP_NAME: MachineOwner MODULE_NAME: nt DEBUG_FLR_IMAGE_TIMESTAMP: 4b88cfeb IMAGE_NAME: memory_corruption FAILURE_BUCKET_ID: X64_0xA_nt!MiIdentifyPfn+23f BUCKET_ID: X64_0xA_nt!MiIdentifyPfn+23f Followup: MachineOwner --------- Code:
DB3G DB3G.sys Mon Nov 07 13:33:11 2005 (436EF527)
http://www.razersupport.com/index.ph...nloaditemid=74
Done. Deleted for sure now. I was sure I had deleted it. I had already done a memtest. Is there no way to pull the results from somewhere? if not I will run it again tonight.
Tews is asking you to rerun it just to double check. How is your system doing since you got rid of that obsolete driver?
Yeah was playing a game for a few hours this afternoon with no problems. Its been on afk until now as well. I'll rerun the memtest tonight.
That is good - it certainly is an improvement.
Within 2 minutes of me posting, while still on the forums it blue screened again. I then started it up again to find that removing the mouse driver file had meant my mouse would no longer move. The new driver must not have kicked in properly. After painfully navigating around with the keyboard, the pc crashed again while trying to post here. Since then I have reinstalled the mouse driver so I can move again. Gonna run the memtest immediatly. Here are the latest dump files.
Yes, please do the memtest to confirm nothing is wrong with the Ram. But personally, I think all of these thing go wrong because of the mouse. See if you can have another mouse to test on your system, with the driver date from 2005, it's hard to say that it is compatible with window 7, even if you still can run your mouse, it will not stable at all, especially when you turned on Driver Verifier, all the crash dump point to that mouse.
Code:
Microsoft (R) Windows Debugger Version 6.12.0002.633 X86 Copyright (c) Microsoft Corporation. All rights reserved. Loading Dump File [C:\Users\TUANTR~1\AppData\Local\Temp\Rar$DI00.666\080210-22417-01.dmp] Mini Kernel Dump File: Only registers and stack trace are available Symbol search path is: SRV*e:\symbols*http://msdl.microsoft.com/download/symbols Executable search path is: Windows 7 Kernel Version 7600 MP (2 procs) Free x64 Product: WinNt, suite: TerminalServer SingleUserTS Personal Built by: 7600.16539.amd64fre.win7_gdr.100226-1909 Machine Name: Kernel base = 0xfffff800`0280b000 PsLoadedModuleList = 0xfffff800`02a48e50 Debug session time: Tue Aug 3 04:41:29.608 2010 (UTC + 7:00) System Uptime: 0 days 1:44:50.137 Loading Kernel Symbols ............................................................... ................................................................ ...... Loading User Symbols Loading unloaded module list ........ ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* Use !analyze -v to get detailed debugging information. BugCheck A, {42228030694d, 2, 0, fffff8000292da2f} Probably caused by : memory_corruption ( nt!MiIdentifyPfn+23f ) Followup: MachineOwner --------- Seems the memtest froze during the night. It had only done 2 passes with no errors. Does it mean there is something wrong? Or coincidence?
�� Quote: Originally Posted by Watson Seems the memtest froze during the night. It had only done 2 passes with no errors. Does it mean there is something wrong? Or coincidence?
New one while trying to comb the razer forums to sort my mouse.
Could any of this be due to overheating? It's a problem I have had before. Anything I can download to check my temperature?
Could any of this be due to overheating? It's a problem I have had before. Anything I can download to check my temperature?
You can use speedfan: SpeedFan - Access temperature sensor in your computer
Are you overclocking at all? If so, restore to defaults
Are you overclocking at all? If so, restore to defaults
Seems normal temperature wise. I am not overclocking.
I am going to try memtest again. The first time I ran it. When I came down before it had frozen as well now I think back. At the time, not knowing how it worked I assumed it had finished when it said no errors at the bottom. But thinking back, I remember it was in the middle of a test and unresponsive. So looks like there is a problem. I'll post back with the results.
I am going to try memtest again. The first time I ran it. When I came down before it had frozen as well now I think back. At the time, not knowing how it worked I assumed it had finished when it said no errors at the bottom. But thinking back, I remember it was in the middle of a test and unresponsive. So looks like there is a problem. I'll post back with the results.
The latest dump is an error code A and points to corrupted memory. I am sure you mouse driver is causing a problem and you may well have other memory issues. Something is obviously corrupting your memory. Take Trans advice and try another mouse. After you have that mouse installed, rename the old mouse driver from.sys to .bak.
When you have done that, follow ZigAag's advice and run Memtest 86. If the mouse driver is causing corruption, you may not be able to successfully run Memtest.
If you cannot find and updated driver from Razer, you will more than likely have to upgrade your mouse. I worked another BSOD involving the Razer mouse, and the OP ended up upgrading to a Microsoft mouse and his problem went away.
When you have done that, follow ZigAag's advice and run Memtest 86. If the mouse driver is causing corruption, you may not be able to successfully run Memtest.
If you cannot find and updated driver from Razer, you will more than likely have to upgrade your mouse. I worked another BSOD involving the Razer mouse, and the OP ended up upgrading to a Microsoft mouse and his problem went away.
I removed the DBG3.sys file and reinstalled the supposably wiundows 7 compatible version driver, but weirdly when in the install it only mentions XP and Vista but not windows 7. It also reinstalled the DB3G.sys file from 2005 so I'm guessing that is all they have. My dad is going to try pick me up one from work tommorow if he can.
Is it worth removing the mouse driver. (got the driver installler as backup). Then run the memtest to avoid possible corruption? Then we can really see if it is the memory causing the freezes during the tests.
Is it worth removing the mouse driver. (got the driver installler as backup). Then run the memtest to avoid possible corruption? Then we can really see if it is the memory causing the freezes during the tests.
Lets wait until you have the new mouse installed and that obsolete driver is gone. After you install the new mouse, you may have to uninstall the old one. After you have uninstalled the old one, check to make sure that driver is gone.
Well earlier I decided to remove the mouse driver altogether. Totally took it off my machine. I left the installer on my desktop so I could easily restore it and I disconnected the razer mouse. Have been navigating using my keyboard since. Ran a memtest like this and yet again it froze. I'm pretty sure it was at the same point as well. Like 42% into test 5 after completing 2 passes with no errors. So where do I go from here?
Anyone?
Ok. What I've done is I have removed all drivers for the razer mouse and disconnected it. I am currently just browsing around best I can with the keyboard. I have set up the verifier again as before. This time there was no mouse based crash on startup as before so maybe one problem solved there. I am gonna leave the verifier on and see what happens. Previously nothing specific (pc use wise) has actually caused the blue screens so even leaving it afk with the verifier on may give some results. I hope it is just the mouse and not something more serious.
What should I make of the memtest freezes? Are they something to be concerned about?
What should I make of the memtest freezes? Are they something to be concerned about?
There is the possibility that the freeze points to bad RAM or other hardware problems. You are running Memtest from a bootable CD? Doing so goes write to the system bypassing Win 7 which is not loaded. Thus Windows is not involved.
Not good then, yes I am using a bootable CD. Maybe the verifier will find out which bit of hardware isn't right.
�� Quote: Originally Posted by Watson Not good then, yes I am using a bootable CD. Maybe the verifier will find out which bit of hardware isn't right.
Computer froze twice yesterday. After I had left it afk and it had gone into sleep. I returned and it brought what was last on the screen but refused to respond to anything which ended up in me having tor eset the machine. Does this point to anything in particular?
Did you get a dump file with the freeze? Several things can cause freezes - network adapter, video adapter, sound adapter, incompatible hardware or software, etc.
Nope no dump file. My dad brought me a old crappy usb mouse from work which I can navigate with fine for now so thats one problem sorted . Still got the verifier on and as yet no blue screens since. So I'm hoping they wont come , or at least if they do I might know the cause.
. Still got the verifier on and as yet no blue screens since. So I'm hoping they wont come , or at least if they do I might know the cause. Very good. We are making progress.
Played almost all day today on Mount and Blade and no problems. Nor yesterday just browsing either. *touches wood* Think that seems to have fixed it. All I can say to you guys that helped is thanks so much. Some rep coming your way.
Very good news, indeed! Congratualtions. Have you turned Driver Verifier off? You can do so now if you haven't. Post back tomorrow and let us know you are running.
had forgotten about the verifier. It has now been switched off. Still working fine Thanks again.
That is great. You ran a long time with Driver Verifier on; so your system must be in good shape. I am pleased that we could help you and happy you are running smoothly. Don't be a stranger to the forum.
Yessssss, it is fixed, it is fixed, I'm happy too...glad that we could help...please visit forum more ok
I could cry. Been ages with nothing but got one today at the most irritating of times. While I was checking to see if I got into uni :S. I did notice it was very shortly after the pc came out of sleep.
Darn, that is not good news and I am sorry to hear it. 
The dump does not point to anything in specific except memory corruption. All of your drivers are up to date. Let's see if this was just a fluke or if you get another crash in the next few days. If you do we will start the process over with Memtest and then Driver Verifier.
The only additional suggestion I have at the moment is make sure your RAM is seated properly.
I have my fingers crossed!
Quote:
STOP 0x0000000A: IRQL_NOT_LESS_OR_EQUAL
Usual causes: Kernel mode driver, System Service, BIOS, Windows, Virus scanner, Backup tool, compatibility
Usual causes: Kernel mode driver, System Service, BIOS, Windows, Virus scanner, Backup tool, compatibility
Code:
******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* Use !analyze -v to get detailed debugging information. BugCheck A, {42228030694d, 2, 0, fffff80002907540} Probably caused by : memory_corruption ( nt!MiResolveTransitionFault+120 ) Followup: MachineOwner --------- 0: kd> !analyze -v ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* IRQL_NOT_LESS_OR_EQUAL (a) An attempt was made to access a pageable (or completely invalid) address at an interrupt request level (IRQL) that is too high. This is usually caused by drivers using improper addresses. If a kernel debugger is available get the stack backtrace. Arguments: Arg1: 000042228030694d, memory referenced Arg2: 0000000000000002, IRQL Arg3: 0000000000000000, bitfield : bit 0 : value 0 = read operation, 1 = write operation bit 3 : value 0 = not an execute operation, 1 = execute operation (only on chips which support this level of status) Arg4: fffff80002907540, address which referenced memory Debugging Details: ------------------ READ_ADDRESS: GetPointerFromAddress: unable to read from fffff80002b0d0e0 000042228030694d CURRENT_IRQL: 2 FAULTING_IP: nt!MiResolveTransitionFault+120 fffff800`02907540 488b08 mov rcx,qword ptr [rax] CUSTOMER_CRASH_COUNT: 1 DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT BUGCHECK_STR: 0xA PROCESS_NAME: iexplore.exe TRAP_FRAME: fffff88006b2a790 -- (.trap 0xfffff88006b2a790) NOTE: The trap frame does not contain all registers. Some register values may be zeroed or incorrect. rax=000042228030694d rbx=0000000000000000 rcx=0000000000000044 rdx=fffff88006b2a9d0 rsi=0000000000000000 rdi=0000000000000000 rip=fffff80002907540 rsp=fffff88006b2a920 rbp=fffff68000078fe8 r8=000000000003fd00 r9=af7000003fdaa886 r10=0000000000000000 r11=0000000000000001 r12=0000000000000000 r13=0000000000000000 r14=0000000000000000 r15=0000000000000000 iopl=0 nv up ei pl nz na po nc nt!MiResolveTransitionFault+0x120: fffff800`02907540 488b08 mov rcx,qword ptr [rax] ds:1d68:00004222`8030694d=???????????????? Resetting default scope LAST_CONTROL_TRANSFER: from fffff800028d4ca9 to fffff800028d5740 STACK_TEXT: fffff880`06b2a648 fffff800`028d4ca9 : 00000000`0000000a 00004222`8030694d 00000000`00000002 00000000`00000000 : nt!KeBugCheckEx fffff880`06b2a650 fffff800`028d3920 : 00000000`00000000 00000000`0f1fd030 00000000`00000000 00000000`00000001 : nt!KiBugCheckDispatch+0x69 fffff880`06b2a790 fffff800`02907540 : 00000000`0f1fd030 fffff680`00078fe8 0000007f`fffffff8 0002a58c`00000080 : nt!KiPageFault+0x260 fffff880`06b2a920 fffff800`028f1d26 : 00000000`00000001 00000000`0f1fd030 00000000`00000000 fffffa80`04d41d68 : nt!MiResolveTransitionFault+0x120 fffff880`06b2a9b0 fffff800`028ef743 : ffffffff`ffffffff 00000000`00000001 0002903c`00000080 fffff880`06b2ab40 : nt!MiDispatchFault+0x946 fffff880`06b2aac0 fffff800`028d382e : 00000000`00000001 00000000`602015b5 00000000`00000001 fffffa80`049538b0 : nt!MmAccessFault+0x343 fffff880`06b2ac20 00000000`773f780d : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiPageFault+0x16e 00000000`02cb9ad8 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x773f780d STACK_COMMAND: kb FOLLOWUP_IP: nt!MiResolveTransitionFault+120 fffff800`02907540 488b08 mov rcx,qword ptr [rax] SYMBOL_STACK_INDEX: 3 SYMBOL_NAME: nt!MiResolveTransitionFault+120 FOLLOWUP_NAME: MachineOwner MODULE_NAME: nt DEBUG_FLR_IMAGE_TIMESTAMP: 4c1c44a9 IMAGE_NAME: memory_corruption FAILURE_BUCKET_ID: X64_0xA_nt!MiResolveTransitionFault+120 BUCKET_ID: X64_0xA_nt!MiResolveTransitionFault+120 Followup: MachineOwner --------- 0: kd> lmtsmn start end module name fffff880`00fa2000 fffff880`00ff9000 ACPI ACPI.sys Mon Jul 13 19:19:34 2009 (4A5BC106) fffff880`03a33000 fffff880`03abd000 afd afd.sys Mon Jul 13 19:21:40 2009 (4A5BC184) fffff880`02c10000 fffff880`02c26000 AgileVpn AgileVpn.sys Mon Jul 13 20:10:24 2009 (4A5BCCF0) fffff880`00de9000 fffff880`00df4000 amdxata amdxata.sys Tue May 19 13:56:59 2009 (4A12F2EB) fffff880`03400000 fffff880`0340b000 asyncmac asyncmac.sys Mon Jul 13 20:10:13 2009 (4A5BCCE5) fffff880`00ee0000 fffff880`00ee9000 atapi atapi.sys Mon Jul 13 19:19:47 2009 (4A5BC113) fffff880`00dbf000 fffff880`00de9000 ataport ataport.SYS Mon Jul 13 19:19:52 2009 (4A5BC118) fffff880`03e88000 fffff880`045b7000 atikmdag atikmdag.sys Tue Jul 06 21:37:28 2010 (4C33DA58) fffff880`03cdd000 fffff880`03d23000 atikmpag atikmpag.sys Tue Jul 06 21:15:42 2010 (4C33D53E) fffff880`018ec000 fffff880`018f3000 Beep Beep.SYS Mon Jul 13 20:00:13 2009 (4A5BCA8D) fffff880`01998000 fffff880`019a9000 blbdrive blbdrive.sys Mon Jul 13 19:35:59 2009 (4A5BC4DF) fffff880`02b5d000 fffff880`02b7b000 bowser bowser.sys Mon Jul 13 19:23:50 2009 (4A5BC206) fffff960`00690000 fffff960`006b7000 cdd cdd.dll unavailable (00000000) fffff880`018b9000 fffff880`018e3000 cdrom cdrom.sys Mon Jul 13 19:19:54 2009 (4A5BC11A) fffff880`00cd5000 fffff880`00d95000 CI CI.dll Mon Jul 13 21:32:13 2009 (4A5BE01D) fffff880`01853000 fffff880`01883000 CLASSPNP CLASSPNP.SYS Mon Jul 13 19:19:58 2009 (4A5BC11E) fffff880`00c77000 fffff880`00cd5000 CLFS CLFS.SYS Mon Jul 13 19:19:57 2009 (4A5BC11D) fffff880`01154000 fffff880`011c7000 cng cng.sys Mon Jul 13 19:49:40 2009 (4A5BC814) fffff880`02c00000 fffff880`02c10000 CompositeBus CompositeBus.sys Mon Jul 13 20:00:33 2009 (4A5BCAA1) fffff880`04d4c000 fffff880`04d5a000 crashdmp crashdmp.sys Mon Jul 13 20:01:01 2009 (4A5BCABD) fffff880`03a0f000 fffff880`03a2d000 dfsc dfsc.sys Mon Jul 13 19:23:44 2009 (4A5BC200) fffff880`03a00000 fffff880`03a0f000 discache discache.sys Mon Jul 13 19:37:18 2009 (4A5BC52E) fffff880`0183d000 fffff880`01853000 disk disk.sys Mon Jul 13 19:19:57 2009 (4A5BC11D) fffff880`04d24000 fffff880`04d46000 drmk drmk.sys Mon Jul 13 21:01:25 2009 (4A5BD8E5) fffff880`04d66000 fffff880`04d6f000 dump_atapi dump_atapi.sys Mon Jul 13 19:19:47 2009 (4A5BC113) fffff880`04d5a000 fffff880`04d66000 dump_dumpata dump_dumpata.sys Mon Jul 13 19:19:47 2009 (4A5BC113) fffff880`04d6f000 fffff880`04d82000 dump_dumpfve dump_dumpfve.sys Mon Jul 13 19:21:51 2009 (4A5BC18F) fffff880`04d82000 fffff880`04d8e000 Dxapi Dxapi.sys Mon Jul 13 19:38:28 2009 (4A5BC574) fffff880`02c51000 fffff880`02d45000 dxgkrnl dxgkrnl.sys Thu Oct 01 21:00:14 2009 (4AC5509E) fffff880`02d45000 fffff880`02d8b000 dxgmms1 dxgmms1.sys Mon Jul 13 19:38:32 2009 (4A5BC578) fffff880`010e2000 fffff880`010f6000 fileinfo fileinfo.sys Mon Jul 13 19:34:25 2009 (4A5BC481) fffff880`01096000 fffff880`010e2000 fltmgr fltmgr.sys Mon Jul 13 19:19:59 2009 (4A5BC11F) fffff880`0122b000 fffff880`01235000 Fs_Rec Fs_Rec.sys Mon Jul 13 19:19:45 2009 (4A5BC111) fffff880`01803000 fffff880`0183d000 fvevol fvevol.sys Fri Sep 25 22:34:26 2009 (4ABD7DB2) fffff880`015a6000 fffff880`015f0000 fwpkclnt fwpkclnt.sys Mon Jul 13 19:21:08 2009 (4A5BC164) fffff800`0281c000 fffff800`02865000 hal hal.dll Mon Jul 13 21:27:36 2009 (4A5BDF08) fffff880`02d8b000 fffff880`02daf000 HDAudBus HDAudBus.sys Mon Jul 13 20:06:13 2009 (4A5BCBF5) fffff880`03c81000 fffff880`03cdd000 HdAudio HdAudio.sys Mon Jul 13 20:06:59 2009 (4A5BCC23) fffff880`04d9c000 fffff880`04db5000 HIDCLASS HIDCLASS.SYS Mon Jul 13 20:06:21 2009 (4A5BCBFD) fffff880`04db5000 fffff880`04dbd080 HIDPARSE HIDPARSE.SYS Mon Jul 13 20:06:17 2009 (4A5BCBF9) fffff880`04d8e000 fffff880`04d9c000 hidusb hidusb.sys Mon Jul 13 20:06:22 2009 (4A5BCBFE) fffff880`02a95000 fffff880`02b5d000 HTTP HTTP.sys Mon Jul 13 19:22:16 2009 (4A5BC1A8) fffff880`0149d000 fffff880`014a6000 hwpolicy hwpolicy.sys Mon Jul 13 19:19:22 2009 (4A5BC0FA) fffff880`019cf000 fffff880`019e5000 intelppm intelppm.sys Mon Jul 13 19:19:25 2009 (4A5BC0FD) fffff880`03d9a000 fffff880`03da9000 kbdclass kbdclass.sys Mon Jul 13 19:19:50 2009 (4A5BC116) fffff880`04dc0000 fffff880`04dce000 kbdhid kbdhid.sys Mon Jul 13 20:00:20 2009 (4A5BCA94) fffff800`00b9b000 fffff800`00ba5000 kdcom kdcom.dll Mon Jul 13 21:31:07 2009 (4A5BDFDB) fffff880`03db8000 fffff880`03dfb000 ks ks.sys Mon Jul 13 20:00:31 2009 (4A5BCA9F) fffff880`01200000 fffff880`0121a000 ksecdd ksecdd.sys Mon Jul 13 19:20:54 2009 (4A5BC156) fffff880`01460000 fffff880`0148b000 ksecpkg ksecpkg.sys Fri Dec 11 01:03:32 2009 (4B21E0B4) fffff880`04d46000 fffff880`04d4b200 ksthunk ksthunk.sys Mon Jul 13 20:00:19 2009 (4A5BCA93) fffff880`04c23000 fffff880`04c38000 lltdio lltdio.sys Mon Jul 13 20:08:50 2009 (4A5BCC92) fffff880`04c00000 fffff880`04c23000 luafv luafv.sys Mon Jul 13 19:26:13 2009 (4A5BC295) fffff880`00c1f000 fffff880`00c63000 mcupdate_GenuineIntel mcupdate_GenuineIntel.dll Mon Jul 13 21:29:10 2009 (4A5BDF66) fffff880`04ddb000 fffff880`04de9000 monitor monitor.sys Mon Jul 13 19:38:52 2009 (4A5BC58C) fffff880`03da9000 fffff880`03db8000 mouclass mouclass.sys Mon Jul 13 19:19:50 2009 (4A5BC116) fffff880`04dce000 fffff880`04ddb000 mouhid mouhid.sys Mon Jul 13 20:00:20 2009 (4A5BCA94) fffff880`00da5000 fffff880`00dbf000 mountmgr mountmgr.sys Mon Jul 13 19:19:54 2009 (4A5BC11A) fffff880`02b7b000 fffff880`02b93000 mpsdrv mpsdrv.sys Mon Jul 13 20:08:25 2009 (4A5BCC79) fffff880`02b93000 fffff880`02bc0000 mrxsmb mrxsmb.sys Sat Feb 27 02:52:19 2010 (4B88CF33) fffff880`02a00000 fffff880`02a4e000 mrxsmb10 mrxsmb10.sys Sat Feb 27 02:52:28 2010 (4B88CF3C) fffff880`02a4e000 fffff880`02a71000 mrxsmb20 mrxsmb20.sys Sat Feb 27 02:52:26 2010 (4B88CF3A) fffff880`01951000 fffff880`0195c000 Msfs Msfs.SYS Mon Jul 13 19:19:47 2009 (4A5BC113) fffff880`00e09000 fffff880`00e13000 msisadrv msisadrv.sys Mon Jul 13 19:19:26 2009 (4A5BC0FE) fffff880`010f6000 fffff880`01154000 msrpc msrpc.sys Mon Jul 13 19:21:32 2009 (4A5BC17C) fffff880`03be9000 fffff880`03bf4000 mssmbios mssmbios.sys Mon Jul 13 19:31:10 2009 (4A5BC3BE) fffff880`0148b000 fffff880`0149d000 mup mup.sys Mon Jul 13 19:23:45 2009 (4A5BC201) fffff880`014b4000 fffff880`015a6000 ndis ndis.sys Mon Jul 13 19:21:40 2009 (4A5BC184) fffff880`03e56000 fffff880`03e62000 ndistapi ndistapi.sys Mon Jul 13 20:10:00 2009 (4A5BCCD8) fffff880`045b7000 fffff880`045e6000 ndiswan ndiswan.sys Mon Jul 13 20:10:11 2009 (4A5BCCE3) fffff880`03c6c000 fffff880`03c81000 NDProxy NDProxy.SYS Mon Jul 13 20:10:05 2009 (4A5BCCDD) fffff880`03b31000 fffff880`03b40000 netbios netbios.sys Mon Jul 13 20:09:26 2009 (4A5BCCB6) fffff880`03abd000 fffff880`03b02000 netbt netbt.sys Mon Jul 13 19:21:28 2009 (4A5BC178) fffff880`01400000 fffff880`01460000 NETIO NETIO.SYS Mon Jul 13 19:21:46 2009 (4A5BC18A) fffff880`0195c000 fffff880`0196d000 Npfs Npfs.SYS Mon Jul 13 19:19:48 2009 (4A5BC114) fffff880`03bdd000 fffff880`03be9000 nsiproxy nsiproxy.sys Mon Jul 13 19:21:02 2009 (4A5BC15E) fffff800`02865000 fffff800`02e41000 nt ntkrnlmp.exe Sat Jun 19 00:16:41 2010 (4C1C44A9) fffff880`01257000 fffff880`013fa000 Ntfs Ntfs.sys Mon Jul 13 19:20:47 2009 (4A5BC14F) fffff880`018e3000 fffff880`018ec000 Null Null.SYS Mon Jul 13 19:19:37 2009 (4A5BC109) fffff880`03b0b000 fffff880`03b31000 pacer pacer.sys Mon Jul 13 20:09:41 2009 (4A5BCCC5) fffff880`02dd9000 fffff880`02df6000 parport parport.sys Mon Jul 13 20:00:40 2009 (4A5BCAA8) fffff880`00e53000 fffff880`00e68000 partmgr partmgr.sys Mon Jul 13 19:19:58 2009 (4A5BC11E) fffff880`00e13000 fffff880`00e46000 pci pci.sys Mon Jul 13 19:19:51 2009 (4A5BC117) fffff880`00ed9000 fffff880`00ee0000 pciide pciide.sys Mon Jul 13 19:19:49 2009 (4A5BC115) fffff880`00d95000 fffff880`00da5000 PCIIDEX PCIIDEX.SYS Mon Jul 13 19:19:48 2009 (4A5BC114) fffff880`0121a000 fffff880`0122b000 pcw pcw.sys Mon Jul 13 19:19:27 2009 (4A5BC0FF) fffff880`03430000 fffff880`034d6000 peauth peauth.sys Mon Jul 13 21:01:19 2009 (4A5BD8DF) fffff880`04ce7000 fffff880`04d24000 portcls portcls.sys Mon Jul 13 20:06:27 2009 (4A5BCC03) fffff880`00c63000 fffff880`00c77000 PSHED PSHED.dll Mon Jul 13 21:32:23 2009 (4A5BE027) fffff880`02c26000 fffff880`02c4a000 rasl2tp rasl2tp.sys Mon Jul 13 20:10:11 2009 (4A5BCCE3) fffff880`03e62000 fffff880`03e7d000 raspppoe raspppoe.sys Mon Jul 13 20:10:17 2009 (4A5BCCE9) fffff880`03d79000 fffff880`03d9a000 raspptp raspptp.sys Mon Jul 13 20:10:18 2009 (4A5BCCEA) fffff880`045e6000 fffff880`04600000 rassstp rassstp.sys Mon Jul 13 20:10:25 2009 (4A5BCCF1) fffff880`03b8c000 fffff880`03bdd000 rdbss rdbss.sys Mon Jul 13 19:24:09 2009 (4A5BC219) fffff880`01936000 fffff880`0193f000 RDPCDD RDPCDD.sys Mon Jul 13 20:16:34 2009 (4A5BCE62) fffff880`0193f000 fffff880`01948000 rdpencdd rdpencdd.sys Mon Jul 13 20:16:34 2009 (4A5BCE62) fffff880`01948000 fffff880`01951000 rdprefmp rdprefmp.sys Mon Jul 13 20:16:35 2009 (4A5BCE63) fffff880`0104c000 fffff880`01086000 rdyboost rdyboost.sys Mon Jul 13 19:34:34 2009 (4A5BC48A) fffff880`04c38000 fffff880`04c50000 rspndr rspndr.sys Mon Jul 13 20:08:50 2009 (4A5BCC92) fffff880`03d23000 fffff880`03d79000 Rt64win7 Rt64win7.sys Wed Jun 23 05:10:45 2010 (4C21CF95) fffff880`034d6000 fffff880`034e1000 secdrv secdrv.SYS Wed Sep 13 09:18:38 2006 (4508052E) fffff880`02dcd000 fffff880`02dd9000 serenum serenum.sys Mon Jul 13 20:00:33 2009 (4A5BCAA1) fffff880`03b40000 fffff880`03b5d000 serial serial.sys Mon Jul 13 20:00:40 2009 (4A5BCAA8) fffff880`015f8000 fffff880`015ff000 speedfan speedfan.sys Sun Sep 24 09:26:48 2006 (45168798) fffff880`015f0000 fffff880`015f8000 spldr spldr.sys Mon May 11 12:56:27 2009 (4A0858BB) fffff880`04c50000 fffff880`04ce6000 srv srv.sys Mon Jun 21 23:21:11 2010 (4C202C27) fffff880`03520000 fffff880`03588000 srv2 srv2.sys Mon Jun 21 23:20:47 2010 (4C202C0F) fffff880`034e1000 fffff880`0350e000 srvnet srvnet.sys Mon Jun 21 23:20:32 2010 (4C202C00) fffff880`02c4a000 fffff880`02c4b480 swenum swenum.sys Mon Jul 13 20:00:18 2009 (4A5BCA92) fffff880`01601000 fffff880`017fe000 tcpip tcpip.sys Sun Jun 13 23:39:04 2010 (4C15A458) fffff880`0350e000 fffff880`03520000 tcpipreg tcpipreg.sys Mon Jul 13 20:09:49 2009 (4A5BCCCD) fffff880`0198b000 fffff880`01998000 TDI TDI.SYS Mon Jul 13 19:21:18 2009 (4A5BC16E) fffff880`0196d000 fffff880`0198b000 tdx tdx.sys Mon Jul 13 19:21:15 2009 (4A5BC16B) fffff880`03b78000 fffff880`03b8c000 termdd termdd.sys Mon Jul 13 20:16:36 2009 (4A5BCE64) fffff960`005c0000 fffff960`005ca000 TSDDD TSDDD.dll unavailable (00000000) fffff880`019a9000 fffff880`019cf000 tunnel tunnel.sys Mon Jul 13 20:09:37 2009 (4A5BCCC1) fffff880`03c00000 fffff880`03c12000 umbus umbus.sys Mon Jul 13 20:06:56 2009 (4A5BCC20) fffff880`04dbe000 fffff880`04dbff00 USBD USBD.SYS Mon Jul 13 20:06:23 2009 (4A5BCBFF) fffff880`02dbc000 fffff880`02dcd000 usbehci usbehci.sys Mon Jul 13 20:06:30 2009 (4A5BCC06) fffff880`03c12000 fffff880`03c6c000 usbhub usbhub.sys Mon Jul 13 20:07:09 2009 (4A5BCC2D) fffff880`03e00000 fffff880`03e56000 USBPORT USBPORT.SYS Mon Jul 13 20:06:31 2009 (4A5BCC07) fffff880`02daf000 fffff880`02dbc000 usbuhci usbuhci.sys Mon Jul 13 20:06:27 2009 (4A5BCC03) fffff880`00e46000 fffff880`00e53000 vdrvroot vdrvroot.sys Mon Jul 13 20:01:31 2009 (4A5BCADB) fffff880`018f3000 fffff880`01901000 vga vga.sys Mon Jul 13 19:38:47 2009 (4A5BC587) fffff880`01901000 fffff880`01926000 VIDEOPRT VIDEOPRT.SYS Mon Jul 13 19:38:51 2009 (4A5BC58B) fffff880`00e68000 fffff880`00e7d000 volmgr volmgr.sys Mon Jul 13 19:19:57 2009 (4A5BC11D) fffff880`00e7d000 fffff880`00ed9000 volmgrx volmgrx.sys Mon Jul 13 19:20:33 2009 (4A5BC141) fffff880`01000000 fffff880`0104c000 volsnap volsnap.sys Mon Jul 13 19:20:08 2009 (4A5BC128) fffff880`03b5d000 fffff880`03b78000 wanarp wanarp.sys Mon Jul 13 20:10:21 2009 (4A5BCCED) fffff880`01926000 fffff880`01936000 watchdog watchdog.sys Mon Jul 13 19:37:35 2009 (4A5BC53F) fffff880`00eef000 fffff880`00f93000 Wdf01000 Wdf01000.sys Mon Jul 13 19:22:07 2009 (4A5BC19F) fffff880`00f93000 fffff880`00fa2000 WDFLDR WDFLDR.SYS Mon Jul 13 19:19:54 2009 (4A5BC11A) fffff880`03b02000 fffff880`03b0b000 wfplwf wfplwf.sys Mon Jul 13 20:09:26 2009 (4A5BCCB6) fffff960`00010000 fffff960`0031f000 win32k win32k.sys unavailable (00000000) fffff880`00e00000 fffff880`00e09000 WMILIB WMILIB.SYS Mon Jul 13 19:19:51 2009 (4A5BC117) Unloaded modules: fffff880`0340b000 fffff880`03417000 hiber_atapor Timestamp: unavailable (00000000) Checksum: 00000000 fffff880`03417000 fffff880`03420000 hiber_atapi. Timestamp: unavailable (00000000) Checksum: 00000000 fffff880`03588000 fffff880`0359b000 hiber_dumpfv Timestamp: unavailable (00000000) Checksum: 00000000 fffff880`03588000 fffff880`035f9000 spsys.sys Timestamp: unavailable (00000000) Checksum: 00000000 fffff880`01883000 fffff880`01891000 crashdmp.sys Timestamp: unavailable (00000000) Checksum: 00000000 fffff880`01891000 fffff880`0189d000 dump_ataport Timestamp: unavailable (00000000) Checksum: 00000000 fffff880`0189d000 fffff880`018a6000 dump_atapi.s Timestamp: unavailable (00000000) Checksum: 00000000 fffff880`018a6000 fffff880`018b9000 dump_dumpfve Timestamp: unavailable (00000000) Checksum: 00000000 The only additional suggestion I have at the moment is make sure your RAM is seated properly.
I have my fingers crossed!
2 ones today
Error code 116 VIDEO_TDR_FAILURE - usually caused by Video driver, overheating, bad video card, ?BIOS, ?Power to card
Error code 1A MEMORY_MANAGEMENT - usually caused by Device driver, memory, kernel
The first dump blames atikmpag.sys; Attempt to reset the display driver and recover from timeout failed. The second dump points to memory corruption.
You video driver is up to date. You can try to reinstall atikmpag.sys it on the offchance is is corrupted. I am wondering if your video card is bad?
Something is definitely corrupting memory. You can re enable Driver Verifier for about 36 hours and see what happens. Maybe one of the other BSOD team members can spot something I have missed.
Error code 1A MEMORY_MANAGEMENT - usually caused by Device driver, memory, kernel
The first dump blames atikmpag.sys; Attempt to reset the display driver and recover from timeout failed. The second dump points to memory corruption.
Code:
Microsoft (R) Windows Debugger Version 6.11.0001.404 X86 Copyright (c) Microsoft Corporation. All rights reserved. Loading Dump File [C:\Users\Owner\AppData\Local\Temp\Temp1_082010-19640-01.zip\082010-19640-01.dmp] Mini Kernel Dump File: Only registers and stack trace are available Symbol search path is: SRV*c:\symbols*Symbol information Executable search path is: Windows 7 Kernel Version 7600 MP (2 procs) Free x64 Product: WinNt, suite: TerminalServer SingleUserTS Personal Built by: 7600.16617.amd64fre.win7_gdr.100618-1621 Machine Name: Kernel base = 0xfffff800`0281f000 PsLoadedModuleList = 0xfffff800`02a5ce50 Debug session time: Fri Aug 20 12:22:42.861 2010 (GMT-4) System Uptime: 0 days 8:05:41.391 Loading Kernel Symbols ............................................................... ................................................................ ....... Loading User Symbols Loading unloaded module list ..... ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* Use !analyze -v to get detailed debugging information. BugCheck 116, {fffffa80025e5290, fffff88003c3bc80, 0, 2} *** WARNING: Unable to verify timestamp for atikmpag.sys *** ERROR: Module load completed but symbols could not be loaded for atikmpag.sys Probably caused by : atikmpag.sys ( atikmpag+6c80 ) Followup: MachineOwner --------- 0: kd> !analyze -v ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* VIDEO_TDR_FAILURE (116) Attempt to reset the display driver and recover from timeout failed. Arguments: Arg1: fffffa80025e5290, Optional pointer to internal TDR recovery context (TDR_RECOVERY_CONTEXT). Arg2: fffff88003c3bc80, The pointer into responsible device driver module (e.g. owner tag). Arg3: 0000000000000000, Optional error code (NTSTATUS) of the last failed operation. Arg4: 0000000000000002, Optional internal context dependent data. Debugging Details: ------------------ FAULTING_IP: atikmpag+6c80 fffff880`03c3bc80 4883ec28 sub rsp,28h DEFAULT_BUCKET_ID: GRAPHICS_DRIVER_TDR_FAULT CUSTOMER_CRASH_COUNT: 1 BUGCHECK_STR: 0x116 PROCESS_NAME: System CURRENT_IRQL: 0 STACK_TEXT: fffff880`02ec29c8 fffff880`03cd7ef8 : 00000000`00000116 fffffa80`025e5290 fffff880`03c3bc80 00000000`00000000 : nt!KeBugCheckEx fffff880`02ec29d0 fffff880`03cd7c02 : fffff880`03c3bc80 fffffa80`025e5290 fffffa80`03f5e950 fffffa80`041d2410 : dxgkrnl!TdrBugcheckOnTimeout+0xec fffff880`02ec2a10 fffff880`04fc7f07 : fffffa80`025e5290 00000000`00000000 fffffa80`03f5e950 fffffa80`041d2410 : dxgkrnl!TdrIsRecoveryRequired+0x1a2 fffff880`02ec2a40 fffff880`04ff1b75 : 00000000`ffffffff 00000000`001c805c 00000000`00000000 00000000`00000002 : dxgmms1!VidSchiReportHwHang+0x40b fffff880`02ec2b20 fffff880`04ff02bb : 00000000`00000102 00000000`00000000 00000000`001c805c 00000000`00000000 : dxgmms1!VidSchiCheckHwProgress+0x71 fffff880`02ec2b50 fffff880`04fc32c6 : ffffffff`ff676980 fffffa80`041d2410 00000000`00000000 00000000`00000000 : dxgmms1!VidSchiWaitForSchedulerEvents+0x1fb fffff880`02ec2bf0 fffff880`04fefe7a : 00000000`00000000 fffffa80`040b2170 00000000`00000080 fffffa80`041d2410 : dxgmms1!VidSchiScheduleCommandToRun+0x1da fffff880`02ec2d00 fffff800`02b33c06 : 00000000`fffffc32 fffffa80`042fcb60 fffffa80`01843b30 fffffa80`042fcb60 : dxgmms1!VidSchiWorkerThread+0xba fffff880`02ec2d40 fffff800`0286dc26 : fffff800`02a09e80 fffffa80`042fcb60 fffff800`02a17c40 fffff880`01261534 : nt!PspSystemThreadStartup+0x5a fffff880`02ec2d80 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxStartSystemThread+0x16 STACK_COMMAND: .bugcheck ; kb FOLLOWUP_IP: atikmpag+6c80 fffff880`03c3bc80 4883ec28 sub rsp,28h SYMBOL_NAME: atikmpag+6c80 FOLLOWUP_NAME: MachineOwner MODULE_NAME: atikmpag IMAGE_NAME: atikmpag.sys DEBUG_FLR_IMAGE_TIMESTAMP: 4c33d53e FAILURE_BUCKET_ID: X64_0x116_IMAGE_atikmpag.sys BUCKET_ID: X64_0x116_IMAGE_atikmpag.sys Followup: MachineOwner --------- Microsoft (R) Windows Debugger Version 6.11.0001.404 X86 Copyright (c) Microsoft Corporation. All rights reserved. Loading Dump File [C:\Users\Owner\AppData\Local\Temp\Temp1_082010-19640-01.zip\082010-19562-01.dmp] Mini Kernel Dump File: Only registers and stack trace are available Symbol search path is: SRV*c:\symbols*Symbol information Executable search path is: Windows 7 Kernel Version 7600 MP (2 procs) Free x64 Product: WinNt, suite: TerminalServer SingleUserTS Personal Built by: 7600.16617.amd64fre.win7_gdr.100618-1621 Machine Name: Kernel base = 0xfffff800`0284d000 PsLoadedModuleList = 0xfffff800`02a8ae50 Debug session time: Thu Aug 19 21:59:14.691 2010 (GMT-4) System Uptime: 0 days 12:19:25.221 Loading Kernel Symbols ............................................................... ................................................................ ....... Loading User Symbols Loading unloaded module list ........ ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* Use !analyze -v to get detailed debugging information. BugCheck 1A, {8886, fffffa80015d0440, fffffa8000bf9070, 500} Probably caused by : memory_corruption ( nt!MiUnlinkPageFromLockedList+298 ) Followup: MachineOwner --------- 1: kd> !analyze -v ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* MEMORY_MANAGEMENT (1a) # Any other values for parameter 1 must be individually examined. Arguments: Arg1: 0000000000008886, The subtype of the bugcheck. Arg2: fffffa80015d0440 Arg3: fffffa8000bf9070 Arg4: 0000000000000500 Debugging Details: ------------------ BUGCHECK_STR: 0x1a_8886 CUSTOMER_CRASH_COUNT: 1 DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT PROCESS_NAME: svchost.exe CURRENT_IRQL: 2 LAST_CONTROL_TRANSFER: from fffff800028de8c8 to fffff800028bd740 STACK_TEXT: fffff880`0280b888 fffff800`028de8c8 : 00000000`0000001a 00000000`00008886 fffffa80`015d0440 fffffa80`00bf9070 : nt!KeBugCheckEx fffff880`0280b890 fffff800`028ef587 : 00000000`06cd72ae fffff680`00000000 0000007f`06cd72ae fffff680`000366b8 : nt!MiUnlinkPageFromLockedList+0x298 fffff880`0280b920 fffff800`028d9d26 : 00000000`00000001 00000000`06cd72ae fffff880`0280bc20 fffffa80`0433dec8 : nt!MiResolveTransitionFault+0x167 fffff880`0280b9b0 fffff800`028d7743 : ffffffff`ffffffff fffff880`0280bb40 0001dab6`00000080 fffff880`0280bb40 : nt!MiDispatchFault+0x946 fffff880`0280bac0 fffff800`028bb82e : 00000000`00000001 00000000`02895550 00000000`00000001 fffffa80`0189ed80 : nt!MmAccessFault+0x343 fffff880`0280bc20 00000000`778a2b7f : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiPageFault+0x16e 00000000`00f4e120 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x778a2b7f STACK_COMMAND: kb FOLLOWUP_IP: nt!MiUnlinkPageFromLockedList+298 fffff800`028de8c8 cc int 3 SYMBOL_STACK_INDEX: 1 SYMBOL_NAME: nt!MiUnlinkPageFromLockedList+298 FOLLOWUP_NAME: MachineOwner MODULE_NAME: nt DEBUG_FLR_IMAGE_TIMESTAMP: 4c1c44a9 IMAGE_NAME: memory_corruption FAILURE_BUCKET_ID: X64_0x1a_8886_nt!MiUnlinkPageFromLockedList+298 BUCKET_ID: X64_0x1a_8886_nt!MiUnlinkPageFromLockedList+298 Followup: MachineOwner ---------
Something is definitely corrupting memory. You can re enable Driver Verifier for about 36 hours and see what happens. Maybe one of the other BSOD team members can spot something I have missed.
Ok had another one. I actually moved my case the other day to put the ethernet cable back in after I had taken it out to use with my Xbox. Maybe I dislodged something. I'll check it out now.
I have the thing running atm with the case open on the floor and am running everything fine so far. The graphics card felt looser than normal and i gave it a few nudges and it seems to fit a bit better. lets hope thats all it was :S.
Cheers for pointing me in that direction and I'll report back
Cheers for pointing me in that direction and I'll report back
�� Quote: Originally Posted by Watson I have the thing running atm with the case open on the floor and am running everything fine so far. The graphics card felt looser than normal and i gave it a few nudges and it seems to fit a bit better. lets hope thats all it was :S.
Cheers for pointing me in that direction and I'll report back
Cheers for pointing me in that direction and I'll report back
Ok after going afk again and the computer going into sleep. I got this blue screen almost as soon as I came back. Something must have changed again during the past few days. Before now I was absolutely fine for days while playing games quite a lot.
Test your RAM again, I turned to previous page and saw that Carl suggested you to check RAM but I've not seen your response. The DMP point to memory corruption with stop code 1A which is memory management.
Download a copy of Memtest86 and burn the ISO to a CD using Iso Recorder or another ISO burning program. Boot from the CD, and leave it running for at least 5 or 6 passes.
Regard,
Tuan
Download a copy of Memtest86 and burn the ISO to a CD using Iso Recorder or another ISO burning program. Boot from the CD, and leave it running for at least 5 or 6 passes.
Code:
Microsoft (R) Windows Debugger Version 6.12.0002.633 X86 Copyright (c) Microsoft Corporation. All rights reserved. Loading Dump File [C:\Users\TUANTR~1\AppData\Local\Temp\Rar$DI00.466\082110-18782-01.dmp] Mini Kernel Dump File: Only registers and stack trace are available Symbol search path is: SRV*e:\symbols*http://msdl.microsoft.com/download/symbols Executable search path is: Windows 7 Kernel Version 7600 MP (2 procs) Free x64 Product: WinNt, suite: TerminalServer SingleUserTS Personal Built by: 7600.16617.amd64fre.win7_gdr.100618-1621 Machine Name: Kernel base = 0xfffff800`02805000 PsLoadedModuleList = 0xfffff800`02a42e50 Debug session time: Sat Aug 21 18:52:13.395 2010 (UTC + 7:00) System Uptime: 0 days 1:28:46.800 Loading Kernel Symbols ............................................................... ................................................................ ........ Loading User Symbols Loading unloaded module list ........ ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* Use !analyze -v to get detailed debugging information. BugCheck 1A, {8886, fffffa8000bf90a0, fffffa8000000210, 600} Probably caused by : memory_corruption ( nt!MiUnlinkPageFromLockedList+298 ) Followup: MachineOwner --------- Tuan
I have got that on CD but I'll dl it and do it again. It kept freezing after a few hours before while I left it overnight. Maybe a fresh cd burn will help.
Got another one after going afk and coming back almost instantly. i'm sure that it's something to do with it going into sleep. So I'm gonna disable that.
Got another one after going afk and coming back almost instantly. i'm sure that it's something to do with it going into sleep. So I'm gonna disable that.
Watson, check your power saving settings. Something is not waking up properly. Control Panel > Power Options > Balanced > Change plan settings. I have mine set for Put the computer to sleep - Never. I put mine to sleep via the Start > Shutdown button.
Now click on Change advanced power settings and review what you have. I have my Wireless adapter setting set to Maximum performance. This resolved the sleep issue I was having. Under Sleep, I have mine set to never and Allow wake timers enabled. PCI Express is set to Moderate power savings. Under Multimedia and When sharing media, I have mine set to Prevent idling to sleep.
Let us know if this helps the problem.
Now click on Change advanced power settings and review what you have. I have my Wireless adapter setting set to Maximum performance. This resolved the sleep issue I was having. Under Sleep, I have mine set to never and Allow wake timers enabled. PCI Express is set to Moderate power savings. Under Multimedia and When sharing media, I have mine set to Prevent idling to sleep.
Let us know if this helps the problem.
I changed it to never and all my settings apart from that were already the same as you specified. On the memtest point. I ran one overnight last night and had 8 passes with no errors.
Yesterday I did blue screen twice, both while playing Mount and Blade Warband. Thing is there is no dump files as on the blue screen it froze at about 65% of the dump. Unfortunately I ddin't write the error message down :S.
Yesterday I did blue screen twice, both while playing Mount and Blade Warband. Thing is there is no dump files as on the blue screen it froze at about 65% of the dump. Unfortunately I ddin't write the error message down :S.
Glad to hear your RAM is OK; but sorry to hear about the freezes. If you get a dump file, be sure to upload it. If I had to guess, I would say a video or network adapter error.
Another one while playing M&B. This time the dump completed so i have something to upload.
Unfortunately, it does not tell us much.
Bugcheck A IRQL_NOT_LESS_OR_EQUAL - BSOD Index
I am stumped. Something is interfering with memory; but I cannot find it.
Bugcheck A IRQL_NOT_LESS_OR_EQUAL - BSOD Index
Code:
******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* Use !analyze -v to get detailed debugging information. BugCheck A, {fffff880027a29f8, 2, 1, fffff800028df3f2} Probably caused by : ntkrnlmp.exe ( nt!KiTimerExpiration+f2 ) Followup: MachineOwner --------- 0: kd> !analyze -v ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* IRQL_NOT_LESS_OR_EQUAL (a) An attempt was made to access a pageable (or completely invalid) address at an interrupt request level (IRQL) that is too high. This is usually caused by drivers using improper addresses. If a kernel debugger is available get the stack backtrace. Arguments: Arg1: fffff880027a29f8, memory referenced Arg2: 0000000000000002, IRQL Arg3: 0000000000000001, bitfield : bit 0 : value 0 = read operation, 1 = write operation bit 3 : value 0 = not an execute operation, 1 = execute operation (only on chips which support this level of status) Arg4: fffff800028df3f2, address which referenced memory Debugging Details: ------------------ WRITE_ADDRESS: GetPointerFromAddress: unable to read from fffff80002b0b0e0 fffff880027a29f8 CURRENT_IRQL: 2 FAULTING_IP: nt!KiTimerExpiration+f2 fffff800`028df3f2 48894808 mov qword ptr [rax+8],rcx CUSTOMER_CRASH_COUNT: 1 DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT BUGCHECK_STR: 0xA PROCESS_NAME: System TRAP_FRAME: fffff80000b9caa0 -- (.trap 0xfffff80000b9caa0) NOTE: The trap frame does not contain all registers. Some register values may be zeroed or incorrect. rax=fffff880027a29f0 rbx=0000000000000000 rcx=fffff80002a52048 rdx=00000000000000ee rsi=0000000000000000 rdi=0000000000000000 rip=fffff800028df3f2 rsp=fffff80000b9cc30 rbp=00000000001aa1ee r8=fffffa800272e9d0 r9=00000000000000c0 r10=00000000000000ee r11=0000000000000000 r12=0000000000000000 r13=0000000000000000 r14=0000000000000000 r15=0000000000000000 iopl=0 nv up ei ng nz ac po cy nt!KiTimerExpiration+0xf2: fffff800`028df3f2 48894808 mov qword ptr [rax+8],rcx ds:fffff880`027a29f8=???????????????? Resetting default scope LAST_CONTROL_TRANSFER: from fffff800028d2ca9 to fffff800028d3740 STACK_TEXT: fffff800`00b9c958 fffff800`028d2ca9 : 00000000`0000000a fffff880`027a29f8 00000000`00000002 00000000`00000001 : nt!KeBugCheckEx fffff800`00b9c960 fffff800`028d1920 : 00000000`00000000 0000003f`654efa77 fffffa80`02f5b900 fffffa80`02f71de0 : nt!KiBugCheckDispatch+0x69 fffff800`00b9caa0 fffff800`028df3f2 : 0000003f`6547593b fffff800`00b9cc58 00000000`001aa1ea fffff800`02a51fc8 : nt!KiPageFault+0x260 fffff800`00b9cc30 fffff800`028decb7 : 00000012`922da9c0 00000012`001aa1ee 00000012`922da94a 00000000`000000ee : nt!KiTimerExpiration+0xf2 fffff800`00b9ccd0 fffff800`028dbeea : fffff800`02a4de80 fffff800`02a5bc40 00000000`00000000 fffff880`04599480 : nt!KiRetireDpcList+0x277 fffff800`00b9cd80 00000000`00000000 : fffff800`00b9d000 fffff800`00b97000 fffff800`00b9cd40 00000000`00000000 : nt!KiIdleLoop+0x5a STACK_COMMAND: kb FOLLOWUP_IP: nt!KiTimerExpiration+f2 fffff800`028df3f2 48894808 mov qword ptr [rax+8],rcx SYMBOL_STACK_INDEX: 3 SYMBOL_NAME: nt!KiTimerExpiration+f2 FOLLOWUP_NAME: MachineOwner MODULE_NAME: nt IMAGE_NAME: ntkrnlmp.exe DEBUG_FLR_IMAGE_TIMESTAMP: 4c1c44a9 FAILURE_BUCKET_ID: X64_0xA_nt!KiTimerExpiration+f2 BUCKET_ID: X64_0xA_nt!KiTimerExpiration+f2 Followup: MachineOwner --------- Try some hardware diagnostics.
Test CPU: http://www.sevenforums.com/tutorials...t-prime95.html
Test temps with Speedfan: SpeedFan - Access temperature sensor in your computer
Test hard drive: HD Diagnostic
Test CPU: http://www.sevenforums.com/tutorials...t-prime95.html
Test temps with Speedfan: SpeedFan - Access temperature sensor in your computer
Test hard drive: HD Diagnostic
Cheers Jonny I'll check those out.
Something is telling me my graphics has got something to do with it. Am getting really screwed up graphics when I run mount and blade at certain parts of the screen. These normally just went away after about 2 minutes and the game ran fine. Recently noticed that it has got worse though. Afew characters have not appeared with faces on some instances and now the armour of some of the men has turned from a blue like colour to green, although blue seems fine on the rest of the pc. I downloaded the latest stuff from the ATI website and I'm gonna have to try other games see what happens. On the plus side I haven't had a blue screen for a while.
Glad to hear no BSODs, but I suspect they will return.
Do you have another GFX card you can try? Perhaps borrow one from a friend, or rob one off another computer.
Do the Furmark test: Video Card - Stress Test with Furmark
Do you have another GFX card you can try? Perhaps borrow one from a friend, or rob one off another computer.
Do the Furmark test: Video Card - Stress Test with Furmark
Nope no spare card.
The test apears to be going Ok, but what ar the temp limits for the gpu? I have absolutely no idea.
The test apears to be going Ok, but what ar the temp limits for the gpu? I have absolutely no idea.
Mine hits a max of 80.
Keep ketting dodgy graphics on M and B even on lower settings. Annoying me now. I need to keep investigating. Ths blue screen happened yesterday while playing.
�� Quote: Originally Posted by Watson Keep ketting dodgy graphics on M and B even on lower settings. Annoying me now. I need to keep investigating. Ths blue screen happened yesterday while playing.
As for the GPU temps: I'm not sure exactly the threshhold, but you may try opening the side of the case and blowing a fan inside, just to see what happens.
Try a RAM test. RAM - Test with Memtest86+
...Summary of the Dumps:
Code:
*** WARNING: Unable to verify timestamp for Unknown_Module_00000000`00a295a0 *** ERROR: Module load completed but symbols could not be loaded for Unknown_Module_00000000`00a295a0 Built by: 7600.16617.amd64fre.win7_gdr.100618-1621 Debug session time: Sat Aug 28 20:16:56.574 2010 (UTC - 4:00) System Uptime: 0 days 16:24:59.103 *** WARNING: Unable to verify timestamp for Unknown_Module_00000000`00a295a0 *** ERROR: Module load completed but symbols could not be loaded for Unknown_Module_00000000`00a295a0 BugCheck 1E, {0, 0, 0, 0} Probably caused by : Unknown_Image ( Unknown_Module_fffffa80`044b47c0>+2fba70 ) BUGCHECK_STR: 0x1E_0 �������������������������������������������������������������������������������������� Have run several mem tests the most recent being a few nights ago. All completed with about 8 passes and no errors. Hard drive tests came back fine. Speedfan is installed and my temperatures all seem OK.
Test your CPU with Prime 95. Select the blended test and Prime will also test your RAM.
http://www.sevenforums.com/tutorials...t-prime95.html
http://www.sevenforums.com/tutorials...t-prime95.html
Ok will use prime95 and get back to you on the results. Using that GPU test posted back my card seemed fine and hit a max of 80 degrees C and stayed around that level. It's even lower than that while playing M&B. I was checking today with speedfan. I still think there is an issue with the graphics card but I am not convinced that it is causing blue screens.
Cheers for your continued patience, not seen many other 9 page threads in this section
Cheers for your continued patience, not seen many other 9 page threads in this section
We will be here as long as it takes.
�� Quote: Originally Posted by Watson Ok will use prime95 and get back to you on the results. Using that GPU test posted back my card seemed fine and hit a max of 80 degrees C and stayed around that level. It's even lower than that while playing M&B. I was checking today with speedfan. I still think there is an issue with the graphics card but I am not convinced that it is causing blue screens.
Cheers for your continued patience, not seen many other 9 page threads in this section
Cheers for your continued patience, not seen many other 9 page threads in this section
Turns out the graphics problem are caused by problems between the most up to date ATI drivers with that one game. Devs should sort that out soon. Now pretty sure my GPU is fine. Got another blue screen for first time in days today. Didn't dump though so no report to upload. Was a system service exception though. Been using my pc alot for 3 days though with no isses up to now.
Very good news that you found the cause of the video problem. I'm glad you have been running more smoothly. If you want to upload that latest dump, we will take a look at it.
Well hello again, sure your sick of hearing of my pc going haywire, but got a dump yesterday with a message i'd never seen before.
page fault in non paged area.
It got to 95% of the memory dump but there is nothing in the folder, so it never finished uploading. Not the first time that the memory dump simply froze before fully uploaded. I don't know if this is a problem on its own.
Cheers for the continued help and suggestions.
page fault in non paged area.
It got to 95% of the memory dump but there is nothing in the folder, so it never finished uploading. Not the first time that the memory dump simply froze before fully uploaded. I don't know if this is a problem on its own.
Cheers for the continued help and suggestions.
Could you follow the BSOD Posting Instructions again?
The dump did not complete so I have nothing to upload unfortunately. What does the error message in my last post suggest? I mean I'm running out of places to look but maybe I've missed something.
�� Quote: Originally Posted by Watson The dump did not complete so I have nothing to upload unfortunately. What does the error message in my last post suggest? I mean I'm running out of places to look but maybe I've missed something.
We really need the actual DMP file.
If you wish to have others assist you with your computer's BSOD symptoms, upload the contents of your "\Windows\Minidump" folder. The procedure:
* Copy the contents of \Windows\Minidump to another (temporary) location somewhere on your machine.
* Zip up the copy.
* Start your own thread in the "Crashes and Debugging" section of the forum and attach the ZIP archive to your post using the "paperclip" (file attachments) button.
* Briefly describe the problem history and circumstances in the same post. Somebody will attend to your query as soon as possible.
Memory test
Download a copy of Memtest86 and burn the ISO to a CD using Iso Recorder or another ISO burning program. Boot from the CD, and leave it running for at least 5 or 6 passes.
Do follow Ken's suggestion, and run a RAM test. See this tutorial: RAM - Test with Memtest86+
I know there is no new dump, but the BSOD scripts gather more than just dumps. Go ahead and upload the report anyway.
I know there is no new dump, but the BSOD scripts gather more than just dumps. Go ahead and upload the report anyway.
4th time I've run the memtest from advice many pages back and its come back fine after 9 or so passes. As for the contents of the minidump folder there is only 2 old dmp files which i have uploaded already from last month. The most recent ones including one I had today have not given me anything when I look in folder upon restart. There is nothing else in the folders at all. Not all the dumps are completing, Sometimes it gets to 80% sometimes only as much as 20% but there is nothing for me to upload at all in the minidump folder. Any file that has ended up in the minidump folder has been uploaded already and can be found on pretty much every one of the last ten pages.
One today is another message I haven't seen before, "vga.sys".
Thank you for your continued patience and help despite being on page 10 :S.
One today is another message I haven't seen before, "vga.sys".
Thank you for your continued patience and help despite being on page 10 :S.
Perhaps there are clues in Event Viewer.
Could you please follow these directions? http://www.sevenforums.com/crashes-d...tructions.html
Could you please follow these directions? http://www.sevenforums.com/crashes-d...tructions.html
Không có nhận xét nào:
Đăng nhận xét