Windows 7 Forums

Welcome to Windows 7 Forums. Our forum is dedicated to helping you find support and solutions for any problems regarding your Windows 7 PC be it Dell, HP, Acer, Asus or a custom build. We also provide an extensive Windows 7 tutorial section that covers a wide range of tips and tricks.


Windows 7: BSOD after fresh install, ntoskrnl.exe

22 Oct 2011   #1
Marcin

Windows 7 Ultimate x64
 
 
BSOD after fresh install, ntoskrnl.exe

I really need help here guys, im out of ideas. About a week ago my computer started getting BSOD randomly while gaming or browsing the web. I thought it was a failing HDD so I re installed windows onto a new one after running stress tests on it to make sure it was good. I have run stress tests on everything and watched temperatures. Windows is up to date. Swapped new ram sticks to make sure memory was OK. Everything seems to check out, but i still get these errors. This is what is in the dump file. If anyone has any ideas i would greatly appreciate it.


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 (8 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Machine Name:
Kernel base = 0xfffff800`02c13000 PsLoadedModuleList = 0xfffff800`02e50e50
Debug session time: Thu Oct 20 00:34:05.156 2011 (UTC - 5:00)
System Uptime: 0 days 0:00:28.296
*********************************************************************
* 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
...
*** WARNING: Unable to verify timestamp for hal.dll
*** ERROR: Module load completed but symbols could not be loaded for hal.dll


My System SpecsSystem Spec
.
22 Oct 2011   #2
zigzag3143

Win 8 Release candidate 8400
 
 

Quote   Quote: Originally Posted by Marcin View Post
I really need help here guys, im out of ideas. About a week ago my computer started getting BSOD randomly while gaming or browsing the web. I thought it was a failing HDD so I re installed windows onto a new one after running stress tests on it to make sure it was good. I have run stress tests on everything and watched temperatures. Windows is up to date. Swapped new ram sticks to make sure memory was OK. Everything seems to check out, but i still get these errors. This is what is in the dump file. If anyone has any ideas i would greatly appreciate it.


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 (8 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Machine Name:
Kernel base = 0xfffff800`02c13000 PsLoadedModuleList = 0xfffff800`02e50e50
Debug session time: Thu Oct 20 00:34:05.156 2011 (UTC - 5:00)
System Uptime: 0 days 0:00:28.296
*********************************************************************
* 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
...
*** WARNING: Unable to verify timestamp for hal.dll
*** ERROR: Module load completed but symbols could not be loaded for hal.dll

We do need the DMP file as it contains the only record of the sequence of events leading up to the crash, what drivers were loaded, and what was responsible.

You may be able to get the DMP files without crashing by booting into safe mode (F8) with networking.

To enable us to assist you with your computer's BSOD symptoms, upload the contents of your "\Windows\Minidump" folder.

The procedure:

* Copy the contents of \Windows\Minidump to another (temporary) location somewhere on your machine.
* Zip up the copy.
* Attach the ZIP archive to your post using the "paperclip" (file attachments) button.
*If the files are too large please upload them to a file sharing service like "Rapidshare" and put a link to them in your reply.


To ensure minidumps are enabled:

* Go to Start, in the Search Box type: sysdm.cpl, press Enter.
* Under the Advanced tab, click on the Startup and Recovery Settings... button.
* Ensure that Automatically restart is unchecked.
* Under the Write Debugging Information header select Small memory dump (256 kB) in the dropdown box (the 256kb varies).
* Ensure that the Small Dump Directory is listed as %systemroot%\Minidump.
* OK your way out.
* Reboot if changes have been made.




My System SpecsSystem Spec
22 Oct 2011   #3
Marcin

Windows 7 Ultimate x64
 
 

ok here it is hope this helps
My System SpecsSystem Spec
.

Reply

 BSOD after fresh install, ntoskrnl.exe




Thread Tools Search this Thread
Search this Thread:

Advanced Search




Similar help and support threads
Thread Forum
Fresh Win7 x64 Install - BSOD / ntoskrnl / 0xf4 / CRITICAL_OBJECT_TERM
Hi all, I did a fresh install of Win7 x64 onto a brand new Intel 730 SSD drive. After installing chipset/USB3/audio/video drivers and connecting all hardware, I started to restore user files to the system via CrashPlan backups from an external hard drive. During that, I got a couple of BSODs. ...
BSOD Help and Support
New Custom Build, Fresh Win7 install, BSOD issues ntoskrnl/win32k
Hi 7Forums, I recently bought a new computer from a pc build website. I installed Win7 HP 64bit and started to instantly experience BSODs. After a bit of diagnostics, memtest told me that one of the RAM sticks was horrifically broken, that has since been sent off for replacement and the...
BSOD Help and Support
BSOD ntoskrnl.exe fresh windows 7 install
Hey guys, I have been having a problem with blue screens on this computer for a few weeks now. I finally got frustrated with it yesterday and reinstalled windows 7. The issues would happen any time I ran windows update. To fix it, I would have to restore to the oldest possible point, run the...
BSOD Help and Support
BSOD - NTOSKRNL.EXE (KMODE_EXCEPION_NOT_HANDLED) on Fresh OS Install
I got BSOD while I was watching a movie on Netflix and playing World of Warcraft. I was setting up my settings for Media Monkey and got this blue screen of death. I recently did a fresh install on my computer no more than a week ago. I am running Windows 7 Enterprise 64 Bit with Service Pack 1. I...
BSOD Help and Support
Fresh Install...NTOSKRNL.exe?
Windows 7 Pro x64 SP1, fresh install Hardware Build: x58a-ud3r i7-970 Less than 24hrs into the installation, after updated chipset drivers, I've had three BSODs (all of which are included in the attached dump.zip It is my belief that it could be a bad ram module but a second opinion...
BSOD Help and Support
Random BSOD - Fresh install, fresh system
Hi. I have installed a whole new windows 7 pro x64. My new mobo an ASus p5e3 pro along with new ram pc12800 gskill 2x2 ddr3 (running in 1066mhz due to my q6600) Everythingi s running perfectly...except some random BSOD. 4 total this week. I have posted a pack of dump file in here, the last 4...
BSOD Help and Support


Our Sites

Site Links

About Us

Find Us

Windows 7 Forums is an independent web site and has not been authorized, sponsored, or otherwise approved by Microsoft Corporation. "Windows 7" and related materials are trademarks of Microsoft Corp.

Designer Media Ltd

All times are GMT -5. The time now is 15:32.

Twitter Facebook Google+



Windows 7 Forums

Seven Forums Android App Seven Forums IOS App