[SOLVED] Random BSOD's

[Revious]

Hey fellas.


(PC SPECS)
OS: Windows 10 Professional (x64) Version 1903 (build 18362.418)
Board: ASUSTeK COMPUTER INC. M5A97 LE R2.0 Rev 1.xx
CPU: AMD FX8350
GPU: AMD RX 480 8GB
Storage:
SAMSUNG HD105SI [Hard drive] (1000.20 GB) -- drive 0, s/n S25GJ90Z504651, rev 1AJ10001, SMART Status: Healthy
Samsung SSD 850 EVO 250GB [Hard drive] (250.06 GB) -- drive 2, s/n S2R5NX0HC01362N, rev EMT02B6Q, SMART Status: Healthy
SanDisk SDSSDP128G (126.04 GB) -- drive 1, s/n 144528401210, rev 3.2.0, SMART Status: Healthy
RAM: 16 gb Kingston hyperx fury ddr3


So I "upgraded" to windows 10 from windows 7 a couple of weeks ago so that I could play some of the modern Windows games (Sea of Thieves, Forza, Outer Worlds, etc.) and all was fine and dandy for a while. That is until I started getting BSOD's at very random times. Sometimes it would happen during a gaming session. In a gaming session, it would happen anywhere from within 5 minutes to over 4 hours and I could not replicate the cause of the problem.

Then came a different kind of BSOD, it would crash whenever I tried to download or install things via a platform like Steam or Origin. I finally got fed up with this, and resorted to reformatting and reinstalling windows 10.

No problems at all installing or downloading programs after that... fast forward 2 days later and now I'm getting ANOTHER BSOD, this time "SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M" (Previous crashes were PNP_FATAL_ERROR or something like that.) -- these BSOD's are happening during gaming sessions again, and sometimes when I've just started a game and I'm focused onto the desktop instead of the game, it crashes within minutes.

I'm in the process of buying new PC components so I'm hoping this won't be an issue moving forward, but if there is a bad piece of hardware and it's not just some residual software glitch I would like to be prepared. I'm also waiting for American Black Friday sales too, and this is making using my PC right now almost unbearable.

Thanks in advance


On Wed 2019-10-30 1:25:55 PM your computer crashed or a problem was reported
crash dump file: C:\WINDOWS\Minidump\103019-10109-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x5E0E)
Bugcheck code: 0x1000007E (0xFFFFFFFFC0000005, 0xFFFFF80409A05E0E, 0xFFFFF60294CF9608, 0xFFFFA801EF446930)
Error: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M
file path: C:\WINDOWS\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that a system thread generated an exception which the error handler did not catch.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.



On Wed 2019-10-30 1:25:55 PM your computer crashed or a problem was reported
crash dump file: C:\WINDOWS\MEMORY.DMP
This was probably caused by the following module: ntkrnlmp.exe (nt!memset+0x6864)
Bugcheck code: 0x7E (0xFFFFFFFFC0000005, 0xFFFFF80409A05E0E, 0xFFFFF60294CF9608, 0xFFFFA801EF446930)
Error: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED
Bug check description: This bug check indicates that a system thread generated an exception that the error handler did not catch.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.



On Wed 2019-10-30 11:49:46 AM your computer crashed or a problem was reported
crash dump file: C:\WINDOWS\Minidump\103019-11265-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x1C1220)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF80310A8D518, 0xFFFFDB8230DD6550, 0x0)
Error: SYSTEM_SERVICE_EXCEPTION
file path: C:\WINDOWS\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that an exception happened while executing a routine that transitions from non-privileged code to privileged code.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.

 

[MrPepka]

See:
Blue Screen of Death (BSOD) Posting Instructions - Windows 10, 8.1, 8, 7 + Vista

 

[Revious]

Sorry, I can't edit my post again apparently.


· OS - Windows 10 x64 professional
· What was the originally installed OS on the system: Windows 7 Ultimate
· Is the OS an OEM version (came pre-installed on system) or full retail version (YOU purchased it from retailer): Retail, my PC is home built
· Age of system (hardware) 8 years
· Age of OS installation - have you re-installed the OS? Yes, first install to windows 7 I can't remember. Recent windows 10 installation was mid-September I believe, issues started a week or two after.

· CPU: AMD FX8350
· Video Card: AMD RX480 8GB
· MotherBoard - ASUS M5A97 LE R2.0
· Power Supply - I believe it's a 650-watt gold. Unsure of brand

· Laptop or Desktop: Desktop

I've run MEMTEST and HDD error checks, I've run registry cleans and malware cleans. Nothing out of the ordinary other than when I first installed windows 10 there was some HDD errors that were supposedly fixed.

Oh yeah, and when I ran driver verifier(before this current reformatted, reinstalled windows 10) it crashed my computer instantly and would crash every time I restarted just seconds after getting ready to hit the start button. I had to put the computer into safe mode w/ networking and that's when I reformatted/reinstalled.

 

[x BlueRobot]

Nothing out of the ordinary other than when I first installed windows 10 there was some HDD errors that were supposedly fixed.

What did you run to for those errors to be reported? chkdsk?

I've run registry cleans

Please refrain from using registry cleaners as usually they either do absolutely nothing, and if they do, they tend to cause more harm than good.

I'll hopefully be able to check the logs either later tonight or over the weekend for you.

 

[Revious]

What did you run to for those errors to be reported? chkdsk?

Yes.

Please refrain from using registry cleaners as usually they either do absolutely nothing, and if they do, they tend to cause more harm than good.

Really? I've used Eusing registry cleaner for over 10-15 years and never had an issue, and it always seems my computer responds and starts faster after it's cleaned. I guess it's a placebo effect.

I'll hopefully be able to check the logs either later tonight or over the weekend for you.

Thank you!

 

[Sysnative Windows Update]

Hi!

Is this still an issue?

 

[Revious]

Hi!

Is this still an issue?

Sorry forgot to reply here, I ended up reformatting the drive, reinstalling windows that fixed the original crash. Then another BSOD happened and I opened the case-- my SSD had become half unplugged which I assume was definitely causing the new(er) crash since plugging it fully and securing it better solved the issue.

If I had to guess, there was a windows 7 driver that wasn't compatible with windows 10 as the BSOD's only started happening after I upgraded to windows 10 from windows 7.

 

[Sysnative Windows Update]

Thanks for letting us know!