[SOLVED] BSOD issue happening yet again - 0x3B

fireweed

fireweed

Active member
Joined
Oct 14, 2021
Posts
40
Location
Alberta, Canada
In January I took my desktop apart for a cleaning, and to upgrade my CPU cooler and M.2. When I did this I also reinstalled windows hoping it would fix some of the stability issues happening. Considering that I've had a crash each day the last two days I'd say that didnt happen. Last month I has some crashes as well- 0xD1 with afd.sys. I did some maintance, driver updates, ect, and things calmed down. I ran driver verifier at the time and the only issue I had was when I was playing Minecraft.

These two most recent ones (and a few in the past) have happened when the computer either turned on or woke from sleep. I'm pretty sure that at least once it was because I turned my headset on during startup, and it crashed as soon as I did that.

Possibly unrelated or paranoid, but I swear my computer turned itself on a few days ago. I turned it off for the night, and I always watch it for a few seconds after it turns off, because sometimes I click restart by accident. It looked to be completely shut down so I went to bed. I wake up and notice the computer is now asleep. I can tell if it's sleeping or off because the RAM rgb stays on if the computer is sleeping. It was very strange, and when I logged in explorer and lsass.exe were crashed and the computer restarted. I'm quite confident the computer was turned off and not restarted as the RAM rgb turned off.

The only thing I have not done is update the bios. I know I should, but as I discovered last time I posted, the Asus driver/bloatware program does not offer any, and when I attempted to run the manual utility driver verifier threw a fit and crashed the system. I'm in the middle of the semester and I cant afford a bricked computer. If it's really the only thing I have left to try I can. Oh, and memory diagnostics I ran a few weeks ago were fine.

Attached is file collection. Not sure if the most recent memory dump got in there or not. When I ran it through my windbg it complained about missing symbols and wouldn't analyze properly.

Thanks
 

Attachments

I am afraid that there will be no need to update the BIOS in this case. Your motherboard has a BIOS flashback feature called BIOS Flashback (or something like that) so you can give it a try
 
MrPepka said:
I am afraid that there will be no need to update the BIOS in this case. Your motherboard has a BIOS flashback feature called BIOS Flashback (or something like that) so you can give it a try
Click to expand...
I've been meaning to update for awhile now. I'm going to look into it again this weekend, I think.
x BlueRobot said:
Which memory diagnostic program did you run?
Click to expand...
I used the built I'm windows one. I couldn't get Prime to work after an hour or so of troubleshooting.
x BlueRobot said:
Please removal MBAM using their removal tool, which can be found here.
Click to expand...
Darn it, I just renewed my yearly premium subscription. Does it look like this is what's causing the bsod? I'll remove it later today when I get home.
 
fireweed said:
Darn it, I just renewed my yearly premium subscription. Does it look like this is what's causing the bsod? I'll remove it later today when I get home.
Click to expand...
It appears to be most likely culprit, you could try a clean install it to the latest version and see if that makes a difference? The instructions are the in the same link.

fireweed said:
I used the built I'm windows one.
Click to expand...
You really should MemTest86, the Windows one isn't that good to be honest.
 
The logs had a lot of paging errors.
If not already tested please test the drive > drives (all drives):

a) Sea Tools long generic
b) HD Tune Health, Benchmark, Full error scan


SeaTools 5 (Windows) | Seagate
HD Tune website



Code: 
------------------------
Disk & DVD/CD-ROM Drives
------------------------
      Drive: C:
 Free Space: 133.1 GB
Total Space: 237.8 GB
File System: NTFS
      Model: KINGSTON SA2000M8250G

      Drive: D:
 Free Space: 996.7 GB
Total Space: 1907.6 GB
File System: NTFS
      Model: ST2000DM008-2FR102

      Drive: E:
 Free Space: 457.7 GB
Total Space: 953.9 GB
File System: NTFS
      Model: Seagate FireCuda 520 SSD ZP1000GM30002



Code: 
Event[19]:
  Log Name: System
  Source: disk
  Date: 2022-03-08T18:08:25.0840000Z
  Event ID: 51
  Task: N/A
  Level: Warning
  Opcode: N/A
  Keyword: Classic
  User: N/A
  User Name: N/A
  Computer: DESKTOP-8TKGGTK
  Description:
An error was detected on device \Device\Harddisk2\DR2 during a paging operation.

Event[20]:
  Log Name: System
  Source: disk
  Date: 2022-03-08T18:08:24.9430000Z
  Event ID: 51
  Task: N/A
  Level: Warning
  Opcode: N/A
  Keyword: Classic
  User: N/A
  User Name: N/A
  Computer: DESKTOP-8TKGGTK
  Description:
An error was detected on device \Device\Harddisk2\DR2 during a paging operation.


Code: 
An error was detected on device \Device\Harddisk4\DR9 during a paging operation.

Code: 
An error was detected on device \Device\Harddisk1\DR1 during a paging operation.
 
Last edited by a moderator:
x BlueRobot said:
It appears to be most likely culprit, you could try a clean install it to the latest version and see if that makes a difference? The instructions are the in the same link.
Click to expand...
I've removed it. Fingers crossed this solves things, but I'll call it fixed if I go a month without crashing.
x BlueRobot said:
You really should MemTest86, the Windows one isn't that good to be honest.
Click to expand...
Last time I tried to run it there were issues getting the program to work. They must have fixed that in an update because it worked this time, RAM did 4 passes no errors.
 
Okay, hopefully you won't have any problems. Ideally, you should run MemTest86 for two sets of 4 passes, but your crashes are too consistent with each other for to be RAM in my opinion, so I wouldn't worry about it for now.
 
x BlueRobot said:
Okay, hopefully you won't have any problems. Ideally, you should run MemTest86 for two sets of 4 passes, but your crashes are too consistent with each other for to be RAM in my opinion, so I wouldn't worry about it for now.
Click to expand...
Yeah, I think it's alright now. Plus since I have 32GB it took absolutely forever.

I know its not directly related, but do you have any idea why my computer may have turned itself on? It's not connected to ethernet so it couldn't be wake on lan. It's in a little closet when it's off so no pets could have pushed the button. (this is why I was so worried because ventilation is shitty when the metal mesh door is closed. I turned off fast startup after it happened and it hasn't happened since. I'm hoping that was the solution...
 
fireweed said:
I know its not directly related, but do you have any idea why my computer may have turned itself on?
Click to expand...
As you just mentioned, I would have said that Modern Standby (fast startup) was the issue here. With Modern Standby, the system doesn't fully switch off and certain system processes such as Windows Update as able to wake the computer. I assume that an application may have been running in the background which caused the system to wake and then subsequently crash at some point.
 

Has Sysnative Forums helped you? Please consider donating to help us support the site!

Back
Top