transam25
asked on
BSOD Stop Error
I cannot find anything for the BSOD issue. Here is the dump file. Anyone have an idea?
Microsoft (R) Windows Debugger Version 6.12.0002.633 X86
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [C:\Users\melissar\Desktop
Mini Kernel Dump File: Only registers and stack trace are available
Symbol search path is: SRV*c:\symbols*http://msdl.microsoft.com/download/symbols;C:\Users\melissar\Symbols
Executable search path is:
Windows 7 Kernel Version 7601 (Service Pack 1) MP (2 procs) Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7601.17803.x86fre.win7sp1_
Machine Name:
Kernel base = 0x82c52000 PsLoadedModuleList = 0x82d9b4d0
Debug session time: Mon Aug 27 10:05:30.813 2012 (UTC - 5:00)
System Uptime: 4 days 0:01:57.436
Loading Kernel Symbols
..........................
..........................
..........................
Loading User Symbols
Loading unloaded module list
..........................
Microsoft (R) Windows Debugger Version 6.12.0002.633 X86
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [C:\Users\melissar\Desktop
Mini Kernel Dump File: Only registers and stack trace are available
Symbol search path is: SRV*c:\symbols*http://msdl.microsoft.com/download/symbols;C:\Users\melissar\Symbols
Executable search path is:
Windows 7 Kernel Version 7601 (Service Pack 1) MP (2 procs) Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7601.17803.x86fre.win7sp1_
Machine Name:
Kernel base = 0x82c52000 PsLoadedModuleList = 0x82d9b4d0
Debug session time: Mon Aug 27 10:05:30.813 2012 (UTC - 5:00)
System Uptime: 4 days 0:01:57.436
Loading Kernel Symbols
..........................
..........................
..........................
Loading User Symbols
Loading unloaded module list
..........................
rindi
Where is the dump file? This is just the beginning of what the debugger loads the file. Just attach the dump file itself, or better zip the last 3 and attach the zip file.
ASKER
Hmmm, that is all that loaded. Here is the dump file.
Is it a full dump, not a minidump? A full dump can be too large to attach. Set your system to create small memory dumps, they are enough, and then wait for the next crash.
ASKER
dump file
082712-68921-01.dmp
082712-68921-01.dmp
It doesn't load properly on my system either. Possibly the dump couldn't finish writing itself to disk. Make sure you now set the system for minidumps, and then wait until you have at least 3 of them, as one crash alone can be a coincidence, it is always better to have several to compare with, and then zip them and attach them.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
See my answer.