Your last dump file that you attached is a build that was leaked by Microsoft on July 10,2009 (ww.mydigitallife.info/2009/07/14/7600-16384-may-not-be-the-final-windows-7-rtm-build-version/). The timestamp is in the build number 090710-1945 (July 10,2009 at 19:45).
If you downloaded it from Technet then I would go back and get the 16385 build.
I can not post links so I had to leave one of the w's off the link, if you are having trouble with it.
I underlined the date of your dump in the code box. It was the last one you attached.
If you downloaded it from Technet then I would go back and get the 16385 build.
I can not post links so I had to leave one of the w's off the link, if you are having trouble with it.
I underlined the date of your dump in the code box. It was the last one you attached.
Code:
Microsoft (R) Windows Debugger Version 6.11.0001.404 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [C:\Users\Webscaper\AppData\Local\Temp\Rar$DI00.446\[U]040710-16036-01.dmp[/U]]
Mini Kernel Dump File: Only registers and stack trace are available
Symbol search path is:
Executable search path is:
Unable to load image 赈儕ﻻ䣿躋ø, Win32 error 0n2
*** WARNING: Unable to verify timestamp for 赈儕ﻻ䣿躋ø
*** ERROR: Module load completed but symbols could not be loaded for 赈儕ﻻ䣿躋ø
Windows 7 Kernel Version 7600 MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7600.16384.amd64fre.win7_rtm.090710-1945
Machine Name:
Kernel base = 0xfffff800`02c62000 PsLoadedModuleList = 0xfffff800`02e9fe50
Debug session time: Wed Apr 7 15:11:04.259 2010 (GMT-4)
System Uptime: 0 days 0:01:16.945
Unable to load image 赈儕ﻻ䣿躋ø, Win32 error 0n2
*** WARNING: Unable to verify timestamp for 赈儕ﻻ䣿躋ø
*** ERROR: Module load completed but symbols could not be loaded for 赈儕ﻻ䣿躋ø
Loading Kernel Symbols
.................................................Unable to load image Unknown_Module_00000000`00000000, Win32 error 0n2
*** WARNING: Unable to verify timestamp for Unknown_Module_00000000`00000000
Unable to add module at 00000000`00000000
Loading User Symbols
Missing image name, possible paged-out or corrupt data.
Loading unloaded module list
.Missing image name, possible paged-out or corrupt data.
.Missing image name, possible paged-out or corrupt data.
...Missing image name, possible paged-out or corrupt data.
.....Missing image name, possible paged-out or corrupt data.
Missing image name, possible paged-out or corrupt data.
.Missing image name, possible paged-out or corrupt data.
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 1E, {0, 0, 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!_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 : ?????_ ( nt+7fa3a )
Followup: MachineOwner
---------