New
#21
run this from cmd prompt as Admin"
slmgr.vbs -dlv
wait for popup and see what it says.
Random rebooting
-
-
New #22
The minidumps all show a STOP 0x124 (WHEA) error.
This is primarily a hardware error, but it's generated by the CPU rather than Windows (so analysis is beyond my abilities).
Here's a summary. The error messages about symbols are typical with Win7. The only things that change are the date stamps and the 2nd parameter of the error:
Here's the last memory dump file:Code:*** WARNING: Unable to verify timestamp for ntoskrnl.exe *** ERROR: Module load completed but symbols could not be loaded for ntoskrnl.exe Debug session time: Mon Jun 8 08:02:13.036 2009 (GMT-4) System Uptime: 0 days 0:00:07.378 *** WARNING: Unable to verify timestamp for ntoskrnl.exe *** ERROR: Module load completed but symbols could not be loaded for ntoskrnl.exe BugCheck 124, {0, 8671a8fc, 0, 0} *** WARNING: Unable to verify timestamp for PSHED.dll *** ERROR: Module load completed but symbols could not be loaded for PSHED.dll Probably caused by : hardware
So, the most likely problem is hardware. It's likely to be:Code:Microsoft (R) Windows Debugger Version 6.11.0001.404 AMD64 Copyright (c) Microsoft Corporation. All rights reserved. Loading Dump File [C:\Users\FUBAR-RC1-Desktop\TempDUMP\DATA\10.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: Unable to load image ntoskrnl.exe, Win32 error 0n2 *** WARNING: Unable to verify timestamp for ntoskrnl.exe *** ERROR: Module load completed but symbols could not be loaded for ntoskrnl.exe Windows 7 Kernel Version 7100 MP (2 procs) Free x86 compatible Product: WinNt, suite: TerminalServer SingleUserTS Machine Name: Kernel base = 0x82a55000 PsLoadedModuleList = 0x82b9d810 Debug session time: Mon Jun 8 08:02:13.036 2009 (GMT-4) System Uptime: 0 days 0:00:07.378 Unable to load image ntoskrnl.exe, Win32 error 0n2 *** WARNING: Unable to verify timestamp for ntoskrnl.exe *** ERROR: Module load completed but symbols could not be loaded for ntoskrnl.exe Loading Kernel Symbols ................................................... Loading User Symbols Mini Kernel Dump does not contain unloaded driver list ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* Use !analyze -v to get detailed debugging information. BugCheck 124, {0, 8671a8fc, 0, 0} ***** 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!_WHEA_ERROR_RECORD_HEADER *** *** *** ************************************************************************* ************************************************************************* *** *** *** *** *** 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!_WHEA_ERROR_RECORD_HEADER *** *** *** ************************************************************************* Unable to load image PSHED.dll, Win32 error 0n2 *** WARNING: Unable to verify timestamp for PSHED.dll *** ERROR: Module load completed but symbols could not be loaded for PSHED.dll ************************************************************************* *** *** *** *** *** 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: pshed!_WHEA_ERROR_RECORD_HEADER *** *** *** ************************************************************************* ************************************************************************* *** *** *** *** *** 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: pshed!_WHEA_ERROR_RECORD_SECTION_DESCRIPTOR *** *** *** ************************************************************************* ************************************************************************* *** *** *** *** *** 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: pshed!_WHEA_ERROR_RECORD_HEADER *** *** *** ************************************************************************* ************************************************************************* *** *** *** *** *** 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: pshed!_WHEA_ERROR_RECORD_HEADER *** *** *** ************************************************************************* ************************************************************************* *** *** *** *** *** 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: pshed!_WHEA_ERROR_RECORD_HEADER *** *** *** ************************************************************************* ************************************************************************* *** *** *** *** *** 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 *** *** *** ************************************************************************* Probably caused by : hardware Followup: MachineOwner --------- 1: kd> !thread;!analyze -v;r;kv;lmtn;lmtsmn;.bugcheck;.logclose;q GetPointerFromAddress: unable to read from 82bbd71c ************************************************************************* *** *** *** *** *** 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!_ETHREAD *** *** *** ************************************************************************* 857f0920: Unable to get thread contents ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* WHEA_UNCORRECTABLE_ERROR (124) A fatal hardware error has occurred. Parameter 1 identifies the type of error source that reported the error. Parameter 2 holds the address of the WHEA_ERROR_RECORD structure that describes the error conditon. Arguments: Arg1: 00000000, Machine Check Exception Arg2: 8671a8fc, Address of the WHEA_ERROR_RECORD structure. Arg3: 00000000, High order 32-bits of the MCi_STATUS value. Arg4: 00000000, Low order 32-bits of the MCi_STATUS value. Debugging Details: ------------------ ***** 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!_WHEA_ERROR_RECORD_HEADER *** *** *** ************************************************************************* ************************************************************************* *** *** *** *** *** 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!_WHEA_ERROR_RECORD_HEADER *** *** *** ************************************************************************* ************************************************************************* *** *** *** *** *** 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: pshed!_WHEA_ERROR_RECORD_HEADER *** *** *** ************************************************************************* ************************************************************************* *** *** *** *** *** 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: pshed!_WHEA_ERROR_RECORD_SECTION_DESCRIPTOR *** *** *** ************************************************************************* ************************************************************************* *** *** *** *** *** 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: pshed!_WHEA_ERROR_RECORD_HEADER *** *** *** ************************************************************************* ************************************************************************* *** *** *** *** *** 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: pshed!_WHEA_ERROR_RECORD_HEADER *** *** *** ************************************************************************* ************************************************************************* *** *** *** *** *** 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: pshed!_WHEA_ERROR_RECORD_HEADER *** *** *** ************************************************************************* ************************************************************************* *** *** *** *** *** 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 *** *** *** ************************************************************************* ADDITIONAL_DEBUG_TEXT: Use '!findthebuild' command to search for the target build information. If the build information is available, run '!findthebuild -s ; .reload' to set symbol path and load symbols. FAULTING_MODULE: 82a55000 nt DEBUG_FLR_IMAGE_TIMESTAMP: 0 BUGCHECK_STR: 0x124_GenuineIntel DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT CURRENT_IRQL: 0 STACK_TEXT: WARNING: Stack unwind information not available. Following frames may be wrong. 8dd27cc4 82b23705 8671a8e0 82bbcc28 82bbcc20 nt+0x3214a3 8dd27ce4 82b2452f 82bbcc20 8671a8e0 82bbcc50 nt+0xce705 8dd27d00 82ab3b3f 82bbcc20 00000000 857f0920 nt+0xcf52f 8dd27d50 82c4fbc3 00000001 bffd2065 00000000 nt+0x5eb3f 8dd27d90 82b12e29 82ab3a32 00000001 00000000 nt+0x1fabc3 00000000 00000000 00000000 00000000 00000000 nt+0xbde29 STACK_COMMAND: kb FOLLOWUP_NAME: MachineOwner MODULE_NAME: hardware IMAGE_NAME: hardware BUCKET_ID: WRONG_SYMBOLS Followup: MachineOwner --------- eax=8dd279d8 ebx=00000000 ecx=00000002 edx=00000000 esi=867cb000 edi=8671a8fc eip=82d764a3 esp=8dd27cb8 ebp=8dd27cc4 iopl=0 nv up ei ng nz na pe nc cs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000 efl=00200286 nt+0x3214a3: 82d764a3 894508 mov dword ptr [ebp+8],eax ss:0010:8dd27ccc=8671a8e0 ChildEBP RetAddr Args to Child WARNING: Stack unwind information not available. Following frames may be wrong. 8dd27cc4 82b23705 8671a8e0 82bbcc28 82bbcc20 nt+0x3214a3 8dd27ce4 82b2452f 82bbcc20 8671a8e0 82bbcc50 nt+0xce705 8dd27d00 82ab3b3f 82bbcc20 00000000 857f0920 nt+0xcf52f 8dd27d50 82c4fbc3 00000001 bffd2065 00000000 nt+0x5eb3f 8dd27d90 82b12e29 82ab3a32 00000001 00000000 nt+0x1fabc3 00000000 00000000 00000000 00000000 00000000 nt+0xbde29 start end module name 80bbf000 80bc7000 kdcom kdcom.dll Wed Apr 22 01:07:23 2009 (49EEA60B) 82a1e000 82a55000 hal hal.dll Tue Apr 21 23:08:30 2009 (49EE8A2E) 82a55000 82e64000 nt ntoskrnl.exe Tue Apr 21 23:13:18 2009 (49EE8B4E) 83408000 83479000 mcupdate mcupdate.dll Wed Apr 22 01:05:20 2009 (49EEA590) 83479000 8348a000 PSHED PSHED.dll Wed Apr 22 01:09:07 2009 (49EEA673) 8348a000 83492000 BOOTVID BOOTVID.dll Wed Apr 22 01:01:42 2009 (49EEA4B6) 83492000 834d4000 CLFS CLFS.SYS Tue Apr 21 23:08:36 2009 (49EE8A34) 834d4000 8357f000 CI CI.dll Wed Apr 22 01:08:59 2009 (49EEA66B) 8357f000 835f0000 Wdf01000 Wdf01000.sys Tue Apr 21 23:09:01 2009 (49EE8A4D) 835f0000 835fe000 WDFLDR WDFLDR.SYS Tue Apr 21 23:08:47 2009 (49EE8A3F) 836ed000 836f6000 WMILIB WMILIB.SYS Tue Apr 21 23:08:46 2009 (49EE8A3E) 836f6000 8371c000 SPTD4701 SPTD4701.SYS Tue Apr 21 23:44:24 2009 (49EE9298) 8371c000 83764000 ACPI ACPI.sys Tue Apr 21 23:08:37 2009 (49EE8A35) 83764000 8376c000 msisadrv msisadrv.sys Tue Apr 21 23:08:33 2009 (49EE8A31) 8376c000 83796000 pci pci.sys Tue Apr 21 23:08:40 2009 (49EE8A38) 83796000 837a1000 vdrvroot vdrvroot.sys Tue Apr 21 23:44:49 2009 (49EE92B1) 837a1000 837b2000 partmgr partmgr.sys Tue Apr 21 23:08:57 2009 (49EE8A49) 837b2000 837c2000 volmgr volmgr.sys Tue Apr 21 23:08:47 2009 (49EE8A3F) 837c2000 83800000 NETIO NETIO.SYS Tue Apr 21 23:10:05 2009 (49EE8A8D) 8ba00000 8ba25000 ksecpkg ksecpkg.sys Tue Apr 21 23:32:15 2009 (49EE8FBF) 8ba37000 8ba82000 volmgrx volmgrx.sys Tue Apr 21 23:09:06 2009 (49EE8A52) 8ba82000 8ba89000 pciide pciide.sys Tue Apr 21 23:08:44 2009 (49EE8A3C) 8ba89000 8ba97000 PCIIDEX PCIIDEX.SYS Tue Apr 21 23:08:40 2009 (49EE8A38) 8ba97000 8baad000 mountmgr mountmgr.sys Tue Apr 21 23:08:51 2009 (49EE8A43) 8baad000 8bab6000 atapi atapi.sys Tue Apr 21 23:08:39 2009 (49EE8A37) 8bab6000 8bad9000 ataport ataport.SYS Tue Apr 21 23:08:42 2009 (49EE8A3A) 8bad9000 8bae2000 amdxata amdxata.sys Tue Mar 10 19:22:16 2009 (49B6F628) 8bae2000 8bb16000 fltmgr fltmgr.sys Tue Apr 21 23:08:39 2009 (49EE8A37) 8bb16000 8bb27000 fileinfo fileinfo.sys Tue Apr 21 23:19:22 2009 (49EE8CBA) 8bb27000 8bb30200 PxHelp20 PxHelp20.sys Wed Mar 12 21:57:44 2008 (47D88A18) 8bb31000 8bbe8000 ndis ndis.sys Tue May 12 22:31:34 2009 (4A0A3106) 8bc00000 8bc0e000 pcw pcw.sys Tue Apr 21 23:08:34 2009 (49EE8A32) 8bc0e000 8bc17000 Fs_Rec Fs_Rec.sys Tue Apr 21 23:08:38 2009 (49EE8A36) 8bc17000 8bc27000 mup mup.sys Tue Apr 21 23:11:32 2009 (49EE8AE4) 8bc2a000 8bd59000 Ntfs Ntfs.sys Tue Apr 21 23:09:31 2009 (49EE8A6B) 8bd59000 8bd84000 msrpc msrpc.sys Tue Apr 21 23:09:19 2009 (49EE8A5F) 8bd84000 8bd97000 ksecdd ksecdd.sys Tue Apr 21 23:09:16 2009 (49EE8A5C) 8bd97000 8bdf4000 cng cng.sys Tue Apr 21 23:31:04 2009 (49EE8F78) 8be00000 8be2d000 rdyboost rdyboost.sys Tue Apr 21 23:19:32 2009 (49EE8CC4) 8be32000 8bf77000 tcpip tcpip.sys Tue May 12 22:32:47 2009 (4A0A314F) 8bf77000 8bfa8000 fwpkclnt fwpkclnt.sys Tue Apr 21 23:09:26 2009 (49EE8A66) 8bfa8000 8bfb0380 vmstorfl vmstorfl.sys Tue Apr 21 23:26:29 2009 (49EE8E65) 8bfb1000 8bfef000 volsnap volsnap.sys Tue Apr 21 23:08:58 2009 (49EE8A4A) 8bfef000 8bff7000 spldr spldr.sys Wed Mar 25 15:16:08 2009 (49CA82F8) 8bff7000 8bfff000 hwpolicy hwpolicy.sys Tue Apr 21 23:08:27 2009 (49EE8A2B) 8c027000 8c059000 fvevol fvevol.sys Tue Apr 21 23:10:25 2009 (49EE8AA1) 8c059000 8c06a000 disk disk.sys Tue Apr 21 23:08:52 2009 (49EE8A44) 8c06a000 8c08f000 CLASSPNP CLASSPNP.SYS Tue Apr 21 23:08:43 2009 (49EE8A3B) 8c08f000 8c09c000 crashdmp crashdmp.sys Tue Apr 21 23:44:19 2009 (49EE9293) 8c09c000 8c0a7000 dump_ataport dump_ataport.sys Tue Apr 21 23:08:41 2009 (49EE8A39) 8c0a7000 8c0b0000 dump_atapi dump_atapi.sys Tue Apr 21 23:08:39 2009 (49EE8A37) 8c0b0000 8c0c1000 dump_dumpfve dump_dumpfve.sys Tue Apr 21 23:10:11 2009 (49EE8A93) Mini Kernel Dump does not contain unloaded driver list start end module name 8371c000 83764000 ACPI ACPI.sys Tue Apr 21 23:08:37 2009 (49EE8A35) 8bad9000 8bae2000 amdxata amdxata.sys Tue Mar 10 19:22:16 2009 (49B6F628) 8baad000 8bab6000 atapi atapi.sys Tue Apr 21 23:08:39 2009 (49EE8A37) 8bab6000 8bad9000 ataport ataport.SYS Tue Apr 21 23:08:42 2009 (49EE8A3A) 8348a000 83492000 BOOTVID BOOTVID.dll Wed Apr 22 01:01:42 2009 (49EEA4B6) 834d4000 8357f000 CI CI.dll Wed Apr 22 01:08:59 2009 (49EEA66B) 8c06a000 8c08f000 CLASSPNP CLASSPNP.SYS Tue Apr 21 23:08:43 2009 (49EE8A3B) 83492000 834d4000 CLFS CLFS.SYS Tue Apr 21 23:08:36 2009 (49EE8A34) 8bd97000 8bdf4000 cng cng.sys Tue Apr 21 23:31:04 2009 (49EE8F78) 8c08f000 8c09c000 crashdmp crashdmp.sys Tue Apr 21 23:44:19 2009 (49EE9293) 8c059000 8c06a000 disk disk.sys Tue Apr 21 23:08:52 2009 (49EE8A44) 8c0a7000 8c0b0000 dump_atapi dump_atapi.sys Tue Apr 21 23:08:39 2009 (49EE8A37) 8c09c000 8c0a7000 dump_ataport dump_ataport.sys Tue Apr 21 23:08:41 2009 (49EE8A39) 8c0b0000 8c0c1000 dump_dumpfve dump_dumpfve.sys Tue Apr 21 23:10:11 2009 (49EE8A93) 8bb16000 8bb27000 fileinfo fileinfo.sys Tue Apr 21 23:19:22 2009 (49EE8CBA) 8bae2000 8bb16000 fltmgr fltmgr.sys Tue Apr 21 23:08:39 2009 (49EE8A37) 8bc0e000 8bc17000 Fs_Rec Fs_Rec.sys Tue Apr 21 23:08:38 2009 (49EE8A36) 8c027000 8c059000 fvevol fvevol.sys Tue Apr 21 23:10:25 2009 (49EE8AA1) 8bf77000 8bfa8000 fwpkclnt fwpkclnt.sys Tue Apr 21 23:09:26 2009 (49EE8A66) 82a1e000 82a55000 hal hal.dll Tue Apr 21 23:08:30 2009 (49EE8A2E) 8bff7000 8bfff000 hwpolicy hwpolicy.sys Tue Apr 21 23:08:27 2009 (49EE8A2B) 80bbf000 80bc7000 kdcom kdcom.dll Wed Apr 22 01:07:23 2009 (49EEA60B) 8bd84000 8bd97000 ksecdd ksecdd.sys Tue Apr 21 23:09:16 2009 (49EE8A5C) 8ba00000 8ba25000 ksecpkg ksecpkg.sys Tue Apr 21 23:32:15 2009 (49EE8FBF) 83408000 83479000 mcupdate mcupdate.dll Wed Apr 22 01:05:20 2009 (49EEA590) 8ba97000 8baad000 mountmgr mountmgr.sys Tue Apr 21 23:08:51 2009 (49EE8A43) 83764000 8376c000 msisadrv msisadrv.sys Tue Apr 21 23:08:33 2009 (49EE8A31) 8bd59000 8bd84000 msrpc msrpc.sys Tue Apr 21 23:09:19 2009 (49EE8A5F) 8bc17000 8bc27000 mup mup.sys Tue Apr 21 23:11:32 2009 (49EE8AE4) 8bb31000 8bbe8000 ndis ndis.sys Tue May 12 22:31:34 2009 (4A0A3106) 837c2000 83800000 NETIO NETIO.SYS Tue Apr 21 23:10:05 2009 (49EE8A8D) 82a55000 82e64000 nt ntoskrnl.exe Tue Apr 21 23:13:18 2009 (49EE8B4E) 8bc2a000 8bd59000 Ntfs Ntfs.sys Tue Apr 21 23:09:31 2009 (49EE8A6B) 837a1000 837b2000 partmgr partmgr.sys Tue Apr 21 23:08:57 2009 (49EE8A49) 8376c000 83796000 pci pci.sys Tue Apr 21 23:08:40 2009 (49EE8A38) 8ba82000 8ba89000 pciide pciide.sys Tue Apr 21 23:08:44 2009 (49EE8A3C) 8ba89000 8ba97000 PCIIDEX PCIIDEX.SYS Tue Apr 21 23:08:40 2009 (49EE8A38) 8bc00000 8bc0e000 pcw pcw.sys Tue Apr 21 23:08:34 2009 (49EE8A32) 83479000 8348a000 PSHED PSHED.dll Wed Apr 22 01:09:07 2009 (49EEA673) 8bb27000 8bb30200 PxHelp20 PxHelp20.sys Wed Mar 12 21:57:44 2008 (47D88A18) 8be00000 8be2d000 rdyboost rdyboost.sys Tue Apr 21 23:19:32 2009 (49EE8CC4) 8bfef000 8bff7000 spldr spldr.sys Wed Mar 25 15:16:08 2009 (49CA82F8) 836f6000 8371c000 SPTD4701 SPTD4701.SYS Tue Apr 21 23:44:24 2009 (49EE9298) 8be32000 8bf77000 tcpip tcpip.sys Tue May 12 22:32:47 2009 (4A0A314F) 83796000 837a1000 vdrvroot vdrvroot.sys Tue Apr 21 23:44:49 2009 (49EE92B1) 8bfa8000 8bfb0380 vmstorfl vmstorfl.sys Tue Apr 21 23:26:29 2009 (49EE8E65) 837b2000 837c2000 volmgr volmgr.sys Tue Apr 21 23:08:47 2009 (49EE8A3F) 8ba37000 8ba82000 volmgrx volmgrx.sys Tue Apr 21 23:09:06 2009 (49EE8A52) 8bfb1000 8bfef000 volsnap volsnap.sys Tue Apr 21 23:08:58 2009 (49EE8A4A) 8357f000 835f0000 Wdf01000 Wdf01000.sys Tue Apr 21 23:09:01 2009 (49EE8A4D) 835f0000 835fe000 WDFLDR WDFLDR.SYS Tue Apr 21 23:08:47 2009 (49EE8A3F) 836ed000 836f6000 WMILIB WMILIB.SYS Tue Apr 21 23:08:46 2009 (49EE8A3E) Mini Kernel Dump does not contain unloaded driver list Bugcheck code 00000124 Arguments 00000000 8671a8fc 00000000 00000000
- a hardware failure
- a hardware incompatibility
- a driver incompatibility
- other stuff :)
-
New #23
Because the memory dump file states "Vista Driver Fault", I'd wonder if running Driver Verifier would help isolate the driver that's at fault.
If you're interested in trying that, please read the following entry in it's entirety before starting:
Using Driver Verifier is an iffy proposition. Most times it'll crash and it'll tell you what the driver is. But sometimes it'll crash and won't tell you the driver. Other times it'll crash before you can log in to Windows. If you can't get to Safe Mode, then you'll have to resort to offline editing of the registry to disable Driver Verifier.
So, I'd suggest that you first backup your stuff and then make sure you've got access to another computer so you can contact us if problems arise. Then make a System Restore point (so you can restore the system using the Vista Startup Repair feature).
Then, here's the procedure:
- Go to Start and type in "verifier" (without the quotes) and press Enter
- Select "Create custom settings (for code developers)" and click "Next"
- Select "Select individual settings from a full list" and click "Next"
- Select everything EXCEPT FOR "Low Resource Simulation" and click "Next"
- Select "Automatically select unsigned drivers" and click "Next"
If no drivers show up, then select "Select driver names from a list" and click "Next"
Then select all drivers NOT provided by Microsoft and click "Next"
- Select "Finish" on the next page.
Reboot the system and wait for it to crash to the Blue Screen.
Reboot into Windows, turn off Driver Verifier by going back in and selecting "Delete existing settings" on the first page, then locate and zip up the memory dump file and upload it with your next post.
If you can't get into Windows because it crashes too soon, try it in Safe Mode.
If you can't get into Safe Mode, try using System Restore from your installation DVD to set the system back to the previous restore point that you created.
If that doesn't work, post back and we'll have to see about fixing the registry entry off-line.
-
New #24
System Restore from command line
You might also try boot to DVD, when ask options enter DOS cmd.
type the following: if your drive for Win7 is not C:\ change to what it is.
System Restore from command line:
rstrui.exe /offline:C:\windows
-
New #25
Attached is an slmgr screenshot...
As for hardware issues, it could be the video card driver, but I have downloaded the Windows 7 recommended driver for my HD4870.
Quote
Related Discussions