Question Repeated BSOD WHEA_UNCORRECTABLE_ERROR (124) on Device Driver Error ?

[johnbl]

I was looking at some of your files that the debugger did not like
the files were from 2020 around June and July.
windows build 19.9.19041
Microsoft has listed this build as "End of servicing"
it could explain why the proper debugging files were not on the server.

it would also mean that your windows updates are blocked from mid 2020

note: window update only updates drivers that vendors actually give to them. Many vendors only give very basic drivers to Microsoft and keep the drivers with more features for their own updates. when windows sees these custom drivers it will not update them with the basic driver and you are expected to know this and get the update from the motherboard vendor or the actual driver vendor. (most people would not know, I try to keep the generic drivers from Microsoft since they get fixed and tested on millions of machines everyday. (less problems for me since windows update will update the generic intel drivers)

 

[niv13]

Any ideas why there is so much mismatched files on my system? I'm contemplating if I should just go for a upgrade on the machine and start everything fresh

 

[johnbl]

Any ideas why there is so much mismatched files on my system? I'm contemplating if I should just go for a upgrade on the machine and start everything fresh

I think the updates are being blocked. you can run the dism.exe command and it might fix the problem but It might just better to wipe and reinstall windows with the current build.

 

[ubuysa]

Before you reinstall, did you ever enable Driver Verifier as I suggested in post #4, and have you uploaded any resulting dumps? It wasn't enabled in any of the dumps you have uploaded.

The problem with reinstalling Windows without knowing what the problem might be - especially if it could be a bad driver - means that there is a high probability that you will reinstall the problem and be back to square one.

 

[johnbl]

Before you reinstall, did you ever enable Driver Verifier as I suggested in post #4, and have you uploaded any resulting dumps? It wasn't enabled in any of the dumps you have uploaded.

The problem with reinstalling Windows without knowing what the problem might be - especially if it could be a bad driver - means that there is a high probability that you will reinstall the problem and be back to square one.

he was running a old windows build with a bunch of modified windows core files. I would expect the system to bugcheck quickly unter verifier and end the end you find that hacks are the problem. looks like Microsoft removed the symbols for the old build from the Microsoft symbol server.

 

[ubuysa]

Fair enough.

 

[niv13]

he was running a old windows build with a bunch of modified windows core files. I would expect the system to bugcheck quickly unter verifier and end the end you find that hacks are the problem. looks like Microsoft removed the symbols for the old build from the Microsoft symbol server.

Can you elaborate more in this? I have a bit difficulty understanding you. Are you saying that my computer potentially was hacked?

What is the "symbols" that you mentioned here?

 

[niv13]

Before you reinstall, did you ever enable Driver Verifier as I suggested in post #4, and have you uploaded any resulting dumps? It wasn't enabled in any of the dumps you have uploaded.

The problem with reinstalling Windows without knowing what the problem might be - especially if it could be a bad driver - means that there is a high probability that you will reinstall the problem and be back to square one.

My computer is over due for a proper upgrade... There are components in there that are over 5 years old at this point.

While I don't think any of the hardware are having physical problems, I'm forced to recognize that with end-of-life coming for Windows10. I'm eventually forced to use Windows 11 and likely with even more driver support issues coming.

What I can't understand is how the window core files have been changed so much like this. I don't recall ever suffering a hack and/or having some malware/ virus in the computer. There's the on and off alert from my antivirus (ESET) warning of attempt to change things but those are usually minor and any attempt gets flagged right away...

 

[niv13]

Before you reinstall, did you ever enable Driver Verifier as I suggested in post #4, and have you uploaded any resulting dumps? It wasn't enabled in any of the dumps you have uploaded.

The problem with reinstalling Windows without knowing what the problem might be - especially if it could be a bad driver - means that there is a high probability that you will reinstall the problem and be back to square one.

I haven't ignored your suggestion. I'm actually quite interested in investigating the issue further using your method. It's just that I would need this computer (as broken as it is with the BOSD) working for now while I prepare to build a 2nd rig to take over. Once I have the 2nd rig's integrity checked and all good to go (in Windows 11), I'll be more inclined to do more tests on this old one.

I'll start another post thread discussing builds for my 2nd rig. Please chip in your opinions there too 🙏