[SOLVED] Event viewer 153 warning and BSOD

[megyesi.andris]

I think my HDD or Motherboard could be failing.
I was playing Skyrim all right and then it randomly crashed. After that I tried reopening it, I got to the main menu and I could start my game but it always crashed out in the loading screen.
I check my event viewer to so whats up and I found 2 disk warnings with the 153 code.

After all this my computer got a BSOD. The computer tried to restart itself but it failed and then it tried to repair itself without any success. I shut it down and I waited for like 5 mins. I booted and it worked.

I started playing Skyrim again and the same thing happened. I check the SMART of my HDD with CrystalDiskInfo and it said it has no problems.

As I am writing this im the the stage where Skyrim crashed and the warnings appeared but I did not try to launch Skyram again and I didnt not get a BSOD.

I really dont know what could be causing this.
Both of the warning say that it retried something also they have the same binary data:

0000: 0004010F 002C0004 00000000 80040099
0010: 00000000 00000000 00000000 00000000
0020: 00000000 00000000 28020000



0000: 0F 01 04 00 04 00 2C 00 ......,.
0008: 00 00 00 00 99 00 04 80 ....™..€
0010: 00 00 00 00 00 00 00 00 ........
0018: 00 00 00 00 00 00 00 00 ........
0020: 00 00 00 00 00 00 00 00 ........
0028: 00 00 02 28 ...(

Edit: The Pc crashed again with unexpected store exception message. It tried to restart itself but it got another BSOD after some minutes with the 0x0000021A error code.

 

[johnbl]

80040099 looks like a error code.
maybe this one:
0x80040099
#define IO_WARNING_IO_OPERATION_RETRIED
The IO operation at logical block address %2 for Disk %3 (PDO name: %4) was retried.

 

[megyesi.andris]

80040099 looks like a error code.
maybe this one:
0x80040099
#define IO_WARNING_IO_OPERATION_RETRIED
The IO operation at logical block address %2 for Disk %3 (PDO name: %4) was retried.

Yes that is the warning im talking about.
That warning has the 153 code/id in the event viewer

 

[johnbl]

windows 10 and 8.x will do low level repairs of the drive. windows 7 will not and you are expected to do your own repairs.

you might just turn off virtual memory, reboot and delete c:\pagefile.sys (if not already deleted) then turn on virutal memory. what version of winodws do you have? do you have a ssd ? or just a regular hard drive.

are there any actual memory dumps in c:\windows\minidump directory?
------------
if you don't think the problem is your hardware (drive) then I would check anything that can slow down access to the drive: ie virus scanners that are going thru a bad network driver version, or too many filter drivers.
You could also change the timeout, remove any old defrag drivers, or special disk drivers.
update sata drivers. best to change the memory dump to kernel and provide c:\windows\memory.dmp file if you get a bugcheck. this will save the proper debug info.

80040099 looks like a error code.
maybe this one:
0x80040099
#define IO_WARNING_IO_OPERATION_RETRIED
The IO operation at logical block address %2 for Disk %3 (PDO name: %4) was retried.

Yes that is the warning im talking about.
That warning has the 153 code/id in the event viewer

 

[megyesi.andris]

windows 10 and 8.x will do low level repairs of the drive. windows 7 will not and you are expected to do your own repairs.

you might just turn off virtual memory, reboot and delete c:\pagefile.sys (if not already deleted) then turn on virutal memory. what version of winodws do you have? do you have a ssd ? or just a regular hard drive.

are there any actual memory dumps in c:\windows\minidump directory?
------------
if you don't think the problem is your hardware (drive) then I would check anything that can slow down access to the drive: ie virus scanners that are going thru a bad network driver version, or too many filter drivers.
You could also change the timeout, remove any old defrag drivers, or special disk drivers.
update sata drivers. best to change the memory dump to kernel and provide c:\windows\memory.dmp file if you get a bugcheck. this will save the proper debug info.

80040099 looks like a error code.
maybe this one:
0x80040099
#define IO_WARNING_IO_OPERATION_RETRIED
The IO operation at logical block address %2 for Disk %3 (PDO name: %4) was retried.

Yes that is the warning im talking about.
That warning has the 153 code/id in the event viewer

I have a Win 10 OS and a WD 1TB HDD. There are 3 dumps in the minidump folder and I also got a bugcheck dump but I don't see the option to upload them here to this site.

 

[johnbl]

you would have to copy them to some cloud server where you have an account, share the files for public access and post a link.

windows 10 and 8.x will do low level repairs of the drive. windows 7 will not and you are expected to do your own repairs.

you might just turn off virtual memory, reboot and delete c:\pagefile.sys (if not already deleted) then turn on virutal memory. what version of winodws do you have? do you have a ssd ? or just a regular hard drive.

are there any actual memory dumps in c:\windows\minidump directory?
------------
if you don't think the problem is your hardware (drive) then I would check anything that can slow down access to the drive: ie virus scanners that are going thru a bad network driver version, or too many filter drivers.
You could also change the timeout, remove any old defrag drivers, or special disk drivers.
update sata drivers. best to change the memory dump to kernel and provide c:\windows\memory.dmp file if you get a bugcheck. this will save the proper debug info.

80040099 looks like a error code.
maybe this one:
0x80040099
#define IO_WARNING_IO_OPERATION_RETRIED
The IO operation at logical block address %2 for Disk %3 (PDO name: %4) was retried.

Yes that is the warning im talking about.
That warning has the 153 code/id in the event viewer

I have a Win 10 OS and a WD 1TB HDD. There are 3 dumps in the minidump folder and I also got a bugcheck dump but I don't see the option to upload them here to this site.

 

[megyesi.andris]

you would have to copy them to some cloud server where you have an account, share the files for public access and post a link.

windows 10 and 8.x will do low level repairs of the drive. windows 7 will not and you are expected to do your own repairs.

you might just turn off virtual memory, reboot and delete c:\pagefile.sys (if not already deleted) then turn on virutal memory. what version of winodws do you have? do you have a ssd ? or just a regular hard drive.

are there any actual memory dumps in c:\windows\minidump directory?
------------
if you don't think the problem is your hardware (drive) then I would check anything that can slow down access to the drive: ie virus scanners that are going thru a bad network driver version, or too many filter drivers.
You could also change the timeout, remove any old defrag drivers, or special disk drivers.
update sata drivers. best to change the memory dump to kernel and provide c:\windows\memory.dmp file if you get a bugcheck. this will save the proper debug info.

80040099 looks like a error code.
maybe this one:
0x80040099
#define IO_WARNING_IO_OPERATION_RETRIED
The IO operation at logical block address %2 for Disk %3 (PDO name: %4) was retried.

Yes that is the warning im talking about.
That warning has the 153 code/id in the event viewer

I have a Win 10 OS and a WD 1TB HDD. There are 3 dumps in the minidump folder and I also got a bugcheck dump but I don't see the option to upload them here to this site.

Here are the dumps: https://www.dropbox.com/sh/edufdh5100c4h8d/AABT8a7hGdrW4q-hIYNoOqNqa?dl=0

 

[johnbl]

last bugcheck the system was running 1 minute 58 seconds
then tried to load a old 32bit winsock 2 dll. (ws2_32.dll)
the file was bad.
2: kd> !error 0xc0000020
Error code: (NTSTATUS) 0xc0000020 (3221225504) - {Bad File} The attributes of the specified mapping file for a section of memory cannot be read.

try an run dism.exe command
dism.exe /online /cleanup-image /restorehealth

you might have to add an option to fix the 32bit subsystem. (not sure)

 

[megyesi.andris]

I ran dism and it finished succesfully.
How do I fix the subsystem?

Update: I'm still getting the disk warnings in the event viewer even after using Dism

 

[johnbl]

I am not sure the dism command I provided does the winsxs subsystem so I looked up the command that does:
start cmd.exe as an admin and run:
Dism.exe /online /Cleanup-Image /StartComponentCleanup

https://www.tenforums.com/tutorials/82643-clean-up-component-store-winsxs-folder-windows-10-a.html

I ran dism and it finished succesfully.
How do I fix the subsystem?

Update: I'm still getting the disk warnings in the event viewer even after using Dism

 

[megyesi.andris]

I am not sure the dism command I provided does the winsxs subsystem so I looked up the command that does:
start cmd.exe as an admin and run:
Dism.exe /online /Cleanup-Image /StartComponentCleanup

https://www.tenforums.com/tutorials/82643-clean-up-component-store-winsxs-folder-windows-10-a.html

I ran dism and it finished succesfully.
How do I fix the subsystem?

Update: I'm still getting the disk warnings in the event viewer even after using Dism

The component cleanup starts without problem but at some point I get the error 1392 and the process stops.

 

[johnbl]

0: kd> !error 0x570
Error code: (Win32) 0x570 (1392) - The file or directory is corrupted and unreadable.

you should look at the end of the dism log file.
it should be located at:
C:\WINDOWS\Logs\DISM\dism.log

something wrong with some file or some issue with the file system
(or the actual drive)

hopefully the .log will tell you the name of the file or directory with the problem. Maybe you can rename the file and run the dism command again so that it will place new file on a new location on your drive.

I am not sure the dism command I provided does the winsxs subsystem so I looked up the command that does:
start cmd.exe as an admin and run:
Dism.exe /online /Cleanup-Image /StartComponentCleanup

https://www.tenforums.com/tutorials/82643-clean-up-component-store-winsxs-folder-windows-10-a.html

I ran dism and it finished succesfully.
How do I fix the subsystem?

Update: I'm still getting the disk warnings in the event viewer even after using Dism

The component cleanup starts without problem but at some point I get the error 1392 and the process stops.

 

[poptweety]

hello, i have ryzen setup for about 2 years, had the same problem appeared like 2 month ago. Ive read so much forums about this problem, tried 30 different solutions but nothing helped me, except one thing - https://www.youtube.com/watch?v=gj4VDXdq03k&t=1s
You have to switch ahci power management to dimp, the error still occurs, but maybe 1 time a week. I have 2 drives in my setup, WD HDD and SSD with system on it, after the problem appeared i started to install any game on HDD only, because if the 153 shit happens again, it never affect the SSD and windows, only HDD, so i dont get any system freeze. So what you have to do in this situation, quit the game, put your computer in sleep mode for like 10 mins, or you can turn it off whatever (for 10 mins also) And after next launch the problem gone, you can start playing again.
So here are some things that ive noticed during this problem: When you use your PC on idle mode (browsing, watching videos etc) after the launch, no matter how long , the disk problem never appear
When you start any online game that you cant put on pause, for example WOW or overwatch(overwatch makes your pc work on high loads even in game menu), so you can also play these games forever and the problem will never appear until you exit the game, even if you launch the game again you will get freeze until you restart/sleep your pc for 10 mins. Also, if you have more than one drive, the problem will appear only on the one you were playing on.
But, if you start any single game that significantly decreases the load on your pc when you pause it, or open game inventory that imitates pause, you will get the disk error again
I couldnt play alien isolation because of that, i was getting disk errors after 30mins of playing, but after i switched ahci power management to DIMP, i played it 4 days without any error, i got the error on 5th day, but after a quick 10 mins reboot i played it for 3 days again without getting a single error.
hope this might help you!
upd: currently using himp+dimp mode, 5 days running without any error