Windows 10 BSOD related to ntoskrnl.exe

T

TheDevilBroly

New Member
Joined
May 25, 2017
Messages
20
I'm having BSOD whenever I run BlueStacks and sometimes when I run a game or Microsoft Edge, but after the crash when the system restarts everything works fine even BlueStacks and I don't encounter any BSOD until I shut down the PC.

After shutdown when I again run BlueStacks the cycle repeats. Most of the time the error code is CRITICAL PROCESS DIED and sometimes MEMORY MANAGEMENT or KERNEL DATA INPAGE ERROR.

I already checked my RAM with Memtest86 ran 4 passes no errors were reported. Checked my HDD with SeaTools for Windows found no errors.

I'm attaching the W7F.zip file.

Any kind of help is appreciated.
 

Attachments

Solution
TheDevilBroly said:
iorate.sys is a Windows Driver
Click to expand...
It is indeed:
http://servicedefaults.com/10/iorate/

TheDevilBroly said:
should I just reinstall Windows 10 or try with any other version of Windows
Click to expand...
Windows may have simply become corrupted and you could try running these scans which might repair the kernel:
File scans
Right click on the Start menu icon and from the revealed list choose 'admin command prompt'. Type:
sfc /scannow
press enter and await results

In the same command prompt and after the above scan has finished type:
dism /online /cleanup-image /restorehealth
Press enter and await results (longer this time).

If the first scan found files it could not repair but the second scan is successful, run the first scan again using the same...
Sort by date Sort by votes
Removed the graphics card but still I got a BSOD . So, is it my HDD the root cause of my problems ?

Should install any other OS like Linux or Ubuntu and see if they also crash or not ? Or should I just replace my HDD ?
 
Upvote 0 Downvote
Code: 
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 154, {ffff81095f737000, ffffab01ec92e420, 2, 0}

*** WARNING: Unable to verify timestamp for win32k.sys
*** ERROR: Module load completed but symbols could not be loaded for win32k.sys
Probably caused by : hardware_disk

Followup:     MachineOwner
The above bugcheck means the Store encountered an exception and looking at your drivers something odd is going on:

dxgkrnl dxgkrnl.sys Tue Apr 24 08:34:26 2029 (6F900902)
dxgmms2 dxgmms2.sys Fri Apr 21 09:13:25 1989 (244EE2A5)
fastfat fastfat.SYS Tue May 17 04:56:00 1977 (0DDE8ED0)
filecrypt filecrypt.sys Tue May 28 09:10:59 2030 (719E1813)

As you can see from the small sample i posted, something is amiss with the dates possibly down to corruption?

What's puzzling tho' is the fact that your scan with SeaTools gave it a pass.

A handy little tool is an app called Speedfan. It's mainly used to control your system fans but it also has a section which checks your drives SMART data and issues an online report about the health of your drive. I did mine as an example although I've not included the online report:


I notice your using MSI's Afterburner which is known for causing blue screens in windows please remove to test.

The above dump file also blamed I/O errors:

Code: 
ERROR_CODE: (NTSTATUS) 0xc0000006 - The instruction at 0x%p referenced memory at 0x%p. The required data was not placed into memory because of an I/O error status of 0x%x.
There is an I/O driver available on your support page which i did ask to be installed. I can't see it in the driver section so maybe you forgot (I do all the time)
Support For H110M PRO-VD PLUS | Motherboard - The world leader in motherboard design | MSI Global
 
Upvote 0 Downvote
Oh no I didn't forget the drivers this time.

Also I don't have MSI Afterburner installed, I have MSI LiveUpdate Utility.

Checking with speedfan now. Do you want me to post the SeaTools report ?
 

Attachments

  • 1212.webp
    65.6 KB · Views: 356
Upvote 0 Downvote
Here is the report of the test that I ran earlier today. Running the Long Generic Test again will post the results soon.

Edit : I just got a BSOD and while the computer was restarting it showed ' A disk read error occured ' I changed the SATA port and cable then it again booted normally.
 

Attachments

  • post.webp
    55.8 KB · Views: 366
Last edited:
Upvote 0 Downvote
Well, the Long Generic Test failed, ran it 2 times failed both times. Here are the reports. So, is this conclusive enough that my HDD is the culprit ?
 

Attachments

  • long generic fail.webp
    56.9 KB · Views: 392
Upvote 0 Downvote
TheDevilBroly said:
So, is this conclusive enough that my HDD is the culprit ?
Click to expand...
Yes I'd say so as everything else passed with flying colours when tested. Shame we didn't run the Seatools scan earlier but at least you know the rest of the system is solid. I would be interested to see the speedfan results if you plan on still running it?
 
Upvote 0 Downvote
Ok, so I noticed a pattern whenever I run the Long Generic Test on Seatools before a BSOD happens the test fails. But after the PC restarts from BSOD, then again when I run the Long Generic Test it passes.

Also, as I have already mentioned in my original post, that my PC works perfectly fine once it restrats after a BSOD until I shoutdown my PC, after shutdown whenever I turn on the PC again, I will encounter a BSOD my PC will restart then it will work fine.

Any idea what's going on ?
 

Attachments

  • 11212.webp
    23 KB · Views: 315
Upvote 0 Downvote
Can you get the non windows version of seatools and boot it from usb or cd. Would be good to know if the drive itself is at fault or something windows is doing.
 
Upvote 0 Downvote
nmsuk said:
Can you get the non windows version of seatools and boot it from usb or cd. Would be good to know if the drive itself is at fault or something windows is doing.
Click to expand...

Well I tried that but SeaTools for DOS is unable to detect my HDD because my motherboard only supports AHCI mode and for SeaTools for DOS needs IDE/SATA mode to be able to detect the drive.

If you have any workaround for this problem I will be happy to test it out.
 
Upvote 0 Downvote
Why not try a chkdsk /r again as this also runs chkdsk /f :
chkdsk /r does the same thing as chkdsk /f only it also checks for bad sectors on the disk and recovers any readable information. Running chkdsk /r implies that also chkdsk /f is run.

Once you've done that try running SeaTools again and see if the error still appears.
 
Upvote 0 Downvote
Ran chkdsk /r after that performed the Long Generic Test on SeaTools still it failed. Here is the screenshot.
 

Attachments

  • Show.webp
    82.6 KB · Views: 358
Upvote 0 Downvote
Well to be honest I would trust Seatools more than the Speedfan result but I notice you do have another drive (HDD) .
One way of testing whether your drive is to blame is to do the same with the drive that's not a suspect and create a 100GB (150-200GB would be better but this only for testing so i leave it up to you) partition. Remove the suspect drive from the machine completely by unplugging the SATA cables and attach or plug in the test drive in it's place.
Install Windows to the partition and see how you go. If you don't blue screen then you other drive is knackered..
 
Upvote 0 Downvote
Well, the other drive is an External HDD, so I don't know if installing Windows in it will be a good idea or not.

Your idea crossed my mind and I'm arranging for a separate HDD from a friend, will update you how that goes.

Again, thanks for your time and all the help, now I think I'm pretty closer to catching the culprit.
 
Upvote 0 Downvote
TheDevilBroly said:
Well, the other drive is an External HDD, so I don't know if installing Windows in it will be a good idea or not.
Click to expand...
Yeah that won't work as Windows won't boot from an external drive.
TheDevilBroly said:
Your idea crossed my mind and I'm arranging for a separate HDD from a friend, will update you how that goes.
Click to expand...
Great idea!
 
Upvote 0 Downvote
You must log in or register to reply here.

Similar threads

  • Solved
Windows 10 BSOD Related to "ntoskrnl.exe+22de6a" ATTEMPTED_TO_WRITE_TO_READ_ONLY_MEMORY
Replies
18
Views
2K
Panic
M
  • Solved
Windows 7 BSOD related to memory dump
Replies
1
Views
2K
ChatGPT
  • Solved
Windows 7 Newly started BSOD - seems to be related to ntoskrnl
Replies
4
Views
2K
Elmer
M
  • Solved
Windows 7 Win7 x64 crashing, no bsod or memory dump written
Replies
1
Views
1K
ChatGPT
B
  • Solved
Windows 7 Troubleshooting Frequent BSODs: Potential SSD Failure or Kaspersky Conflict?
Replies
15
Views
18K
snolan669
S