New
#1
BSOD caused by ntoskrnl.exe
Hello,
I have a problem and I hope you can help. Thank you in advance :)
I am running
AMD Athlon(tm) 7850 Dual-Core Processor
4,00 GB RAM
Asus M2N68-AM SE2 motherboard
NVIDIA GeForce 9400 GT 1gb
I have a pretty disturbing Problem with my Computer for some time. I am becoming irregularly BSOD.
I was running a windows XP 32 bit OS, and I had problems with the sound and with different drivers. I became a some BSOD and the cause according to the WDK (Windows Debugging Tools) minidump check was the driver of my TV-USB Stick, then of my wireless-n usb stick and at the end
ntoskrnl.exe. At some point I even lost my HDD. As I started the computer the HDD couldn't be find. I have tested it on another computer and it was found. Well I bought a new one for my PC and installed my XP again, but I got again the BSODs. At the end I thought that my 32 bit XP doesn't work good on my system.
I got an Windows 7 Professional 64 bit licence through my University. I have formatted the HDD and installed the brand new Windows 7 64 bit OS. I was running the computer for a good 2 days. I managed to install and prepare everything as it should be (latest updates etc.).
And today I got a new BSOD. I opened the minidump with the WDK and the cause is ntoskrnl.exe
What is actually doing this ntoskrnl.exe ? Why am do I still become this BSOD ?
I have tested my memory with memtest and other programs. Everything is ok. I have also checked my brand new HDD, and everything is ok.
I am going even a little crazy thinking of BIOS Viruses. I need the PC for my research at the university and so on. I can't lose it.
Here what I get by opening the minidump with WDK. (you can find the minidump attached)
Microsoft (R) Windows Debugger Version 6.12.0002.633 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [E:\Mini Dump Win 7\050810-18252-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\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 7600 MP (2 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7600.16539.amd64fre.win7_gdr.100226-1909
Machine Name:
Kernel base = 0xfffff800`0281c000 PsLoadedModuleList = 0xfffff800`02a59e50
Debug session time: Sat May *8 20:26:01.208 2010 (UTC + 2:00)
System Uptime: 0 days 3:57:13.018
*********************************************************************
* 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\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
Loading unloaded module list
...........
*******************************************************************************
* * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * *
* * * * * * * * * * * * *Bugcheck Analysis * * * * * * * * * * * * * * * * * **
* * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 1, {75072dd9, 0, fffe, fffff88007cd1ca0}
***** 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!_KTHREAD * * * * * * * * * * * * * * * * * ***
*** * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * ***
*************************************************************************
*************************************************************************
*** * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * ***
*** * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * ***
*** * *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 : ntoskrnl.exe ( nt+70600 )
==================================================================================================== ===
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.
MODULE_NAME: nt
DEBUG_FLR_IMAGE_TIMESTAMP: *4b88cfeb
FAULTING_IP:*
+6131363034346434
00000000`75072dd9 ?? * * * * * * *???
CUSTOMER_CRASH_COUNT: *1
DEFAULT_BUCKET_ID: *VISTA_DRIVER_FAULT
BUGCHECK_STR: *0x1
CURRENT_IRQL: *0
LAST_CONTROL_TRANSFER: *from fffff8000288bb69 to fffff8000288c600
STACK_TEXT: *
fffff880`07cd1a68 fffff800`0288bb69 : 00000000`00000001 00000000`75072dd9 00000000`00000000 00000000`0000fffe : nt+0x70600
fffff880`07cd1a70 00000000`00000001 : 00000000`75072dd9 00000000`00000000 00000000`0000fffe fffff880`07cd1ca0 : nt+0x6fb69
fffff880`07cd1a78 00000000`75072dd9 : 00000000`00000000 00000000`0000fffe fffff880`07cd1ca0 fffffa80`075fb8d0 : 0x1
fffff880`07cd1a80 00000000`00000000 : 00000000`0000fffe fffff880`07cd1ca0 fffffa80`075fb8d0 000005a0`00000010 : 0x75072dd9
STACK_COMMAND: *kb
FOLLOWUP_IP:*
nt+70600
fffff800`0288c600 48894c2408 * * *mov * * qword ptr [rsp+8],rcx
SYMBOL_STACK_INDEX: *0
SYMBOL_NAME: *nt+70600
FOLLOWUP_NAME: *MachineOwner
IMAGE_NAME: *ntoskrnl.exe
BUCKET_ID: *WRONG_SYMBOLS
Followup: MachineOwner
---------