New
#1
BSOD at random times, mostly error 0x3b
Hi all,
I searched the BSOD section of this forum for threads with similar problems, but none of the solutions seem to have the desired effect. I'm wondering if maybe I'm missing something, or if my pc is really dying..
Since a month or so, I've been receiving loads of BSODs while basically doing nothing special (random browsing, Spotify, MS Excel, sometimes even when idling). Most of the times the error code was 0x3b, system service exception, 'caused by' driver ntoskrnl.exe. From what these forums and WhoCrashed tell me, this is likely not really the causing driver. Sometimes other error codes (d1, 7e) occur, although I suspect the latter to be the result of me messing around with driver updates in order to fix the 3b-error problem.
Notably, the 3b-errors started to become frequent after returning from holiday and switching the pc back on after 3 weeks of absence (end of August). Previously I only had the 3b-error a couple of times over the course of 3 years, but it DID happen before, so there might be some underlying cause that has always been there. Anyway, a few days later the errors seemed to be gone again, but about a week ago the sh*t really hit the fan, so to say, and the 3b-BSODs now happen pretty much 10 times a day...
What I've already tried:
- Updating the drivers. I also looked to see if the BIOS needed updating, but apparently I already have the latest version
- Checking if all wires and cables were plugged in decently and removing excessive dust (although there wasn't really much dust)
- System restore to the point before the BSODs started happening 10 times a day
- Running memtest86+ for I think 13 or so passes, 0 errors found
- Running Driver Verifier, which did make the system BSOD, but I still couldn't figure out the culprit. Come to think of it, I've updated a lot of drivers afterwards, so I'll run it again to see if it does anything, any upcoming dumpfiles I will post later.
All these, as you'd figured from me starting this thread, to no avail..
I have to admit I'm really unfamiliar with these kinds of issues, so I only have a slight clue as how to interpret all various diagnostic tools (WhoCrashed, windbg), so to you there might be something obvious that I simply cannot figure out. If I need to do anything, a (link to) some sort of explanation how to do so would be much appreciated.
Enclosed you find the stuff DM log collector gathered, I hope that'll be a good starting point for any analysis.