![]() |
|
|||||||
|
|
|
|
|
|
I keep getting the dreaded blue screen of death :(. I managed to pull the minidump file though, so if anyone knows hot to fix the problem that would be great. Thanks....
|
![]() |
|
|
Thread Tools |
|
#1
|
|||
|
|||
|
I keep getting the dreaded blue screen of death :(. I managed to pull the minidump file though, so if anyone knows hot to fix the problem that would be great. Thanks.
|
|
#2
|
||||||||||||
|
||||||||||||
|
whats your specs?
OS and hardware have you added any new hardware lately?
__________________
__________________
The temperature inside this apple pie is over 1000 degrees.
If I squeeze it, a jet of molten bramley apple will squirt out. Could go your way; could go mine. Either way, one of us is going down!!!! My System: Mine
|
|
#3
|
|||
|
|||
|
Sorry, thought I'd put those in already... It's Windows Vista, added some new ram the other day but the problem existed long before I did. It's just become more persistent lately.
|
|
#4
|
|||
|
|||
|
Thought I'd copy the whole of the minidump file for those of you that don't want to download it. Any help would be great:
Microsoft (R) Windows Debugger Version 6.8.0004.0 X86 Copyright (c) Microsoft Corporation. All rights reserved. Loading Dump File [C:\Users\Sean\Desktop\Mini030108-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 Vista Kernel Version 6000 MP (2 procs) Free x86 compatible Product: WinNt, suite: TerminalServer SingleUserTS Personal Kernel base = 0x81c00000 PsLoadedModuleList = 0x81d11e10 Debug session time: Sat Mar 1 09:19:10.763 2008 (GMT+0) System Uptime: 0 days 11:44:05.354 ************************************************** ******************* * 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 C5, {0, 2, 1, 81ce88d9} ***** 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 *** *** *** ************************************************** *********************** ************************************************** ******************* * 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+e88d9 ) Followup: MachineOwner --------- |
|
#5
|
|||
|
|||
|
the culprit seems to be the ntkrnlpa.exe
ive surfed for ya and its quite common but i cant find a fix what vista are you running? 32 or 64 bit how much ram have you got installed? you may have too much ram installed, its quite common with bsod
__________________
The temperature inside this apple pie is over 1000 degrees.
If I squeeze it, a jet of molten bramley apple will squirt out. Could go your way; could go mine. Either way, one of us is going down!!!! |
|
#6
|
|||
|
|||
|
along with this give the computer a good clean, dust etc
then make sure you have all new drivers for your hardware if you have only for e.g. 3gb installed on a 32 bit system vista (maximum it can use) move the ram sticks around if you have more than 3gb take it down to 3gb
__________________
The temperature inside this apple pie is over 1000 degrees.
If I squeeze it, a jet of molten bramley apple will squirt out. Could go your way; could go mine. Either way, one of us is going down!!!! |
|
#7
|
|||
|
|||
|
It's 32 bit and I have 3GB of ram all exactly the same. I need to buy some compressed air, give it a good clean. Thanks for the reply.
|
|
#8
|
|||
|
|||
|
try just moving one stick into another port
that was a simple fix that worked for me
__________________
The temperature inside this apple pie is over 1000 degrees.
If I squeeze it, a jet of molten bramley apple will squirt out. Could go your way; could go mine. Either way, one of us is going down!!!! |
|
#9
|
|||
|
|||
|
Found that the error is caused by some software I have, it only occurs after a few minutes of It being turned on. Tried uninstalling and re-installing it, that didn't do a thing.
|
|
#10
|
|||
|
|||
|
yeh i tried researching that .exe file that was stated but found lots of problems of bsod but no solutions
ill let ya know if i find sumit
__________________
The temperature inside this apple pie is over 1000 degrees.
If I squeeze it, a jet of molten bramley apple will squirt out. Could go your way; could go mine. Either way, one of us is going down!!!! |
![]() |
|
| Bookmarks |
Similar Threads
|
||||
| Thread | Thread Starter | Forum | Replies | Last Post |
| BSOD Help | xsonarx | Windows Operating Systems | 10 | 2nd Dec 2008 08:34 |
| Bsod | carpious | General Hardware Chat | 1 | 26th Sep 2008 06:12 |
| Bsod | manojneo | Windows Operating Systems | 5 | 14th Jun 2008 13:46 |
| BSOD.....being a sod | alex | Windows Operating Systems | 2 | 12th Jul 2007 07:37 |
| Thread Tools | |
|
|