F5F Stay Refreshed Software Operating Systems Hey, can I get some help figuring out what made our brand new computer crash into a black screen?

Hey, can I get some help figuring out what made our brand new computer crash into a black screen?

Hey, can I get some help figuring out what made our brand new computer crash into a black screen?

Pages (2): 1 2 Next
A
ayapasdepb
Member
128
09-28-2026, 03:56 PM
#1
Hi guys. I bought a new PC and put Windows 11 on it. Since then, my computer keeps crashing many times every day. Sometimes this happens when I turn off into sleep mode or even while using it normally. Here is what my system looks like: https://drive.google.com/file/d/18vBKP6K...drive_link These are the crash log files summary: https://drive.google.com/file/d/134qCD5e...drive_link Things I tried to fix it - Updated the graphics card driver to the newest version - Used Driver verifier as suggested on this thread but didn't find a faulty driver - Ran my mainboard memory test and there were no errors Can you help me figure out why is this happening? Thanks
A
ayapasdepb
09-28-2026, 03:56 PM #1

Hi guys. I bought a new PC and put Windows 11 on it. Since then, my computer keeps crashing many times every day. Sometimes this happens when I turn off into sleep mode or even while using it normally. Here is what my system looks like: https://drive.google.com/file/d/18vBKP6K...drive_link These are the crash log files summary: https://drive.google.com/file/d/134qCD5e...drive_link Things I tried to fix it - Updated the graphics card driver to the newest version - Used Driver verifier as suggested on this thread but didn't find a faulty driver - Ran my mainboard memory test and there were no errors Can you help me figure out why is this happening? Thanks

P
Party_Big
Junior Member
25
09-28-2026, 08:35 PM
#2
P
Party_Big
09-28-2026, 08:35 PM #2

K
Kayania
Junior Member
13
09-29-2026, 01:54 AM
#3
My power supply is an Asus Rog Strix 1000W Aura Edition. My BIOS has been updated to the latest version. Here are my results from UserBenchmark: https://www.userbenchmark.com/UserRun/67084063 I tried running sfc /scannow, and it said that there were corrupt files, but it fixed them (which is good). Then I installed Samsung Magician software and updated all the drivers. I also reinstalled my Nvidia driver using DDU. I can confirm that I am using an XMP profile for my memory sticks. I'm worried about whether this might be a problem with high-frequency RAM. Now I am waiting to see if a new Blue Screen of Death (BSOD) shows up. PS: I still have the same BSOD error: ntoskrnl.exe at fffff806`49047000 0x16b96037
K
Kayania
09-29-2026, 01:54 AM #3

My power supply is an Asus Rog Strix 1000W Aura Edition. My BIOS has been updated to the latest version. Here are my results from UserBenchmark: https://www.userbenchmark.com/UserRun/67084063 I tried running sfc /scannow, and it said that there were corrupt files, but it fixed them (which is good). Then I installed Samsung Magician software and updated all the drivers. I also reinstalled my Nvidia driver using DDU. I can confirm that I am using an XMP profile for my memory sticks. I'm worried about whether this might be a problem with high-frequency RAM. Now I am waiting to see if a new Blue Screen of Death (BSOD) shows up. PS: I still have the same BSOD error: ntoskrnl.exe at fffff806`49047000 0x16b96037

K
KlayDog1
Senior Member
685
09-29-2026, 03:11 AM
#4
Your dump files aren't useful right now. You should always send over real dump files instead. Using that info doesn't make sense because what you pasted isn't actually a dump file; it's just output from BlueScreenView, which is completely useless for figuring out why your BSOD happened!
K
KlayDog1
09-29-2026, 03:11 AM #4

Your dump files aren't useful right now. You should always send over real dump files instead. Using that info doesn't make sense because what you pasted isn't actually a dump file; it's just output from BlueScreenView, which is completely useless for figuring out why your BSOD happened!

B
63
09-29-2026, 04:34 AM
#6
I tried fixing it with a verifier, but the computer crashed because the igovsd.sys driver caused trouble. That crash might be coming from my ASUS sound card. Can you tell me how to check if that's really what broke things?
B
bunnywithabowl
09-29-2026, 04:34 AM #6

I tried fixing it with a verifier, but the computer crashed because the igovsd.sys driver caused trouble. That crash might be coming from my ASUS sound card. Can you tell me how to check if that's really what broke things?

S
soldier2craft
Member
58
09-29-2026, 06:58 AM
#7
Only one of those five dumps had Driver Verifier turned on, but it still showed igovsd.sys in there (I guess you used BlueScreenView to figure that out?). That isn't actually your problem though; if you look at all five dumps together, you will almost certainly see a RAM issue. The other four dumps did not have Driver Verifier turned on, and three of them had bugcheck 0x1E with exception code 0xC0000005. That error means the computer tried to read from memory but couldn't do it because the data was corrupted or missing. Also, in those same four dumps, some call stacks pointed to unusual addresses that aren't normal for computers. These signs all point to bad RAM.

The other dump had a different kind of failure (0x50 bugcheck) and also showed strange addresses on the stack. Even the one caused by Driver Verifier failed because it couldn't find valid data in memory pools, which is often due to faulty RAM. I suggest you run a full RAM test so you can be sure your memory is working correctly. It will take a long time with 64GB of RAM but you really have no other option; your RAM needs checking.

Download Memtest86 (it's free), then use the imageUSB.exe tool to make a bootable USB drive that has Memtest86 on it. Make sure this USB is bigger than 1GB because enough space will be there. If possible, try doing this on another computer so you aren't relying on yours right now. Then plug that USB into your PC. As soon as the PC starts up, Memtest86 will begin running automatically.

If no errors are found after four rounds of testing with all 13 checks included in the free version, just start again and do another four rounds. Even one small error means you have a problem. Let me know how that goes.
S
soldier2craft
09-29-2026, 06:58 AM #7

Only one of those five dumps had Driver Verifier turned on, but it still showed igovsd.sys in there (I guess you used BlueScreenView to figure that out?). That isn't actually your problem though; if you look at all five dumps together, you will almost certainly see a RAM issue. The other four dumps did not have Driver Verifier turned on, and three of them had bugcheck 0x1E with exception code 0xC0000005. That error means the computer tried to read from memory but couldn't do it because the data was corrupted or missing. Also, in those same four dumps, some call stacks pointed to unusual addresses that aren't normal for computers. These signs all point to bad RAM.

The other dump had a different kind of failure (0x50 bugcheck) and also showed strange addresses on the stack. Even the one caused by Driver Verifier failed because it couldn't find valid data in memory pools, which is often due to faulty RAM. I suggest you run a full RAM test so you can be sure your memory is working correctly. It will take a long time with 64GB of RAM but you really have no other option; your RAM needs checking.

Download Memtest86 (it's free), then use the imageUSB.exe tool to make a bootable USB drive that has Memtest86 on it. Make sure this USB is bigger than 1GB because enough space will be there. If possible, try doing this on another computer so you aren't relying on yours right now. Then plug that USB into your PC. As soon as the PC starts up, Memtest86 will begin running automatically.

If no errors are found after four rounds of testing with all 13 checks included in the free version, just start again and do another four rounds. Even one small error means you have a problem. Let me know how that goes.

S
Summer_Cool
Member
175
09-30-2026, 04:32 PM
#8
I used WinDbg to find the problem. I tested my RAM with Memtest on the Asus BIOS, and it didn't crash yet. But when I tried the standalone app, things changed. What do you think about that XMP profile? And what about those 5600Hz sticks? Someone told me that high-speed RAM can make the system unstable.
S
Summer_Cool
09-30-2026, 04:32 PM #8

I used WinDbg to find the problem. I tested my RAM with Memtest on the Asus BIOS, and it didn't crash yet. But when I tried the standalone app, things changed. What do you think about that XMP profile? And what about those 5600Hz sticks? Someone told me that high-speed RAM can make the system unstable.

Z
52
10-08-2026, 07:07 AM
#9
Don't get BSODs when your computer crashes; just take out all the extra settings for speed up now. Even though the memory is officially tested for those high speeds, it's safer to remove the XMP boost setting instead.
Z
zamoraktheking
10-08-2026, 07:07 AM #9

Don't get BSODs when your computer crashes; just take out all the extra settings for speed up now. Even though the memory is officially tested for those high speeds, it's safer to remove the XMP boost setting instead.

J
JebThePleb
Posting Freak
898
10-10-2026, 10:39 AM
#10
There were a lot of mistakes in Test 10 on one of my memory chips, so I am going to fix the RAM and report back to you later.
J
JebThePleb
10-10-2026, 10:39 AM #10

There were a lot of mistakes in Test 10 on one of my memory chips, so I am going to fix the RAM and report back to you later.

Pages (2): 1 2 Next