 | |
| |
| 21 Apr 2011 | #1 |
| | New Computer BSOD Consistent Brand new computer (specs to follow) with minimal software installed. No regular pattern but usually happens within first 15 minutes of starting the computer, including safe mode. The following is information taken from an analysis software. As you can see there has been numerous crashes within 2 days, note the computer was purchased and arrived on the 20th April so less than 2 days use. Any help greatly appreciated. System Information (local) computer name: WINDOWS7_64BIT windows version: Windows 7 , 6.1, build: 7600 windows dir: C:\Windows CPU: AuthenticAMD AMD Athlon(tm) II X4 640 Processor AMD586, level: 16 4 logical processors, active mask: 15 RAM: 4025802752 total VM: 2147352576, free: 1950105600 Crash Dump Analysis Crash dump directory: C:\Windows\Minidump Crash dumps are enabled on your computer. On Thu 21/04/2011 17:12:17 GMT your computer crashed crash dump file: C:\Windows\Minidump\042111-19640-01.dmp This was probably caused by the following module: win32k.sys (win32k+0xCA36B) Bugcheck code: 0x3B (0xC0000005, 0xFFFFF960000FA36B, 0xFFFFF88003C12040, 0x0) Error: SYSTEM_SERVICE_EXCEPTION file path: C:\Windows\system32\win32k.sys product: Microsoft® Windows® Operating System company: Microsoft Corporation description: Multi-User Win32 Driver Bug check description: This indicates that an exception happened while executing a routine that transitions from non-privileged code to privileged code. This appears to be a typical software driver bug and is not likely to be caused by a hardware problem. The crash took place in a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system which cannot be identified at this time. On Thu 21/04/2011 17:12:17 GMT your computer crashed crash dump file: C:\Windows\memory.dmp This was probably caused by the following module: win32k.sys (win32k!memset+0x652B) Bugcheck code: 0x3B (0xC0000005, 0xFFFFF960000FA36B, 0xFFFFF88003C12040, 0x0) Error: SYSTEM_SERVICE_EXCEPTION file path: C:\Windows\system32\win32k.sys product: Microsoft® Windows® Operating System company: Microsoft Corporation description: Multi-User Win32 Driver Bug check description: This indicates that an exception happened while executing a routine that transitions from non-privileged code to privileged code. This appears to be a typical software driver bug and is not likely to be caused by a hardware problem. The crash took place in a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system which cannot be identified at this time. On Thu 21/04/2011 05:46:23 GMT your computer crashed crash dump file: C:\Windows\Minidump\042111-20125-01.dmp This was probably caused by the following module: athurx.sys (athurx+0x60DDA) Bugcheck code: 0xD1 (0x1206, 0x2, 0x1, 0xFFFFF8800886CDDA) Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL file path: C:\Windows\system32\drivers\athurx.sys product: Driver for Atheros CB42/CB43/MB42/MB43 Network Adapter company: Atheros Communications, Inc. description: Atheros Extensible Wireless LAN device driver Bug check description: This indicates that a kernel-mode driver attempted to access pageable memory at a process IRQL that was too high. This appears to be a typical software driver bug and is not likely to be caused by a hardware problem. A third party driver was identified as the probable root cause of this system error. It is suggested you look for an update for the following driver: athurx.sys (Atheros Extensible Wireless LAN device driver, Atheros Communications, Inc.). Google query: athurx.sys Atheros Communications, Inc. DRIVER_IRQL_NOT_LESS_OR_EQUAL On Wed 20/04/2011 21:54:48 GMT your computer crashed crash dump file: C:\Windows\Minidump\042111-31031-01.dmp This was probably caused by the following module: usbport.sys (USBPORT+0x22194) Bugcheck code: 0x1000007E (0xFFFFFFFFC0000005, 0xFFFFF88003330194, 0xFFFFF88001F87F38, 0xFFFFF88001F877A0) Error: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M file path: C:\Windows\system32\drivers\usbport.sys product: Microsoft® Windows® Operating System company: Microsoft Corporation description: USB 1.1 & 2.0 Port Driver Bug check description: This indicates that a system thread generated an exception which the error handler did not catch. This appears to be a typical software driver bug and is not likely to be caused by a hardware problem. The crash took place in a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system which cannot be identified at this time. On Wed 20/04/2011 21:52:00 GMT your computer crashed crash dump file: C:\Windows\Minidump\042011-31296-01.dmp This was probably caused by the following module: dxgmms1.sys (dxgmms1+0xABD7) Bugcheck code: 0x3B (0xC0000005, 0xFFFFF88010B83BD7, 0xFFFFF88007F57830, 0x0) Error: SYSTEM_SERVICE_EXCEPTION file path: C:\Windows\system32\drivers\dxgmms1.sys product: Microsoft® Windows® Operating System company: Microsoft Corporation description: DirectX Graphics MMS Bug check description: This indicates that an exception happened while executing a routine that transitions from non-privileged code to privileged code. This appears to be a typical software driver bug and is not likely to be caused by a hardware problem. The crash took place in a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system which cannot be identified at this time. On Wed 20/04/2011 21:01:26 GMT your computer crashed crash dump file: C:\Windows\Minidump\042011-32375-01.dmp This was probably caused by the following module: ntoskrnl.exe (nt+0x70740) Bugcheck code: 0x3B (0xC0000005, 0xFFFFF80002894021, 0xFFFFF880089C2A00, 0x0) Error: SYSTEM_SERVICE_EXCEPTION file path: C:\Windows\system32\ntoskrnl.exe product: Microsoft® Windows® Operating System company: Microsoft Corporation description: NT Kernel & System Bug check description: This indicates that an exception happened while executing a routine that transitions from non-privileged code to privileged code. This appears to be a typical software driver bug and is not likely to be caused by a hardware problem. The crash took place in the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time. On Wed 20/04/2011 20:55:42 GMT your computer crashed crash dump file: C:\Windows\Minidump\042011-30156-01.dmp This was probably caused by the following module: athurx.sys (athurx+0x5465E) Bugcheck code: 0x1000007E (0xFFFFFFFFC0000005, 0xFFFFF8800985465E, 0xFFFFF88008BA07E8, 0xFFFFF88008BA0040) Error: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M file path: C:\Windows\system32\drivers\athurx.sys product: Driver for Atheros CB42/CB43/MB42/MB43 Network Adapter company: Atheros Communications, Inc. description: Atheros Extensible Wireless LAN device driver Bug check description: This indicates that a system thread generated an exception which the error handler did not catch. This appears to be a typical software driver bug and is not likely to be caused by a hardware problem. A third party driver was identified as the probable root cause of this system error. It is suggested you look for an update for the following driver: athurx.sys (Atheros Extensible Wireless LAN device driver, Atheros Communications, Inc.). Google query: athurx.sys Atheros Communications, Inc. SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M On Tue 19/04/2011 13:38:23 GMT your computer crashed crash dump file: C:\Windows\Minidump\041911-24265-01.dmp This was probably caused by the following module: ntoskrnl.exe (nt+0x71F00) Bugcheck code: 0x1A (0x41201, 0xFFFFF683FF7E8E00, 0xCD50000166398025, 0xFFFFFA8003868110) Error: MEMORY_MANAGEMENT file path: C:\Windows\system32\ntoskrnl.exe product: Microsoft® Windows® Operating System company: Microsoft Corporation description: NT Kernel & System Bug check description: This indicates that a severe memory management error occurred. This might be a case of memory corruption. More often memory corruption happens because of software errors in buggy drivers, not because of faulty RAM modules. The crash took place in the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time. |
My System Specs | |
| 21 Apr 2011 | #2 |
| | 
Quote: Originally Posted by davidbain  Brand new computer (specs to follow) with minimal software installed. No regular pattern but usually happens within first 15 minutes of starting the computer, including safe mode. The following is information taken from an analysis software. As you can see there has been numerous crashes within 2 days, note the computer was purchased and arrived on the 20th April so less than 2 days use. Any help greatly appreciated. System Information (local) computer name: WINDOWS7_64BIT windows version: Windows 7 , 6.1, build: 7600 windows dir: C:\Windows CPU: AuthenticAMD AMD Athlon(tm) II X4 640 Processor AMD586, level: 16 4 logical processors, active mask: 15 RAM: 4025802752 total VM: 2147352576, free: 1950105600 Crash Dump Analysis Crash dump directory: C:\Windows\Minidump Crash dumps are enabled on your computer. On Thu 21/04/2011 17:12:17 GMT your computer crashed crash dump file: C:\Windows\Minidump\042111-19640-01.dmp This was probably caused by the following module: win32k.sys (win32k+0xCA36B) Bugcheck code: 0x3B (0xC0000005, 0xFFFFF960000FA36B, 0xFFFFF88003C12040, 0x0) Error: SYSTEM_SERVICE_EXCEPTION file path: C:\Windows\system32\win32k.sys product: Microsoft® Windows® Operating System company: Microsoft Corporation description: Multi-User Win32 Driver Bug check description: This indicates that an exception happened while executing a routine that transitions from non-privileged code to privileged code. This appears to be a typical software driver bug and is not likely to be caused by a hardware problem. The crash took place in a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system which cannot be identified at this time. On Thu 21/04/2011 17:12:17 GMT your computer crashed crash dump file: C:\Windows\memory.dmp This was probably caused by the following module: win32k.sys (win32k!memset+0x652B) Bugcheck code: 0x3B (0xC0000005, 0xFFFFF960000FA36B, 0xFFFFF88003C12040, 0x0) Error: SYSTEM_SERVICE_EXCEPTION file path: C:\Windows\system32\win32k.sys product: Microsoft® Windows® Operating System company: Microsoft Corporation description: Multi-User Win32 Driver Bug check description: This indicates that an exception happened while executing a routine that transitions from non-privileged code to privileged code. This appears to be a typical software driver bug and is not likely to be caused by a hardware problem. The crash took place in a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system which cannot be identified at this time. On Thu 21/04/2011 05:46:23 GMT your computer crashed crash dump file: C:\Windows\Minidump\042111-20125-01.dmp This was probably caused by the following module: athurx.sys (athurx+0x60DDA) Bugcheck code: 0xD1 (0x1206, 0x2, 0x1, 0xFFFFF8800886CDDA) Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL file path: C:\Windows\system32\drivers\athurx.sys product: Driver for Atheros CB42/CB43/MB42/MB43 Network Adapter company: Atheros Communications, Inc. description: Atheros Extensible Wireless LAN device driver Bug check description: This indicates that a kernel-mode driver attempted to access pageable memory at a process IRQL that was too high. This appears to be a typical software driver bug and is not likely to be caused by a hardware problem. A third party driver was identified as the probable root cause of this system error. It is suggested you look for an update for the following driver: athurx.sys (Atheros Extensible Wireless LAN device driver, Atheros Communications, Inc.). Google query: athurx.sys Atheros Communications, Inc. DRIVER_IRQL_NOT_LESS_OR_EQUAL On Wed 20/04/2011 21:54:48 GMT your computer crashed crash dump file: C:\Windows\Minidump\042111-31031-01.dmp This was probably caused by the following module: usbport.sys (USBPORT+0x22194) Bugcheck code: 0x1000007E (0xFFFFFFFFC0000005, 0xFFFFF88003330194, 0xFFFFF88001F87F38, 0xFFFFF88001F877A0) Error: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M file path: C:\Windows\system32\drivers\usbport.sys product: Microsoft® Windows® Operating System company: Microsoft Corporation description: USB 1.1 & 2.0 Port Driver Bug check description: This indicates that a system thread generated an exception which the error handler did not catch. This appears to be a typical software driver bug and is not likely to be caused by a hardware problem. The crash took place in a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system which cannot be identified at this time. On Wed 20/04/2011 21:52:00 GMT your computer crashed crash dump file: C:\Windows\Minidump\042011-31296-01.dmp This was probably caused by the following module: dxgmms1.sys (dxgmms1+0xABD7) Bugcheck code: 0x3B (0xC0000005, 0xFFFFF88010B83BD7, 0xFFFFF88007F57830, 0x0) Error: SYSTEM_SERVICE_EXCEPTION file path: C:\Windows\system32\drivers\dxgmms1.sys product: Microsoft® Windows® Operating System company: Microsoft Corporation description: DirectX Graphics MMS Bug check description: This indicates that an exception happened while executing a routine that transitions from non-privileged code to privileged code. This appears to be a typical software driver bug and is not likely to be caused by a hardware problem. The crash took place in a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system which cannot be identified at this time. On Wed 20/04/2011 21:01:26 GMT your computer crashed crash dump file: C:\Windows\Minidump\042011-32375-01.dmp This was probably caused by the following module: ntoskrnl.exe (nt+0x70740) Bugcheck code: 0x3B (0xC0000005, 0xFFFFF80002894021, 0xFFFFF880089C2A00, 0x0) Error: SYSTEM_SERVICE_EXCEPTION file path: C:\Windows\system32\ntoskrnl.exe product: Microsoft® Windows® Operating System company: Microsoft Corporation description: NT Kernel & System Bug check description: This indicates that an exception happened while executing a routine that transitions from non-privileged code to privileged code. This appears to be a typical software driver bug and is not likely to be caused by a hardware problem. The crash took place in the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time. On Wed 20/04/2011 20:55:42 GMT your computer crashed crash dump file: C:\Windows\Minidump\042011-30156-01.dmp This was probably caused by the following module: athurx.sys (athurx+0x5465E) Bugcheck code: 0x1000007E (0xFFFFFFFFC0000005, 0xFFFFF8800985465E, 0xFFFFF88008BA07E8, 0xFFFFF88008BA0040) Error: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M file path: C:\Windows\system32\drivers\athurx.sys product: Driver for Atheros CB42/CB43/MB42/MB43 Network Adapter company: Atheros Communications, Inc. description: Atheros Extensible Wireless LAN device driver Bug check description: This indicates that a system thread generated an exception which the error handler did not catch. This appears to be a typical software driver bug and is not likely to be caused by a hardware problem. A third party driver was identified as the probable root cause of this system error. It is suggested you look for an update for the following driver: athurx.sys (Atheros Extensible Wireless LAN device driver, Atheros Communications, Inc.). Google query: athurx.sys Atheros Communications, Inc. SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M On Tue 19/04/2011 13:38:23 GMT your computer crashed crash dump file: C:\Windows\Minidump\041911-24265-01.dmp This was probably caused by the following module: ntoskrnl.exe (nt+0x71F00) Bugcheck code: 0x1A (0x41201, 0xFFFFF683FF7E8E00, 0xCD50000166398025, 0xFFFFFA8003868110) Error: MEMORY_MANAGEMENT file path: C:\Windows\system32\ntoskrnl.exe product: Microsoft® Windows® Operating System company: Microsoft Corporation description: NT Kernel & System Bug check description: This indicates that a severe memory management error occurred. This might be a case of memory corruption. More often memory corruption happens because of software errors in buggy drivers, not because of faulty RAM modules. The crash took place in the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time. We need the actual dmp files for examination To enable us to 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. * Attach the ZIP archive to your post using the "paperclip" (file attachments) button. To ensure minidumps are enabled: Go to Start, in the Search Box type: sysdm.cpl, press Enter. Under the Advanced tab, click on the Startup and Recovery Settings... button. Ensure that Automatically restart is unchecked. Under the Write Debugging Information header select Small memory dump (256 kB) in the dropdown box (the 256kb varies). Ensure that the Small Dump Directory is listed as %systemroot%\Minidump. OK your way out. Reboot if changes have been made. |
| My System Specs |
| 21 Apr 2011 | #3 |
| | Not a problem, I'll get them to you soon. The issue is on a friends computer, I'll get him to post on here with the files soon! Many thanks! |
| My System Specs |
| . |
| |
| 21 Apr 2011 | #4 |
| | Here are a bunch of .dmp files, thanks!  |
| My System Specs |
| 21 Apr 2011 | #5 |
| | Hi, David; I looked at the four most resent dumps from those you uploaded. I will look further later on. Each of the dumps shows a different stop error code; this usually indicates a hardware/ hardware related problem. All four dumps indicate memory corruption I would like to look deeper into the system. Please read this tutorial, run the tool, and upload the resulting files in your next post: http://www.sevenforums.com/crashes-d...tructions.html. This will help us to help you better. Quote: Bugcheck A, IRQL_NOT_LESS_OR_EQUAL. Usual causes: Kernel mode driver, System Service, BIOS, Windows, Virus scanner, Backup tool, compatibility. Bugcheck 3B, SYSTEM_SERVICE_EXCEPTION. Usual causes: System service, Device driver, graphics driver, ?memory. Bugcheck D1, DRIVER_IRQL_NOT_LESS_OR_EQUAL. Usual causes: Device driver. Bugcheck 7E, SYSTEM_THREAD_EXCEPTION_NOT_HANDLED. Usual causes: Insufficient disk space, Device driver, Video card, BIOS, Breakpoint with no debugger attached, Hardware incompatibility, Faulty system service, Memory, 3rd party remote control. 2. Update the following driver. Update it from the computer manufacture's website or the link provided. Do not use Windows update. This driver is definitely out of date. Quote: nvm62x64.sys Fri Oct 17 17:01:06 2008 - nVidia Ethernet Networking Driver (nForce chipset driver). Drivers - Download NVIDIA Drivers Code: Windows 7 Kernel Version 7600 MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7600.16695.amd64fre.win7_gdr.101026-1503
Machine Name:
Kernel base = 0xfffff800`02863000 PsLoadedModuleList = 0xfffff800`02aa0e50
Debug session time: Thu Apr 21 13:28:44.243 2011 (GMT-4)
System Uptime: 0 days 0:15:43.946
Loading Kernel Symbols
...............................................................
................................................................
....................
Loading User Symbols
Loading unloaded module list
......
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck A, {e, 2, 1, fffff800028ea312}
Probably caused by : ntkrnlmp.exe ( nt!KeReleaseSemaphore+a2 )
Followup: MachineOwner
---------
3: 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: 000000000000000e, 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: fffff800028ea312, address which referenced memory
Debugging Details:
------------------
WRITE_ADDRESS: GetPointerFromAddress: unable to read from fffff80002b0b0e0
000000000000000e
CURRENT_IRQL: 2
FAULTING_IP:
nt!KeReleaseSemaphore+a2
fffff800`028ea312 48894108 mov qword ptr [rcx+8],rax
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
BUGCHECK_STR: 0xA
PROCESS_NAME: csrss.exe
TRAP_FRAME: fffff880043b0790 -- (.trap 0xfffff880043b0790)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=fffff880046474e8 rbx=0000000000000000 rcx=0000000000000006
rdx=fffffa80064a1b58 rsi=0000000000000000 rdi=0000000000000000
rip=fffff800028ea312 rsp=fffff880043b0920 rbp=0000000000000006
r8=0000000000000100 r9=0000000000000000 r10=0000000000000000
r11=fffff8a008380e00 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0 nv up ei ng nz ac pe cy
nt!KeReleaseSemaphore+0xa2:
fffff800`028ea312 48894108 mov qword ptr [rcx+8],rax ds:0001:00000000`0000000e=????????????????
Resetting default scope
LAST_CONTROL_TRANSFER: from fffff800028d2ca9 to fffff800028d3740
STACK_TEXT:
fffff880`043b0648 fffff800`028d2ca9 : 00000000`0000000a 00000000`0000000e 00000000`00000002 00000000`00000001 : nt!KeBugCheckEx
fffff880`043b0650 fffff800`028d1920 : 00000000`00000001 fffffa80`064a1dd0 fffff8a0`06db15c0 00000000`00000001 : nt!KiBugCheckDispatch+0x69
fffff880`043b0790 fffff800`028ea312 : fffffa80`064a1dd0 fffffa80`064a1a10 fffffa80`064a1b58 00000000`00000001 : nt!KiPageFault+0x260
fffff880`043b0920 fffff800`02bd7066 : fffff8a0`00000000 00000000`00000001 fffffa80`05d37a60 fffff8a0`08380d00 : nt!KeReleaseSemaphore+0xa2
fffff880`043b09a0 fffff800`02bd119d : 00000000`0044fb40 fffffa80`05d43b60 fffffa80`064a1a10 00000000`0044fb40 : nt!AlpcpDispatchReplyToWaitingThread+0x2d6
fffff880`043b0a00 fffff800`02bd2bd9 : fffffa80`05d43b00 fffff800`00000001 00000000`00000000 fffffa80`04e6db01 : nt!AlpcpSendMessage+0x66b
fffff880`043b0b00 fffff800`028d2993 : fffffa80`05d43b60 fffff880`043b0ca0 00000000`0044fa98 fffff800`02be7254 : nt!NtAlpcSendWaitReceivePort+0xb9
fffff880`043b0bb0 00000000`774dff0a : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
00000000`0044fa78 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x774dff0a
STACK_COMMAND: kb
FOLLOWUP_IP:
nt!KeReleaseSemaphore+a2
fffff800`028ea312 48894108 mov qword ptr [rcx+8],rax
SYMBOL_STACK_INDEX: 3
SYMBOL_NAME: nt!KeReleaseSemaphore+a2
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: nt
IMAGE_NAME: ntkrnlmp.exe
DEBUG_FLR_IMAGE_TIMESTAMP: 4cc791bd
FAILURE_BUCKET_ID: X64_0xA_nt!KeReleaseSemaphore+a2
BUCKET_ID: X64_0xA_nt!KeReleaseSemaphore+a2
Followup: MachineOwner
---------
Debug session time: Thu Apr 21 13:12:17.468 2011 (GMT-4)
System Uptime: 0 days 0:02:47.171
Loading Kernel Symbols
...............................................................
................................................................
..................
Loading User Symbols
Loading unloaded module list
....
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 3B, {c0000005, fffff960000fa36b, fffff88003c12040, 0}
Probably caused by : win32k.sys ( win32k!ThreadUnlock1+b )
Followup: MachineOwner
---------
1: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
SYSTEM_SERVICE_EXCEPTION (3b)
An exception happened while executing a system service routine.
Arguments:
Arg1: 00000000c0000005, Exception code that caused the bugcheck
Arg2: fffff960000fa36b, Address of the exception record for the exception that caused the bugcheck
Arg3: fffff88003c12040, Address of the context record for the exception that caused the bugcheck
Arg4: 0000000000000000, zero.
Debugging Details:
------------------
EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.
FAULTING_IP:
win32k!ThreadUnlock1+b
fffff960`000fa36b 488b8a50010000 mov rcx,qword ptr [rdx+150h]
CONTEXT: fffff88003c12040 -- (.cxr 0xfffff88003c12040)
rax=0000000055555598 rbx=0000000000000021 rcx=00000000000000c8
rdx=0000000000000000 rsi=fffff900c00e93d0 rdi=000000000000000d
rip=fffff960000fa36b rsp=fffff88003c12a10 rbp=0000000000000000
r8=00000000fffffff7 r9=0000000000000000 r10=000000000000001c
r11=fffff900c01c3af0 r12=0000000000000000 r13=fffff960003122c0
r14=0000000000000002 r15=0000000000000000
iopl=0 nv up ei ng nz na pe nc
cs=0010 ss=0018 ds=002b es=002b fs=0053 gs=002b efl=00010282
win32k!ThreadUnlock1+0xb:
fffff960`000fa36b 488b8a50010000 mov rcx,qword ptr [rdx+150h] ds:002b:00000000`00000150=????????????????
Resetting default scope
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
BUGCHECK_STR: 0x3B
PROCESS_NAME: csrss.exe
CURRENT_IRQL: 0
LAST_CONTROL_TRANSFER: from fffff96000145dc5 to fffff960000fa36b
STACK_TEXT:
fffff880`03c12a10 fffff960`00145dc5 : 00000000`00000001 00000000`00000000 fffff900`c00e93d0 00000000`0000000d : win32k!ThreadUnlock1+0xb
fffff880`03c12a40 fffff960`000f2f5d : fffff900`c302cb70 00000000`0000000f 00000000`7fffffff fffff800`028921e3 : win32k!zzzAnimateCursor+0xed
fffff880`03c12aa0 fffff960`000f39e4 : 00000000`00000000 fffff960`00312a90 00000000`00000004 00000000`00000001 : win32k!TimersProc+0xf1
fffff880`03c12af0 fffff960`0008455c : fffffa80`0000007b 00000000`0000000f fffff880`00000001 ffffffff`80000390 : win32k!RawInputThread+0x9b4
fffff880`03c12bc0 fffff960`0010419a : fffffa80`00000002 fffff880`02ef4f40 00000000`00000020 00000000`00000000 : win32k!xxxCreateSystemThreads+0x58
fffff880`03c12bf0 fffff800`02885993 : fffffa80`05f55b60 00000000`00000004 000007ff`fffd4000 00000000`00000000 : win32k!NtUserCallNoParam+0x36
fffff880`03c12c20 000007fe`fd8b3d5a : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
00000000`017afec8 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x7fe`fd8b3d5a
FOLLOWUP_IP:
win32k!ThreadUnlock1+b
fffff960`000fa36b 488b8a50010000 mov rcx,qword ptr [rdx+150h]
SYMBOL_STACK_INDEX: 0
SYMBOL_NAME: win32k!ThreadUnlock1+b
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: win32k
IMAGE_NAME: win32k.sys
DEBUG_FLR_IMAGE_TIMESTAMP: 4d6f11c9
STACK_COMMAND: .cxr 0xfffff88003c12040 ; kb
FAILURE_BUCKET_ID: X64_0x3B_win32k!ThreadUnlock1+b
BUCKET_ID: X64_0x3B_win32k!ThreadUnlock1+b
Followup: MachineOwner
---------
Debug session time: Thu Apr 21 01:46:23.224 2011 (GMT-4)
System Uptime: 0 days 0:05:58.943
Loading Kernel Symbols
...............................................................
................................................................
........................
Loading User Symbols
Loading unloaded module list
.....
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck D1, {1206, 2, 1, fffff8800886cdda}
Unable to load image \SystemRoot\system32\DRIVERS\athurx.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for athurx.sys
*** ERROR: Module load completed but symbols could not be loaded for athurx.sys
Probably caused by : hardware ( athurx+60dda )
Followup: MachineOwner
---------
3: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
DRIVER_IRQL_NOT_LESS_OR_EQUAL (d1)
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 kernel debugger is available get stack backtrace.
Arguments:
Arg1: 0000000000001206, memory referenced
Arg2: 0000000000000002, IRQL
Arg3: 0000000000000001, value 0 = read operation, 1 = write operation
Arg4: fffff8800886cdda, address which referenced memory
Debugging Details:
------------------
OVERLAPPED_MODULE: Address regions for 'nvmf6264' and 'nvm62x64.sys' overlap
WRITE_ADDRESS: GetPointerFromAddress: unable to read from fffff80002b010e0
0000000000001206
CURRENT_IRQL: 2
FAULTING_IP:
athurx+60dda
fffff880`0886cdda 800000 add byte ptr [rax],0
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
BUGCHECK_STR: 0xD1
PROCESS_NAME: System
TRAP_FRAME: fffff88004365160 -- (.trap 0xfffff88004365160)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=0000000000001206 rbx=0000000000000000 rcx=fffffa80056cc3b0
rdx=0000000000000005 rsi=0000000000000000 rdi=0000000000000000
rip=fffff8800886cdda rsp=fffff880043652f0 rbp=0000000000000080
r8=fffffa8003daa050 r9=0000000000000001 r10=fffff880089c03c8
r11=0000000000000000 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0 nv up ei pl nz ac pe nc
athurx+0x60dda:
fffff880`0886cdda 800000 add byte ptr [rax],0 ds:dd70:00000000`00001206=??
Resetting default scope
MISALIGNED_IP:
athurx+60dda
fffff880`0886cdda 800000 add byte ptr [rax],0
LAST_CONTROL_TRANSFER: from fffff800028c8ca9 to fffff800028c9740
STACK_TEXT:
fffff880`04365018 fffff800`028c8ca9 : 00000000`0000000a 00000000`00001206 00000000`00000002 00000000`00000001 : nt!KeBugCheckEx
fffff880`04365020 fffff800`028c7920 : fffff880`0176e9a0 00000000`00057a19 fffffa80`046ad000 fffffa80`046ad000 : nt!KiBugCheckDispatch+0x69
fffff880`04365160 fffff880`0886cdda : fffffa80`037d7720 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiPageFault+0x260
fffff880`043652f0 fffffa80`037d7720 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : athurx+0x60dda
fffff880`043652f8 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0xfffffa80`037d7720
STACK_COMMAND: kb
FOLLOWUP_IP:
athurx+60dda
fffff880`0886cdda 800000 add byte ptr [rax],0
SYMBOL_STACK_INDEX: 3
SYMBOL_NAME: athurx+60dda
FOLLOWUP_NAME: MachineOwner
IMAGE_NAME: hardware
DEBUG_FLR_IMAGE_TIMESTAMP: 0
MODULE_NAME: hardware
FAILURE_BUCKET_ID: X64_IP_MISALIGNED_athurx.sys
BUCKET_ID: X64_IP_MISALIGNED_athurx.sys
Followup: MachineOwner
---------
Debug session time: Wed Apr 20 17:54:48.687 2011 (GMT-4)
System Uptime: 0 days 0:00:58.250
Loading Kernel Symbols
...............................................................
........................................................
Loading User Symbols
Loading unloaded module list
.....
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 1000007E, {ffffffffc0000005, fffff88003330194, fffff88001f87f38, fffff88001f877a0}
Unable to load image \SystemRoot\system32\DRIVERS\usbhub.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for usbhub.sys
*** ERROR: Module load completed but symbols could not be loaded for usbhub.sys
Probably caused by : USBPORT.SYS ( USBPORT!USBPORT_ProcessURB+914 )
Followup: MachineOwner
---------
2: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M (1000007e)
This is a very common bugcheck. Usually the exception address pinpoints
the driver/function that caused the problem. Always note this address
as well as the link date of the driver/image that contains this address.
Some common problems are exception code 0x80000003. This means a hard
coded breakpoint or assertion was hit, but this system was booted
/NODEBUG. This is not supposed to happen as developers should never have
hardcoded breakpoints in retail code, but ...
If this happens, make sure a debugger gets connected, and the
system is booted /DEBUG. This will let us see why this breakpoint is
happening.
Arguments:
Arg1: ffffffffc0000005, The exception code that was not handled
Arg2: fffff88003330194, The address that the exception occurred at
Arg3: fffff88001f87f38, Exception Record Address
Arg4: fffff88001f877a0, Context Record Address
Debugging Details:
------------------
EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.
FAULTING_IP:
USBPORT!USBPORT_ProcessURB+914
fffff880`03330194 ff15fee00000 call qword ptr [USBPORT!_imp_MmBuildMdlForNonPagedPool (fffff880`0333e298)]
EXCEPTION_RECORD: fffff88001f87f38 -- (.exr 0xfffff88001f87f38)
ExceptionAddress: fffff88003330194 (USBPORT!USBPORT_ProcessURB+0x0000000000000914)
ExceptionCode: c0000005 (Access violation)
ExceptionFlags: 00000000
NumberParameters: 2
Parameter[0]: 0000000000000000
Parameter[1]: ffffffffffffffff
Attempt to read from address ffffffffffffffff
CONTEXT: fffff88001f877a0 -- (.cxr 0xfffff88001f877a0)
rax=fffffa80056e07d0 rbx=fffffa8004f01010 rcx=fffffa80056e07d0
rdx=fffffa80056e07d1 rsi=fffffa8004f69050 rdi=fffffa80058eef70
rip=fffff88003330194 rsp=fffff88001f88170 rbp=0000000000000000
r8=fffffa80056e07d0 r9=0000000000000000 r10=fffff80001e4d700
r11=0000000000000000 r12=00000000c000000d r13=fffffa8005900a10
r14=0000000000000000 r15=fffffa8005841db8
iopl=0 nv up ei pl nz na pe nc
cs=0010 ss=0018 ds=002b es=002b fs=0053 gs=002b efl=00010202
USBPORT!USBPORT_ProcessURB+0x914:
fffff880`03330194 ff15fee00000 call qword ptr [USBPORT!_imp_MmBuildMdlForNonPagedPool (fffff880`0333e298)] ds:002b:fffff880`0333e298=0000000000038b20
Resetting default scope
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
PROCESS_NAME: System
CURRENT_IRQL: 0
ERROR_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.
EXCEPTION_PARAMETER1: 0000000000000000
EXCEPTION_PARAMETER2: ffffffffffffffff
READ_ADDRESS: GetPointerFromAddress: unable to read from fffff80001f010e0
ffffffffffffffff
FOLLOWUP_IP:
USBPORT!USBPORT_ProcessURB+914
fffff880`03330194 ff15fee00000 call qword ptr [USBPORT!_imp_MmBuildMdlForNonPagedPool (fffff880`0333e298)]
BUGCHECK_STR: 0x7E
LAST_CONTROL_TRANSFER: from fffff88003338d44 to fffff88003330194
STACK_TEXT:
fffff880`01f88170 fffff880`03338d44 : fffffa80`0505ab20 fffffa80`05020009 fffffa80`0505ab20 fffffa80`058eef70 : USBPORT!USBPORT_ProcessURB+0x914
fffff880`01f88220 fffff880`03312ad4 : 00000000`00000000 fffffa80`05025050 fffffa80`05f7a220 fffffa80`0505ab20 : USBPORT!USBPORT_PdoInternalDeviceControlIrp+0x138
fffff880`01f88260 fffff880`03692566 : fffffa80`0502e050 fffffa80`04f1b060 fffffa80`0505ab20 fffffa80`0502e1a0 : USBPORT!USBPORT_Dispatch+0x1dc
fffff880`01f882a0 fffffa80`0502e050 : fffffa80`04f1b060 fffffa80`0505ab20 fffffa80`0502e1a0 fffffa80`0505ab20 : usbhub+0x3566
fffff880`01f882a8 fffffa80`04f1b060 : fffffa80`0505ab20 fffffa80`0502e1a0 fffffa80`0505ab20 fffff880`036c2cab : 0xfffffa80`0502e050
fffff880`01f882b0 fffffa80`0505ab20 : fffffa80`0502e1a0 fffffa80`0505ab20 fffff880`036c2cab 00000000`00000000 : 0xfffffa80`04f1b060
fffff880`01f882b8 fffffa80`0502e1a0 : fffffa80`0505ab20 fffff880`036c2cab 00000000`00000000 00000000`00000000 : 0xfffffa80`0505ab20
fffff880`01f882c0 fffffa80`0505ab20 : fffff880`036c2cab 00000000`00000000 00000000`00000000 fffffa80`04f1b060 : 0xfffffa80`0502e1a0
fffff880`01f882c8 fffff880`036c2cab : 00000000`00000000 00000000`00000000 fffffa80`04f1b060 fffffa80`05904b30 : 0xfffffa80`0505ab20
fffff880`01f882d0 00000000`00000000 : 00000000`00000000 fffffa80`04f1b060 fffffa80`05904b30 00000000`00000000 : usbhub+0x33cab
SYMBOL_STACK_INDEX: 0
SYMBOL_NAME: USBPORT!USBPORT_ProcessURB+914
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: USBPORT
IMAGE_NAME: USBPORT.SYS
DEBUG_FLR_IMAGE_TIMESTAMP: 4a5bcc07
STACK_COMMAND: .cxr 0xfffff88001f877a0 ; kb
FAILURE_BUCKET_ID: X64_0x7E_USBPORT!USBPORT_ProcessURB+914
BUCKET_ID: X64_0x7E_USBPORT!USBPORT_ProcessURB+914
Followup: MachineOwner
---------
2: kd> lmtsmn
start end module name
fffff880`00f94000 fffff880`00feb000 ACPI ACPI.sys Mon Jul 13 19:19:34 2009 (4A5BC106)
fffff880`02c6c000 fffff880`02cf6000 afd afd.sys Mon Jul 13 19:21:40 2009 (4A5BC184)
fffff880`02c0b000 fffff880`02c21000 AgileVpn AgileVpn.sys Mon Jul 13 20:10:24 2009 (4A5BCCF0)
fffff880`010d6000 fffff880`010e1000 amdxata amdxata.sys Tue May 19 13:56:59 2009 (4A12F2EB)
fffff880`00cda000 fffff880`00ce3000 atapi atapi.sys Mon Jul 13 19:19:47 2009 (4A5BC113)
fffff880`00d76000 fffff880`00da0000 ataport ataport.SYS Mon Jul 13 19:19:52 2009 (4A5BC118)
fffff880`03e37000 fffff880`03fff000 athurx athurx.sys Mon Jan 04 22:23:16 2010 (4B42B0A4)
fffff880`0181c000 fffff880`01823000 Beep Beep.SYS Mon Jul 13 20:00:13 2009 (4A5BCA8D)
fffff880`0322a000 fffff880`0323b000 blbdrive blbdrive.sys Mon Jul 13 19:35:59 2009 (4A5BC4DF)
fffff880`04564000 fffff880`04582000 bowser bowser.sys Wed Feb 23 00:15:06 2011 (4D6497DA)
fffff880`0370a000 fffff880`03727000 cdfs cdfs.sys Mon Jul 13 19:19:46 2009 (4A5BC112)
fffff880`03200000 fffff880`0322a000 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`01987000 fffff880`019b7000 CLASSPNP CLASSPNP.SYS Mon Jul 13 19:19:58 2009 (4A5BC11E)
fffff880`00d18000 fffff880`00d76000 CLFS CLFS.SYS Mon Jul 13 19:19:57 2009 (4A5BC11D)
fffff880`01000000 fffff880`01073000 cng cng.sys Mon Jul 13 19:49:40 2009 (4A5BC814)
fffff880`02dec000 fffff880`02dfc000 CompositeBus CompositeBus.sys Mon Jul 13 20:00:33 2009 (4A5BCAA1)
fffff880`0377b000 fffff880`03789000 crashdmp crashdmp.sys Mon Jul 13 20:01:01 2009 (4A5BCABD)
fffff880`0323c000 fffff880`032bf000 csc csc.sys Mon Jul 13 19:24:26 2009 (4A5BC22A)
fffff880`03727000 fffff880`03739000 dc3d dc3d.sys Fri Apr 08 18:58:20 2011 (4D9F930C)
fffff880`032bf000 fffff880`032dd000 dfsc dfsc.sys Mon Jul 13 19:23:44 2009 (4A5BC200)
fffff880`01971000 fffff880`01987000 disk disk.sys Mon Jul 13 19:19:57 2009 (4A5BC11D)
fffff880`03789000 fffff880`03793000 dump_diskdump dump_diskdump.sys Mon Jul 12 23:32:05 2010 (4C3BDE35)
fffff880`037be000 fffff880`037d1000 dump_dumpfve dump_dumpfve.sys Mon Jul 13 19:21:51 2009 (4A5BC18F)
fffff880`03793000 fffff880`037be000 dump_nvstor dump_nvstor.sys Wed May 20 02:45:37 2009 (4A13A711)
fffff880`036fe000 fffff880`0370a000 Dxapi Dxapi.sys Mon Jul 13 19:38:28 2009 (4A5BC574)
fffff960`00490000 fffff960`004ae000 dxg dxg.sys unavailable (00000000)
fffff880`0112d000 fffff880`01141000 fileinfo fileinfo.sys Mon Jul 13 19:34:25 2009 (4A5BC481)
fffff880`010e1000 fffff880`0112d000 fltmgr fltmgr.sys Mon Jul 13 19:19:59 2009 (4A5BC11F)
fffff960`00830000 fffff960`00839000 framebuf framebuf.dll unavailable (00000000)
fffff880`013e8000 fffff880`013f2000 Fs_Rec Fs_Rec.sys Mon Jul 13 19:19:45 2009 (4A5BC111)
fffff880`01937000 fffff880`01971000 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)
fffff800`01c10000 fffff800`01c59000 hal hal.dll Mon Jul 13 21:27:36 2009 (4A5BDF08)
fffff880`03375000 fffff880`03399000 HDAudBus HDAudBus.sys Mon Jul 13 20:06:13 2009 (4A5BCBF5)
fffff880`03747000 fffff880`03760000 HIDCLASS HIDCLASS.SYS Mon Jul 13 20:06:21 2009 (4A5BCBFD)
fffff880`03e2c000 fffff880`03e34080 HIDPARSE HIDPARSE.SYS Mon Jul 13 20:06:17 2009 (4A5BCBF9)
fffff880`03739000 fffff880`03747000 hidusb hidusb.sys Mon Jul 13 20:06:22 2009 (4A5BCBFE)
fffff880`0192e000 fffff880`01937000 hwpolicy hwpolicy.sys Mon Jul 13 19:19:22 2009 (4A5BC0FA)
fffff880`0145a000 fffff880`01469000 kbdclass kbdclass.sys Mon Jul 13 19:19:50 2009 (4A5BC116)
fffff880`03760000 fffff880`0376e000 kbdhid kbdhid.sys Mon Jul 13 20:00:20 2009 (4A5BCA94)
fffff800`00bbf000 fffff800`00bc9000 kdcom kdcom.dll Sat Feb 05 07:21:45 2011 (4D4D40D9)
fffff880`0363a000 fffff880`0367d000 ks ks.sys Wed Mar 03 23:32:25 2010 (4B8F37D9)
fffff880`013bd000 fffff880`013d7000 ksecdd ksecdd.sys Mon Jul 13 19:20:54 2009 (4A5BC156)
fffff880`015bd000 fffff880`015e8000 ksecpkg ksecpkg.sys Fri Dec 11 01:03:32 2009 (4B21E0B4)
fffff880`00cf7000 fffff880`00d04000 mcupdate_AuthenticAMD mcupdate_AuthenticAMD.dll Mon Jul 13 21:29:09 2009 (4A5BDF65)
fffff880`011eb000 fffff880`011fa000 mouclass mouclass.sys Mon Jul 13 19:19:50 2009 (4A5BC116)
fffff880`0376e000 fffff880`0377b000 mouhid mouhid.sys Mon Jul 13 20:00:20 2009 (4A5BCA94)
fffff880`00cc0000 fffff880`00cda000 mountmgr mountmgr.sys Mon Jul 13 19:19:54 2009 (4A5BC11A)
fffff880`04582000 fffff880`0459a000 mpsdrv mpsdrv.sys Mon Jul 13 20:08:25 2009 (4A5BCC79)
fffff880`0459a000 fffff880`045c7000 mrxsmb mrxsmb.sys Wed Feb 23 00:15:23 2011 (4D6497EB)
fffff880`04400000 fffff880`0444e000 mrxsmb10 mrxsmb10.sys Wed Feb 23 00:15:14 2011 (4D6497E2)
fffff880`0444e000 fffff880`04471000 mrxsmb20 mrxsmb20.sys Wed Feb 23 00:15:13 2011 (4D6497E1)
fffff880`0186f000 fffff880`0187a000 Msfs Msfs.SYS Mon Jul 13 19:19:47 2009 (4A5BC113)
fffff880`00ff4000 fffff880`00ffe000 msisadrv msisadrv.sys Mon Jul 13 19:19:26 2009 (4A5BC0FE)
fffff880`01141000 fffff880`0119f000 msrpc msrpc.sys Mon Jul 13 19:21:32 2009 (4A5BC17C)
fffff880`02c00000 fffff880`02c0b000 mssmbios mssmbios.sys Mon Jul 13 19:31:10 2009 (4A5BC3BE)
fffff880`0191c000 fffff880`0192e000 mup mup.sys Mon Jul 13 19:23:45 2009 (4A5BC201)
fffff880`0146b000 fffff880`0155d000 ndis ndis.sys Mon Jul 13 19:21:40 2009 (4A5BC184)
fffff880`02c45000 fffff880`02c51000 ndistapi ndistapi.sys Mon Jul 13 20:10:00 2009 (4A5BCCD8)
fffff880`04551000 fffff880`04564000 ndisuio ndisuio.sys Mon Jul 13 20:09:25 2009 (4A5BCCB5)
fffff880`00dcb000 fffff880`00dfa000 ndiswan ndiswan.sys Mon Jul 13 20:10:11 2009 (4A5BCCE3)
fffff880`036e9000 fffff880`036fe000 NDProxy NDProxy.SYS Mon Jul 13 20:10:05 2009 (4A5BCCDD)
fffff880`02d80000 fffff880`02d8f000 netbios netbios.sys Mon Jul 13 20:09:26 2009 (4A5BCCB6)
fffff880`02cf6000 fffff880`02d3b000 netbt netbt.sys Mon Jul 13 19:21:28 2009 (4A5BC178)
fffff880`0155d000 fffff880`015bd000 NETIO NETIO.SYS Thu Apr 08 22:43:59 2010 (4BBE946F)
fffff880`0187a000 fffff880`0188b000 Npfs Npfs.SYS Mon Jul 13 19:19:48 2009 (4A5BC114)
fffff880`02de0000 fffff880`02dec000 nsiproxy nsiproxy.sys Mon Jul 13 19:21:02 2009 (4A5BC15E)
fffff800`01c59000 fffff800`02236000 nt ntkrnlmp.exe Tue Oct 26 22:43:09 2010 (4CC791BD)
fffff880`0121a000 fffff880`013bd000 Ntfs Ntfs.sys Mon Jul 13 19:20:47 2009 (4A5BC14F)
fffff880`01813000 fffff880`0181c000 Null Null.SYS Mon Jul 13 19:19:37 2009 (4A5BC109)
fffff880`03399000 fffff880`033fcd80 nvm62x64 nvm62x64.sys Fri Oct 17 17:01:06 2008 (48F8FD12)
fffff880`00da0000 fffff880`00dcb000 nvstor nvstor.sys Wed May 20 02:45:37 2009 (4A13A711)
fffff880`044fe000 fffff880`04551000 nwifi nwifi.sys Mon Jul 13 20:07:23 2009 (4A5BCC3B)
fffff880`02d44000 fffff880`02d6a000 pacer pacer.sys Mon Jul 13 20:09:41 2009 (4A5BCCC5)
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`00ec6000 fffff880`00ecd000 pciide pciide.sys Mon Jul 13 19:19:49 2009 (4A5BC115)
fffff880`00ecd000 fffff880`00edd000 PCIIDEX PCIIDEX.SYS Mon Jul 13 19:19:48 2009 (4A5BC114)
fffff880`013d7000 fffff880`013e8000 pcw pcw.sys Mon Jul 13 19:19:27 2009 (4A5BC0FF)
fffff880`00d04000 fffff880`00d18000 PSHED PSHED.dll Mon Jul 13 21:32:23 2009 (4A5BE027)
fffff880`02c21000 fffff880`02c45000 rasl2tp rasl2tp.sys Mon Jul 13 20:10:11 2009 (4A5BCCE3)
fffff880`02c51000 fffff880`02c6c000 raspppoe raspppoe.sys Mon Jul 13 20:10:17 2009 (4A5BCCE9)
fffff880`018b6000 fffff880`018d7000 raspptp raspptp.sys Mon Jul 13 20:10:18 2009 (4A5BCCEA)
fffff880`01200000 fffff880`0121a000 rassstp rassstp.sys Mon Jul 13 20:10:25 2009 (4A5BCCF1)
fffff880`02d8f000 fffff880`02de0000 rdbss rdbss.sys Mon Jul 13 19:24:09 2009 (4A5BC219)
fffff880`018d7000 fffff880`018e2000 rdpbus rdpbus.sys Mon Jul 13 20:17:46 2009 (4A5BCEAA)
fffff880`01866000 fffff880`0186f000 rdpencdd rdpencdd.sys Mon Jul 13 20:16:34 2009 (4A5BCE62)
fffff880`018e2000 fffff880`0191c000 rdyboost rdyboost.sys Mon Jul 13 19:34:34 2009 (4A5BC48A)
fffff880`01074000 fffff880`010d6000 storport storport.sys Mon Jul 13 20:01:18 2009 (4A5BCACE)
fffff880`033fd000 fffff880`033fe480 swenum swenum.sys Mon Jul 13 20:00:18 2009 (4A5BCA92)
fffff880`01603000 fffff880`01800000 tcpip tcpip.sys Sun Jun 13 23:39:04 2010 (4C15A458)
fffff880`018a9000 fffff880`018b6000 TDI TDI.SYS Mon Jul 13 19:21:18 2009 (4A5BC16E)
fffff880`0188b000 fffff880`018a9000 tdx tdx.sys Mon Jul 13 19:21:15 2009 (4A5BC16B)
fffff880`015e8000 fffff880`015fc000 termdd termdd.sys Mon Jul 13 20:16:36 2009 (4A5BCE64)
fffff960`00650000 fffff960`0065a000 TSDDD TSDDD.dll unavailable (00000000)
fffff880`032dd000 fffff880`03303000 tunnel tunnel.sys Mon Jul 13 20:09:37 2009 (4A5BCCC1)
fffff880`0367d000 fffff880`0368f000 umbus umbus.sys Mon Jul 13 20:06:56 2009 (4A5BCC20)
fffff880`03e0d000 fffff880`03e2a000 usbccgp usbccgp.sys Mon Jul 13 20:06:45 2009 (4A5BCC15)
fffff880`03e2a000 fffff880`03e2bf00 USBD USBD.SYS Mon Jul 13 20:06:23 2009 (4A5BCBFF)
fffff880`03364000 fffff880`03375000 usbehci usbehci.sys Sat Oct 24 00:27:33 2009 (4AE28235)
fffff880`0368f000 fffff880`036e9000 usbhub usbhub.sys Sat Oct 24 00:28:24 2009 (4AE28268)
fffff880`03303000 fffff880`0330e000 usbohci usbohci.sys Mon Jul 13 20:06:30 2009 (4A5BCC06)
fffff880`0330e000 fffff880`03364000 USBPORT USBPORT.SYS Mon Jul 13 20:06:31 2009 (4A5BCC07)
fffff880`00e33000 fffff880`00e40000 vdrvroot vdrvroot.sys Mon Jul 13 20:01:31 2009 (4A5BCADB)
fffff880`01823000 fffff880`01831000 vga vga.sys Mon Jul 13 19:38:47 2009 (4A5BC587)
fffff880`01831000 fffff880`01856000 VIDEOPRT VIDEOPRT.SYS Mon Jul 13 19:38:51 2009 (4A5BC58B)
fffff880`0144a000 fffff880`0145a000 vmstorfl vmstorfl.sys Mon Jul 13 19:42:54 2009 (4A5BC67E)
fffff880`00e55000 fffff880`00e6a000 volmgr volmgr.sys Mon Jul 13 19:19:57 2009 (4A5BC11D)
fffff880`00e6a000 fffff880`00ec6000 volmgrx volmgrx.sys Mon Jul 13 19:20:33 2009 (4A5BC141)
fffff880`0119f000 fffff880`011eb000 volsnap volsnap.sys Mon Jul 13 19:20:08 2009 (4A5BC128)
fffff880`03e00000 fffff880`03e0d000 vwifibus vwifibus.sys Mon Jul 13 20:07:21 2009 (4A5BCC39)
fffff880`02d6a000 fffff880`02d80000 vwififlt vwififlt.sys Mon Jul 13 20:07:22 2009 (4A5BCC3A)
fffff880`01856000 fffff880`01866000 watchdog watchdog.sys Mon Jul 13 19:37:35 2009 (4A5BC53F)
fffff880`00ee1000 fffff880`00f85000 Wdf01000 Wdf01000.sys Mon Jul 13 19:22:07 2009 (4A5BC19F)
fffff880`00f85000 fffff880`00f94000 WDFLDR WDFLDR.SYS Mon Jul 13 19:19:54 2009 (4A5BC11A)
fffff880`02d3b000 fffff880`02d44000 wfplwf wfplwf.sys Mon Jul 13 20:09:26 2009 (4A5BCCB6)
fffff960`000b0000 fffff960`003c2000 win32k win32k.sys unavailable (00000000)
fffff880`00feb000 fffff880`00ff4000 WMILIB WMILIB.SYS Mon Jul 13 19:19:51 2009 (4A5BC117)
fffff880`037d1000 fffff880`037f2000 WudfPf WudfPf.sys Mon Jul 13 20:05:37 2009 (4A5BCBD1)
Unloaded modules:
fffff880`019b7000 fffff880`019c5000 crashdmp.sys
Timestamp: unavailable (00000000)
Checksum: 00000000
fffff880`019c5000 fffff880`019cf000 dump_storpor
Timestamp: unavailable (00000000)
Checksum: 00000000
fffff880`019cf000 fffff880`019fa000 dump_nvstor.
Timestamp: unavailable (00000000)
Checksum: 00000000
fffff880`01800000 fffff880`01813000 dump_dumpfve
Timestamp: unavailable (00000000)
Checksum: 00000000
fffff880`0145a000 fffff880`01462000 spldr.sys
Timestamp: unavailable (00000000)
Checksum: 00000000 |
| My System Specs |
| 21 Apr 2011 | #6 |
| | Hi Carl, you are absolutely amazing. Thanks for the fast reply! I have them reading through this now and will let you know and get you the files from that tool some time soon. |
| My System Specs |
| 21 Apr 2011 | #7 |
| | Fixed...Maybe Hi I am Matt, daves friend. It is my computer he has been trying to fix and while messing around on it and nVidia's site, I found the drivers you were talking about and installed them and well it hasn't crashed since *touch wood* even when doing tasks that caused it to BSOD before. Should I still update to SP1 and run the other driver tool. Or should I just leave it, create a restore point and see how it goes on? Cheers you guys for all your help! |
| My System Specs |
| 21 Apr 2011 | #8 |
| | Matt, you are very welcome for the help. I suggest you run your computer and see how it does. Outdated drivers can definitely cause conflicts, memory corruption and BSOD's. For now, if your system is stable, just use it. If you get another BSOD, run the tool and upload all of the resulting files which will include the latest dump(s). Then enable Driver Verifier as I mentioned above. I hope simply updating drivers solved your problem. Feel free to post any questions you have. |
| My System Specs |
| 22 Apr 2011 | #9 |
| | Not again!! Yeah it has happened again multiple times, so I set up driver verifier and rebooted then after one crash here are all the dumps from the mini-dumps folder. Please can you help me sort out this problem. I want to be able to use my new sparkly computer! |
| My System Specs |
| 22 Apr 2011 | #10 |
| | Good morning, Matt. I am sorry you are still having problems. Is Driver Verifier still enabled? If not, please turn it back on. I looked at the three dumps I had not previously seen. The latest is a Driver Verifier enabled dump and it blames ntkrnlmp.exe, which is Windows system core file and highly unlikely to be the real cause. Please run the tool following the instructions in this tutorial. I need to take a look at your system: http://www.sevenforums.com/crashes-d...tructions.html. The files from this tool will let me look at your system. For example, I look at your programs that load on startup and I can see what applications are crashing. Generally speaking, when dumps are spitting out random bugcheck codes as your are doing, it indicates a hardware or hardware related problem. Quote: Bugcheck 7E, SYSTEM_THREAD_EXCEPTION_NOT_HANDLED. Driver Verifier enabled. Usual causes: Insufficient disk space, Device driver, Video card, BIOS, Breakpoint with no debugger attached, Hardware incompatibility, Faulty system service, Memory, 3rd party remote control. Bugcheck 24, NTFS File system. Usual causes: Disk corruption, insufficient physical memory, Device driver, Indexing, Resident antivirus, backup, defrag programs, Disk/Drive failing/failure. Bugcheck 50, Usual causes: Defective hardware (particularly memory - but not just RAM), Faulty system service, Antivirus, Device driver, NTFS corruption, BIOS. What antivirus are you running and what firewall are you running? 1. Update your OS by installing Service Pack 1. This is essential. http://windows.microsoft.com/en-US/w...ice-pack-1-sp1. Then install important Windows updates. Let's get your system up to date. 2. See if you can update this driver. I can't say this driver is causing problems. But it is out of date and Win 7 is finicky about networking drivers. Quote: nvmf6264.sys Thu Apr 30 15:45:59 2009 - nVidia nForce network driver. Drivers - Download NVIDIA Drivers. Quote: Run CHKDSK /R /F from an elevated (Run as adminstrator) Command Prompt. Please do this for each hard drive on your system. When it tells you it can't do it right now - and asks you if you'd like to do it at the next reboot - answer Y (for Yes) and press Enter. Then reboot and let the test run. It may take a while for it to run, but keep an occasional eye on it to see if it generates any errors. See "CHKDSK LogFile" below in order to check the results of the test. Elevated Command Prompt: Go to Start and type in "cmd.exe" (without the quotes) At the top of the Search Box, right click on Cmd.exe and select "Run as administrator" CHKDSK LogFile: Go to Start and type in "eventvwr.msc" (without the quotes) and press Enter Expand the Windows logs heading, then select the Application log file entry. Double click on the Source column header. Scroll down the list until you find the Chkdsk entry (wininit for Windows 7). 4. Next, run a bootable hard drive diagnostic program. Read the details at this link. This will tell you whether or not you have a a hard drive problem. HD Diagnostic 5. Run Driver Verifier for 24 hours of computer operating time. Depending on the results, we will go from there. I know this is frustrating for you. But when the dumps do not give us a specific cause, we have to troubleshoot by the process of elimination. It appears that you have a conflict somewhere or a hardware problem. I hope the files the the JC Griff tool generates will help narrow down the search. Code: Windows 7 Kernel Version 7600 MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7600.16695.amd64fre.win7_gdr.101026-1503
Machine Name:
Kernel base = 0xfffff800`02a05000 PsLoadedModuleList = 0xfffff800`02c42e50
Debug session time: Fri Apr 22 04:05:55.341 2011 (GMT-4)
System Uptime: 0 days 0:02:17.060
Loading Kernel Symbols
...............................................................
................................................................
......................
Loading User Symbols
Loading unloaded module list
....
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 50, {fffffa8044f50794, 0, fffff88004001bd3, 5}
Unable to load image \SystemRoot\system32\DRIVERS\usbhub.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for usbhub.sys
*** ERROR: Module load completed but symbols could not be loaded for usbhub.sys
Could not read faulting driver name
Probably caused by : USBPORT.SYS ( USBPORT!MPf_GetEndpointStatus+47 )
Followup: MachineOwner
---------
3: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
PAGE_FAULT_IN_NONPAGED_AREA (50)
Invalid system memory was referenced. This cannot be protected by try-except,
it must be protected by a Probe. Typically the address is just plain bad or it
is pointing at freed memory.
Arguments:
Arg1: fffffa8044f50794, memory referenced.
Arg2: 0000000000000000, value 0 = read operation, 1 = write operation.
Arg3: fffff88004001bd3, If non-zero, the instruction address which referenced the bad memory
address.
Arg4: 0000000000000005, (reserved)
Debugging Details:
------------------
Could not read faulting driver name
READ_ADDRESS: GetPointerFromAddress: unable to read from fffff80002cad0e0
fffffa8044f50794
FAULTING_IP:
USBPORT!MPf_GetEndpointStatus+47
fffff880`04001bd3 f686f405000040 test byte ptr [rsi+5F4h],40h
MM_INTERNAL_CODE: 5
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
BUGCHECK_STR: 0x50
PROCESS_NAME: System
CURRENT_IRQL: 0
TRAP_FRAME: fffff88003cd0340 -- (.trap 0xfffff88003cd0340)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=fffffa8004f53010 rbx=0000000000000000 rcx=fffffa8005ac6a10
rdx=0000000050456368 rsi=0000000000000000 rdi=0000000000000000
rip=fffff88004001bd3 rsp=fffff88003cd04d0 rbp=fffffa8005ac6a10
r8=0000000050456368 r9=fffffa80056dc410 r10=fffff88002fd3b80
r11=0000000000000000 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0 nv up ei ng nz na pe nc
USBPORT!MPf_GetEndpointStatus+0x47:
fffff880`04001bd3 f686f405000040 test byte ptr [rsi+5F4h],40h ds:01a0:00000000`000005f4=??
Resetting default scope
LAST_CONTROL_TRANSFER: from fffff80002af48c1 to fffff80002a75740
STACK_TEXT:
fffff880`03cd01d8 fffff800`02af48c1 : 00000000`00000050 fffffa80`44f50794 00000000`00000000 fffff880`03cd0340 : nt!KeBugCheckEx
fffff880`03cd01e0 fffff800`02a7382e : 00000000`00000000 fffffa80`03883800 00000000`00000000 00000000`ffffffff : nt! ?? ::FNODOBFM::`string'+0x40e8b
fffff880`03cd0340 fffff880`04001bd3 : 00000000`00000000 fffff880`0400715a 00000000`00000000 fffffa80`04f50050 : nt!KiPageFault+0x16e
fffff880`03cd04d0 fffff880`04012693 : fffffa80`03883800 fffffa80`05ac6a10 fffffa80`04f50050 fffffa80`05af1c40 : USBPORT!MPf_GetEndpointStatus+0x47
fffff880`03cd0500 fffff880`040227da : fffffa80`04f50050 fffffa80`05af1c40 fffffa80`04f50050 fffffa80`056dc410 : USBPORT!USBPORT_Core_QueueTransferUrb+0xd7
fffff880`03cd0540 fffff880`040223c4 : fffffa80`056dc410 fffffa80`05af1ce0 fffffa80`05af1c40 fffffa80`04f50050 : USBPORT!USBPORT_BulkOrInterruptTransfer+0xca
fffff880`03cd05c0 fffff880`0402ad44 : fffffa80`05af1ce0 fffffa80`05150009 fffffa80`05af1ce0 fffffa80`05af1c40 : USBPORT!USBPORT_ProcessURB+0xb44
fffff880`03cd0670 fffff880`04004ad4 : 00000000`00000000 fffffa80`05150050 fffffa80`0480c190 fffffa80`05af1ce0 : USBPORT!USBPORT_PdoInternalDeviceControlIrp+0x138
fffff880`03cd06b0 fffff880`04a6d566 : fffffa80`05163050 fffffa80`05796060 fffffa80`05af1ce0 fffffa80`051631a0 : USBPORT!USBPORT_Dispatch+0x1dc
fffff880`03cd06f0 fffffa80`05163050 : fffffa80`05796060 fffffa80`05af1ce0 fffffa80`051631a0 fffffa80`05af1ce0 : usbhub+0x3566
fffff880`03cd06f8 fffffa80`05796060 : fffffa80`05af1ce0 fffffa80`051631a0 fffffa80`05af1ce0 fffff880`04a9dcab : 0xfffffa80`05163050
fffff880`03cd0700 fffffa80`05af1ce0 : fffffa80`051631a0 fffffa80`05af1ce0 fffff880`04a9dcab 00000000`00000000 : 0xfffffa80`05796060
fffff880`03cd0708 fffffa80`051631a0 : fffffa80`05af1ce0 fffff880`04a9dcab 00000000`00000000 00000000`00000000 : 0xfffffa80`05af1ce0
fffff880`03cd0710 fffffa80`05af1ce0 : fffff880`04a9dcab 00000000`00000000 00000000`00000000 fffffa80`05796060 : 0xfffffa80`051631a0
fffff880`03cd0718 fffff880`04a9dcab : 00000000`00000000 00000000`00000000 fffffa80`05796060 fffffa80`05ae4e30 : 0xfffffa80`05af1ce0
fffff880`03cd0720 00000000`00000000 : 00000000`00000000 fffffa80`05796060 fffffa80`05ae4e30 00000000`00000000 : usbhub+0x33cab
STACK_COMMAND: kb
FOLLOWUP_IP:
USBPORT!MPf_GetEndpointStatus+47
fffff880`04001bd3 f686f405000040 test byte ptr [rsi+5F4h],40h
SYMBOL_STACK_INDEX: 3
SYMBOL_NAME: USBPORT!MPf_GetEndpointStatus+47
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: USBPORT
IMAGE_NAME: USBPORT.SYS
DEBUG_FLR_IMAGE_TIMESTAMP: 4a5bcc07
FAILURE_BUCKET_ID: X64_0x50_USBPORT!MPf_GetEndpointStatus+47
BUCKET_ID: X64_0x50_USBPORT!MPf_GetEndpointStatus+47
Followup: MachineOwner
---------
Debug session time: Fri Apr 22 04:11:11.193 2011 (GMT-4)
System Uptime: 0 days 0:04:17.896
Loading Kernel Symbols
...............................................................
................................................................
........................
Loading User Symbols
Loading unloaded module list
....
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 24, {1904fb, fffff880074da150, fffff880074da1f0, fffff80002af8034}
Probably caused by : Ntfs.sys ( Ntfs!NtfsReadUsnJournal+aad )
Followup: MachineOwner
---------
2: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
NTFS_FILE_SYSTEM (24)
If you see NtfsExceptionFilter on the stack then the 2nd and 3rd
parameters are the exception record and context record. Do a .cxr
on the 3rd parameter and then kb to obtain a more informative stack
trace.
Arguments:
Arg1: 00000000001904fb
Arg2: fffff880074da150
Arg3: fffff880074da1f0
Arg4: fffff80002af8034
Debugging Details:
------------------
EXCEPTION_RECORD: fffff880074da150 -- (.exr 0xfffff880074da150)
ExceptionAddress: fffff80002af8034 (nt!RtlRaiseStatus+0x0000000000000018)
ExceptionCode: c0000005 (Access violation)
ExceptionFlags: 00000001
NumberParameters: 0
CONTEXT: fffff880074da1f0 -- (.cxr 0xfffff880074da1f0)
rax=00000000ffffff00 rbx=00000000c0000005 rcx=fffff880074da1f0
rdx=0000000000060001 rsi=00000000c0000005 rdi=0000000000000000
rip=fffff80002af8034 rsp=fffff880074da130 rbp=fffff880074da960
r8=0000000000000000 r9=0000000000000005 r10=0000000000000000
r11=fffff880074d9138 r12=0000000000000000 r13=fffffa800675e8f0
r14=0000000000000798 r15=fffffa8004291ce0
iopl=0 nv up ei ng nz na po nc
cs=0010 ss=0018 ds=002b es=002b fs=0053 gs=002b efl=00000286
nt!RtlRaiseStatus+0x18:
fffff800`02af8034 488b8424b8010000 mov rax,qword ptr [rsp+1B8h] ss:0018:fffff880`074da2e8=fffff80002af8034
Resetting default scope
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
PROCESS_NAME: SearchIndexer.
CURRENT_IRQL: 0
ERROR_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.
EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.
WRITE_ADDRESS: GetPointerFromAddress: unable to read from fffff80002d010e0
fffff880074da1e0
FOLLOWUP_IP:
Ntfs!NtfsReadUsnJournal+aad
fffff880`012d086e 90 nop
FAULTING_IP:
nt!RtlRaiseStatus+18
fffff800`02af8034 488b8424b8010000 mov rax,qword ptr [rsp+1B8h]
BUGCHECK_STR: 0x24
LAST_CONTROL_TRANSFER: from fffff880012d086e to fffff80002af8034
STACK_TEXT:
fffff880`074da130 fffff880`012d086e : 00000000`00000060 fffff8a0`001f2c70 00000000`00000000 00000000`0000000e : nt!RtlRaiseStatus+0x18
fffff880`074da6d0 fffff880`012c8576 : fffffa80`0675e8f0 fffffa80`04291940 fffffa80`04649800 fffff880`074da801 : Ntfs!NtfsReadUsnJournal+0xaad
fffff880`074da840 fffff880`012c42ed : fffffa80`0675e8f0 00000000`00000000 fffff880`074da960 00000000`00000000 : Ntfs!NtfsUserFsRequest+0x122
fffff880`074da880 fffff880`0116e23f : fffff880`074da9d0 fffffa80`04291940 fffff880`074da900 fffffa80`0675e8f0 : Ntfs!NtfsFsdFileSystemControl+0x13d
fffff880`074da920 fffff880`0118d91e : fffffa80`046498e0 fffffa80`06ab86f0 fffffa80`04649800 fffffa80`04291940 : fltmgr!FltpLegacyProcessingAfterPreCallbacksCompleted+0x24f
fffff880`074da9b0 fffff800`02de2547 : fffffa80`06ab86f0 fffff880`074daca0 fffffa80`04291d28 fffffa80`04291940 : fltmgr!FltpFsControl+0xee
fffff880`074daa10 fffff800`02dab80a : fffffa80`06d18b30 00000000`0000087c 00000000`00000000 00000000`0118f880 : nt!IopXxxControlFile+0x607
fffff880`074dab40 fffff800`02ac8993 : fffffa80`06d18b30 00000000`00000001 fffffa80`06d585f0 fffff800`02ddd254 : nt!NtFsControlFile+0x56
fffff880`074dabb0 00000000`779efa4a : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
00000000`047be958 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x779efa4a
SYMBOL_STACK_INDEX: 1
SYMBOL_NAME: Ntfs!NtfsReadUsnJournal+aad
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: Ntfs
IMAGE_NAME: Ntfs.sys
DEBUG_FLR_IMAGE_TIMESTAMP: 4a5bc14f
STACK_COMMAND: .cxr 0xfffff880074da1f0 ; kb
FAILURE_BUCKET_ID: X64_0x24_INVALID_STACK_ACCESS_Ntfs!NtfsReadUsnJournal+aad
BUCKET_ID: X64_0x24_INVALID_STACK_ACCESS_Ntfs!NtfsReadUsnJournal+aad
Followup: MachineOwner
---------
Debug session time: Fri Apr 22 04:23:53.067 2011 (GMT-4)
System Uptime: 0 days 0:08:28.801
Loading Kernel Symbols
...............................................................
................................................................
........................
Loading User Symbols
Loading unloaded module list
.....
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 1000007E, {ffffffffc0000005, fffff80002e14c09, fffff880076c87d8, fffff880076c8040}
Probably caused by : ntkrnlmp.exe ( nt!PfTEntryInfoLookup+29 )
Followup: MachineOwner
---------
0: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M (1000007e)
This is a very common bugcheck. Usually the exception address pinpoints
the driver/function that caused the problem. Always note this address
as well as the link date of the driver/image that contains this address.
Some common problems are exception code 0x80000003. This means a hard
coded breakpoint or assertion was hit, but this system was booted
/NODEBUG. This is not supposed to happen as developers should never have
hardcoded breakpoints in retail code, but ...
If this happens, make sure a debugger gets connected, and the
system is booted /DEBUG. This will let us see why this breakpoint is
happening.
Arguments:
Arg1: ffffffffc0000005, The exception code that was not handled
Arg2: fffff80002e14c09, The address that the exception occurred at
Arg3: fffff880076c87d8, Exception Record Address
Arg4: fffff880076c8040, Context Record Address
Debugging Details:
------------------
EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.
FAULTING_IP:
nt!PfTEntryInfoLookup+29
fffff800`02e14c09 428b449110 mov eax,dword ptr [rcx+r10*4+10h]
EXCEPTION_RECORD: fffff880076c87d8 -- (.exr 0xfffff880076c87d8)
ExceptionAddress: fffff80002e14c09 (nt!PfTEntryInfoLookup+0x0000000000000029)
ExceptionCode: c0000005 (Access violation)
ExceptionFlags: 00000000
NumberParameters: 2
Parameter[0]: 0000000000000000
Parameter[1]: ffffffffffffffff
Attempt to read from address ffffffffffffffff
CONTEXT: fffff880076c8040 -- (.cxr 0xfffff880076c8040)
rax=fffff880076c8a18 rbx=3100310042002d28 rcx=3100310042002d00
rdx=fffff8a0072c2c70 rsi=fffff80002c1b540 rdi=fffff880076c8a70
rip=fffff80002e14c09 rsp=fffff880076c8a10 rbp=fffff880076c8ae8
r8=fffff880076c8a70 r9=fffff880076c8ae8 r10=0000000000000000
r11=3100310042002d00 r12=fffff880076c8a90 r13=000000000000ffff
r14=000000000000ffff r15=000000000000ffff
iopl=0 nv up ei pl nz na po nc
cs=0010 ss=0018 ds=002b es=002b fs=0053 gs=002b efl=00010206
nt!PfTEntryInfoLookup+0x29:
fffff800`02e14c09 428b449110 mov eax,dword ptr [rcx+r10*4+10h] ds:002b:31003100`42002d10=????????
Resetting default scope
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: VERIFIER_ENABLED_VISTA_MINIDUMP
PROCESS_NAME: System
CURRENT_IRQL: 0
ERROR_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.
EXCEPTION_PARAMETER1: 0000000000000000
EXCEPTION_PARAMETER2: ffffffffffffffff
READ_ADDRESS: GetPointerFromAddress: unable to read from fffff80002cc50e0
ffffffffffffffff
FOLLOWUP_IP:
nt!PfTEntryInfoLookup+29
fffff800`02e14c09 428b449110 mov eax,dword ptr [rcx+r10*4+10h]
BUGCHECK_STR: 0x7E
LAST_CONTROL_TRANSFER: from fffff80002e1b447 to fffff80002e14c09
STACK_TEXT:
fffff880`076c8a10 fffff800`02e1b447 : 31003100`42002d00 fffff8a0`072c2c70 fffff880`076c8ae8 fffff800`02c1b540 : nt!PfTEntryInfoLookup+0x29
fffff880`076c8a20 fffff800`02e1b5ae : fffff800`02c1b660 fffff8a0`072c2c70 00000000`00000000 fffffa80`05f9a701 : nt!PfTAcquireEntryInfo+0x37
fffff880`076c8a70 fffff800`02ede700 : fffffa80`069ed770 fffff800`02b69601 fffff880`076c8b10 00000000`00000000 : nt!PfpLogPageAccess+0x6e
fffff880`076c8ae0 fffff800`02edeb71 : 00000000`001cb001 fffffa80`069ed770 fffffa80`069ebfd0 fffffa80`069ebfa0 : nt!PfpCopyEvent+0xe0
fffff880`076c8b30 fffff800`02edee06 : 00000000`00000000 00000000`00000080 00000000`00000000 fffffa80`00000000 : nt!PfpFlushEventBuffers+0x61
fffff880`076c8b70 fffff800`02f00620 : fffffa80`05f9a701 00000000`00000080 fffffa80`036e5040 fffff800`02c1b568 : nt!PfpFlushBuffers+0x46
fffff880`076c8c10 fffff800`02d307c6 : ffffffff`ff676980 fffffa80`05f9a750 fffff880`076c8db0 fffffa80`05f9a750 : nt!PfTLoggingWorker+0xe0
fffff880`076c8d40 fffff800`02a6bc26 : fffff880`02fd5180 fffffa80`05f9a750 fffff880`02fdffc0 fffff880`0124c534 : nt!PspSystemThreadStartup+0x5a
fffff880`076c8d80 00000000`00000000 : fffff880`076c9000 fffff880`076c3000 fffff880`076c7310 00000000`00000000 : nt!KxStartSystemThread+0x16
SYMBOL_STACK_INDEX: 0
SYMBOL_NAME: nt!PfTEntryInfoLookup+29
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: nt
IMAGE_NAME: ntkrnlmp.exe
DEBUG_FLR_IMAGE_TIMESTAMP: 4cc791bd
STACK_COMMAND: .cxr 0xfffff880076c8040 ; kb
FAILURE_BUCKET_ID: X64_0x7E_VRF_nt!PfTEntryInfoLookup+29
BUCKET_ID: X64_0x7E_VRF_nt!PfTEntryInfoLookup+29
Followup: MachineOwner
---------
0: kd> lmtsmn
start end module name
fffff880`00ea2000 fffff880`00ef9000 ACPI ACPI.sys Mon Jul 13 19:19:34 2009 (4A5BC106)
fffff880`0408a000 fffff880`04114000 afd afd.sys Mon Jul 13 19:21:40 2009 (4A5BC184)
fffff880`0618e000 fffff880`061a4000 AgileVpn AgileVpn.sys Mon Jul 13 20:10:24 2009 (4A5BCCF0)
fffff880`043c8000 fffff880`043dd000 amdppm amdppm.sys Mon Jul 13 19:19:25 2009 (4A5BC0FD)
fffff880`0108b000 fffff880`01096000 amdxata amdxata.sys Tue May 19 13:56:59 2009 (4A12F2EB)
fffff880`0439b000 fffff880`043a2000 AsrAppCharger AsrAppCharger.sys Fri Jun 11 02:37:12 2010 (4C11D998)
fffff880`06930000 fffff880`0693b000 asyncmac asyncmac.sys Mon Jul 13 20:10:13 2009 (4A5BCCE5)
fffff880`00e1a000 fffff880`00e23000 atapi atapi.sys Mon Jul 13 19:19:47 2009 (4A5BC113)
fffff880`00e23000 fffff880`00e4d000 ataport ataport.SYS Mon Jul 13 19:19:52 2009 (4A5BC118)
fffff880`02431000 fffff880`025f9000 athurx athurx.sys Mon Jan 04 22:23:16 2010 (4B42B0A4)
fffff880`0188f000 fffff880`01896000 Beep Beep.SYS Mon Jul 13 20:00:13 2009 (4A5BCA8D)
fffff880`0438a000 fffff880`0439b000 blbdrive blbdrive.sys Mon Jul 13 19:35:59 2009 (4A5BC4DF)
fffff880`03b9b000 fffff880`03bb9000 bowser bowser.sys Wed Feb 23 00:15:06 2011 (4D6497DA)
fffff960`00600000 fffff960`00627000 cdd cdd.dll unavailable (00000000)
fffff880`015c0000 fffff880`015ea000 cdrom cdrom.sys Mon Jul 13 19:19:54 2009 (4A5BC11A)
fffff880`00c97000 fffff880`00d57000 CI CI.dll Mon Jul 13 21:32:13 2009 (4A5BE01D)
fffff880`01800000 fffff880`01830000 CLASSPNP CLASSPNP.SYS Mon Jul 13 19:19:58 2009 (4A5BC11E)
fffff880`00c39000 fffff880`00c97000 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`0617e000 fffff880`0618e000 CompositeBus CompositeBus.sys Mon Jul 13 20:00:33 2009 (4A5BCAA1)
fffff880`04ae0000 fffff880`04aee000 crashdmp crashdmp.sys Mon Jul 13 20:01:01 2009 (4A5BCABD)
fffff880`042e9000 fffff880`0436c000 csc csc.sys Mon Jul 13 19:24:26 2009 (4A5BC22A)
fffff880`0240d000 fffff880`0241f000 dc3d dc3d.sys Fri Apr 08 18:58:20 2011 (4D9F930C)
fffff880`0436c000 fffff880`0438a000 dfsc dfsc.sys Mon Jul 13 19:23:44 2009 (4A5BC200)
fffff880`04068000 fffff880`04077000 discache discache.sys Mon Jul 13 19:37:18 2009 (4A5BC52E)
fffff880`019d8000 fffff880`019ee000 disk disk.sys Mon Jul 13 19:19:57 2009 (4A5BC11D)
fffff880`04abe000 fffff880`04ae0000 drmk drmk.sys Mon Jul 13 21:01:25 2009 (4A5BD8E5)
fffff880`04e00000 fffff880`04e0a000 dump_diskdump dump_diskdump.sys Mon Jul 12 23:32:05 2010 (4C3BDE35)
fffff880`04b19000 fffff880`04b2c000 dump_dumpfve dump_dumpfve.sys Mon Jul 13 19:21:51 2009 (4A5BC18F)
fffff880`04aee000 fffff880`04b19000 dump_nvstor dump_nvstor.sys Wed May 20 02:45:37 2009 (4A13A711)
fffff880`04fec000 fffff880`04ff8000 Dxapi Dxapi.sys Mon Jul 13 19:38:28 2009 (4A5BC574)
fffff880`04453000 fffff880`04547000 dxgkrnl dxgkrnl.sys Tue Jan 25 23:22:56 2011 (4D3FA1A0)
fffff880`06138000 fffff880`0617e000 dxgmms1 dxgmms1.sys Tue Jan 25 23:22:12 2011 (4D3FA174)
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`01211000 fffff880`0121b000 Fs_Rec Fs_Rec.sys Mon Jul 13 19:19:45 2009 (4A5BC111)
fffff880`0199e000 fffff880`019d8000 fvevol fvevol.sys Fri Sep 25 22:34:26 2009 (4ABD7DB2)
fffff880`0189b000 fffff880`018e5000 fwpkclnt fwpkclnt.sys Mon Jul 13 19:21:08 2009 (4A5BC164)
fffff800`02ffa000 fffff800`03043000 hal hal.dll Mon Jul 13 21:27:36 2009 (4A5BDF08)
fffff880`0427e000 fffff880`042a2000 HDAudBus HDAudBus.sys Mon Jul 13 20:06:13 2009 (4A5BCBF5)
fffff880`04b57000 fffff880`04b70000 HIDCLASS HIDCLASS.SYS Mon Jul 13 20:06:21 2009 (4A5BCBFD)
fffff880`04b70000 fffff880`04b78080 HIDPARSE HIDPARSE.SYS Mon Jul 13 20:06:17 2009 (4A5BCBF9)
fffff880`04b49000 fffff880`04b57000 hidusb hidusb.sys Mon Jul 13 20:06:22 2009 (4A5BCBFE)
fffff880`03ad3000 fffff880`03b9b000 HTTP HTTP.sys Mon Jul 13 19:22:16 2009 (4A5BC1A8)
fffff880`01995000 fffff880`0199e000 hwpolicy hwpolicy.sys Mon Jul 13 19:19:22 2009 (4A5BC0FA)
fffff880`04547000 fffff880`04556000 kbdclass kbdclass.sys Mon Jul 13 19:19:50 2009 (4A5BC116)
fffff880`04b79000 fffff880`04b87000 kbdhid kbdhid.sys Mon Jul 13 20:00:20 2009 (4A5BCA94)
fffff800`00bb2000 fffff800`00bbc000 kdcom kdcom.dll Sat Feb 05 07:21:45 2011 (4D4D40D9)
fffff880`04565000 fffff880`045a8000 ks ks.sys Wed Mar 03 23:32:25 2010 (4B8F37D9)
fffff880`013e1000 fffff880`013fb000 ksecdd ksecdd.sys Mon Jul 13 19:20:54 2009 (4A5BC156)
fffff880`01595000 fffff880`015c0000 ksecpkg ksecpkg.sys Fri Dec 11 01:03:32 2009 (4B21E0B4)
fffff880`04fe6000 fffff880`04feb200 ksthunk ksthunk.sys Mon Jul 13 20:00:19 2009 (4A5BCA93)
fffff880`04bd8000 fffff880`04bed000 lltdio lltdio.sys Mon Jul 13 20:08:50 2009 (4A5BCC92)
fffff880`04b94000 fffff880`04bb7000 luafv luafv.sys Mon Jul 13 19:26:13 2009 (4A5BC295)
fffff880`00c18000 fffff880`00c25000 mcupdate_AuthenticAMD mcupdate_AuthenticAMD.dll Mon Jul 13 21:29:09 2009 (4A5BDF65)
fffff880`0241f000 fffff880`0242d000 monitor monitor.sys Mon Jul 13 19:38:52 2009 (4A5BC58C)
fffff880`04556000 fffff880`04565000 mouclass mouclass.sys Mon Jul 13 19:19:50 2009 (4A5BC116)
fffff880`04b87000 fffff880`04b94000 mouhid mouhid.sys Mon Jul 13 20:00:20 2009 (4A5BCA94)
fffff880`00e00000 fffff880`00e1a000 mountmgr mountmgr.sys Mon Jul 13 19:19:54 2009 (4A5BC11A)
fffff880`01400000 fffff880`01431000 MpFilter MpFilter.sys Tue Sep 14 20:19:28 2010 (4C901110)
fffff880`0689a000 fffff880`068aa000 MpNWMon MpNWMon.sys Tue Sep 14 20:19:30 2010 (4C901112)
fffff880`03bb9000 fffff880`03bd1000 mpsdrv mpsdrv.sys Mon Jul 13 20:08:25 2009 (4A5BCC79)
fffff880`03bd1000 fffff880`03bfe000 mrxsmb mrxsmb.sys Wed Feb 23 00:15:23 2011 (4D6497EB)
fffff880`03a00000 fffff880`03a4e000 mrxsmb10 mrxsmb10.sys Wed Feb 23 00:15:14 2011 (4D6497E2)
fffff880`03a4e000 fffff880`03a71000 mrxsmb20 mrxsmb20.sys Wed Feb 23 00:15:13 2011 (4D6497E1)
fffff880`01224000 fffff880`0122f000 Msfs Msfs.SYS Mon Jul 13 19:19:47 2009 (4A5BC113)
fffff880`00f02000 fffff880`00f0c000 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`0405d000 fffff880`04068000 mssmbios mssmbios.sys Mon Jul 13 19:31:10 2009 (4A5BC3BE)
fffff880`01983000 fffff880`01995000 mup mup.sys Mon Jul 13 19:23:45 2009 (4A5BC201)
fffff880`01443000 fffff880`01535000 ndis ndis.sys Mon Jul 13 19:21:40 2009 (4A5BC184)
fffff880`061c8000 fffff880`061d4000 ndistapi ndistapi.sys Mon Jul 13 20:10:00 2009 (4A5BCCD8)
fffff880`04bed000 fffff880`04c00000 ndisuio ndisuio.sys Mon Jul 13 20:09:25 2009 (4A5BCCB5)
fffff880`05600000 fffff880`0562f000 ndiswan ndiswan.sys Mon Jul 13 20:10:11 2009 (4A5BCCE3)
fffff880`04aa9000 fffff880`04abe000 NDProxy NDProxy.SYS Mon Jul 13 20:10:05 2009 (4A5BCCDD)
fffff880`0419e000 fffff880`041ad000 netbios netbios.sys Mon Jul 13 20:09:26 2009 (4A5BCCB6)
fffff880`04114000 fffff880`04159000 netbt netbt.sys Mon Jul 13 19:21:28 2009 (4A5BC178)
fffff880`01535000 fffff880`01595000 NETIO NETIO.SYS Thu Apr 08 22:43:59 2010 (4BBE946F)
fffff880`068aa000 fffff880`068bf000 NisDrvWFP NisDrvWFP.sys Tue Sep 14 20:20:25 2010 (4C901149)
fffff880`011ec000 fffff880`011fd000 Npfs Npfs.SYS Mon Jul 13 19:19:48 2009 (4A5BC114)
fffff880`04051000 fffff880`0405d000 nsiproxy nsiproxy.sys Mon Jul 13 19:21:02 2009 (4A5BC15E)
fffff800`02a1d000 fffff800`02ffa000 nt ntkrnlmp.exe Tue Oct 26 22:43:09 2010 (4CC791BD)
fffff880`0123e000 fffff880`013e1000 Ntfs Ntfs.sys Mon Jul 13 19:20:47 2009 (4A5BC14F)
fffff880`01886000 fffff880`0188f000 Null Null.SYS Mon Jul 13 19:19:37 2009 (4A5BC109)
fffff880`06136000 fffff880`06137180 nvBridge nvBridge.kmd Tue Jul 14 15:26:48 2009 (4A5CDBF8)
fffff880`0566a000 fffff880`06135f00 nvlddmkm nvlddmkm.sys Tue Jul 14 15:50:52 2009 (4A5CE19C)
fffff880`04401000 fffff880`04452380 nvmf6264 nvmf6264.sys Thu Apr 30 15:45:59 2009 (49F9FFF7)
fffff880`00e4d000 fffff880`00e78000 nvstor nvstor.sys Wed May 20 02:45:37 2009 (4A13A711)
fffff880`01830000 fffff880`01883000 nwifi nwifi.sys Mon Jul 13 20:07:23 2009 (4A5BCC3B)
fffff880`04162000 fffff880`04188000 pacer pacer.sys Mon Jul 13 20:09:41 2009 (4A5BCCC5)
fffff880`043dd000 fffff880`043fa000 parport parport.sys Mon Jul 13 20:00:40 2009 (4A5BCAA8)
fffff880`00f4c000 fffff880`00f61000 partmgr partmgr.sys Mon Jul 13 19:19:58 2009 (4A5BC11E)
fffff880`00f0c000 fffff880`00f3f000 pci pci.sys Mon Jul 13 19:19:51 2009 (4A5BC117)
fffff880`00fd2000 fffff880`00fd9000 pciide pciide.sys Mon Jul 13 19:19:49 2009 (4A5BC115)
fffff880`00fd9000 fffff880`00fe9000 PCIIDEX PCIIDEX.SYS Mon Jul 13 19:19:48 2009 (4A5BC114)
fffff880`01200000 fffff880`01211000 pcw pcw.sys Mon Jul 13 19:19:27 2009 (4A5BC0FF)
fffff880`0625d000 fffff880`06303000 peauth peauth.sys Mon Jul 13 21:01:19 2009 (4A5BD8DF)
fffff880`04fa9000 fffff880`04fe6000 portcls portcls.sys Mon Jul 13 20:06:27 2009 (4A5BCC03)
fffff880`00c25000 fffff880`00c39000 PSHED PSHED.dll Mon Jul 13 21:32:23 2009 (4A5BE027)
fffff880`061a4000 fffff880`061c8000 rasl2tp rasl2tp.sys Mon Jul 13 20:10:11 2009 (4A5BCCE3)
fffff880`0562f000 fffff880`0564a000 raspppoe raspppoe.sys Mon Jul 13 20:10:17 2009 (4A5BCCE9)
fffff880`061d4000 fffff880`061f5000 raspptp raspptp.sys Mon Jul 13 20:10:18 2009 (4A5BCCEA)
fffff880`0564a000 fffff880`05664000 rassstp rassstp.sys Mon Jul 13 20:10:25 2009 (4A5BCCF1)
fffff880`04000000 fffff880`04051000 rdbss rdbss.sys Mon Jul 13 19:24:09 2009 (4A5BC219)
fffff880`061f5000 fffff880`06200000 rdpbus rdpbus.sys Mon Jul 13 20:17:46 2009 (4A5BCEAA)
fffff880`015ea000 fffff880`015f3000 RDPCDD RDPCDD.sys Mon Jul 13 20:16:34 2009 (4A5BCE62)
fffff880`015f3000 fffff880`015fc000 rdpencdd rdpencdd.sys Mon Jul 13 20:16:34 2009 (4A5BCE62)
fffff880`0121b000 fffff880`01224000 rdprefmp rdprefmp.sys Mon Jul 13 20:16:35 2009 (4A5BCE63)
fffff880`01949000 fffff880`01983000 rdyboost rdyboost.sys Mon Jul 13 19:34:34 2009 (4A5BC48A)
fffff880`04a00000 fffff880`04a18000 rspndr rspndr.sys Mon Jul 13 20:08:50 2009 (4A5BCC92)
fffff880`06303000 fffff880`0630e000 secdrv secdrv.SYS Wed Sep 13 09:18:38 2006 (4508052E)
fffff880`04200000 fffff880`0420c000 serenum serenum.sys Mon Jul 13 20:00:33 2009 (4A5BCAA1)
fffff880`041ad000 fffff880`041ca000 serial serial.sys Mon Jul 13 20:00:40 2009 (4A5BCAA8)
fffff880`01941000 fffff880`01949000 spldr spldr.sys Mon May 11 12:56:27 2009 (4A0858BB)
fffff880`06805000 fffff880`0689a000 srv srv.sys Wed Feb 23 00:16:24 2011 (4D649828)
fffff880`0634d000 fffff880`063b4000 srv2 srv2.sys Wed Feb 23 00:15:59 2011 (4D64980F)
fffff880`0630e000 fffff880`0633b000 srvnet srvnet.sys Wed Feb 23 00:15:49 2011 (4D649805)
fffff880`01029000 fffff880`0108b000 storport storport.sys Mon Jul 13 20:01:18 2009 (4A5BCACE)
fffff880`05664000 fffff880`05665480 swenum swenum.sys Mon Jul 13 20:00:18 2009 (4A5BCA92)
fffff880`01602000 fffff880`017ff000 tcpip tcpip.sys Sun Jun 13 23:39:04 2010 (4C15A458)
fffff880`0633b000 fffff880`0634d000 tcpipreg tcpipreg.sys Mon Jul 13 20:09:49 2009 (4A5BCCCD)
fffff880`0122f000 fffff880`0123c000 TDI TDI.SYS Mon Jul 13 19:21:18 2009 (4A5BC16E)
fffff880`01000000 fffff880`0101e000 tdx tdx.sys Mon Jul 13 19:21:15 2009 (4A5BC16B)
fffff880`041e5000 fffff880`041f9000 termdd termdd.sys Mon Jul 13 20:16:36 2009 (4A5BCE64)
fffff960`00460000 fffff960`0046a000 TSDDD TSDDD.dll unavailable (00000000)
fffff880`043a2000 fffff880`043c8000 tunnel tunnel.sys Mon Jul 13 20:09:37 2009 (4A5BCCC1)
fffff880`0693b000 fffff880`0698f000 udfs udfs.sys Mon Jul 13 19:23:37 2009 (4A5BC1F9)
fffff880`045a8000 fffff880`045ba000 umbus umbus.sys Mon Jul 13 20:06:56 2009 (4A5BCC20)
fffff880`04b2c000 fffff880`04b49000 usbccgp usbccgp.sys Mon Jul 13 20:06:45 2009 (4A5BCC15)
fffff880`04ff8000 fffff880`04ff9f00 USBD USBD.SYS Mon Jul 13 20:06:23 2009 (4A5BCBFF)
fffff880`0426d000 fffff880`0427e000 usbehci usbehci.sys Sat Oct 24 00:27:33 2009 (4AE28235)
fffff880`04a4f000 fffff880`04aa9000 usbhub usbhub.sys Sat Oct 24 00:28:24 2009 (4AE28268)
fffff880`0420c000 fffff880`04217000 usbohci usbohci.sys Mon Jul 13 20:06:30 2009 (4A5BCC06)
fffff880`04217000 fffff880`0426d000 USBPORT USBPORT.SYS Mon Jul 13 20:06:31 2009 (4A5BCC07)
fffff880`00f3f000 fffff880`00f4c000 vdrvroot vdrvroot.sys Mon Jul 13 20:01:31 2009 (4A5BCADB)
fffff880`019ee000 fffff880`019fc000 vga vga.sys Mon Jul 13 19:38:47 2009 (4A5BC587)
fffff880`04e0a000 fffff880`04fa9000 viahduaa viahduaa.sys Thu Sep 17 07:04:15 2009 (4AB217AF)
fffff880`011c7000 fffff880`011ec000 VIDEOPRT VIDEOPRT.SYS Mon Jul 13 19:38:51 2009 (4A5BC58B)
fffff880`018e5000 fffff880`018f5000 vmstorfl vmstorfl.sys Mon Jul 13 19:42:54 2009 (4A5BC67E)
fffff880`00f61000 fffff880`00f76000 volmgr volmgr.sys Mon Jul 13 19:19:57 2009 (4A5BC11D)
fffff880`00f76000 fffff880`00fd2000 volmgrx volmgrx.sys Mon Jul 13 19:20:33 2009 (4A5BC141)
fffff880`018f5000 fffff880`01941000 volsnap volsnap.sys Mon Jul 13 19:20:08 2009 (4A5BC128)
fffff880`02400000 fffff880`0240d000 vwifibus vwifibus.sys Mon Jul 13 20:07:21 2009 (4A5BCC39)
fffff880`04188000 fffff880`0419e000 vwififlt vwififlt.sys Mon Jul 13 20:07:22 2009 (4A5BCC3A)
fffff880`041ca000 fffff880`041e5000 wanarp wanarp.sys Mon Jul 13 20:10:21 2009 (4A5BCCED)
fffff880`01431000 fffff880`01441000 watchdog watchdog.sys Mon Jul 13 19:37:35 2009 (4A5BC53F)
fffff880`00d57000 fffff880`00dfb000 Wdf01000 Wdf01000.sys Mon Jul 13 19:22:07 2009 (4A5BC19F)
fffff880`00c00000 fffff880`00c0f000 WDFLDR WDFLDR.SYS Mon Jul 13 19:19:54 2009 (4A5BC11A)
fffff880`04159000 fffff880`04162000 wfplwf wfplwf.sys Mon Jul 13 20:09:26 2009 (4A5BCCB6)
fffff960`000d0000 fffff960`003e2000 win32k win32k.sys unavailable (00000000)
fffff880`00ef9000 fffff880`00f02000 WMILIB WMILIB.SYS Mon Jul 13 19:19:51 2009 (4A5BC117)
fffff880`04bb7000 fffff880`04bd8000 WudfPf WudfPf.sys Mon Jul 13 20:05:37 2009 (4A5BCBD1)
Unloaded modules:
fffff880`068bf000 fffff880`06930000 spsys.sys
Timestamp: unavailable (00000000)
Checksum: 00000000
fffff880`01830000 fffff880`0183e000 crashdmp.sys
Timestamp: unavailable (00000000)
Checksum: 00000000
fffff880`0183e000 fffff880`01848000 dump_storpor
Timestamp: unavailable (00000000)
Checksum: 00000000
fffff880`01848000 fffff880`01873000 dump_nvstor.
Timestamp: unavailable (00000000)
Checksum: 00000000
fffff880`01873000 fffff880`01886000 dump_dumpfve
Timestamp: unavailable (00000000)
Checksum: 00000000 |
| My System Specs |
 |
New Computer BSOD Consistent problems?
| Thread Tools | |
| Similar help and support threads for: New Computer BSOD Consistent | ||||
| Thread | Forum | |||
| Consistent BSOD after boot | BSOD Help and Support | |||
| Tried to quit BF3 got BSOD. Now consistent. | BSOD Help and Support | |||
 Consistent BSOD, BCCode d1 | BSOD Help and Support | |||
| Consistent BSOD | BSOD Help and Support | |||
| Consistent BSOD after new PC build | BSOD Help and Support | |||
All times are GMT -5. The time now is 04:05 AM.
