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 - ntoskrnl.exe

11 Dec 2010   #1
James Park

Windows 7 Ultimate x64
 
 
BSOD - ntoskrnl.exe

UPDATE: Please read my most recent reply

Hello, I've been doing some research on this issue. It appears that others have trouble with the BSOD regarding ntoskrnl.exe. I used a tool called "BlueScreenView". It basically gives me a summary of all computer crashes. With an exception of a few, ntoskrnl.exe has been the primary cause of my BSOD. My laptop has crashed before, but today has been very frustrating while my computer hit BSOD 9 times and counting! I followed the instructions from the sticky and included a .ZIP file of BSOD's data so it can be analysed.

HP dv8t-1200 - Windows 7 Ultimate 64-bit

Windows 7 64-bit Home Edition - Preinstalled
I did a clean install*

Hardware is less than a year old.
OS is less than 3 months old.
Intel i5
6GB Ram


Help would be appreciated! Thanks!

Also if it would be of anymore help, I could set up a remote desktop session using programs: Mikogo or Team Viewer and communicate over Skype.


My System SpecsSystem Spec
.
11 Dec 2010   #2
yowanvista

Windows 10 Pro x64, Arch Linux
 
 

The dmp(s) point to ntoskrnl.exe as the probable cause. We know this is not the case, as these are core OS files, and will definitely not cause a BSOD. They are just the default files the debuggers blame when they can't see a better cause. We need to run driver verifier to pinpoint the faulting driver...

- Go to Start and type in "verifier" (without the quotes) and press Enter
- Select "Create custom settings (for code developers)" and click "Next"
- Select "Select individual settings from a full list" and click "Next"
- Select everything EXCEPT FOR "Low Resource Simulation" and click "Next"
- Select "Select driver names from a list" and click "Next"
Then select all drivers NOT provided by Microsoft and click "Next"
- Select "Finish" on the next page.

Reboot the system and wait for it to crash to the Blue Screen. Continue to use your system normally, and if you know what causes the crash, do that repeatedly. The objective here is to get the system to crash because Driver Verifier is stressing the drivers out.

Then if it blue screens again upload the contents of C:\Windows\Minidump



My System SpecsSystem Spec
11 Dec 2010   #3
DeanP

Win 7 Pro x64 SP1 OS X Snow Leopard 10.6.7
 
 

ntoskrnl.exe is a file used in Windows, I don't really think that may cause the problem.
While the BSOD Team is analyzing your dump files, here's some things you should do.
---------------------------------------
Uninstall your current anti-virus software and replace it with Microsoft Security Essentials (it's free and easy to use).

Do chkdsk /f and sfc /scannow in command prompt for corrupt files/damaged/missing files.

Update all of your drivers to the latest.
Quote:
Please remove any CD virtualization programs such as Daemon Tools and Alcohol 120%. They use a driver, found in your dmp, sptd.sys, that is notorious for causing BSODs. Use this SPTD uninstaller when you're done: DuplexSecure - Downloads
You can use MagicDisc as an alternative.
If you recently installed software, uninstall it or use system restore if you have problems uninstalling it. Software can conflict with the system because of incompatibility or other reasons and cause errors or BSODs.

EDIT: Typed a little bit slow, ignore some bits.
My System SpecsSystem Spec
.

11 Dec 2010   #4
yowanvista

Windows 10 Pro x64, Arch Linux
 
 

Quote   Quote: Originally Posted by DeanP View Post
ntoskrnl.exe is a file used in Windows, I don't really think that may cause the problem.
While the BSOD Team is analyzing your dump files, here's some things you should do.
---------------------------------------
Uninstall your current anti-virus software and replace it with Microsoft Security Essentials (it's free and easy to use).

Do chkdsk /f and sfc /scannow in command prompt for corrupt files/damaged/missing files.

Update all of your drivers to the latest.
Quote:
Please remove any CD virtualization programs such as Daemon Tools and Alcohol 120%. They use a driver, found in your dmp, sptd.sys, that is notorious for causing BSODs. Use this SPTD uninstaller when you're done: DuplexSecure - Downloads
You can use MagicDisc as an alternative.
If you recently installed software, uninstall it or use system restore if you have problems uninstalling it. Software can conflict with the system because of incompatibility or other reasons and cause errors or BSODs.

EDIT: Typed a little bit slow, ignore some bits.
The posted doesn't have any sptd.sys in the dumps
My System SpecsSystem Spec
11 Dec 2010   #5
DeanP

Win 7 Pro x64 SP1 OS X Snow Leopard 10.6.7
 
 

Quote:
Quote: Originally Posted by DeanP
ntoskrnl.exe is a file used in Windows, I don't really think that may cause the problem.
While the BSOD Team is analyzing your dump files, here's some things you should do.
---------------------------------------
Uninstall your current anti-virus software and replace it with Microsoft Security Essentials (it's free and easy to use).

Do chkdsk /f and sfc /scannow in command prompt for corrupt files/damaged/missing files.

Update all of your drivers to the latest.
Quote:
Please remove any CD virtualization programs such as Daemon Tools and Alcohol 120%. They use a driver, found in your dmp, sptd.sys, that is notorious for causing BSODs. Use this SPTD uninstaller when you're done: DuplexSecure - Downloads
You can use MagicDisc as an alternative.



If you recently installed software, uninstall it or use system restore if you have problems uninstalling it. Software can conflict with the system because of incompatibility or other reasons and cause errors or BSODs.

EDIT: Typed a little bit slow, ignore some bits.



The posted doesn't have any sptd.sys in the dumps
How can you and the BSOD Team analyze the crash dumps? I try to analyze my crash dumps with WinDBG and BlueScreenViewer, doesn't work well.

It end up saying that the driver was caused by a file to do with Windows, not by software. (ie. win32k.sys, csrss.exe)
My System SpecsSystem Spec
11 Dec 2010   #6
James Park

Windows 7 Ultimate x64
 
 

Alright guys thanks for the input. I'll let you know when BSOD appears again.

My security system is ZoneAlarm Extreme. It's my Firewall/Anti-Virus/Anti-Spyware.
My System SpecsSystem Spec
11 Dec 2010   #7
James Park

Windows 7 Ultimate x64
 
 

Quote   Quote: Originally Posted by yowanvista View Post
The dmp(s) point to ntoskrnl.exe as the probable cause. We know this is not the case, as these are core OS files, and will definitely not cause a BSOD. They are just the default files the debuggers blame when they can't see a better cause. We need to run driver verifier to pinpoint the faulting driver...

- Go to Start and type in "verifier" (without the quotes) and press Enter
- Select "Create custom settings (for code developers)" and click "Next"
- Select "Select individual settings from a full list" and click "Next"
- Select everything EXCEPT FOR "Low Resource Simulation" and click "Next"
- Select "Select driver names from a list" and click "Next"
Then select all drivers NOT provided by Microsoft and click "Next"
- Select "Finish" on the next page.

Reboot the system and wait for it to crash to the Blue Screen. Continue to use your system normally, and if you know what causes the crash, do that repeatedly. The objective here is to get the system to crash because Driver Verifier is stressing the drivers out.

Then if it blue screens again upload the contents of C:\Windows\Minidump


So basically what I have to do is start up the Driver Verier and use my computer until it crashes? And when it does, send the BSOD Team another crash file?
My System SpecsSystem Spec
11 Dec 2010   #8
yowanvista

Windows 10 Pro x64, Arch Linux
 
 

Quote   Quote: Originally Posted by James Park View Post
Quote   Quote: Originally Posted by yowanvista View Post
The dmp(s) point to ntoskrnl.exe as the probable cause. We know this is not the case, as these are core OS files, and will definitely not cause a BSOD. They are just the default files the debuggers blame when they can't see a better cause. We need to run driver verifier to pinpoint the faulting driver...

- Go to Start and type in "verifier" (without the quotes) and press Enter
- Select "Create custom settings (for code developers)" and click "Next"
- Select "Select individual settings from a full list" and click "Next"
- Select everything EXCEPT FOR "Low Resource Simulation" and click "Next"
- Select "Select driver names from a list" and click "Next"
Then select all drivers NOT provided by Microsoft and click "Next"
- Select "Finish" on the next page.

Reboot the system and wait for it to crash to the Blue Screen. Continue to use your system normally, and if you know what causes the crash, do that repeatedly. The objective here is to get the system to crash because Driver Verifier is stressing the drivers out.

Then if it blue screens again upload the contents of C:\Windows\Minidump


So basically what I have to do is start up the Driver Verier and use my computer until it crashes? And when it does, send the BSOD Team another crash file?
Yes this is what you have to do
My System SpecsSystem Spec
11 Dec 2010   #9
James Park

Windows 7 Ultimate x64
 
 

Quote   Quote: Originally Posted by yowanvista View Post
Quote   Quote: Originally Posted by James Park View Post
Quote   Quote: Originally Posted by yowanvista View Post
The dmp(s) point to ntoskrnl.exe as the probable cause. We know this is not the case, as these are core OS files, and will definitely not cause a BSOD. They are just the default files the debuggers blame when they can't see a better cause. We need to run driver verifier to pinpoint the faulting driver...

- Go to Start and type in "verifier" (without the quotes) and press Enter
- Select "Create custom settings (for code developers)" and click "Next"
- Select "Select individual settings from a full list" and click "Next"
- Select everything EXCEPT FOR "Low Resource Simulation" and click "Next"
- Select "Select driver names from a list" and click "Next"
Then select all drivers NOT provided by Microsoft and click "Next"
- Select "Finish" on the next page.

Reboot the system and wait for it to crash to the Blue Screen. Continue to use your system normally, and if you know what causes the crash, do that repeatedly. The objective here is to get the system to crash because Driver Verifier is stressing the drivers out.

Then if it blue screens again upload the contents of C:\Windows\Minidump


So basically what I have to do is start up the Driver Verier and use my computer until it crashes? And when it does, send the BSOD Team another crash file?
Yes this is what you have to do
I noticed that a lot of people are having the same problem regarding ntoskrnl.exe. What exactly is it and why is it so hard to just point to a specific cause?
My System SpecsSystem Spec
26 Dec 2010   #10
James Park

Windows 7 Ultimate x64
 
 

Ok, I'm still having trouble with the BSOD. It hasn't happened 10 times in a day like before, but it's been happening every other day. It feels entirely random as I cannot pinpoint what software or program might be causing this. I followed all the directions the first time and I'm not sure what I can do! I have no viruses or spywares on my computer because I scan regularly with Zone Alarm Extreme Security. Does this have anything to do with my registry? I have no programs that "cleans" it out. Please help!

Thanks and happy holidays!
My System SpecsSystem Spec
Reply

 BSOD - ntoskrnl.exe




Thread Tools




Similar help and support threads
Thread Forum
0x00000124 ntoskrnl.exe ntoskrnl.exe+4a63cc BSOD Error runninganygame
i keep getting BSOD when playing game new graphics i dont know where to start when its comes to BSOD stuff 110414-10576-01.dmp 11/4/2014 10:48:39 PM 0x00000124 00000000`00000000 fffffa80`0af318f8 00000000`00000000 00000000`00000000 ntoskrnl.exe ntoskrnl.exe+4a63cc ...
BSOD Help and Support
BSOD Address:ntoskrnl.exe+75bc0; dxgmms1.sys,ntoskrnl.exe,Ntfs.sys
Hi, to make things easier for you,below is the Bug Check String, Driver, and crash address SYSTEM_SERVICE_EXCEPTION___dxgmms1.sys___ntoskrnl.exe+75bc0 MEMORY_MANAGEMENT_______ntoskrnl.exe____ntoskrnl.exe+75bc0 SYSTEM_SERVICE_EXCEPTION___ntoskrnl.exe____ntoskrnl.exe+75bc0...
BSOD Help and Support
BSOD when goes sleep, ntoskrnl.exe+e96d2/ntoskrnl.exe+81e7a
When I put my pc in sleep mode it often crashes: the screen goes normally in sleep mode, but the pc continues to stay awake for several minutes than BSOD & restart or BSOD & shut off. Thanks to BlueScreenView I found what is seemingly the guilty process, but I don't know what to do now. Thanks...
BSOD Help and Support
BSOD ntoskrnl.exe , All the Time !! Crash Address ntoskrnl.exe+80640
Jan 2014 //------------------------------------------- How to Solve : 1- I've uninstalled my windows and recover my laptop with recovery DVD to it's original factory state.(original windows :)) 2- Never installed Norton internet security again , I'm using Microsoft Security Essentials now. 3-...
BSOD Help and Support
Random BSOD Reporting ntoskrnl.exe+75c40 & ntoskrnl.exe+7efc0
I'm getting random Blue Screens and can't figure out why. I'm not running any hardcore programs. I'm mostly just using Microsoft Office and Firefox. The BSOD's seem to happen when I'm in Outlook, Excel or Firefox. Haven't been able to determine exactly which at the time as I'm moving back and...
BSOD Help and Support
BSOD Ntoskrnl.exe+7efc0 and Ntoskrnl.exe+75c40
I keep getting a BSOD (Critical_Object_Termination) but have no idea what is causing the issue. I tried in vain to debug my own minidump files but ended up getting nowhere. So far i have run MemTest over the weekend with 107 passes. I also ran Prime95 64-bit for 4 hours on each of the FFT tests...
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 22:20.
Twitter Facebook Google+ Seven Forums iOS App Seven Forums Android App