[SOLVED] BSOD once a day

Toggle sidebar Toggle sidebar
Marcusktm9

Marcusktm9

Prominent
May 2, 2020
23
0
520
As the title states, i get a BSOD once or twice every day, more during gaming.

Some of the BSOD codes from the latest days

MEMORY_MANAGEMENT
IRQL_NOT_LESS_OR_EQUAL
PAGE_FAULT_IN_NONPAGED_AREA
CLOCK_WATCHDOG_TIMEOUT
MEMORY_MANAGEMENT

BlueScreenView highlights "ntoskrnl.exe" as the filename on every one of the BSOD's

I have done memtest86 and it passed all 4 passes with 0 errors.

MB: x570 Aorous Elite (bios version F33a)
Memory: 2 x 8 GB 4000 mhz G.Skill Trident z CL 18 (18-19-19-39-(58) ((F4-4000C18D-16GTZR Model)
CPU 5800x
GPU 3080
Drive 1: Samsung 980 PRO gen 4 nvme
Drive 2: Samsung 970 EVO gen 3 nvme
Drive 3: Samsung 860 EVO 2'5 SSD

I have enabled XMP standard profile

Please help me, it is really disturbing
 
Last edited:
Sort by date Sort by votes
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

Open Windows File Explorer

Navigate to C:\Windows\Minidump

Copy the mini-dump files out onto your Desktop

Do not use Winzip, use the built in facility in Windows

Select those files on your Desktop, right click them and choose 'Send to' - Compressed (zipped) folder

Upload the zip file to the Cloud (OneDrive, DropBox . . . etc.)

Then post a link here to the zip file, so we can take a look for you . . .
 
Upvote 1 Downvote
Colif said:
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

Open Windows File Explorer

Navigate to C:\Windows\Minidump

Copy the mini-dump files out onto your Desktop

Do not use Winzip, use the built in facility in Windows

Select those files on your Desktop, right click them and choose 'Send to' - Compressed (zipped) folder

Upload the zip file to the Cloud (OneDrive, DropBox . . . etc.)

Then post a link here to the zip file, so we can take a look for you . . .
Click to expand...

https://drive.google.com/file/d/1_KiekGDV7_vK9Te2pE4X5I7yIN5GQz8U/view?usp=sharing
This should work
 
Upvote 0 Downvote
Marcusktm9 said:
Yeah that was my first thought aswell, but wouldn't the Memtest86 have ruled that out? plus its just standard XMP
Click to expand...
Memtest86 is more for diagnosing faulty ram than testing stability. 4000Mhz isn't a standard ram speed and isn't guaranteed to work. The way to rule out memory stability as a cause is to set the ram to standard 2133Mhz and see if the issue persists.
 
  • Like
Reactions: Krotow
Upvote 0 Downvote
Flayed said:
Memtest86 is more for diagnosing faulty ram than testing stability. 4000Mhz isn't a standard ram speed and isn't guaranteed to work. The way to rule out memory stability as a cause is to set the ram to standard 2133Mhz and see if the issue persists.
Click to expand...
Ah okay. i thought it was more of a "run it and rule out ram" kind of thing.
Though my motherboard does support the 4000 mhz option per official specs.
Is there a ram benchmark that can possibly test if the 4000 mhz option is stable?
 
Upvote 0 Downvote
Just go into the BIOS and disable the XMP profile, leave the RAM at its base speed, try the PC for a day or two and see if the BSOD happends again or not.

If the PC does not BSOD, then you can go and enable XMP again.

Thats the best way to test if the system is or isnt stable at DDR4 4000.


Is this RAM of yours included on the qvl list for the mobo?

Have you checked for new BIOS that may improve memory support and stability?

Is this a new clean install of Winwdows 10?
 
  • Like
Reactions: Krotow
Upvote 0 Downvote
Hi, I ran the dump files through the debugger and got the following information: https://jsfiddle.net/1q7mgc8u/show This link is for anyone wanting to help. You do not have to view it. It is safe to "run the fiddle" as the page asks.
File information:020821-8031-01.dmp (Feb 8 2021 - 17:06:39)
Bugcheck:MEMORY_MANAGEMENT (1A)
Probably caused by:memory_corruption (Process: 7DaysToDie.exe)
Uptime:1 Day(s), 1 Hour(s), 38 Min(s), and 11 Sec(s)

File information:020721-7968-01.dmp (Feb 7 2021 - 15:28:03)
Bugcheck:CLOCK_WATCHDOG_TIMEOUT (101)
Probably caused by:memory_corruption (Process: System)
Uptime:1 Day(s), 5 Hour(s), 37 Min(s), and 40 Sec(s)

File information:020521-9671-01.dmp (Feb 5 2021 - 06:01:45)
Bugcheck:PAGE_FAULT_IN_NONPAGED_AREA (50)
Probably caused by:memory_corruption (Process: System)
Uptime:2 Day(s), 19 Hour(s), 49 Min(s), and 10 Sec(s)

File information:012821-5062-01.dmp (Jan 28 2021 - 06:20:35)
Bugcheck:IRQL_NOT_LESS_OR_EQUAL (A)
Probably caused by:memory_corruption (Process: EscapeFromTarkov.exe)
Uptime:0 Day(s), 13 Hour(s), 44 Min(s), and 06 Sec(s)

File information:012721-5140-01.dmp (Jan 27 2021 - 16:34:56)
Bugcheck:MEMORY_MANAGEMENT (1A)
Probably caused by:memory_corruption (Process: League of Legends.exe)
Uptime:0 Day(s), 0 Hour(s), 05 Min(s), and 59 Sec(s)
Possible Motherboard page: https://www.gigabyte.com/us/Motherboard/X570-AORUS-ELITE-rev-10
You have the latest BIOS already installed, version F33a.

This information can be used by others to help you. Someone else will post with more information. Please wait for additional answers. Good luck.
 
  • Like
Reactions: RodroX
Upvote 1 Downvote
So which memory and infinity fabric settings do you recommend i change to?

From what iv'e gathered setting infinity fabric to 1900 and my memory multiplier to 38 (3800 mhz) and still having timings in xmp auto settings, should be correct.
i have changed to these settings now and will try and see if i get the same behaviour/crashes as before.
 
Last edited:
Upvote 0 Downvote
Marcusktm9 said:
So which memory and infinity fabric settings do you recommend i change to?

From what iv'e gathered setting infinity fabric to 1900 and my memory multiplier to 38 (3800 mhz) and still having timings in xmp auto settings, should be correct.
i have changed to these settings now and will try and see if i get the same behaviour/crashes as before.
Click to expand...
I don't really know any more than you about it, I'm not an overclocker, I don't have the patience for all the stability testing. What you suggested doing sounds reasonable though. You can get far with trial and error if you have the time, just don't set the memory voltage too high.
 
Upvote 0 Downvote
I am neither, but i tried to run 3dmark timespy with these settings and got strong sound artifacts, and at the end of the warmup sequence my entire pc crashed (no BSOD just double black screen followed by slow reboot acting weird) tried it again to see for consistency and it did the exact same thing again.

Will try with 1800-3600 now.
Update: Ran the test without anomalies now, but like 200 points lower cpu score. which is totally fine if it is actually stable the next couple of days... Will stick with these settings for now and see.
 
Last edited:
Upvote 0 Downvote
Marcusktm9 said:
I am neither, but i tried to run 3dmark timespy with these settings and got strong sound artifacts, and at the end of the warmup sequence my entire pc crashed (no BSOD just double black screen followed by slow reboot acting weird) tried it again to see for consistency and it did the exact same thing again.

Will try with 1800-3600 now.
Click to expand...

Im sorry to insist on this but, have you tried what I wrote on my post?
 
Upvote 0 Downvote
RodroX said:
Im sorry to insist on this but, have you tried what I wrote on my post?
Click to expand...


RodroX said:
Just go into the BIOS and disable the XMP profile, leave the RAM at its base speed, try the PC for a day or two and see if the BSOD happends again or not.

If the PC does not BSOD, then you can go and enable XMP again.

Thats the best way to test if the system is or isnt stable at DDR4 4000.


Is this RAM of yours included on the qvl list for the mobo?

Have you checked for new BIOS that may improve memory support and stability?

Is this a new clean install of Winwdows 10?
Click to expand...


Well this is kinda what im doing right now with the 3600 mhz settings.

the exact same model in 8 GB variant is on the QVL list of it yes ( i assume it is single stick 8 gb so 2x8 is good)

Yes i am on the absolute latest F33a bios from gigabytes website.

it is clean install from early-mid January.
 
Upvote 0 Downvote
note: ;Many bsod show memory corruption, they aren't all caused by ram

having said that, the dump results aren't exactly telling me an answer.
most of them happen after PC talks to hdd, so you could look at the storage drives as well, as Windows counts C drive as memory because that is where page file is.

vanguard, although needed for some games, can cause BSOD
should be a newer version of Icue
try updating chipset driver - https://www.amd.com/en/support/chipsets/amd-socket-am4/x570
 
  • Like
Reactions: RodroX
Upvote 1 Downvote
Colif said:
note: ;Many bsod show memory corruption, they aren't all caused by ram

having said that, the dump results aren't exactly telling me an answer.
most of them happen after PC talks to hdd, so you could look at the storage drives as well, as Windows counts C drive as memory because that is where page file is.

vanguard, although needed for some games, can cause BSOD
should be a newer version of Icue
try updating chipset driver - https://www.amd.com/en/support/chipsets/amd-socket-am4/x570
Click to expand...


I can imagine Vanguard could cause some problems, and i have disabled it now.
I had some severe USB problems with icue (not BSOD), and got it to work some time ago so i would prefer not to screw it up to that state again.
The link you sent i have now used to update the drivers, incase those i had downloaded were wrong or outdated.

I will take a in depth look at the drives if i keep getting the problems

Now i can just play the waiting game the next couple of days.

UPDATE 2 DAYS LATER

No instabilities and zero crashes, even ones i once thought were game-caused crashes, have totally stopped.

Main thing that helped for other users that encounter the same problem:

Reducing memory clock to 3600 mhz, and manually setting 1:1 FLCK to 1800 (havent tried with auto though)

Possible things that could have helped

Disabling Riot Vanguard
Re-installing chipset driver
 
Last edited:
Upvote 0 Downvote
You must log in or register to reply here.

TRENDING THREADS

Latest posts

Moderators online

Share this page

COMPANY
RESOURCES
FOLLOW
Top Bottom