Windows 7 Forums

Welcome to Windows 7 Forums. Our forum is dedicated to helping you find support and solutions for any problems regarding your Windows 7 PC be it Dell, HP, Acer, Asus or a custom build. We also provide an extensive Windows 7 tutorial section that covers a wide range of tips and tricks.


Windows 7: BSOD during Booting

26 Nov 2009   #1
eldora

Windows 7 Ultimate x86
 
 
BSOD during Booting

I am using Widows 7 Ultimate on my new laptop. So I can be quite sure that this problem is not cause by hardware failure. I keep getting BSOD during booting. Startup recovery is unable to repair my problem.
Can anyone help me to point out what is the problem?

Below is the dump file


Microsoft (R) Windows Debugger Version 6.11.0001.404 X86
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Windows\Minidump\112609-24351-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: *** Invalid ***
****************************************************************************
* Symbol loading may be unreliable without a symbol search path. *
* Use .symfix to have the debugger choose a symbol path. *
* After setting your symbol path, use .reload to refresh symbol locations. *
****************************************************************************
Executable search path is:
*********************************************************************
* Symbols can not be loaded because symbol path is not initialized. *
* *
* The Symbol Path can be set by: *
* using the _NT_SYMBOL_PATH environment variable. *
* using the -y <symbol_path> argument when starting the debugger. *
* using .sympath and .sympath+ *
*********************************************************************
Unable to load image \SystemRoot\system32\ntkrnlpa.exe, Win32 error 0n2
*** WARNING: Unable to verify timestamp for ntkrnlpa.exe
*** ERROR: Module load completed but symbols could not be loaded for ntkrnlpa.exe
Windows 7 Kernel Version 7600 MP (2 procs) Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7600.16385.x86fre.win7_rtm.090713-1255
Machine Name:
Kernel base = 0x82a45000 PsLoadedModuleList = 0x82b8d810
Debug session time: Thu Nov 26 13:47:00.237 2009 (GMT+8)
System Uptime: 0 days 0:00:08.845
*********************************************************************
* Symbols can not be loaded because symbol path is not initialized. *
* *
* The Symbol Path can be set by: *
* using the _NT_SYMBOL_PATH environment variable. *
* using the -y <symbol_path> argument when starting the debugger. *
* using .sympath and .sympath+ *
*********************************************************************
Unable to load image \SystemRoot\system32\ntkrnlpa.exe, Win32 error 0n2
*** WARNING: Unable to verify timestamp for ntkrnlpa.exe
*** ERROR: Module load completed but symbols could not be loaded for ntkrnlpa.exe
Loading Kernel Symbols
...............................................................
.....................
Loading User Symbols
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 1000007E, {c0000005, 82c6708f, 80786890, 80786470}

*** WARNING: Unable to verify timestamp for mssmbios.sys
*** ERROR: Module load completed but symbols could not be loaded for mssmbios.sys
***** Kernel symbols are WRONG. Please fix symbols to do analysis.

*************************************************************************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!_KPRCB ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!KPRCB ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!_KPRCB ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!KPRCB ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!_KPRCB ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!_KPRCB ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!_KPRCB ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!_KPRCB ***
*** ***
*************************************************************************
*********************************************************************
* Symbols can not be loaded because symbol path is not initialized. *
* *
* The Symbol Path can be set by: *
* using the _NT_SYMBOL_PATH environment variable. *
* using the -y <symbol_path> argument when starting the debugger. *
* using .sympath and .sympath+ *
*********************************************************************
*********************************************************************
* Symbols can not be loaded because symbol path is not initialized. *
* *
* The Symbol Path can be set by: *
* using the _NT_SYMBOL_PATH environment variable. *
* using the -y <symbol_path> argument when starting the debugger. *
* using .sympath and .sympath+ *
*********************************************************************
Probably caused by : ntkrnlpa.exe ( nt+22208f )

Followup: MachineOwner
---------


Thanks in advance!


My System SpecsSystem Spec
.
26 Nov 2009   #2
torrentg

7600.20510 x86
 
 

Hi.

Update your video card driver from NVIDIA's site and follow this to post further crash dumps if you need.
My System SpecsSystem Spec
26 Nov 2009   #3
eldora

Windows 7 Ultimate x86
 
 

My graphic card is ATI HD4670
So I need to update my graphic card from ATI instead?
My System SpecsSystem Spec
.

26 Nov 2009   #4
torrentg

7600.20510 x86
 
 

Yes, you're correct. Sorry about that.

Always good to run the latest drivers of everything. So that's why I suggested straight away. Let's see the crash dumps and then we can advise.
My System SpecsSystem Spec
26 Nov 2009   #5
eldora

Windows 7 Ultimate x86
 
 

Thanks for the reply. I already updated my graphic card driver, reboot it. No BSOD occurs. Hope that this solve the problem. If BSOD occurs again I will post my crash dump as soon as possible.
Thanks for the help torrentg
My System SpecsSystem Spec
28 Nov 2009   #6
eldora

Windows 7 Ultimate x86
 
 

Hi, its seems that my problem didn't solve completely. BSOD happen again 2 days after i update my graphic card. Below is the latest crash dump details:


Microsoft (R) Windows Debugger Version 6.11.0001.404 X86
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Windows\Minidump\112809-32463-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: *** Invalid ***
****************************************************************************
* Symbol loading may be unreliable without a symbol search path. *
* Use .symfix to have the debugger choose a symbol path. *
* After setting your symbol path, use .reload to refresh symbol locations. *
****************************************************************************
Executable search path is:
*********************************************************************
* Symbols can not be loaded because symbol path is not initialized. *
* *
* The Symbol Path can be set by: *
* using the _NT_SYMBOL_PATH environment variable. *
* using the -y <symbol_path> argument when starting the debugger. *
* using .sympath and .sympath+ *
*********************************************************************
Unable to load image \SystemRoot\system32\ntkrnlpa.exe, Win32 error 0n2
*** WARNING: Unable to verify timestamp for ntkrnlpa.exe
*** ERROR: Module load completed but symbols could not be loaded for ntkrnlpa.exe
Windows 7 Kernel Version 7600 MP (2 procs) Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7600.16385.x86fre.win7_rtm.090713-1255
Machine Name:
Kernel base = 0x82a01000 PsLoadedModuleList = 0x82b49810
Debug session time: Sat Nov 28 22:47:36.301 2009 (GMT+8)
System Uptime: 0 days 0:00:07.909
*********************************************************************
* Symbols can not be loaded because symbol path is not initialized. *
* *
* The Symbol Path can be set by: *
* using the _NT_SYMBOL_PATH environment variable. *
* using the -y <symbol_path> argument when starting the debugger. *
* using .sympath and .sympath+ *
*********************************************************************
Unable to load image \SystemRoot\system32\ntkrnlpa.exe, Win32 error 0n2
*** WARNING: Unable to verify timestamp for ntkrnlpa.exe
*** ERROR: Module load completed but symbols could not be loaded for ntkrnlpa.exe
Loading Kernel Symbols
...............................................................
......................
Loading User Symbols
Loading unloaded module list
.
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck A, {313c, 2, 0, 82ac2012}

*** WARNING: Unable to verify timestamp for mssmbios.sys
*** ERROR: Module load completed but symbols could not be loaded for mssmbios.sys
***** Kernel symbols are WRONG. Please fix symbols to do analysis.

*************************************************************************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!_KPRCB ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!KPRCB ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!_KPRCB ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!KPRCB ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!_KPRCB ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!_KPRCB ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!_KPRCB ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!_KPRCB ***
*** ***
*************************************************************************
*********************************************************************
* Symbols can not be loaded because symbol path is not initialized. *
* *
* The Symbol Path can be set by: *
* using the _NT_SYMBOL_PATH environment variable. *
* using the -y <symbol_path> argument when starting the debugger. *
* using .sympath and .sympath+ *
*********************************************************************
*********************************************************************
* Symbols can not be loaded because symbol path is not initialized. *
* *
* The Symbol Path can be set by: *
* using the _NT_SYMBOL_PATH environment variable. *
* using the -y <symbol_path> argument when starting the debugger. *
* using .sympath and .sympath+ *
*********************************************************************
Probably caused by : ntkrnlpa.exe ( nt+c1012 )

Followup: MachineOwner
---------

Hope that anyone can help me solve this problem. Thanks in advance!!
My System SpecsSystem Spec
28 Nov 2009   #7
usasma
Microsoft MVP

 
 

Please follow Step E in this link to set your symbol path correctly: WinDbg Analysis Report
Code:
E. In the window that opens, insert the exact text on the next line in the Symbol File Path box. This is a critical step, and if done incorrectly you'll end up with symbol errors:
SRV*c:\symbols*http://msdl.microsoft.com/download/symbols
The easiest thing to do is copy the above bolded text and then paste it into the box. Once that is done, click on OKto exit the dialog. Next, click on File menu and then select the Save Workspace menu option. This will save the symbol path for future use. NOTE: You MUST be connected to the internet in order to use the Symbol server listed above.

Also, please do the following to provide us with more information:
Quote:
Upload Dump Files
Please go to C:\Windows\Minidump and zip up the contents of the folder. Then upload/attach the .zip file with your next post.

If you have issues with "Access Denied" errors, try copying the files to your desktop and zipping them up from there. If it still won't let you zip them up, post back for further advice.

If you don't have anything in that folder, please check in C:\Windows for a file named MEMORY.DMP. If you find it, zip it up and upload it to a free file hosting service - then post the link to it.
Then, follow the directions here to set your system for Minidumps (much smaller than the MEMORY.DMP file): Set MiniDump

MSINFO32
Please go to Start and type in "msinfo32.exe" (without the quotes) and press Enter
Save the report as an .nfo file, then zip up the .nfo file and upload/attach the .zip file with your next post.
My System SpecsSystem Spec
28 Nov 2009   #8
eldora

Windows 7 Ultimate x86
 
 

I am so sorry for posting without adhering to the forum rules. Sorry for creating so much trouble. Below is the attachment for my crash dump and msinfo.

However, after i set the SRV*c:\symbols*Symbol information for my symbol file path, I can't open the crash dump file. It prompt error as debugger not connected. I am pretty sure I am connected to the Internet.

I am sorry again for the trouble. Thanks in advance
My System SpecsSystem Spec
28 Nov 2009   #9
usasma
Microsoft MVP

 
 

Don't worry about the differences in posting styles.
Please upload ALL of your mindump files. In particular I'd like to see the dump files from:

28/11/2009 2:50 PM STOP 0x0A
26/11/2009 6:02 AM STOP 0x7E
25/11/2009 4:16 AM STOP 0xC5
23/11/2009 6:06 AM STOP 0xC5

You have a fastcap video capture device that's disabled. Can you uninstall the software and remove the device from your system?

Otherwise there's nothing that I can see in the memory dump files. Once you upload the rest of them this could change. If not, then we'll resort to Driver Verifier - but don't try that yet.

Here's the latest memory dump analysis:
Code:
Microsoft (R) Windows Debugger Version 6.11.0001.404 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Users\FUBAR\TempDUMP\DATA\01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*c:\symbols*http://msdl.microsoft.com/download/symbols
Executable search path is: 
Windows 7 Kernel Version 7600 MP (2 procs) Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7600.16385.x86fre.win7_rtm.090713-1255
Machine Name:
Kernel base = 0x82a01000 PsLoadedModuleList = 0x82b49810
Debug session time: Sat Nov 28 09:47:36.301 2009 (GMT-5)
System Uptime: 0 days 0:00:07.909
Loading Kernel Symbols
...............................................................
......................
Loading User Symbols
Loading unloaded module list
.
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck A, {313c, 2, 0, 82ac2012}

Probably caused by : ntkrpamp.exe ( nt!PromoteNode+2c )

Followup: MachineOwner
---------

1: kd> !thread;!analyze -v;r;kv;lmtn;lmtsmn;.bugcheck;.logclose;q
GetPointerFromAddress: unable to read from 82b6971c
THREAD 851dad48  Cid 0004.0030  Teb: 00000000 Win32Thread: 00000000 RUNNING on processor 1
Not impersonating
GetUlongFromAddress: unable to read from 82b2949c
Owning Process            851487e0       Image:         System
Attached Process          N/A            Image:         N/A
ffdf0000: Unable to get shared data
Wait Start TickCount      506          
Context Switch Count      299             
ReadMemory error: Cannot get nt!KeMaximumIncrement value.
UserTime                  00:00:00.000
KernelTime                00:00:00.000
Win32 Start Address nt!ExpWorkerThread (0x82a6ee1e)
Stack Init 8d317fd0 Current 8d316768 Base 8d318000 Limit 8d315000 Call 0
Priority 12 BasePriority 12 UnusualBoost 0 ForegroundBoost 0 IoPriority 2 PagePriority 5
ChildEBP RetAddr  Args to Child              
8d3174a4 82ac2012 badb0d00 00000000 67727453 nt!KiTrap0E+0x2cf (FPO: [0,0] TrapFrame @ 8d3174a4)
8d317518 82ac204e 85120a98 86478318 86478301 nt!PromoteNode+0x2c (FPO: [0,0,1])
8d31752c 82abaf5f 85120a98 82b36680 86478328 nt!RebalanceNode+0x26
8d317540 82a1f0e3 85120a98 86478328 00000004 nt!RtlInsertElementGenericTableFullAvl+0xa7
8d317564 82a1a16f 85ec21e8 86478328 00000004 nt!RtlInsertElementGenericTableAvl+0x28
8d317580 82a1a056 00000515 85eb9678 900fb440 nt!VfAvlInsertReservedTreeNode+0x2b
8d31759c 82bc77e0 9083d000 00515000 00000000 nt!VfTargetDriversAdd+0xa6
8d3175b4 82bc5718 00000000 00000000 00000000 nt!VfDriverLoadImage+0x36
8d3175f8 82bc52ec 900fb440 8d317800 8d317668 nt!MiDriverLoadSucceeded+0x2f
8d317678 82ba42c0 8d317800 00000000 00000000 nt!MmLoadSystemImage+0x6e1
8d31786c 82babfe7 00000000 00000000 8d317894 nt!IopLoadDriver+0x386
8d317918 82bf0e4e 900f9778 00000001 900f9764 nt!PipCallDriverAddDeviceQueryRoutine+0x34b
8d317950 82bf90a2 00000001 8d317a1c c0000034 nt!RtlpCallQueryRegistryRoutine+0x2cd
8d3179bc 82ba9108 40000000 80000164 8d317a38 nt!RtlQueryRegistryValues+0x31d
8d317a98 82ba8876 85eeb008 8d317cc8 00000000 nt!PipCallDriverAddDevice+0x383
8d317c94 82b8ca2a 851fe518 86468b00 8d317cc8 nt!PipProcessDevNodeTree+0x15d
8d317cd4 82a14f99 86468b00 82b64e80 851dad48 nt!PiProcessStartSystemDevices+0x6d
8d317d00 82a6ef2b 00000000 00000000 851dad48 nt!PnpDeviceActionWorker+0x241
8d317d50 82c0f66d 00000001 a6568918 00000000 nt!ExpWorkerThread+0x10d
8d317d90 82ac10d9 82a6ee1e 00000001 00000000 nt!PspSystemThreadStartup+0x9e
00000000 00000000 00000000 00000000 00000000 nt!KiThreadStartup+0x19

*******************************************************************************
*                                                                             *
*                        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: 0000313c, memory referenced
Arg2: 00000002, IRQL
Arg3: 00000000, 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: 82ac2012, address which referenced memory

Debugging Details:
------------------


READ_ADDRESS: GetPointerFromAddress: unable to read from 82b69718
Unable to read MiSystemVaType memory at 82b49160
 0000313c 

CURRENT_IRQL:  2

FAULTING_IP: 
nt!PromoteNode+2c
82ac2012 394604          cmp     dword ptr [esi+4],eax

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

BUGCHECK_STR:  0xA

PROCESS_NAME:  System

TRAP_FRAME:  8d3174a4 -- (.trap 0xffffffff8d3174a4)
.trap 0xffffffff8d3174a4
ErrCode = 00000000
eax=86467d60 ebx=86478301 ecx=85ec21e8 edx=00000000 esi=00003138 edi=86467d60
eip=82ac2012 esp=8d317518 ebp=8d31752c iopl=0         nv up ei pl zr na pe nc
cs=0008  ss=0010  ds=0023  es=0023  fs=0030  gs=0000             efl=00210246
nt!PromoteNode+0x2c:
82ac2012 394604          cmp     dword ptr [esi+4],eax ds:0023:0000313c=????????
.trap
Resetting default scope

LOCK_ADDRESS:  82b66f60 -- (!locks 82b66f60)
!locks ffffffff82b66f60

Resource @ nt!PiEngineLock (0x82b66f60)    Available

WARNING: SystemResourcesList->Flink chain invalid. Resource may be corrupted, or already deleted.


WARNING: SystemResourcesList->Blink chain invalid. Resource may be corrupted, or already deleted.

1 total locks

PNP_TRIAGE: 
    Lock address  : 0x82b66f60
    Thread Count  : 0
    Thread address: 0x00000000
    Thread wait   : 0x0

LAST_CONTROL_TRANSFER:  from 82ac2012 to 82a477eb

STACK_TEXT:  
8d3174a4 82ac2012 badb0d00 00000000 67727453 nt!KiTrap0E+0x2cf
8d317518 82ac204e 85120a98 86478318 86478301 nt!PromoteNode+0x2c
8d31752c 82abaf5f 85120a98 82b36680 86478328 nt!RebalanceNode+0x26
8d317540 82a1f0e3 85120a98 86478328 00000004 nt!RtlInsertElementGenericTableFullAvl+0xa7
8d317564 82a1a16f 85ec21e8 86478328 00000004 nt!RtlInsertElementGenericTableAvl+0x28
8d317580 82a1a056 00000515 85eb9678 900fb440 nt!VfAvlInsertReservedTreeNode+0x2b
8d31759c 82bc77e0 9083d000 00515000 00000000 nt!VfTargetDriversAdd+0xa6
8d3175b4 82bc5718 00000000 00000000 00000000 nt!VfDriverLoadImage+0x36
8d3175f8 82bc52ec 900fb440 8d317800 8d317668 nt!MiDriverLoadSucceeded+0x2f
8d317678 82ba42c0 8d317800 00000000 00000000 nt!MmLoadSystemImage+0x6e1
8d31786c 82babfe7 00000000 00000000 8d317894 nt!IopLoadDriver+0x386
8d317918 82bf0e4e 900f9778 00000001 900f9764 nt!PipCallDriverAddDeviceQueryRoutine+0x34b
8d317950 82bf90a2 00000001 8d317a1c c0000034 nt!RtlpCallQueryRegistryRoutine+0x2cd
8d3179bc 82ba9108 40000000 80000164 8d317a38 nt!RtlQueryRegistryValues+0x31d
8d317a98 82ba8876 85eeb008 8d317cc8 00000000 nt!PipCallDriverAddDevice+0x383
8d317c94 82b8ca2a 851fe518 86468b00 8d317cc8 nt!PipProcessDevNodeTree+0x15d
8d317cd4 82a14f99 86468b00 82b64e80 851dad48 nt!PiProcessStartSystemDevices+0x6d
8d317d00 82a6ef2b 00000000 00000000 851dad48 nt!PnpDeviceActionWorker+0x241
8d317d50 82c0f66d 00000001 a6568918 00000000 nt!ExpWorkerThread+0x10d
8d317d90 82ac10d9 82a6ee1e 00000001 00000000 nt!PspSystemThreadStartup+0x9e
00000000 00000000 00000000 00000000 00000000 nt!KiThreadStartup+0x19


STACK_COMMAND:  kb

FOLLOWUP_IP: 
nt!PromoteNode+2c
82ac2012 394604          cmp     dword ptr [esi+4],eax

SYMBOL_STACK_INDEX:  1

SYMBOL_NAME:  nt!PromoteNode+2c

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nt

IMAGE_NAME:  ntkrpamp.exe

DEBUG_FLR_IMAGE_TIMESTAMP:  4a5bc007

FAILURE_BUCKET_ID:  0xA_nt!PromoteNode+2c

BUCKET_ID:  0xA_nt!PromoteNode+2c

Followup: MachineOwner
---------

eax=82b3817c ebx=8d317502 ecx=00000001 edx=00000000 esi=807c4120 edi=00000000
eip=82a477eb esp=8d31748c ebp=8d3174a4 iopl=0         nv up ei pl nz na po nc
cs=0008  ss=0010  ds=0023  es=0023  fs=0030  gs=0000             efl=00200202
nt!KiTrap0E+0x2cf:
82a477eb 833dc44ab68200  cmp     dword ptr [nt!KiFreezeFlag (82b64ac4)],0 ds:0023:82b64ac4=????????
ChildEBP RetAddr  Args to Child              
8d3174a4 82ac2012 badb0d00 00000000 67727453 nt!KiTrap0E+0x2cf (FPO: [0,0] TrapFrame @ 8d3174a4)
8d317518 82ac204e 85120a98 86478318 86478301 nt!PromoteNode+0x2c (FPO: [0,0,1])
8d31752c 82abaf5f 85120a98 82b36680 86478328 nt!RebalanceNode+0x26
8d317540 82a1f0e3 85120a98 86478328 00000004 nt!RtlInsertElementGenericTableFullAvl+0xa7
8d317564 82a1a16f 85ec21e8 86478328 00000004 nt!RtlInsertElementGenericTableAvl+0x28
8d317580 82a1a056 00000515 85eb9678 900fb440 nt!VfAvlInsertReservedTreeNode+0x2b
8d31759c 82bc77e0 9083d000 00515000 00000000 nt!VfTargetDriversAdd+0xa6
8d3175b4 82bc5718 00000000 00000000 00000000 nt!VfDriverLoadImage+0x36
8d3175f8 82bc52ec 900fb440 8d317800 8d317668 nt!MiDriverLoadSucceeded+0x2f
8d317678 82ba42c0 8d317800 00000000 00000000 nt!MmLoadSystemImage+0x6e1
8d31786c 82babfe7 00000000 00000000 8d317894 nt!IopLoadDriver+0x386
8d317918 82bf0e4e 900f9778 00000001 900f9764 nt!PipCallDriverAddDeviceQueryRoutine+0x34b
8d317950 82bf90a2 00000001 8d317a1c c0000034 nt!RtlpCallQueryRegistryRoutine+0x2cd
8d3179bc 82ba9108 40000000 80000164 8d317a38 nt!RtlQueryRegistryValues+0x31d
8d317a98 82ba8876 85eeb008 8d317cc8 00000000 nt!PipCallDriverAddDevice+0x383
8d317c94 82b8ca2a 851fe518 86468b00 8d317cc8 nt!PipProcessDevNodeTree+0x15d
8d317cd4 82a14f99 86468b00 82b64e80 851dad48 nt!PiProcessStartSystemDevices+0x6d
8d317d00 82a6ef2b 00000000 00000000 851dad48 nt!PnpDeviceActionWorker+0x241
8d317d50 82c0f66d 00000001 a6568918 00000000 nt!ExpWorkerThread+0x10d
8d317d90 82ac10d9 82a6ee1e 00000001 00000000 nt!PspSystemThreadStartup+0x9e
start    end        module name
80ba8000 80bb0000   kdcom    kdcom.dll    Mon Jul 13 21:08:58 2009 (4A5BDAAA)
82a01000 82e11000   nt       ntkrpamp.exe Mon Jul 13 19:15:19 2009 (4A5BC007)
82e11000 82e48000   hal      halmacpi.dll Mon Jul 13 19:11:03 2009 (4A5BBF07)
8ac02000 8ac7a000   mcupdate_GenuineIntel mcupdate_GenuineIntel.dll Mon Jul 13 21:06:41 2009 (4A5BDA21)
8ac7a000 8ac8b000   PSHED    PSHED.dll    Mon Jul 13 21:09:36 2009 (4A5BDAD0)
8ac8b000 8ac93000   BOOTVID  BOOTVID.dll  Mon Jul 13 21:04:34 2009 (4A5BD9A2)
8ac93000 8acd5000   CLFS     CLFS.SYS     Mon Jul 13 19:11:10 2009 (4A5BBF0E)
8acd5000 8ad80000   CI       CI.dll       Mon Jul 13 21:09:28 2009 (4A5BDAC8)
8ad80000 8adf1000   Wdf01000 Wdf01000.sys Mon Jul 13 19:11:36 2009 (4A5BBF28)
8adf1000 8adff000   WDFLDR   WDFLDR.SYS   Mon Jul 13 19:11:25 2009 (4A5BBF1D)
8ae00000 8ae10000   volmgr   volmgr.sys   Mon Jul 13 19:11:25 2009 (4A5BBF1D)
8ae2b000 8af1e000   sptd     sptd.sys     Sun Oct 11 16:54:02 2009 (4AD245EA)
8af1e000 8af27000   WMILIB   WMILIB.SYS   Mon Jul 13 19:11:22 2009 (4A5BBF1A)
8af27000 8af4d000   SCSIPORT SCSIPORT.SYS Mon Jul 13 19:45:55 2009 (4A5BC733)
8af4d000 8af95000   ACPI     ACPI.sys     Mon Jul 13 19:11:11 2009 (4A5BBF0F)
8af95000 8af9d000   msisadrv msisadrv.sys Mon Jul 13 19:11:09 2009 (4A5BBF0D)
8af9d000 8afa8000   vdrvroot vdrvroot.sys Mon Jul 13 19:46:19 2009 (4A5BC74B)
8afa8000 8afd2000   pci      pci.sys      Mon Jul 13 19:11:16 2009 (4A5BBF14)
8afd2000 8afe3000   partmgr  partmgr.sys  Mon Jul 13 19:11:35 2009 (4A5BBF27)
8afe3000 8afeb000   compbatt compbatt.sys Mon Jul 13 19:19:18 2009 (4A5BC0F6)
8afeb000 8aff6000   BATTC    BATTC.SYS    Mon Jul 13 19:19:15 2009 (4A5BC0F3)
8b000000 8b021000   tunnel   tunnel.sys   Mon Jul 13 19:54:03 2009 (4A5BC91B)
8b030000 8b07b000   volmgrx  volmgrx.sys  Mon Jul 13 19:11:41 2009 (4A5BBF2D)
8b07b000 8b091000   mountmgr mountmgr.sys Mon Jul 13 19:11:27 2009 (4A5BBF1F)
8b091000 8b09a000   atapi    atapi.sys    Mon Jul 13 19:11:15 2009 (4A5BBF13)
8b09a000 8b0bd000   ataport  ataport.SYS  Mon Jul 13 19:11:18 2009 (4A5BBF16)
8b0bd000 8b0c7000   msahci   msahci.sys   Mon Jul 13 19:45:50 2009 (4A5BC72E)
8b0c7000 8b0d5000   PCIIDEX  PCIIDEX.SYS  Mon Jul 13 19:11:15 2009 (4A5BBF13)
8b0d5000 8b0de000   amdxata  amdxata.sys  Tue May 19 13:57:35 2009 (4A12F30F)
8b0de000 8b112000   fltmgr   fltmgr.sys   Mon Jul 13 19:11:13 2009 (4A5BBF11)
8b112000 8b123000   fileinfo fileinfo.sys Mon Jul 13 19:21:51 2009 (4A5BC18F)
8b123000 8b12c300   PxHelp20 PxHelp20.sys Fri May 15 17:42:35 2009 (4A0DE1CB)
8b12d000 8b1e4000   ndis     ndis.sys     Mon Jul 13 19:12:24 2009 (4A5BBF58)
8b206000 8b335000   Ntfs     Ntfs.sys     Mon Jul 13 19:12:05 2009 (4A5BBF45)
8b335000 8b360000   msrpc    msrpc.sys    Mon Jul 13 19:11:59 2009 (4A5BBF3F)
8b360000 8b373000   ksecdd   ksecdd.sys   Mon Jul 13 19:11:56 2009 (4A5BBF3C)
8b373000 8b3d0000   cng      cng.sys      Mon Jul 13 19:32:55 2009 (4A5BC427)
8b3d0000 8b3de000   pcw      pcw.sys      Mon Jul 13 19:11:10 2009 (4A5BBF0E)
8b3de000 8b3e7000   Fs_Rec   Fs_Rec.sys   Mon Jul 13 19:11:14 2009 (4A5BBF12)
8b400000 8b431000   fwpkclnt fwpkclnt.sys Mon Jul 13 19:12:03 2009 (4A5BBF43)
8b434000 8b472000   NETIO    NETIO.SYS    Mon Jul 13 19:12:35 2009 (4A5BBF63)
8b472000 8b497000   ksecpkg  ksecpkg.sys  Mon Jul 13 19:34:00 2009 (4A5BC468)
8b497000 8b5e0000   tcpip    tcpip.sys    Mon Jul 13 19:13:18 2009 (4A5BBF8E)
8b5e0000 8b5e8380   vmstorfl vmstorfl.sys Mon Jul 13 19:28:44 2009 (4A5BC32C)
8b5e9000 8b600000   tdx      tdx.sys      Mon Jul 13 19:12:10 2009 (4A5BBF4A)
8b60f000 8b64e000   volsnap  volsnap.sys  Mon Jul 13 19:11:34 2009 (4A5BBF26)
8b64e000 8b656000   spldr    spldr.sys    Mon May 11 12:13:47 2009 (4A084EBB)
8b656000 8b683000   rdyboost rdyboost.sys Mon Jul 13 19:22:02 2009 (4A5BC19A)
8b683000 8b693000   mup      mup.sys      Mon Jul 13 19:14:14 2009 (4A5BBFC6)
8b693000 8b69b000   hwpolicy hwpolicy.sys Mon Jul 13 19:11:01 2009 (4A5BBF05)
8b69b000 8b6cd000   fvevol   fvevol.sys   Mon Jul 13 19:13:01 2009 (4A5BBF7D)
8b6cd000 8b6de000   disk     disk.sys     Mon Jul 13 19:11:28 2009 (4A5BBF20)
8b6de000 8b703000   CLASSPNP CLASSPNP.SYS Mon Jul 13 19:11:20 2009 (4A5BBF18)
8b703000 8b710000   crashdmp crashdmp.sys Mon Jul 13 19:45:50 2009 (4A5BC72E)
8b710000 8b71b000   dump_dumpata dump_dumpata.sys Mon Jul 13 19:11:16 2009 (4A5BBF14)
8b71b000 8b725000   dump_msahci dump_msahci.sys Mon Jul 13 19:45:50 2009 (4A5BC72E)
8b725000 8b736000   dump_dumpfve dump_dumpfve.sys Mon Jul 13 19:12:47 2009 (4A5BBF6F)
8b736000 8b755000   cdrom    cdrom.sys    Mon Jul 13 19:11:24 2009 (4A5BBF1C)
8b755000 8b776680   MpFilter MpFilter.sys Wed Jun 10 21:04:25 2009 (4A305819)
8b777000 8b77e000   Null     Null.SYS     Mon Jul 13 19:11:12 2009 (4A5BBF10)
8b77e000 8b785000   Beep     Beep.SYS     Mon Jul 13 19:45:00 2009 (4A5BC6FC)
8b785000 8b791000   vga      vga.sys      Mon Jul 13 19:25:50 2009 (4A5BC27E)
8b791000 8b7b2000   VIDEOPRT VIDEOPRT.SYS Mon Jul 13 19:25:49 2009 (4A5BC27D)
8b7b2000 8b7bf000   watchdog watchdog.sys Mon Jul 13 19:24:10 2009 (4A5BC21A)
8b7bf000 8b7c7000   RDPCDD   RDPCDD.sys   Mon Jul 13 20:01:40 2009 (4A5BCAE4)
8b7c7000 8b7cf000   rdpencdd rdpencdd.sys Mon Jul 13 20:01:39 2009 (4A5BCAE3)
8b7cf000 8b7d7000   rdprefmp rdprefmp.sys Mon Jul 13 20:01:41 2009 (4A5BCAE5)
8b7d7000 8b7e2000   Msfs     Msfs.SYS     Mon Jul 13 19:11:26 2009 (4A5BBF1E)
8b7e2000 8b7f0000   Npfs     Npfs.SYS     Mon Jul 13 19:11:31 2009 (4A5BBF23)
8b7f0000 8b7fb000   TDI      TDI.SYS      Mon Jul 13 19:12:12 2009 (4A5BBF4C)
9021e000 90278000   afd      afd.sys      Mon Jul 13 19:12:34 2009 (4A5BBF62)
90278000 902aa000   netbt    netbt.sys    Mon Jul 13 19:12:18 2009 (4A5BBF52)
902aa000 902b1000   wfplwf   wfplwf.sys   Mon Jul 13 19:53:51 2009 (4A5BC90F)
902b1000 902d0000   pacer    pacer.sys    Mon Jul 13 19:53:58 2009 (4A5BC916)
902d0000 902de000   netbios  netbios.sys  Mon Jul 13 19:53:54 2009 (4A5BC912)
902de000 902f1000   wanarp   wanarp.sys   Mon Jul 13 19:55:02 2009 (4A5BC956)
902f1000 90301000   termdd   termdd.sys   Mon Jul 13 20:01:35 2009 (4A5BCADF)
90301000 9030ea60   SCDEmu   SCDEmu.SYS   Sun Nov 08 22:21:19 2009 (4AF78AAF)
9030f000 90350000   rdbss    rdbss.sys    Mon Jul 13 19:14:26 2009 (4A5BBFD2)
90350000 9035a000   nsiproxy nsiproxy.sys Mon Jul 13 19:12:08 2009 (4A5BBF48)
9035a000 90364000   mssmbios mssmbios.sys Mon Jul 13 19:19:25 2009 (4A5BC0FD)
90364000 90370000   discache discache.sys Mon Jul 13 19:24:04 2009 (4A5BC214)
90370000 903d4000   csc      csc.sys      Mon Jul 13 19:15:08 2009 (4A5BBFFC)
903d4000 903ec000   dfsc     dfsc.sys     Mon Jul 13 19:14:16 2009 (4A5BBFC8)
903ec000 903fa000   blbdrive blbdrive.sys Mon Jul 13 19:23:04 2009 (4A5BC1D8)
9083d000 90d52000   atikmdag atikmdag.sys Mon Aug 17 23:03:58 2009 (4A8A1A1E)

Unloaded modules:
90200000 9020c000   ATITool.sys
    Timestamp: unavailable (00000000)
    Checksum:  00000000
start    end        module name
8af4d000 8af95000   ACPI     ACPI.sys     Mon Jul 13 19:11:11 2009 (4A5BBF0F)
9021e000 90278000   afd      afd.sys      Mon Jul 13 19:12:34 2009 (4A5BBF62)
8b0d5000 8b0de000   amdxata  amdxata.sys  Tue May 19 13:57:35 2009 (4A12F30F)
8b091000 8b09a000   atapi    atapi.sys    Mon Jul 13 19:11:15 2009 (4A5BBF13)
8b09a000 8b0bd000   ataport  ataport.SYS  Mon Jul 13 19:11:18 2009 (4A5BBF16)
9083d000 90d52000   atikmdag atikmdag.sys Mon Aug 17 23:03:58 2009 (4A8A1A1E)
8afeb000 8aff6000   BATTC    BATTC.SYS    Mon Jul 13 19:19:15 2009 (4A5BC0F3)
8b77e000 8b785000   Beep     Beep.SYS     Mon Jul 13 19:45:00 2009 (4A5BC6FC)
903ec000 903fa000   blbdrive blbdrive.sys Mon Jul 13 19:23:04 2009 (4A5BC1D8)
8ac8b000 8ac93000   BOOTVID  BOOTVID.dll  Mon Jul 13 21:04:34 2009 (4A5BD9A2)
8b736000 8b755000   cdrom    cdrom.sys    Mon Jul 13 19:11:24 2009 (4A5BBF1C)
8acd5000 8ad80000   CI       CI.dll       Mon Jul 13 21:09:28 2009 (4A5BDAC8)
8b6de000 8b703000   CLASSPNP CLASSPNP.SYS Mon Jul 13 19:11:20 2009 (4A5BBF18)
8ac93000 8acd5000   CLFS     CLFS.SYS     Mon Jul 13 19:11:10 2009 (4A5BBF0E)
8b373000 8b3d0000   cng      cng.sys      Mon Jul 13 19:32:55 2009 (4A5BC427)
8afe3000 8afeb000   compbatt compbatt.sys Mon Jul 13 19:19:18 2009 (4A5BC0F6)
8b703000 8b710000   crashdmp crashdmp.sys Mon Jul 13 19:45:50 2009 (4A5BC72E)
90370000 903d4000   csc      csc.sys      Mon Jul 13 19:15:08 2009 (4A5BBFFC)
903d4000 903ec000   dfsc     dfsc.sys     Mon Jul 13 19:14:16 2009 (4A5BBFC8)
90364000 90370000   discache discache.sys Mon Jul 13 19:24:04 2009 (4A5BC214)
8b6cd000 8b6de000   disk     disk.sys     Mon Jul 13 19:11:28 2009 (4A5BBF20)
8b710000 8b71b000   dump_dumpata dump_dumpata.sys Mon Jul 13 19:11:16 2009 (4A5BBF14)
8b725000 8b736000   dump_dumpfve dump_dumpfve.sys Mon Jul 13 19:12:47 2009 (4A5BBF6F)
8b71b000 8b725000   dump_msahci dump_msahci.sys Mon Jul 13 19:45:50 2009 (4A5BC72E)
8b112000 8b123000   fileinfo fileinfo.sys Mon Jul 13 19:21:51 2009 (4A5BC18F)
8b0de000 8b112000   fltmgr   fltmgr.sys   Mon Jul 13 19:11:13 2009 (4A5BBF11)
8b3de000 8b3e7000   Fs_Rec   Fs_Rec.sys   Mon Jul 13 19:11:14 2009 (4A5BBF12)
8b69b000 8b6cd000   fvevol   fvevol.sys   Mon Jul 13 19:13:01 2009 (4A5BBF7D)
8b400000 8b431000   fwpkclnt fwpkclnt.sys Mon Jul 13 19:12:03 2009 (4A5BBF43)
82e11000 82e48000   hal      halmacpi.dll Mon Jul 13 19:11:03 2009 (4A5BBF07)
8b693000 8b69b000   hwpolicy hwpolicy.sys Mon Jul 13 19:11:01 2009 (4A5BBF05)
80ba8000 80bb0000   kdcom    kdcom.dll    Mon Jul 13 21:08:58 2009 (4A5BDAAA)
8b360000 8b373000   ksecdd   ksecdd.sys   Mon Jul 13 19:11:56 2009 (4A5BBF3C)
8b472000 8b497000   ksecpkg  ksecpkg.sys  Mon Jul 13 19:34:00 2009 (4A5BC468)
8ac02000 8ac7a000   mcupdate_GenuineIntel mcupdate_GenuineIntel.dll Mon Jul 13 21:06:41 2009 (4A5BDA21)
8b07b000 8b091000   mountmgr mountmgr.sys Mon Jul 13 19:11:27 2009 (4A5BBF1F)
8b755000 8b776680   MpFilter MpFilter.sys Wed Jun 10 21:04:25 2009 (4A305819)
8b0bd000 8b0c7000   msahci   msahci.sys   Mon Jul 13 19:45:50 2009 (4A5BC72E)
8b7d7000 8b7e2000   Msfs     Msfs.SYS     Mon Jul 13 19:11:26 2009 (4A5BBF1E)
8af95000 8af9d000   msisadrv msisadrv.sys Mon Jul 13 19:11:09 2009 (4A5BBF0D)
8b335000 8b360000   msrpc    msrpc.sys    Mon Jul 13 19:11:59 2009 (4A5BBF3F)
9035a000 90364000   mssmbios mssmbios.sys Mon Jul 13 19:19:25 2009 (4A5BC0FD)
8b683000 8b693000   mup      mup.sys      Mon Jul 13 19:14:14 2009 (4A5BBFC6)
8b12d000 8b1e4000   ndis     ndis.sys     Mon Jul 13 19:12:24 2009 (4A5BBF58)
902d0000 902de000   netbios  netbios.sys  Mon Jul 13 19:53:54 2009 (4A5BC912)
90278000 902aa000   netbt    netbt.sys    Mon Jul 13 19:12:18 2009 (4A5BBF52)
8b434000 8b472000   NETIO    NETIO.SYS    Mon Jul 13 19:12:35 2009 (4A5BBF63)
8b7e2000 8b7f0000   Npfs     Npfs.SYS     Mon Jul 13 19:11:31 2009 (4A5BBF23)
90350000 9035a000   nsiproxy nsiproxy.sys Mon Jul 13 19:12:08 2009 (4A5BBF48)
82a01000 82e11000   nt       ntkrpamp.exe Mon Jul 13 19:15:19 2009 (4A5BC007)
8b206000 8b335000   Ntfs     Ntfs.sys     Mon Jul 13 19:12:05 2009 (4A5BBF45)
8b777000 8b77e000   Null     Null.SYS     Mon Jul 13 19:11:12 2009 (4A5BBF10)
902b1000 902d0000   pacer    pacer.sys    Mon Jul 13 19:53:58 2009 (4A5BC916)
8afd2000 8afe3000   partmgr  partmgr.sys  Mon Jul 13 19:11:35 2009 (4A5BBF27)
8afa8000 8afd2000   pci      pci.sys      Mon Jul 13 19:11:16 2009 (4A5BBF14)
8b0c7000 8b0d5000   PCIIDEX  PCIIDEX.SYS  Mon Jul 13 19:11:15 2009 (4A5BBF13)
8b3d0000 8b3de000   pcw      pcw.sys      Mon Jul 13 19:11:10 2009 (4A5BBF0E)
8ac7a000 8ac8b000   PSHED    PSHED.dll    Mon Jul 13 21:09:36 2009 (4A5BDAD0)
8b123000 8b12c300   PxHelp20 PxHelp20.sys Fri May 15 17:42:35 2009 (4A0DE1CB)
9030f000 90350000   rdbss    rdbss.sys    Mon Jul 13 19:14:26 2009 (4A5BBFD2)
8b7bf000 8b7c7000   RDPCDD   RDPCDD.sys   Mon Jul 13 20:01:40 2009 (4A5BCAE4)
8b7c7000 8b7cf000   rdpencdd rdpencdd.sys Mon Jul 13 20:01:39 2009 (4A5BCAE3)
8b7cf000 8b7d7000   rdprefmp rdprefmp.sys Mon Jul 13 20:01:41 2009 (4A5BCAE5)
8b656000 8b683000   rdyboost rdyboost.sys Mon Jul 13 19:22:02 2009 (4A5BC19A)
90301000 9030ea60   SCDEmu   SCDEmu.SYS   Sun Nov 08 22:21:19 2009 (4AF78AAF)
8af27000 8af4d000   SCSIPORT SCSIPORT.SYS Mon Jul 13 19:45:55 2009 (4A5BC733)
8b64e000 8b656000   spldr    spldr.sys    Mon May 11 12:13:47 2009 (4A084EBB)
8ae2b000 8af1e000   sptd     sptd.sys     Sun Oct 11 16:54:02 2009 (4AD245EA)
8b497000 8b5e0000   tcpip    tcpip.sys    Mon Jul 13 19:13:18 2009 (4A5BBF8E)
8b7f0000 8b7fb000   TDI      TDI.SYS      Mon Jul 13 19:12:12 2009 (4A5BBF4C)
8b5e9000 8b600000   tdx      tdx.sys      Mon Jul 13 19:12:10 2009 (4A5BBF4A)
902f1000 90301000   termdd   termdd.sys   Mon Jul 13 20:01:35 2009 (4A5BCADF)
8b000000 8b021000   tunnel   tunnel.sys   Mon Jul 13 19:54:03 2009 (4A5BC91B)
8af9d000 8afa8000   vdrvroot vdrvroot.sys Mon Jul 13 19:46:19 2009 (4A5BC74B)
8b785000 8b791000   vga      vga.sys      Mon Jul 13 19:25:50 2009 (4A5BC27E)
8b791000 8b7b2000   VIDEOPRT VIDEOPRT.SYS Mon Jul 13 19:25:49 2009 (4A5BC27D)
8b5e0000 8b5e8380   vmstorfl vmstorfl.sys Mon Jul 13 19:28:44 2009 (4A5BC32C)
8ae00000 8ae10000   volmgr   volmgr.sys   Mon Jul 13 19:11:25 2009 (4A5BBF1D)
8b030000 8b07b000   volmgrx  volmgrx.sys  Mon Jul 13 19:11:41 2009 (4A5BBF2D)
8b60f000 8b64e000   volsnap  volsnap.sys  Mon Jul 13 19:11:34 2009 (4A5BBF26)
902de000 902f1000   wanarp   wanarp.sys   Mon Jul 13 19:55:02 2009 (4A5BC956)
8b7b2000 8b7bf000   watchdog watchdog.sys Mon Jul 13 19:24:10 2009 (4A5BC21A)
8ad80000 8adf1000   Wdf01000 Wdf01000.sys Mon Jul 13 19:11:36 2009 (4A5BBF28)
8adf1000 8adff000   WDFLDR   WDFLDR.SYS   Mon Jul 13 19:11:25 2009 (4A5BBF1D)
902aa000 902b1000   wfplwf   wfplwf.sys   Mon Jul 13 19:53:51 2009 (4A5BC90F)
8af1e000 8af27000   WMILIB   WMILIB.SYS   Mon Jul 13 19:11:22 2009 (4A5BBF1A)

Unloaded modules:
90200000 9020c000   ATITool.sys
    Timestamp: unavailable (00000000)
    Checksum:  00000000
Bugcheck code 0000000A
Arguments 0000313c 00000002 00000000 82ac2012
My System SpecsSystem Spec
30 Nov 2009   #10
eldora

Windows 7 Ultimate x86
 
 

Okay, i already attached the other dump files.

I already uninstall the facial recognition software, but blue screen still occurs.

The last crash dump file is the dump that record bluescreen after I remove facial recognition software

Thanks in advance
My System SpecsSystem Spec
Reply

 BSOD during Booting




Thread Tools




Similar help and support threads
Thread Forum
BSOD after booting
Hi guys i have BSOD problem with my PC, so basically i turned on the pc and goes normal, but after around 40 minutes my PC freezing, then i decided to restart, after succesful booting BSOD appear. it was so fast that i can't take a picture of it. i had used the dm collector but it seems...
BSOD Help and Support
BSOD after booting into 7
Working on a Dell Inspiron N7110 running Windows 7 Home Premium SP1. The computer will boot into Windows fine, but after about 30 seconds to a minute it will blue screen and reboot. I have re-seated the memory and run memtest, as well as Dell's built in diagnostics and everything passed. Safe mode...
BSOD Help and Support
Issue booting Win 7, booting directly into XP & no boot manager
Hi, I just got a ASUS G75V series and updated it to windows 7 professional with Intel core i7. I was able to work with it and everything was fine until I had to install XP because some softwares are not compatible with Win 7 x64. I have Win 7 on drive C: and windows xp on drive E: which in...
Installation & Setup
BSOD while doing nothing or just after booting.
Well, I've got a new copy of windows 7 (32 bit version) I have got 4 GB ram only 3,25 in use (like I had on the XP version, running on the same PC) and after I boot up the PC I just look at the desktop, play with some random games, create and delete folders, do some little stress to the RAM or...
BSOD Help and Support
BSOD During Booting-up ...
Hey guys, I need help on this issue, During starting up on my computer, when it was about to boot up, a BSOD screen appears. I could only access to Windows after the reset. This occurs alternately. Usually the error code reads 0x00000001e, but I've came across other variants of these. I...
BSOD Help and Support
BSOD when booting
I run Win 7 and I recently updated my bios from 1.3 to 1.8 on my Toshiba Satellite A305, there was a screen issue where it just turns off or freezes.. fixed that but now I get BSOD when i boot normally. Compressed 6 of the minidump files and attached the folder.
BSOD Help and Support


Our Sites

Site Links

About Us

Find Us

Windows 7 Forums is an independent web site and has not been authorized, sponsored, or otherwise approved by Microsoft Corporation. "Windows 7" and related materials are trademarks of Microsoft Corp.

Designer Media Ltd

All times are GMT -5. The time now is 19:09.
Twitter Facebook Google+ Seven Forums iOS App Seven Forums Android App