[SOLVED] BSOD only when not playing games. pls help

3XD3

Prominent
Dec 27, 2019
15
0
510
I recently decided to upgrade the cpu, motherboard and ram that is in my system and ever since doing so I have had nothing but BSODs every 10-20 minutes. The only time it doesnt go to a BSOD is when i'm playing a relatively intensive game like the new Call of duty and State of decay 2 (I still get Blue screens when playing light games like FTL).

I've tried a whole range of fixes such as, updating all drivers (using "Driver Reviver" and Device Manager), windows memory diagnostic, sfc scans, disk checks, memtest86, CCleaner, turning fast boot off and disabling write caching on my storage devices. Nothing seems to work..

As far as games go all the hardware performs amazing and i'm seeing good results all round when playing games it's just when watching YouTube and browsing the web I am seeing this problem.

Please can someone tell me whats wrong with my computer it's really annoying me.

| System Specs |
CPU
- Ryzen 5 3600x
RAM - 2X8 gb DDR4 3600mhz (Patriot Viper Steel)
GPU - GTX 1080
SSD - Intenso 256 gb
HDD - WD Blue 1TB
Motherboard - Aorus AX370 GAMING K5
PSU - Corsair VS650



Log Name: System
Source: Microsoft-Windows-Kernel-Power
Date: 28/12/2019 00:35:26
Event ID: 41
Task Category: (63)
Level: Critical
Keywords: (70368744177664),(2)
User: SYSTEM
Computer: DESKTOP-MNKR1IL
Description:
The system has rebooted without cleanly shutting down first. This error could be caused if the system stopped responding, crashed, or lost power unexpectedly.
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
<System>
<Provider Name="Microsoft-Windows-Kernel-Power" Guid="{331c3b3a-2005-44c2-ac5e-77220c37d6b4}" />
<EventID>41</EventID>
<Version>6</Version>
<Level>1</Level>
<Task>63</Task>
<Opcode>0</Opcode>
<Keywords>0x8000400000000002</Keywords>
<TimeCreated SystemTime="2019-12-28T00:35:26.803572500Z" />
<EventRecordID>10030</EventRecordID>
<Correlation />
<Execution ProcessID="4" ThreadID="8" />
<Channel>System</Channel>
<Computer>DESKTOP-MNKR1IL</Computer>
<Security UserID="S-1-5-18" />
</System>
<EventData>
<Data Name="BugcheckCode">313</Data>
<Data Name="BugcheckParameter1">0x0</Data>
<Data Name="BugcheckParameter2">0x0</Data>
<Data Name="BugcheckParameter3">0x0</Data>
<Data Name="BugcheckParameter4">0x0</Data>
<Data Name="SleepInProgress">0</Data>
<Data Name="PowerButtonTimestamp">0</Data>
<Data Name="BootAppStatus">0</Data>
<Data Name="Checkpoint">0</Data>
<Data Name="ConnectedStandbyInProgress">false</Data>
<Data Name="SystemSleepTransitionsToOn">0</Data>
<Data Name="CsEntryScenarioInstanceId">0</Data>
<Data Name="BugcheckInfoFromEFI">false</Data>
<Data Name="CheckpointStatus">0</Data>
</EventData>
</Event>

Log Name: System
Source: Microsoft-Windows-Kernel-Power
Date: 27/12/2019 23:33:23
Event ID: 41
Task Category: (63)
Level: Critical
Keywords: (70368744177664),(2)
User: SYSTEM
Computer: DESKTOP-MNKR1IL
Description:
The system has rebooted without cleanly shutting down first. This error could be caused if the system stopped responding, crashed, or lost power unexpectedly.
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
<System>
<Provider Name="Microsoft-Windows-Kernel-Power" Guid="{331c3b3a-2005-44c2-ac5e-77220c37d6b4}" />
<EventID>41</EventID>
<Version>6</Version>
<Level>1</Level>
<Task>63</Task>
<Opcode>0</Opcode>
<Keywords>0x8000400000000002</Keywords>
<TimeCreated SystemTime="2019-12-27T23:33:23.365240700Z" />
<EventRecordID>9407</EventRecordID>
<Correlation />
<Execution ProcessID="4" ThreadID="8" />
<Channel>System</Channel>
<Computer>DESKTOP-MNKR1IL</Computer>
<Security UserID="S-1-5-18" />
</System>
<EventData>
<Data Name="BugcheckCode">10</Data>
<Data Name="BugcheckParameter1">0x989628</Data>
<Data Name="BugcheckParameter2">0xff</Data>
<Data Name="BugcheckParameter3">0x95</Data>
<Data Name="BugcheckParameter4">0xfffff8026fa22829</Data>
<Data Name="SleepInProgress">0</Data>
<Data Name="PowerButtonTimestamp">0</Data>
<Data Name="BootAppStatus">0</Data>
<Data Name="Checkpoint">0</Data>
<Data Name="ConnectedStandbyInProgress">false</Data>
<Data Name="SystemSleepTransitionsToOn">0</Data>
<Data Name="CsEntryScenarioInstanceId">0</Data>
<Data Name="BugcheckInfoFromEFI">false</Data>
<Data Name="CheckpointStatus">0</Data>
</EventData>
</Event>
 
Last edited:
Solution
if Driver verifer doesn't crash, it means the problem isn't a driver. That leads back to a hardware cause again.

IRQ are data errors. Normally caused by drivers, can be memory (Ram or other)

RAM doesn't appear on any listing on gigabyte site but then there isn't a listing for Matisse. It does show up if you use PC PArt picker to part match ram of that speed to board.

Memory also includes - storage device, CPU (as memory controller is on CPU)
Intenso don't have a tool, try running crytstal disk mark on it - https://crystalmark.info/en/software/crystaldiskinfo/
WD - https://support.wdc.com/downloads.aspx?p=3&lang=en

CPU - - https://www.mersenne.org/download/

if both drives and CPU check out, i am wondering if...
I recently decided to upgrade the cpu, motherboard and ram that is in my system and ever since doing so I have had nothing but BSODs every 10-20 minutes. The only time it doesnt go to a BSOD is when i'm playing a relatively intensive game like the new Call of duty and State of decay 2 (I still get Blue screens when playing light games like FTL).

I've tried a whole range of fixes such as, updating all drivers (using "Driver Reviver" and Device Manager), windows memory diagnostic, sfc scans, disk checks, memtest86, CCleaner, turning fast boot off and disabling write caching on my storage devices. Nothing seems to work..

Have you clean installed windows? If you swap CPU, Mobo & Ram you essentially have a new PC and it helps to reinstall windows in this case

If you have reinstalled,
Can you follow option one on the following link - here - and then do this step below: Small memory dumps - Have Windows Create a Small Memory Dump (Minidump) on BSOD - that creates a file in c windows/minidump after the next BSOD

copy that file to documents
upload the copy from documents to a file sharing web site, and share the link in your thread so we can help fix the problem
 
Have you clean installed windows? If you swap CPU, Mobo & Ram you essentially have a new PC and it helps to reinstall windows in this case

If you have reinstalled,
Can you follow option one on the following link - here - and then do this step below: Small memory dumps - Have Windows Create a Small Memory Dump (Minidump) on BSOD - that creates a file in c windows/minidump after the next BSOD

copy that file to documents
upload the copy from documents to a file sharing web site, and share the link in your thread so we can help fix the problem



I havn't reinstalled windows yet. I'll try this later on when I get some free time and update you on if it has worked or not, thank you.
 
Hi, I ran the dump file through the debugger and got the following information: https://unknowingyesterday.htmlpasta.com/

File information:122819-7140-01.dmp (Dec 28 2019 - 13:08:45)
Bugcheck:IRQL_NOT_LESS_OR_EQUAL (A)
Probably caused by:memory_corruption (Process: System)
Uptime:0 Day(s), 0 Hour(s), 24 Min(s), and 36 Sec(s)

BIOS info was not included in the dump file. This can sometimes mean an outdated BIOS is being used.

This information can be used by others to help you. I can't help you with this. Someone else will post with more information. Please wait for additional answers. Good luck.
 
Hi, I ran the dump file through the debugger and got the following information: https://unknowingyesterday.htmlpasta.com/

File information:122819-7140-01.dmp (Dec 28 2019 - 13:08:45)
Bugcheck:IRQL_NOT_LESS_OR_EQUAL (A)
Probably caused by:memory_corruption (Process: System)
Uptime:0 Day(s), 0 Hour(s), 24 Min(s), and 36 Sec(s)

BIOS info was not included in the dump file. This can sometimes mean an outdated BIOS is being used.

This information can be used by others to help you. I can't help you with this. Someone else will post with more information. Please wait for additional answers. Good luck.
Okay, thanks
 
unrelated: what device is logitech surround sound driver for?

Do you have the latest BIOS? Are you getting drivers from the Gigabyte website? Why aren't you using the Gigabyte APp Centre to update drivers - you shouldn't use 3rd party installers like "Driver reviver" as they can often download wrong drivers. Especially don't need them if motherboard has its own app - https://www.gigabyte.com/au/Motherboard/GA-AX370-Gaming-K5-rev-1x/support#support-dl-utility

how long did you run memtest for? On each stick by themselves?
 
unrelated: what device is logitech surround sound driver for?

Do you have the latest BIOS? Are you getting drivers from the Gigabyte website? Why aren't you using the Gigabyte APp Centre to update drivers - you shouldn't use 3rd party installers like "Driver reviver" as they can often download wrong drivers. Especially don't need them if motherboard has its own app - https://www.gigabyte.com/au/Motherboard/GA-AX370-Gaming-K5-rev-1x/support#support-dl-utility

how long did you run memtest for? On each stick by themselves?

The Logitech Surround driver is for my logitech headset.

I do have the latest BIOS (F50a). I got the drivers for the bios on the Gigabyte website on my motherboard page and flashed them onto my motherboard using a USB. I didn't use the Gigabyte APP Centre because it just used to freeze up, however now it seems to work. On top of this I used Driver Reviver because when I checked my drivers in device manager for updates it said they were all up to date, but I was still receiving the Blue Screens so I used that software to update them instead.

I ran the memtest with both sticks inserted and on the default settings which lasted 3 hours 25 minutes and 9 seconds. I never ran the sticks by themselves because no errors came up so I thought it was alright.
 
memtest: okay. main reason you do them alone is to isolate errors. If you run 2 at once, you can't tell which is problem. But it passed so thats just for future :)

amdppm was last process running before crash. Its the AMD chipset driver.

you have what appears to be 2 but could just be one AMD chipset driver installed
Mar 14 2016amdgpio3.sysAMD GPIO Controller Driver from Advanced Micro Devices http://support.amd.com/
Oct 28 2019amdgpio2.sysAMD GPIO Controller Driver from Advanced Micro Devices http://support.amd.com/

I say they could be 2 as sometimes driver bundles do have more than 1 installed. What did Driver reviver install? Do you remember?
The October driver is newer than whats on the Gigabyte website

newest from AMD is from November - https://www.amd.com/en/support/chipsets/amd-socket-am4/x370
 
memtest: okay. main reason you do them alone is to isolate errors. If you run 2 at once, you can't tell which is problem. But it passed so thats just for future :)

amdppm was last process running before crash. Its the AMD chipset driver.

you have what appears to be 2 but could just be one AMD chipset driver installed
Mar 14 2016amdgpio3.sysAMD GPIO Controller Driver from Advanced Micro Devices http://support.amd.com/

Oct 28 2019amdgpio2.sysAMD GPIO Controller Driver from Advanced Micro Devices http://support.amd.com/

I say they could be 2 as sometimes driver bundles do have more than 1 installed. What did Driver reviver install? Do you remember?
The October driver is newer than whats on the Gigabyte website

newest from AMD is from November - https://www.amd.com/en/support/chipsets/amd-socket-am4/x370

I can't fully remember what it installed but I do remember a few.

  • "High Precision Event Timer"
  • "SD590_S24D590PL (HDMI)
  • "ASUS PA248"
  • "Microsoft Kernel Debug Network Adapter" (not certain about this one)
 
SD590_S24D590PL (HDMI) appears to be monitor drivers
ASUS PA248 are also monitor drivers (it seems to like them)
HPET is motherboard related although not sure what it would have installed exactly.

Last one is part of windows.

Try updating using the AMD site.
 
I can't fully remember what it installed but I do remember a few.

  • "High Precision Event Timer"
  • "SD590_S24D590PL (HDMI)
  • "ASUS PA248"
  • "Microsoft Kernel Debug Network Adapter" (not certain about this one)

Okay. I'll update now and see if the problems still persists.
 
i only asked about logitech drivers as I have a set of 5.1 speakers and was wondering if I was missing something - I expect not.

What is the memory codes? I like how your motherboard supports Matisse (which is what CPU is) but it doesn't have a Support list for Matisse memory so how are you to choose the right ram? https://www.gigabyte.com/au/Motherboard/GA-AX370-Gaming-K5-rev-1x/support#support-doc

For the logitech software I use the Logitech G Hub and enable the surround sound through there. Just thought I'd let you know in case you needed it.

Where would I find the memory codes?

I installed the AMD Chipset software from the AMD website. This didn't seem to fix the blue screen error, however the error has changed here are the last 3 BSODs that happened after download the software.

https://www.dropbox.com/s/jaqr29lzs56h82n/122919-7484-01.dmp?dl=0

https://www.dropbox.com/s/xlo7jahq02vwm80/122919-7500-01.dmp?dl=0

https://www.dropbox.com/s/9o33izkft8yqkp2/122919-7515-01.dmp?dl=0
 
PVS416G360C7K - PE000636 - Patriot Viper Steel 16 GB (2 x 8 GB) DDR4-3600 Memory

I don't see any memory on any of the lists that goes faster than 2933 which is what AMD see as 3000. How did you pick the ram? its odd to me that there isn't a memory page for that CPU on the motherboard website.

Advice I got was
Use the G.Skill memory configurator or the Corsair memory finder application based on the criteria of motherboard and then where necessary, CPU as well. That is your best chance of getting memory that doesn't either not work or requires significant manual configuration in order to get it to work.
 
I picked the ram from looking through amazon and went off of the reviews it had. Do you think that my choice of ram might be whats giving me issues.

I just think its strange that my PC wont Blue screen if I have a game open in the background. I had "the hunter call of the wild" open on the main menu yesterday and my PC worked fine. Obviously it's not ideal to have a game open all the time so that is why I wanted to get this issue fixed.
 
Ryzen CPU are very selective of ram, especially if its not on their list.

if I put current CPU + Motherboard into PC Part picker, your ram is on the list... it mentions the motherboard needs a new bios to work with CPU but you have that. Without an actual list of memory on the Gigabyte site its unclear if its okay or not.

I will wait for Gardenman to convert the last 3 dumps and see what they say,
 
I ran the dump files through the debugger and got the following information: https://wayfarersing.htmlpasta.com/
File information:122919-7515-01.dmp (Dec 29 2019 - 09:56:16)
Bugcheck:KMODE_EXCEPTION_NOT_HANDLED (1E)
Probably caused by:ntkrnlmp.exe (Process: System)
Uptime:0 Day(s), 0 Hour(s), 02 Min(s), and 17 Sec(s)

File information:122919-7500-01.dmp (Dec 29 2019 - 10:02:39)
Bugcheck:KMODE_EXCEPTION_NOT_HANDLED (1E)
Probably caused by:memory_corruption (Process: System)
Uptime:0 Day(s), 0 Hour(s), 04 Min(s), and 33 Sec(s)

File information:122919-7484-01.dmp (Dec 29 2019 - 06:24:43)
Bugcheck:KERNEL_SECURITY_CHECK_FAILURE (139)
Probably caused by:memory_corruption (Process: System)
Uptime:0 Day(s), 0 Hour(s), 16 Min(s), and 55 Sec(s)
This information can be used by others to help you. I can't help you with this. Someone else will post with more information. Please wait for additional answers. Good luck.
 
Jul 26 2008MODAPI.sysModAPI Development Kit driver
is also part of RGB Fusion
Oct 17 2008inpoutx64.sysKernel level port access driver http://www.highrez.co.uk/
is of unknown use but I see it enough on Gigabyte boards to assume its okay
I suspect errors are caused by a driver but I cannot see any obvious ones.

Try post two here and run driver verifer. FOllow the precautions as it can sometimes put you in a boot loop. Its part of windows designed to test drivers in ways they aren't designed, if any bad drivers, it will find them and cause a BSOD. Post the resulting dumps here and we see what it says - https://forums.tomshardware.com/thr...nclude-in-blue-screen-of-death-posts.3468965/
 
if Driver verifer doesn't crash, it means the problem isn't a driver. That leads back to a hardware cause again.

IRQ are data errors. Normally caused by drivers, can be memory (Ram or other)

RAM doesn't appear on any listing on gigabyte site but then there isn't a listing for Matisse. It does show up if you use PC PArt picker to part match ram of that speed to board.

Memory also includes - storage device, CPU (as memory controller is on CPU)
Intenso don't have a tool, try running crytstal disk mark on it - https://crystalmark.info/en/software/crystaldiskinfo/
WD - https://support.wdc.com/downloads.aspx?p=3&lang=en

CPU - - https://www.mersenne.org/download/

if both drives and CPU check out, i am wondering if contacting Gigabyte to confirm ram should work isn't a bad idea to try.
 
Solution