[SOLVED] Getting BSODs every few hours

Nov 30, 2019
7
0
10
Hello, so i built my first gaming PC and everything is working perfectly!... Except for some nasty BSODs every few hours.

They send the message "IRQL_NOT_LESS_OR_EQUAL"
"PAGE FAULT IN NON PAGED AREA"

My specs are:
Ryzen 7 3700x, stock cooler
Gigabyte Gaming X X570 MoBo
Gigabyte RX 5700XT Gaming OC
8X2 3200MHz Corsair Vengeance Pro RGB
Samsung 970Evo 500GB

I've already tried Chkdsk, Memory diagnostic, Restoring windows, but to no avail.

Bluescreenviw marks "partmgr.sys" and "ntoskrnl.exe" as the origin.

Edit: Forgot to write it, but I have s¡the suspicion that it may be some Audio Interface Drivers i downloaded, I downgraded the version of it to see if it changes somethng
Any help would be great
 
Solution
Apologies @gardenman - I think you would've been asked about this, but i stumbled across it and thought I'd do it whilst I had the time. Always welcome to have your input too as your software does extract it all better :)

I have run the dump file(s) and you can see the full report(s) here:

https://pste.eu/p/j5PW.html - IRQL_NOT_LESS_OR_EQUAL
https://pste.eu/p/naIj.html - KMODE_EXCEPTION_NOT_HANDLED

Summary of findings:
IRQL_NOT_LESS_OR_EQUAL
Bug check 0xA is usually caused by kernel mode device drivers using improper addresses. This is either a bad memory pointer or a pageability problem with the device driver code. Examine the third party drivers .

KMODE_EXCEPTION_NOT_HANDLED
This can be driver or...

Colif

Win 11 Master
Moderator
partmgr.sys = partition manager
ntoskrnl = Windows kernel. It often gets blamed but its never the problem. It is what crashed but its always pushed.

both could be drivers

Can you go to c:/ windows/minidump
copy the minidump files o documents
upload the copyiesfrom documents to a file sharing web site, and share the link in your thread so we can help fix the problem
 

PC Tailor

Illustrious
Ambassador
Apologies @gardenman - I think you would've been asked about this, but i stumbled across it and thought I'd do it whilst I had the time. Always welcome to have your input too as your software does extract it all better :)

I have run the dump file(s) and you can see the full report(s) here:

https://pste.eu/p/j5PW.html - IRQL_NOT_LESS_OR_EQUAL
https://pste.eu/p/naIj.html - KMODE_EXCEPTION_NOT_HANDLED

Summary of findings:
IRQL_NOT_LESS_OR_EQUAL
Bug check 0xA is usually caused by kernel mode device drivers using improper addresses. This is either a bad memory pointer or a pageability problem with the device driver code. Examine the third party drivers .

KMODE_EXCEPTION_NOT_HANDLED
This can be driver or hardware based. If you are encountering other hardware issues, you may have to look at hardware diagnosis. - Confirm that hardware is compatible with your system. - View the third party modules of the report to view which drivers may be misbehaving.

Some things to consider:
  • Both of these stop codes are typically caused by misbehaving drivers.
  • They both identify Microsoft drivers as the cause, however this is unlikely to be the case.
  • Both identify network related drivers so I'd check for an update for:

rt640x64.sys28/08/2018RealtekRealtek Ethernet Driver (Link)

I'd also check the version you have installed for your MB/Chipset drivers:

Not sure of the OEM for these:
umc_audio.sys05/12/2017UnknownTUSBAudio Class Driver
umc_audioks.sys05/12/2017UnknownTUSBAudio Class Driver

However not sure if these are inbuilt - but you have both these as well as Realtak Audio drivers, do you have a USB audio device?
 
  • Like
Reactions: gardenman
Solution
Nov 30, 2019
7
0
10
Yes, I have a USB Interface, maybe that's causing the conflict between drivers. Because all the other drivers i know are the latest.
Thanks for the help!!
Gonna try disabling one of them and Will give you feedback of that
 

PC Tailor

Illustrious
Ambassador
I have run the dump file(s) and you can see the full report(s) here: https://pste.eu/p/1epP.html

Summary of findings:
SYSTEM_SERVICE_EXCEPTION
"This is typically driver based and therefore you should reference the third party modules loaded to check which ones may be misbehaving. If any are out of date, try updating or disabling them.

Look at the STACK TEXT for clues on what was running when the failure occurred. If multiple dump files are available, compare information to look for common code that is in the stack"

Some things to consider:
- You've got a C5 exception code, which is effectively a STATUS ACCESS VIOLATION (the most common exception in this scenario) which effectively means there was an "access denied" to physical memory. It's typically driver based as it attempts to access physical memory and is denied.

I can see the 2 audio drivers are still running and neither have been disabled - I would update or disable both of them:
umc_audio.sys05/12/2017UnknownTUSBAudio Class Driver
umc_audioks.sys05/12/2017UnknownTUSBAudio Class Driver

You can disable them from starting using Autoruns (in modules tab of the report)
I'd also be tempted to remove Malwarebytes for now and simply run on Defender for the time being as AV can often cause various problems.
I know of some Gigabyte RGB software causing issues too, but at this point because the dump file doesn't state anything specific, we're estimating.

May be apt to run driver verifier as per this post: https://www.sysnative.com/forums/threads/driver-verifier-bsod-related-windows-10-8-1-8-7-vista.29/ if the above does not work.