Question PC Crashes when idle

[OneShotRengo]

Hey guys, so I've been having this issue since the day I built my pc. And yes, before any of you ask, I have reinstalled windows about two times now and the issue still persist. I've opened the minidump file using Windbg and this is what the debug says. I've removed any overclocks I had applied. I've also tried using memtest and it said everything is fine. I don't know how to read this and figure out what is causing it, but if you can please tell me I would really appreciate it. Also, I want to point out that it also crashes even when playing a game, as long as the game is idle and I am not alt tabbing or playing at the time (for example: if I afk while playing a game), it would crash eventually. I also have a minidump of the crash that occured while having World of Warcraft on.


https://pastebin.com/SLdiutV3 This is the mini dump of my pc crashing just by logging into windows and leaving it idle.

https://pastebin.com/ztZ4bi1W This is the mini dump of my pc crashing when logging into wow, and sitting in a queue and just being afk/idle while I get into the game.

 

[rgd1101]

full system spec? include make and model of the psu

 

[OneShotRengo]

This is the full build

https://pcpartpicker.com/list/ky3jYT

Edit: Here's an imgur in case link does not work

 

[OneShotRengo]

This is the most current crash I've gotten, so far I've removed the 3200 clock on my ram from the bios. I also removed my nvidia drivers and I reinstalled 419.67. I also got another crash earlier and I looked at the mini dump and it mention something from razer called razergamemanager or somethimg, I removed it and everything was good for a few hours. This is the current crash I am getting.My pc crashes, gets a blue screen that goes to 100% but never restarts. It freezes on the blue screen.

https://pastebin.com/9esdzTVF
Any help is greatly appreciated.

 

[vMax]

Looks like a driver issue...In device manager do you see a device with a yellow exclamation mark? Also in startup disable all non essential programs from starting up especially the NZXT monitoring software (if you are using it) as sometimes that can be an issue. Make sure you have all the very latest drivers installed.

Sorry I cannot be of more help but fingers crossed others will jump in soon but it looks like a driver issue somewhere.

 

[OneShotRengo]

Looks like a driver issue...In device manager do you see a device with a yellow exclamation mark? Also in startup disable all non essential programs from starting up especially the NZXT monitoring software (if you are using it) as sometimes that can be an issue. Make sure you have all the very latest drivers installed.

Sorry I cannot be of more help but fingers crossed others will jump in soon but it looks like a driver issue somewhere.

I checked my device manager, and no there were no exclamation marks anywhere. As for my NZXT, it's NZXT CAM, I only use it to control my lighting, but I will give that a shot and see what happens.

 

[OneShotRengo]

I gave it a try and no luck. This is my most current crash mini dump.

https://pastebin.com/cVGv3rLD

 

[Flayed]

I gave it a try and no luck. This is my most current crash mini dump.

https://pastebin.com/cVGv3rLD

https://docs.microsoft.com/en-us/wi...r/bug-check-0x50--page-fault-in-nonpaged-area

Cause
Bug check 0x50 can be caused by the installation of a faulty system service or faulty driver code. Antivirus software can also trigger this error, as can a corrupted NTFS volume.

It could also occur after the installation of faulty hardware or in the event of failure of installed hardware (usually related to defective RAM, be it main memory, L2 RAM cache, or video RAM).

It could be your ram. I suggest setting the ram to the loosest timings and lowest frequency in the bios and see if the problem persists.

 

[scout_03]

recheck all driver for the latest ones give a look in the gpu one also .

 

[OneShotRengo]

https://docs.microsoft.com/en-us/wi...r/bug-check-0x50--page-fault-in-nonpaged-area

Cause
Bug check 0x50 can be caused by the installation of a faulty system service or faulty driver code. Antivirus software can also trigger this error, as can a corrupted NTFS volume.

It could also occur after the installation of faulty hardware or in the event of failure of installed hardware (usually related to defective RAM, be it main memory, L2 RAM cache, or video RAM).

It could be your ram. I suggest setting the ram to the loosest timings and lowest frequency in the bios and see if the problem persists.

Sounds good, I will give that a try tomorrow and see what happens. This is a crash that I got a few minutes before replying to this. Not sure if it's different to any of the other ones, but it did look like it. The error it gave me on the blue screen was different. https://pastebin.com/F1BipbZd

edit: Gave this a try and it didn't work. However. it did give me a different name crash. Here is the current mini dump I got while doing this. https://pastebin.com/fBPXmG7C . I tried setting the ram to 1333 and it seemed to crash around the same time it normally does.

 

[Karadjgne]

Do you use ccleaner from piriform.com? If not, you can try that, use the cleaner until it's empty, but also alternate with the registry tool. Leave at default settings and say Yes to save prompts. Many times there's orphans or incomplete erasure/deletion by windows or other programs/drivers that'll still contain addresses, and that can conflict, can happen during idle when windows is running background stuff.

 

[Flayed]

Sounds good, I will give that a try tomorrow and see what happens. This is a crash that I got a few minutes before replying to this. Not sure if it's different to any of the other ones, but it did look like it. The error it gave me on the blue screen was different. https://pastebin.com/F1BipbZd

Looks like another memory related crash. To rule out a driver or other software boot into safe mode and see if the machine crashes.

 

[OneShotRengo]

Do you use ccleaner from piriform.com? If not, you can try that, use the cleaner until it's empty, but also alternate with the registry tool. Leave at default settings and say Yes to save prompts. Many times there's orphans or incomplete erasure/deletion by windows or other programs/drivers that'll still contain addresses, and that can conflict, can happen during idle when windows is running background stuff.

No I don't use ccleaner nor have it installed, but I'll download it and give it a shot!

edit: Gave this a try and no luck, although it did show like 100 things that got fixed.

 

[OneShotRengo]

The strange part I don't understand is that it will only crash if it is idle. As long as I am playing a game or alt tabbing or doing multiple things without stopping it will not crash. I could be playing for hours, and when I go use the restroom and come back I'll see my monitor with a blue screen. It never restarts, it always loads the blue screen to 100% and freezes.

https://pastebin.com/fBPXmG7C Most current crash 10/24/2019 (while underclocking ram to 1333mhz.)

 

[Ketchup79]

Well it's crashing on your video card driver in the last one, but all others are plain memory corruption, which is interesting since you were underclocking the RAM on the last one. I know you said you were overclocking, but now you are not. Did you have crashes before you dropped the overclock? Makes me wonder if there are some bad files at play here. What are your temp like? If you haven't already, run sfc /scannow and see if it finds any problems. If this issue continues, you may want to consider a re-install of Windows, just to rule out a software problem.

 

[Flayed]

The strange part I don't understand is that it will only crash if it is idle. As long as I am playing a game or alt tabbing or doing multiple things without stopping it will not crash. I could be playing for hours, and when I go use the restroom and come back I'll see my monitor with a blue screen. It never restarts, it always loads the blue screen to 100% and freezes.

https://pastebin.com/fBPXmG7C Most current crash 10/24/2019 (while underclocking ram to 1333mhz.)

Crashing when idle has got me thinking about the power saving settings in the bios, C states? I vaguely remember another thread on a different forum changing those settings in the bios fixed instability. I don't really know much about it but I think it would be worth investigating, perhaps try disabling all the power saving at first and see is it still crashes, if not play around with the settings a bit.

 

[OneShotRengo]

Crashing when idle has got me thinking about the power saving settings in the bios, C states? I vaguely remember another thread on a different forum changing those settings in the bios fixed instability. I don't really know much about it but I think it would be worth investigating, perhaps try disabling all the power saving at first and see is it still crashes, if not play around with the settings a bit.

Gonna give this a try first thing tomorrow morning!

Edit: Was really hoping this would fix it because I never thought of trying this, but sadly it didn't. It did give me a new crash name though, I think it was something the lines of dxgkrnl or something like that. Here is most current mini dump that happened https://pastebin.com/UgGaLZ7r .

 

[OneShotRengo]

Well it's crashing on your video card driver in the last one, but all others are plain memory corruption, which is interesting since you were underclocking the RAM on the last one. I know you said you were overclocking, but now you are not. Did you have crashes before you dropped the overclock? Makes me wonder if there are some bad files at play here. What are your temp like? If you haven't already, run sfc /scannow and see if it finds any problems. If this issue continues, you may want to consider a re-install of Windows, just to rule out a software problem.

Yeah I was getting crashes prior to under clocking the ram. I have also tried that sfc /scannow before multiple times, but I guess it doesn't hurt to try again. I am just trying to do what I can before reinstalling windows because everytime that has been my go to fix but it always ends up not working in the end.

 

[OneShotRengo]

Most current crash with bios on default settings with c states off. https://pastebin.com/UgGaLZ7r 10/25/2019

 

[Flayed]

Think I would be getting annoyed now and start RMAing stuff, CPU, motherboard, Ram lol