Jump to content


Register a free account to unlock additional features at BleepingComputer.com
Welcome to BleepingComputer, a free community where people like yourself come together to discuss and learn how to use their computers. Using the site is easy and fun. As a guest, you can browse and view the various discussions in the forums, but can not create a new topic or reply to an existing one unless you are logged in. Other benefits of registering an account are subscribing to topics and forums, creating a blog, and having no ads shown anywhere on the site.

Click here to Register a free account now! or read our Welcome Guide to learn how to use this site.


ntoskrnl.exe bsod

  • Please log in to reply
2 replies to this topic

#1 basha54


  • Members
  • 1 posts
  • Local time:11:15 AM

Posted 20 August 2013 - 06:28 PM

my pc keeping getting bsod i dont know why it keeps doing it. if anyone could help me fix this it would be much appreciated. 

Attached Files

Edited by basha54, 20 August 2013 - 06:36 PM.

BC AdBot (Login to Remove)


#2 Marth_01


  • Members
  • 49 posts
  • Local time:09:15 AM

Posted 20 August 2013 - 07:17 PM


Here's the file you attached "082013-25318-01.dmp" read using the program BlueScreenView.
This helps for quick reference so you and others won't have to download and read a dmp file.

8/20/2013 7:04:54 PM
0x0000001e ffffffff`c0000005 fffff800`02d00247 00000000`00000000 00000000`7fef205b
Caused by file: ntoskrnl.exe
From googling "KMODE_EXCEPTION_NOT_HANDLED" and remembering the first error code is 0x1E...

Possible troubleshooting:

1. Download and install updates and device drivers for your computer from Windows Update.
2. Scan your computer for computer viruses. (Use Malwarebytes Anti Malware and similar)
3. Check your hard disk for errors. (Use command /sfc scannow and chkdsk /f)
4. Try booting to your windows install CD and doing a repair.
5. Follow this advice: http://www.tomshardware.com/forum/269897-45-ntoskrnl-corrupt, where they boot to the windows install CD and copy over a fresh ntoskrnl.exe

6. Others reported just going into the BIOS and resaving the settings to update the CMOS.
7. Others reported finding out of date or corrupted drivers, even a person's USB 3.0 driver: http://www.pchelpforum.com/xf/threads/bsod-on-windows-7-ntoskrnl-exe.145569/

8. Keep googling based on this information and your DMP file.
9. If all else fails, save data to another drive and reinstall windows!

Good luck!

Edited by Marth_01, 20 August 2013 - 07:19 PM.

#3 Anshad Edavana

Anshad Edavana

  • Members
  • 2,805 posts
  • Gender:Male
  • Location:India
  • Local time:08:45 PM

Posted 20 August 2013 - 11:21 PM

Hi basha54


Thanks for uploading the dump but unfortunately a single dump is not much helpful in finding the root cause. At least three or more crash dumps are necessary to find a pattern. Please try the below steps.


:step1: Test the memory modules.


 A failing RAM is the most common reason for frequent blue screens. We can use the free tool Memtest86+ to stress test the RAM modules. Please read the below tutorial carefully and execute the memtest for at least 7 or more passes.




Depending on the amount of RAM in your system, test may take a long time to complete seven passes. You can stop the test either when there are errors detected or it completes seven passes.



:step2: Scan for malwares.


Boot the system in to safe mode with networking and use the below tools to scan the system for possible infections.


1. Malwarebytes free : http://www.bleepingcomputer.com/download/malwarebytes-anti-malware/


2. ESET online scannerhttp://forums.majorgeeks.com/showthread.php?t=149856



Report the result of memory test and malware scanning in next reply. 

0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users