BSOD - ntoskrnl.exe - Windows 7

Toggle sidebar Toggle sidebar
pufut

pufut

Distinguished
Aug 30, 2014
78
0
18,630
Hello all,

I have just now experience a BSOD while having serious lag issues with a game. I had played it yesterday perfectly, at about 50/60fps and today I couldn't even navigate the menu. Anyway, after a few minutes of tabbing out, restarting the game, etc. I was met with a BSOD and my PC rebooted.

Here's an image of the dump using BlueScreenView: http://prntscr.com/b52i48

If it helps, I installed a new HDD yesterday too, a second one since my main disk was pretty full. It is working fine and have had no issues with it, but I've researched this particular BSOD and some have said it is to do with memory or your hard drive - is this the case here?

Anyway, if anyone could help me out, or just clarify what exactly the issue was/is, that would be much appreciated.
 
Solution
neieus
Well first you're going to want to make sure all of your windows system updates have been installed then make sure that you have updated all of your device drivers to their latest version. After you've done this you will then need to use your system for a time to see if the problem returns and if so the crash dump from that event will need to be checked out.
Sort by date Sort by votes
neieus

neieus

Distinguished
Dec 29, 2011
1,776
0
20,460
Your computer can experience a BSOD for several reasons but keep in mind anytime the error tells you that it was the ntoskrl.exe at fault then it will most likely be something else. What most likely happened is that something that was accessing it crashed and because of that took the kernel down with it. You're going to need to look at the crash dump that was created when the BSOD occurred. You will need something like the windows debugger or whocrashed to view this information but the file can be found C:\Windows\Minidump and it should be the file with the most recent time stamp date.
 
Upvote 0 Downvote
pufut

pufut

Distinguished
Aug 30, 2014
78
0
18,630


I downloaded WhoCrashed and the free version doesn't tell me anything more than what I already know, which in itself doesn't make any sense to me. Are you able to "translate" the information I attached in the above screenshot I posted? Like I said, I have looked online for those who have had a similar error, but there are still differences.

I've just ran a malware scan, and ran windows maintenance, which have returned nothing. Is this just something I can forget about?
 
Upvote 0 Downvote
pufut

pufut

Distinguished
Aug 30, 2014
78
0
18,630


No, I haven't actually. I'll do that now.

To be honest, I've got quite a few concerns. Dying Light (the demo version) like I said was playing perfectly yesterday, and today, both before and after the blue screen, it is unplayable. I've also noticed that while I'm writing this, with nothing open but Chrome, my CPU usage is between 60% and 100%. My PC is stuttering all over the place.

I'm not really sure what's happened or what's going on. I'll apply those updates now and let you know if anything improves.
 
Upvote 0 Downvote
neieus

neieus

Distinguished
Dec 29, 2011
1,776
0
20,460
Well the first thing you need to do is make sure windows has all of the available updates installed. Next if you have any programs or games installed that are cracked versions they should be uninstalled even if they worked before all of this just to insure that everything is working correctly. Otherwise troubleshooting your BSOD is pointless if you don't have all of the windows updates installed because a lot of times they fix the issues you are experiencing. Also make sure to run a virus can to make sure you are clean.
 
Upvote 0 Downvote
pufut

pufut

Distinguished
Aug 30, 2014
78
0
18,630


I'm currently trying to update a large backlog of neglected updates (oops) but every time I try to update it's attempting to download Windows 10. I've gone into installed updates and deleted the ones associated with Windows 10, just restarting now to see if that's worked.

I ran a virus scan, clear. Just going to run memory diagnostics to make sure its not my RAM going bad.

I'll keep you updated. Thank you for all your help so far
 
Upvote 0 Downvote
J

johnbl

Polypheme
Nov 4, 2012
10,072
185
67,090
the driver that crashes with this bugcheck is the victim of memory corruption. You don't know if it corrupted its own kernel data or it another driver corrupted the kernel data.

generally you turn on verifier functions to catch the memory corrupt at the point of corruption rather than wait until another driver crashes because of the corruption.

 
Upvote 0 Downvote
pufut

pufut

Distinguished
Aug 30, 2014
78
0
18,630


What should I do?
 
Upvote 0 Downvote
neieus

neieus

Distinguished
Dec 29, 2011
1,776
0
20,460
Well first you're going to want to make sure all of your windows system updates have been installed then make sure that you have updated all of your device drivers to their latest version. After you've done this you will then need to use your system for a time to see if the problem returns and if so the crash dump from that event will need to be checked out.
 
Upvote 0 Downvote
Solution
pufut

pufut

Distinguished
Aug 30, 2014
78
0
18,630


Okay, I'll do that. Thank you both for your help!
 
Upvote 0 Downvote
You must log in or register to reply here.

TRENDING THREADS

Latest posts

Moderators online

Share this page

COMPANY
RESOURCES
FOLLOW
Top Bottom