Fresh install 20H2 PC crashed while streaming

[MajorFoley]

So was streaming for a bit and my computer had decided to crash. This is a pretty fresh install, only a day old all updates installed on latest windows. Wasnt a BSOD but my screens went distorted and colours were weird, i wasn't able to get a picture on my phone in time but when i checked event viewer it came up wit ha bugchecker ""The bugcheck was: 0x00000139 (0x0000000000000003, 0xfffffe8618f3a890, 0xfffffe8618f3a7e8, 0x0000000000000000"

It gave me a memory dump file too thats about 1gb. Should i post it here?

Thanks.

Specs

Win 10 pro

MB x570 prime pro Asus

Ryzen 3700x

Nvidia ASUS TUF 3070

Corsair 750W RMx

G.skill cl16 3600mhz Trident z Neo

 

[jaslion]

Don't post a 1gb dump file. It's literally that a dump. The chances you get anything useful out of it is rare.

 

What I'd do is DDU the drivers and try streaming again could very well be a one time thing.

[MajorFoley]

2 minutes ago, jaslion said:

Don't post a 1gb dump file. It's literally that a dump. The chances you get anything useful out of it is rare.

 

What I'd do is DDU the drivers and try streaming again could very well be a one time thing.

The GPU drivers? I did see Nvidia has some new ones think mine were from the start of April. Guess I'll give it a shot.

[jaslion]

Just now, MajorFoley said:

The GPU drivers? I did see Nvidia has some new ones think mine were from the start of April. Guess I'll give it a shot.

Yes but use DDU (display driver uninstaller) first to uninstall the old ones this makes sure nothing that caused issues is left behind. Do make sure you have the new ones downloaded beforehand so windows doesn't try to autoinstall some random old problematic ones.

[MajorFoley]

Just now, jaslion said:

Yes but use DDU (display driver uninstaller) first to uninstall the old ones this makes sure nothing that caused issues is left behind. Do make sure you have the new ones downloaded beforehand so windows doesn't try to autoinstall some random old problematic ones.

Yeah first time i did the fresh install i had an issue with infinite updating. When i do use DDU i do it in safe mode with the adapter disabled and the new drivers already downloaded

[StDragon]

https://www.resplendence.com/whocrashed to analyze the minidump files located in C:\Windows\Minidump

 

and make sure you don't have RAM errors with Memtest86

 

https://www.memtest86.com/

 

Reinstalling Windows and drivers won't fix an underlaying hardware issue.

[MajorFoley]

8 minutes ago, StDragon said:

https://www.resplendence.com/whocrashed to analyze the minidump files located in C:\Windows\Minidump

 

and make sure you don't have RAM errors with Memtest86

 

https://www.memtest86.com/

 

Reinstalling Windows and drivers won't fix an underlaying hardware issue.

I ran memtest a month ago while i was still on my older install (i did use the USB one). Definitely no errors there passed its checks. According to that who crashed program this file could have been responsible for it?
ntkrnlmp.exe

Doesnt say anything else...

[StDragon]

36 minutes ago, MajorFoley said:

According to that who crashed program this file could have been responsible for it?
ntkrnlmp.exe

Doesnt say anything else...

ntkrnlmp.exe is kernel space. It's the core of the OS. A BSOD (Blue Screen of Death) is also known as a "kernel panic". For whatever reason, when something is miscalculated in this area, it will essentially throw up its hands and crash leaving behind a trace of evidence (dump files) to assist in tracking down the root cause. But do understand that correlation doesn't imply causation. Antimalware programs and device drivers run in kernel space. While a driver might be associated with the crash, it doesn't mean the driver itself was bugged as written, rather there was a hardware level fault that caused the driver to fault the kernel.

TLDR; if you have random BSOD events (not just timing), it's usually CPU, RAM, or MB related. However for example you have BSODs with a video driver causing it, then you probably either have a bugged driver, or the GPU or its VRAM is malfunctioning.

[MajorFoley]

1 minute ago, StDragon said:

ntkrnlmp.exe is kernel space. It's the core of the OS. A BSOD (Blue Screen of Death) is also known as a "kernel panic". For whatever reason, when something is miscalculated in this area, it will essentially throw up its hands and crash leaving behind a trace of evidence (dump files) to assist in tracking down the root cause. But do understand that correlation doesn't imply causation. Antimalware programs and device drivers run in kernel space. While a driver might be associated with the crash, it doesn't mean the driver itself was bugged, rather there was a hardware level fault that caused the driver to fault the kernel.

TLDR; if you have random BSOD events (not just timing), it's usually CPU, RAM, or MB related. However for example you have BSODs with a video driver causing it, then you probably either have a bugged driver, or the GPU or its VRAM is malfunctioning.

Yay a 3070 that would have a hardware issue would be just wonderful... or my 3700x... I'm hoping the driver reinstallation would stop it and its a one of thing but i guess we will see... I don't really want to buy a 5000 series CPU yet or ever really. And since im pretty sure it isn't ram the only 2 culprits would be the CPU or GPU, i did update my chipset via AMD chipset drivers and not my manufacturers as well.

[StDragon]

2 minutes ago, MajorFoley said:

Yay a 3070 that would have a hardware issue would be just wonderful... or my 3700x... I'm hoping the driver reinstallation would stop it and its a one of thing but i guess we will see... I don't really want to buy a 5000 series CPU yet or ever really. And since im pretty sure it isn't ram the only 2 culprits would be the CPU or GPU, i did update my chipset via AMD chipset drivers and not my manufacturers as well.

"G.skill cl16 3600mhz Trident z Neo"

 

That right there is a telling sign. That's overclocked memory. Try stepping that down to 3200 or 2666 and see if that clears it up. If it does, you've isolated the scope of the issue.

[MajorFoley]

6 minutes ago, StDragon said:

"G.skill cl16 3600mhz Trident z Neo"

 

That right there is a telling sign. That's overclocked memory. Try stepping that down to 3200 or 2666 and see if that clears it up. If it does, you've isolated the scope of the issue.

If the issue continues after the driver wipe i will. I'm hoping it wont come to that. Especially since my QVL list says its supported. I might run another memtest just in case as well.

[StDragon]

A memtest will generally tease out any faults or timing issues with the DIMMs. But often synthetic tests won't get everything. Sometimes it's the interplay of the entire system such as CPU load, and dynamic clock rate.

 

Also be sure you have the two DIMMs in the correct slots. That will be listed in the MB manual.

[MajorFoley]

Just now, StDragon said:

A memtest will generally tease out any faults or timing issues with the DIMMs. But often synthetic tests won't get everything. Sometimes it's the interplay of the entire system such as CPU load, and dynamic clock rate.

 

Also be sure you have the two DIMMs in the correct slots. That will be listed in the MB manual.

Yup made sure of that too when i had to replace my Motherboard for a different issue. If i recall though i think my last test only did 6 passes and its recommended to run 8 or more. So better safe than sorry i guess.

[MajorFoley]

So the error popped up once again. It seems to only happen with a certain game, that being Warhammer 40k Dark crusade. Anything else i can do just fine so im wondering why. It is an old game but ive done a bunch of older games just fine...