Hello. I'm helping a friend's dad out with their computer. Right now it's BSODing randomly and we can't seem how to figure out how to replicate the issue on command. I installed BSOD viewer and tried to do my own research, but hit a wall. I'm hoping one of you tenforums guru's can come to his aid. Thanks!
OS: Win 10 21H2 (OS Build 19044.1466)
Zip file was too big for forum so I put in in Google Drive: MINNICH-PC-(2022-02-08_16-18-58).zip - Google Drive
Hello
To give you a chance on this, the first thing i would do is,
Goto 'System' and then the 'Advanced' option. Now select the Advanced tab and at the bottom of that Window, is a box which says 'Startup and Recovery'. Go into there.
You'll see a box which says 'Automatically Restart' below System failure options, which for now take the tick out, so when it crashes next time, the BSOD will stay on the screen and you can have abit more of a look and chance to see the error.
Also make sure you have the system writing a 'Memory Dump' and not a 'Kernel Dump'
With the BSOD frozen on the screen, write down the info and get back to us
I have one single question. Why is your friends dad using a volume license (enterprise)?
genuine.txt said:What is a volume Mak channel?
Volume Licensing (MAK/KMS)
Enterprise buys Windows license in bulk under Volume Licensing Program. There are two types of keys under this scheme – MAK and KMS. You can use MAK keys only once, while KMS keys can be used again.
Got it, I will do this now and wait for the next occurrence.Hello
To give you a chance on this, the first thing i would do is,
Goto 'System' and then the 'Advanced' option. Now select the Advanced tab and at the bottom of that Window, is a box which says 'Startup and Recovery'. Go into there.
You'll see a box which says 'Automatically Restart' below System failure options, which for now take the tick out, so when it crashes next time, the BSOD will stay on the screen and you can have abit more of a look and chance to see the error.
Also make sure you have the system writing a 'Memory Dump' and not a 'Kernel Dump'
With the BSOD frozen on the screen, write down the info and get back to us
UPDATE: I unchecked restart, and it was set to Automatic Memory Dump.
- - - Updated - - -
I suppose so. I think his office IT built this PC. It's not a pre-manufactured one.
EDIT: it just BSODed again, here is a picture of the screen.
Last edited by manchua; 09 Feb 2022 at 11:48.
In the Search box,start typing in---reliability history---.
If there are any red flagged events,then select ---view tech details--- and lines 1-3 should give you information,which can be used to find a possible solution.
Ok,
As a test i'd create another Administrator account and use that for a while and do the same again, see if it happens.
User account control option might be good to disable and enable as two other tests, whilst you wait for it to crash again.
Try that next, would be a productive test.
You can type into the Start Run menu for a IRQ tool
msconfig
Then in the tab which says 'tools' , scroll down and you'll see a line saying 'System Information'. Launch that program and you'll see all the interupt requests throughout the system, which might give you a lead on where the issue could be.
Did the forum tool that creates a zip file not include the minidump folder? There are lots of bdos logs or reports in that folder. Not sure if those could be helpful if they weren't included. In the meantime, I'm going to create a new user and go from there. I'll also look at the reliability history today. Thanks for helping.
UPDATE: it BSODed on a new admin user.
Last edited by manchua; 11 Feb 2022 at 12:55.
I suspect the PSU is making the CPU cores unstable. Post #4 is the same stop code I used to get with my T-bird 900@1050, because it couldn't do 1050 MHz.
In the OP's case it's not an unstable CPU OC, however. But it's the same stop code that XP gave me back in 2002 when running Need For Speed III, when my Athlon T-bird couldn't do 1050 MHz. And in my case, I did have a crappy power supply, a Deer DR 250 ATX. Eww!
Almost exactly 20 years ago, maybe it was my power supply that caused me to be unable to do 1.05 GHz with my Thunderbird! All I did for my OC, was raise the CPU multiplier to what would be 10.5 from the stock 9.0. (and Vcore set to 1.85V)
So the installer itself BSODed as I was reinstalling windows which made me (for obvious reasons) suspect hardware issues. I'm currently running memtest 86, but a PSU swap is easy enough to do, so I'll try that after memtest has run a few cycles.
- - - Updated - - -
Update. I've replaced the PSU with a brand new one. The old one was an 80+ bronze antec one, but it still BSODed. This is a brand new Windows 10 installation now. I had some trouble with memtest, so I've removed one of the two sticks of ram and I'm going to see if the issues persists, and if so, use the other stick by itself. This PC also has a GPU in it. Is there anything in the logs that could indicate it being the problem? Thanks!
Quote
