Help
I installed Vista Home Premium on my computer earlier this year. For the first several months, I had no problems with it at all. For the last couple of months, I've been experiencing intermittent BSODs. I have noticed no consistency (not doing the same thing each time) - it will crash 3 or 4 times in a row, then will go 4-5 days without any. I searched the internet and came across Topic 173011 about getting help with the blue screens...I have followed the instructions and the results of the minidump (the first of four today so far) are below:
By the way: I'm running Intel Core 2 Duo E6750, an Asus P5K-E Wifi-AP motherboard with 4GB of memory on Vista Home Premium...
Microsoft ® Windows Debugger Version 6.9.0003.113 X86
Copyright © Microsoft Corporation. All rights reserved.
Loading Dump File [C:\Windows\Minidump\Mini110108-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 Server 2008 Kernel Version 6001 (Service Pack 1) MP (2 procs) Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 6001.18145.x86fre.vistasp1_gdr.080917-1612
Kernel base = 0x82805000 PsLoadedModuleList = 0x8291cc70
Debug session time: Fri Oct 31 23:33:40.181 2008 (GMT-4)
System Uptime: 0 days 11:51:52.031
Loading Kernel Symbols
..................................................................................................................................................................
Loading User Symbols
Loading unloaded module list
...........
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 1000008E, {c0000005, 828423cf, 9b360728, 0}
Probably caused by : ntkrpamp.exe ( nt!FsRtlAcquireFileExclusiveCommon+31 )
Followup: MachineOwner
---------
1: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
KERNEL_MODE_EXCEPTION_NOT_HANDLED_M (1000008e)
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: c0000005, The exception code that was not handled
Arg2: 828423cf, The address that the exception occurred at
Arg3: 9b360728, Trap Frame
Arg4: 00000000
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!IoGetRelatedDeviceObject+2e
828423cf 8b4908 mov ecx,dword ptr [ecx+8]
TRAP_FRAME: 9b360728 -- (.trap 0xffffffff9b360728)
ErrCode = 00000000
eax=85bb3190 ebx=85bb3190 ecx=00000007 edx=85bb3195 esi=00000000 edi=85bb3190
eip=828423cf esp=9b36079c ebp=9b3607a4 iopl=0 nv up ei pl nz na po nc
cs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000 efl=00010202
nt!IoGetRelatedDeviceObject+0x2e:
828423cf 8b4908 mov ecx,dword ptr [ecx+8] ds:0023:0000000f=????????
Resetting default scope
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
BUGCHECK_STR: 0x8E
PROCESS_NAME: svchost.exe
CURRENT_IRQL: 0
LAST_CONTROL_TRANSFER: from 82a33d7c to 828423cf
STACK_TEXT:
9b3607a4 82a33d7c 85bb3190 85bb3190 00000000 nt!IoGetRelatedDeviceObject+0x2e
9b3608f8 82a33f7e 85bb3190 00000000 00000006 nt!FsRtlAcquireFileExclusiveCommon+0x31
9b36090c 8282b59f 85bb3190 85bb3190 85ba27dc nt!FsRtlAcquireFileExclusive+0x12
9b360944 82a4e308 85bb3190 005ec87e 00000000 nt!CcZeroEndOfLastPage+0x46
9b36099c 829a3df4 9b360a2c 0000000d 9b3609d0 nt!NtCreateSection+0x1a7
9b360a18 829a3b35 9b360aec d68afca8 00000000 nt!PfpFileBuildReadSupport+0xe4
9b360aac 829a42d7 00360aec 9b360be4 00000001 nt!PfpPrefetchFilesTrickle+0xdf
9b360b00 829a4574 d68ae000 005ecab6 9b360bf8 nt!PfpPrefetchRequestPerform+0x295
9b360b54 829e34b2 9b360be4 828fd801 005ecdfa nt!PfpPrefetchRequest+0x16e
9b360c18 829fccf3 029afa10 00000014 828fd801 nt!PfSetSuperfetchInformation+0x182
9b360d50 8285ca1a 0000004f 00000000 00000014 nt!NtSetSystemInformation+0x908
9b360d50 77499a94 0000004f 00000000 00000014 nt!KiFastCallEntry+0x12a
WARNING: Frame IP not in any known module. Following frames may be wrong.
029afa28 00000000 00000000 00000000 00000000 0x77499a94
STACK_COMMAND: kb
FOLLOWUP_IP:
nt!FsRtlAcquireFileExclusiveCommon+31
82a33d7c ff7508 push dword ptr [ebp+8]
SYMBOL_STACK_INDEX: 1
SYMBOL_NAME: nt!FsRtlAcquireFileExclusiveCommon+31
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: nt
IMAGE_NAME: ntkrpamp.exe
DEBUG_FLR_IMAGE_TIMESTAMP: 48d1b7fa
FAILURE_BUCKET_ID: 0x8E_nt!FsRtlAcquireFileExclusiveCommon+31
BUCKET_ID: 0x8E_nt!FsRtlAcquireFileExclusiveCommon+31
Followup: MachineOwner
---------
1: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
KERNEL_MODE_EXCEPTION_NOT_HANDLED_M (1000008e)
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: c0000005, The exception code that was not handled
Arg2: 828423cf, The address that the exception occurred at
Arg3: 9b360728, Trap Frame
Arg4: 00000000
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!IoGetRelatedDeviceObject+2e
828423cf 8b4908 mov ecx,dword ptr [ecx+8]
TRAP_FRAME: 9b360728 -- (.trap 0xffffffff9b360728)
ErrCode = 00000000
eax=85bb3190 ebx=85bb3190 ecx=00000007 edx=85bb3195 esi=00000000 edi=85bb3190
eip=828423cf esp=9b36079c ebp=9b3607a4 iopl=0 nv up ei pl nz na po nc
cs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000 efl=00010202
nt!IoGetRelatedDeviceObject+0x2e:
828423cf 8b4908 mov ecx,dword ptr [ecx+8] ds:0023:0000000f=????????
Resetting default scope
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
BUGCHECK_STR: 0x8E
PROCESS_NAME: svchost.exe
CURRENT_IRQL: 0
LAST_CONTROL_TRANSFER: from 82a33d7c to 828423cf
STACK_TEXT:
9b3607a4 82a33d7c 85bb3190 85bb3190 00000000 nt!IoGetRelatedDeviceObject+0x2e
9b3608f8 82a33f7e 85bb3190 00000000 00000006 nt!FsRtlAcquireFileExclusiveCommon+0x31
9b36090c 8282b59f 85bb3190 85bb3190 85ba27dc nt!FsRtlAcquireFileExclusive+0x12
9b360944 82a4e308 85bb3190 005ec87e 00000000 nt!CcZeroEndOfLastPage+0x46
9b36099c 829a3df4 9b360a2c 0000000d 9b3609d0 nt!NtCreateSection+0x1a7
9b360a18 829a3b35 9b360aec d68afca8 00000000 nt!PfpFileBuildReadSupport+0xe4
9b360aac 829a42d7 00360aec 9b360be4 00000001 nt!PfpPrefetchFilesTrickle+0xdf
9b360b00 829a4574 d68ae000 005ecab6 9b360bf8 nt!PfpPrefetchRequestPerform+0x295
9b360b54 829e34b2 9b360be4 828fd801 005ecdfa nt!PfpPrefetchRequest+0x16e
9b360c18 829fccf3 029afa10 00000014 828fd801 nt!PfSetSuperfetchInformation+0x182
9b360d50 8285ca1a 0000004f 00000000 00000014 nt!NtSetSystemInformation+0x908
9b360d50 77499a94 0000004f 00000000 00000014 nt!KiFastCallEntry+0x12a
WARNING: Frame IP not in any known module. Following frames may be wrong.
029afa28 00000000 00000000 00000000 00000000 0x77499a94
STACK_COMMAND: kb
FOLLOWUP_IP:
nt!FsRtlAcquireFileExclusiveCommon+31
82a33d7c ff7508 push dword ptr [ebp+8]
SYMBOL_STACK_INDEX: 1
SYMBOL_NAME: nt!FsRtlAcquireFileExclusiveCommon+31
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: nt
IMAGE_NAME: ntkrpamp.exe
DEBUG_FLR_IMAGE_TIMESTAMP: 48d1b7fa
FAILURE_BUCKET_ID: 0x8E_nt!FsRtlAcquireFileExclusiveCommon+31
BUCKET_ID: 0x8E_nt!FsRtlAcquireFileExclusiveCommon+31
Followup: MachineOwner
---------
1: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
KERNEL_MODE_EXCEPTION_NOT_HANDLED_M (1000008e)
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: c0000005, The exception code that was not handled
Arg2: 828423cf, The address that the exception occurred at
Arg3: 9b360728, Trap Frame
Arg4: 00000000
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!IoGetRelatedDeviceObject+2e
828423cf 8b4908 mov ecx,dword ptr [ecx+8]
TRAP_FRAME: 9b360728 -- (.trap 0xffffffff9b360728)
ErrCode = 00000000
eax=85bb3190 ebx=85bb3190 ecx=00000007 edx=85bb3195 esi=00000000 edi=85bb3190
eip=828423cf esp=9b36079c ebp=9b3607a4 iopl=0 nv up ei pl nz na po nc
cs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000 efl=00010202
nt!IoGetRelatedDeviceObject+0x2e:
828423cf 8b4908 mov ecx,dword ptr [ecx+8] ds:0023:0000000f=????????
Resetting default scope
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
BUGCHECK_STR: 0x8E
PROCESS_NAME: svchost.exe
CURRENT_IRQL: 0
LAST_CONTROL_TRANSFER: from 82a33d7c to 828423cf
STACK_TEXT:
9b3607a4 82a33d7c 85bb3190 85bb3190 00000000 nt!IoGetRelatedDeviceObject+0x2e
9b3608f8 82a33f7e 85bb3190 00000000 00000006 nt!FsRtlAcquireFileExclusiveCommon+0x31
9b36090c 8282b59f 85bb3190 85bb3190 85ba27dc nt!FsRtlAcquireFileExclusive+0x12
9b360944 82a4e308 85bb3190 005ec87e 00000000 nt!CcZeroEndOfLastPage+0x46
9b36099c 829a3df4 9b360a2c 0000000d 9b3609d0 nt!NtCreateSection+0x1a7
9b360a18 829a3b35 9b360aec d68afca8 00000000 nt!PfpFileBuildReadSupport+0xe4
9b360aac 829a42d7 00360aec 9b360be4 00000001 nt!PfpPrefetchFilesTrickle+0xdf
9b360b00 829a4574 d68ae000 005ecab6 9b360bf8 nt!PfpPrefetchRequestPerform+0x295
9b360b54 829e34b2 9b360be4 828fd801 005ecdfa nt!PfpPrefetchRequest+0x16e
9b360c18 829fccf3 029afa10 00000014 828fd801 nt!PfSetSuperfetchInformation+0x182
9b360d50 8285ca1a 0000004f 00000000 00000014 nt!NtSetSystemInformation+0x908
9b360d50 77499a94 0000004f 00000000 00000014 nt!KiFastCallEntry+0x12a
WARNING: Frame IP not in any known module. Following frames may be wrong.
029afa28 00000000 00000000 00000000 00000000 0x77499a94
STACK_COMMAND: kb
FOLLOWUP_IP:
nt!FsRtlAcquireFileExclusiveCommon+31
82a33d7c ff7508 push dword ptr [ebp+8]
SYMBOL_STACK_INDEX: 1
SYMBOL_NAME: nt!FsRtlAcquireFileExclusiveCommon+31
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: nt
IMAGE_NAME: ntkrpamp.exe
DEBUG_FLR_IMAGE_TIMESTAMP: 48d1b7fa
FAILURE_BUCKET_ID: 0x8E_nt!FsRtlAcquireFileExclusiveCommon+31
BUCKET_ID: 0x8E_nt!FsRtlAcquireFileExclusiveCommon+31
Followup: MachineOwner
---------
1: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
KERNEL_MODE_EXCEPTION_NOT_HANDLED_M (1000008e)
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: c0000005, The exception code that was not handled
Arg2: 828423cf, The address that the exception occurred at
Arg3: 9b360728, Trap Frame
Arg4: 00000000
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!IoGetRelatedDeviceObject+2e
828423cf 8b4908 mov ecx,dword ptr [ecx+8]
TRAP_FRAME: 9b360728 -- (.trap 0xffffffff9b360728)
ErrCode = 00000000
eax=85bb3190 ebx=85bb3190 ecx=00000007 edx=85bb3195 esi=00000000 edi=85bb3190
eip=828423cf esp=9b36079c ebp=9b3607a4 iopl=0 nv up ei pl nz na po nc
cs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000 efl=00010202
nt!IoGetRelatedDeviceObject+0x2e:
828423cf 8b4908 mov ecx,dword ptr [ecx+8] ds:0023:0000000f=????????
Resetting default scope
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
BUGCHECK_STR: 0x8E
PROCESS_NAME: svchost.exe
CURRENT_IRQL: 0
LAST_CONTROL_TRANSFER: from 82a33d7c to 828423cf
STACK_TEXT:
9b3607a4 82a33d7c 85bb3190 85bb3190 00000000 nt!IoGetRelatedDeviceObject+0x2e
9b3608f8 82a33f7e 85bb3190 00000000 00000006 nt!FsRtlAcquireFileExclusiveCommon+0x31
9b36090c 8282b59f 85bb3190 85bb3190 85ba27dc nt!FsRtlAcquireFileExclusive+0x12
9b360944 82a4e308 85bb3190 005ec87e 00000000 nt!CcZeroEndOfLastPage+0x46
9b36099c 829a3df4 9b360a2c 0000000d 9b3609d0 nt!NtCreateSection+0x1a7
9b360a18 829a3b35 9b360aec d68afca8 00000000 nt!PfpFileBuildReadSupport+0xe4
9b360aac 829a42d7 00360aec 9b360be4 00000001 nt!PfpPrefetchFilesTrickle+0xdf
9b360b00 829a4574 d68ae000 005ecab6 9b360bf8 nt!PfpPrefetchRequestPerform+0x295
9b360b54 829e34b2 9b360be4 828fd801 005ecdfa nt!PfpPrefetchRequest+0x16e
9b360c18 829fccf3 029afa10 00000014 828fd801 nt!PfSetSuperfetchInformation+0x182
9b360d50 8285ca1a 0000004f 00000000 00000014 nt!NtSetSystemInformation+0x908
9b360d50 77499a94 0000004f 00000000 00000014 nt!KiFastCallEntry+0x12a
WARNING: Frame IP not in any known module. Following frames may be wrong.
029afa28 00000000 00000000 00000000 00000000 0x77499a94
STACK_COMMAND: kb
FOLLOWUP_IP:
nt!FsRtlAcquireFileExclusiveCommon+31
82a33d7c ff7508 push dword ptr [ebp+8]
SYMBOL_STACK_INDEX: 1
SYMBOL_NAME: nt!FsRtlAcquireFileExclusiveCommon+31
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: nt
IMAGE_NAME: ntkrpamp.exe
DEBUG_FLR_IMAGE_TIMESTAMP: 48d1b7fa
FAILURE_BUCKET_ID: 0x8E_nt!FsRtlAcquireFileExclusiveCommon+31
BUCKET_ID: 0x8E_nt!FsRtlAcquireFileExclusiveCommon+31
Followup: MachineOwner
---------
1: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
KERNEL_MODE_EXCEPTION_NOT_HANDLED_M (1000008e)
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: c0000005, The exception code that was not handled
Arg2: 828423cf, The address that the exception occurred at
Arg3: 9b360728, Trap Frame
Arg4: 00000000
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!IoGetRelatedDeviceObject+2e
828423cf 8b4908 mov ecx,dword ptr [ecx+8]
TRAP_FRAME: 9b360728 -- (.trap 0xffffffff9b360728)
ErrCode = 00000000
eax=85bb3190 ebx=85bb3190 ecx=00000007 edx=85bb3195 esi=00000000 edi=85bb3190
eip=828423cf esp=9b36079c ebp=9b3607a4 iopl=0 nv up ei pl nz na po nc
cs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000 efl=00010202
nt!IoGetRelatedDeviceObject+0x2e:
828423cf 8b4908 mov ecx,dword ptr [ecx+8] ds:0023:0000000f=????????
Resetting default scope
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
BUGCHECK_STR: 0x8E
PROCESS_NAME: svchost.exe
CURRENT_IRQL: 0
LAST_CONTROL_TRANSFER: from 82a33d7c to 828423cf
STACK_TEXT:
9b3607a4 82a33d7c 85bb3190 85bb3190 00000000 nt!IoGetRelatedDeviceObject+0x2e
9b3608f8 82a33f7e 85bb3190 00000000 00000006 nt!FsRtlAcquireFileExclusiveCommon+0x31
9b36090c 8282b59f 85bb3190 85bb3190 85ba27dc nt!FsRtlAcquireFileExclusive+0x12
9b360944 82a4e308 85bb3190 005ec87e 00000000 nt!CcZeroEndOfLastPage+0x46
9b36099c 829a3df4 9b360a2c 0000000d 9b3609d0 nt!NtCreateSection+0x1a7
9b360a18 829a3b35 9b360aec d68afca8 00000000 nt!PfpFileBuildReadSupport+0xe4
9b360aac 829a42d7 00360aec 9b360be4 00000001 nt!PfpPrefetchFilesTrickle+0xdf
9b360b00 829a4574 d68ae000 005ecab6 9b360bf8 nt!PfpPrefetchRequestPerform+0x295
9b360b54 829e34b2 9b360be4 828fd801 005ecdfa nt!PfpPrefetchRequest+0x16e
9b360c18 829fccf3 029afa10 00000014 828fd801 nt!PfSetSuperfetchInformation+0x182
9b360d50 8285ca1a 0000004f 00000000 00000014 nt!NtSetSystemInformation+0x908
9b360d50 77499a94 0000004f 00000000 00000014 nt!KiFastCallEntry+0x12a
WARNING: Frame IP not in any known module. Following frames may be wrong.
029afa28 00000000 00000000 00000000 00000000 0x77499a94
STACK_COMMAND: kb
FOLLOWUP_IP:
nt!FsRtlAcquireFileExclusiveCommon+31
82a33d7c ff7508 push dword ptr [ebp+8]
SYMBOL_STACK_INDEX: 1
SYMBOL_NAME: nt!FsRtlAcquireFileExclusiveCommon+31
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: nt
IMAGE_NAME: ntkrpamp.exe
DEBUG_FLR_IMAGE_TIMESTAMP: 48d1b7fa
FAILURE_BUCKET_ID: 0x8E_nt!FsRtlAcquireFileExclusiveCommon+31
BUCKET_ID: 0x8E_nt!FsRtlAcquireFileExclusiveCommon+31
Followup: MachineOwner
---------
1: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
KERNEL_MODE_EXCEPTION_NOT_HANDLED_M (1000008e)
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: c0000005, The exception code that was not handled
Arg2: 828423cf, The address that the exception occurred at
Arg3: 9b360728, Trap Frame
Arg4: 00000000
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!IoGetRelatedDeviceObject+2e
828423cf 8b4908 mov ecx,dword ptr [ecx+8]
TRAP_FRAME: 9b360728 -- (.trap 0xffffffff9b360728)
ErrCode = 00000000
eax=85bb3190 ebx=85bb3190 ecx=00000007 edx=85bb3195 esi=00000000 edi=85bb3190
eip=828423cf esp=9b36079c ebp=9b3607a4 iopl=0 nv up ei pl nz na po nc
cs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000 efl=00010202
nt!IoGetRelatedDeviceObject+0x2e:
828423cf 8b4908 mov ecx,dword ptr [ecx+8] ds:0023:0000000f=????????
Resetting default scope
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
BUGCHECK_STR: 0x8E
PROCESS_NAME: svchost.exe
CURRENT_IRQL: 0
LAST_CONTROL_TRANSFER: from 82a33d7c to 828423cf
STACK_TEXT:
9b3607a4 82a33d7c 85bb3190 85bb3190 00000000 nt!IoGetRelatedDeviceObject+0x2e
9b3608f8 82a33f7e 85bb3190 00000000 00000006 nt!FsRtlAcquireFileExclusiveCommon+0x31
9b36090c 8282b59f 85bb3190 85bb3190 85ba27dc nt!FsRtlAcquireFileExclusive+0x12
9b360944 82a4e308 85bb3190 005ec87e 00000000 nt!CcZeroEndOfLastPage+0x46
9b36099c 829a3df4 9b360a2c 0000000d 9b3609d0 nt!NtCreateSection+0x1a7
9b360a18 829a3b35 9b360aec d68afca8 00000000 nt!PfpFileBuildReadSupport+0xe4
9b360aac 829a42d7 00360aec 9b360be4 00000001 nt!PfpPrefetchFilesTrickle+0xdf
9b360b00 829a4574 d68ae000 005ecab6 9b360bf8 nt!PfpPrefetchRequestPerform+0x295
9b360b54 829e34b2 9b360be4 828fd801 005ecdfa nt!PfpPrefetchRequest+0x16e
9b360c18 829fccf3 029afa10 00000014 828fd801 nt!PfSetSuperfetchInformation+0x182
9b360d50 8285ca1a 0000004f 00000000 00000014 nt!NtSetSystemInformation+0x908
9b360d50 77499a94 0000004f 00000000 00000014 nt!KiFastCallEntry+0x12a
WARNING: Frame IP not in any known module. Following frames may be wrong.
029afa28 00000000 00000000 00000000 00000000 0x77499a94
STACK_COMMAND: kb
FOLLOWUP_IP:
nt!FsRtlAcquireFileExclusiveCommon+31
82a33d7c ff7508 push dword ptr [ebp+8]
SYMBOL_STACK_INDEX: 1
SYMBOL_NAME: nt!FsRtlAcquireFileExclusiveCommon+31
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: nt
IMAGE_NAME: ntkrpamp.exe
DEBUG_FLR_IMAGE_TIMESTAMP: 48d1b7fa
FAILURE_BUCKET_ID: 0x8E_nt!FsRtlAcquireFileExclusiveCommon+31
BUCKET_ID: 0x8E_nt!FsRtlAcquireFileExclusiveCommon+31
Followup: MachineOwner
---------
1: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
KERNEL_MODE_EXCEPTION_NOT_HANDLED_M (1000008e)
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: c0000005, The exception code that was not handled
Arg2: 828423cf, The address that the exception occurred at
Arg3: 9b360728, Trap Frame
Arg4: 00000000
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!IoGetRelatedDeviceObject+2e
828423cf 8b4908 mov ecx,dword ptr [ecx+8]
TRAP_FRAME: 9b360728 -- (.trap 0xffffffff9b360728)
ErrCode = 00000000
eax=85bb3190 ebx=85bb3190 ecx=00000007 edx=85bb3195 esi=00000000 edi=85bb3190
eip=828423cf esp=9b36079c ebp=9b3607a4 iopl=0 nv up ei pl nz na po nc
cs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000 efl=00010202
nt!IoGetRelatedDeviceObject+0x2e:
828423cf 8b4908 mov ecx,dword ptr [ecx+8] ds:0023:0000000f=????????
Resetting default scope
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
BUGCHECK_STR: 0x8E
PROCESS_NAME: svchost.exe
CURRENT_IRQL: 0
LAST_CONTROL_TRANSFER: from 82a33d7c to 828423cf
STACK_TEXT:
9b3607a4 82a33d7c 85bb3190 85bb3190 00000000 nt!IoGetRelatedDeviceObject+0x2e
9b3608f8 82a33f7e 85bb3190 00000000 00000006 nt!FsRtlAcquireFileExclusiveCommon+0x31
9b36090c 8282b59f 85bb3190 85bb3190 85ba27dc nt!FsRtlAcquireFileExclusive+0x12
9b360944 82a4e308 85bb3190 005ec87e 00000000 nt!CcZeroEndOfLastPage+0x46
9b36099c 829a3df4 9b360a2c 0000000d 9b3609d0 nt!NtCreateSection+0x1a7
9b360a18 829a3b35 9b360aec d68afca8 00000000 nt!PfpFileBuildReadSupport+0xe4
9b360aac 829a42d7 00360aec 9b360be4 00000001 nt!PfpPrefetchFilesTrickle+0xdf
9b360b00 829a4574 d68ae000 005ecab6 9b360bf8 nt!PfpPrefetchRequestPerform+0x295
9b360b54 829e34b2 9b360be4 828fd801 005ecdfa nt!PfpPrefetchRequest+0x16e
9b360c18 829fccf3 029afa10 00000014 828fd801 nt!PfSetSuperfetchInformation+0x182
9b360d50 8285ca1a 0000004f 00000000 00000014 nt!NtSetSystemInformation+0x908
9b360d50 77499a94 0000004f 00000000 00000014 nt!KiFastCallEntry+0x12a
WARNING: Frame IP not in any known module. Following frames may be wrong.
029afa28 00000000 00000000 00000000 00000000 0x77499a94
STACK_COMMAND: kb
FOLLOWUP_IP:
nt!FsRtlAcquireFileExclusiveCommon+31
82a33d7c ff7508 push dword ptr [ebp+8]
SYMBOL_STACK_INDEX: 1
SYMBOL_NAME: nt!FsRtlAcquireFileExclusiveCommon+31
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: nt
IMAGE_NAME: ntkrpamp.exe
DEBUG_FLR_IMAGE_TIMESTAMP: 48d1b7fa
FAILURE_BUCKET_ID: 0x8E_nt!FsRtlAcquireFileExclusiveCommon+31
BUCKET_ID: 0x8E_nt!FsRtlAcquireFileExclusiveCommon+31
Followup: MachineOwner
---------
Thanks for any help...
kittybox
Page 1 of 1
A Vista Blue Screen of Death
Back to top
#2
- Still visually handicapped, new avatar (a camel) :0)
-
- Group: Members
- Posts: 16,690
- Joined: 02-October 05
- Gender:Male
- Location:Southeastern CT, USA
Posted 01 November 2008 - 03:44 PM
This error is usually a hardware incompatibility issue. Assuming that you haven't changed any hardware recently, then it's likely that this has to do with something that was installed recently.
To further troubleshoot it, you'll have to enable Driver Verifier.
To further troubleshoot it, you'll have to enable Driver Verifier.
Quote
I would suggest enabling Driver Verifier in order to further hunt down the culprit. Do do this, go to Start and type in "verifier.exe" (without the quotes) and press Enter.
In the next screen, click on "Next" to accept the default of "Create standard settings"
In the next screen, click on "Next" to accept the default of "Automatically select unsigned drivers"
In the next screen, click on "Finish" to accept the list of unsigned drivers that Windows detected.
Then, reboot the system and wait for the crash.
Once it crashes, perform an analysis as you did in Post #4.
Once you've analyzed the dump file, go back in to Driver Verifier and select the "Delete existing settings" in the first screen to stop Driver Verifier from running.
In most cases Driver Verifier will have identified the faulty driver, but in some cases it'll just give more clues (and we'll have to do further testing).
In the next screen, click on "Next" to accept the default of "Create standard settings"
In the next screen, click on "Next" to accept the default of "Automatically select unsigned drivers"
In the next screen, click on "Finish" to accept the list of unsigned drivers that Windows detected.
Then, reboot the system and wait for the crash.
Once it crashes, perform an analysis as you did in Post #4.
Once you've analyzed the dump file, go back in to Driver Verifier and select the "Delete existing settings" in the first screen to stop Driver Verifier from running.
In most cases Driver Verifier will have identified the faulty driver, but in some cases it'll just give more clues (and we'll have to do further testing).
- John
**If you need a more detailed explanation, please ask for it. I have the Knack. **
**If you need a more detailed explanation, please ask for it. I have the Knack. **
Share this topic:
Page 1 of 1