[SOLVED] Random BSOD need help

Dec 13, 2021
3
0
10
After 3 days of constant troubleshooting, I need help, out of idea. I'll explain as best as I can. It started Saturday night, while watching Netflix, paused to get a drink only to come back to a BSOD: UNEXPECTED_STORE_EXCEPTION (154) (I will include the minidump). At this point, my first reaction is to do DISM.exe /Online /Cleanup-image /Restorehealth and then SFC /scannow. As I expected, I got the "Windows Resource Protection found corrupt files and successfully repaired them." Now I proceed to restart the PC and then run SFC /scannow a second time, as well as chkdsk on both drives. Everything turned out fine, so I stop troubleshooting and resume to play on the PC the rest of the night, without problems. Sunday morning, I was watching YouTube, suddenly the video froze as if it couldn't load, trying to quit full screen was unsuccessful and the PC just froze and then crashed: KERNEL_DATA_INPAGE_ERROR. I suppose then that I missed something on Saturday night and decide to go through the same process, this time though nothing was found. Going through the event viewer I couldn't find much substantial, but these two: "The device HID-compliant headset (location (unknown)) is offline due to a user-mode driver crash." "The RasMan service depends on the SstpSvc service which failed to start because of the following error: The operation completed successfully."
I checked the device HID-compliant headset, no errors were reported recently, nor any other peripheral associated. I'm running out of ideas, so I run a RAM test for 7 hours using Karhu Software. No errors. I did all updates available. Yesterday I cleaned my SSD, one more RAM test, chkdsk /f on both drives, more Windows updates, attempted windows repair, ticked off and then back on “Automatically manage paging file size for all drives”. Trying to check the minidumps myself was a failure, though I noticed two more minidump of the same UNEXPECTED_STORE_EXCEPTION (154) generated two and three months prior respectively, during weekdays while the PC was left unused. Right now all I get in event viewer is "The Driver \Driver\WudfRd failed to load for the device HID\VID_0951&PID_16A4&MI_03&Col02\7&1c94fa2&0&0001". Yet I found no problem with any drivers, whatsoever.
Still don't know if it will occur again, I assume the problem is not fixed. Considering I had two other BSOD of the same kind before, which I was not even aware of, make me think that.
https://www.mediafire.com/file/su372r9ioa7i6cm/121121-9812-01.dmp/file

Specs:

Intel® Core™ i7-8700 3.20GHz
Nvidia GeForce RTX® 2070
16GB RAM (2x 8GB)
256GB SSD (Kingston)
2TB HDD (Seagate)
 
Solution
error one mentioned ndis.sys which is Network Driver Interface Specification
so its likely the lan drivers
May 11 2018rt640x64.sysRealtek NICDRV 8169 PCIe GBE Family Controller driver https://www.realtek.com/en/
Download Win10/Win11 Auto Installation Program (NDIS) from under windows header here - https://www.realtek.com/en/componen...0-1000m-gigabit-ethernet-pci-express-software

Error 2 isn't so clear. It could be same cause. It only shows memory actions, no processes I can say this = that. it happened after cpu tried to access ram, but that doesn't tell me a lot. CPU talking to ram is normal.
Hi, I ran the dump files through the debugger and got the following information: https://jsfiddle.net/45hjre0w/show This link is for anyone wanting to help. You do not have to view it. It is safe to "run the fiddle" as the page asks.
File information:121221-11109-01.dmp (Dec 12 2021 - 12:58:52)
Bugcheck:KERNEL_DATA_INPAGE_ERROR (7A)
Probably caused by:memory_corruption (Process: System)
Uptime:0 Day(s), 17 Hour(s), 46 Min(s), and 55 Sec(s)

File information:121121-9812-01.dmp (Dec 11 2021 - 17:28:43)
Bugcheck:UNEXPECTED_STORE_EXCEPTION (154)
Probably caused by:hardware_disk (Process: MemCompression)
Uptime:0 Day(s), 6 Hour(s), 55 Min(s), and 59 Sec(s)
Comment : hardware_disk was mentioned in one of the crashes. This is unusual as memory_corruption is listed in 98% of the dumps that I look at.

Possible Motherboard page: https://www.msi.com/Motherboard/z370-a-pro
There may be a BIOS update, but the MSI website is such a mess that it would take me 15 minutes to find your motherboard from the tiny drop down list on the support page. If there is an update, don't update just yet. Wait for more info.

This information can be used by others to help you. Someone else will post with more information. Please wait for additional answers. Good luck.
 
  • Like
Reactions: MrDboy12
error one mentioned ndis.sys which is Network Driver Interface Specification
so its likely the lan drivers
May 11 2018rt640x64.sysRealtek NICDRV 8169 PCIe GBE Family Controller driver https://www.realtek.com/en/
Download Win10/Win11 Auto Installation Program (NDIS) from under windows header here - https://www.realtek.com/en/componen...0-1000m-gigabit-ethernet-pci-express-software

Error 2 isn't so clear. It could be same cause. It only shows memory actions, no processes I can say this = that. it happened after cpu tried to access ram, but that doesn't tell me a lot. CPU talking to ram is normal.
 
Solution
Thanks, I'll check lan driver when I get home. The 2nd BSOD is the first I got last Saturday and is the same from the others (checked the minidump) they all state (nt!RtlDecompressBufferXpressLz+0x0000000000000050)
First was in july, I remember. Then 2nd and 3rd I had no clue, during weekdays when I wasn't home, in September, then in November. But sfc /scannow found corrupted files and repaired them following Saturday's crash, so maybe it's fixed now.
 
yeah, its all memory operations. Most of it virtual memory which doesn't really exist in any physical location, windows lies to applications about how much memory they could access, if they really need it. It manages to juggle it using page file and RAM.

The store that Unexpected Store Exception refers to is used to track all items in virtual memory.

(nt!RtlDecompressBufferXpressLz+0x0000000000000050)
this was last action before a page fault. Page faults are badly named actions of windows, they are normal.
Page fault - when CPU needs to access ram for an action
Hard fault - when CPU needs to look on page file
there are more but thats enough.

it appears the CPU tried to write info into ram but it didn't work. I cannot tell why, but if it has happened after the same action in a few errors, I would say the driver is giving it the wrong instructions.