BSOD while idle

A

AlbDel

Active member
ubuysa said:
Apologies. Have you run that tool on your system?
Click to expand...
Yes, as already said it installed all the needed driver, from Integrated GPU to Chipset. Latest one, not recommended one. (already tried both various times).
Also Windows seems to always fail to write the dumps (both complete and mini) since the blue screen .. crashes?
 
Last edited:
ubuysa

ubuysa

The BSOD Doctor
AlbDel said:
Also Windows seems to always fail to write the dumps (both complete and mini) since the blue screen .. crashes?
Click to expand...
Nothing should stop a minidump being written. These are written deliberately though (via the dump command) as part of error recovery, not every crash writes a minidump.

The main cause of a kernel dump not being written is a paging file that's too small, this should always be system managed.
 
ubuysa

ubuysa

The BSOD Doctor
AlbDel said:
It already is. I followed your pinned guide 🤗
Click to expand...
No idea then, but you wouldn't be the first to not get kernel dumps written - it's a not uncommon problem that doesn't seem to have a single or reliable solution.
 
A

AlbDel

Active member
I've asked a friend of mine to lend me a M.2 to try out, I will get it probably tomorrow. Will keep the post updated if any more BSOD (with dumps) will rise before I change it
 
A

AlbDel

Active member
Uhm, I've downloaded Crystal disk and each time I try to run the test I get a BSOD, or a Reboot, or a freeze. Don't want to celebrate too early, but I might have found the coulprit?
 
ubuysa

ubuysa

The BSOD Doctor
AlbDel said:
Uhm, I've downloaded Crystal disk and each time I try to run the test I get a BSOD, or a Reboot, or a freeze. Don't want to celebrate too early, but I might have found the coulprit?
Click to expand...
This is on your existing M.2 drive?

Pop it out and back in, we've had several strange issues solved by reseating an M.2 SSD drive....
 
ubuysa

ubuysa

The BSOD Doctor
This BSOD is an IRQL_NOT_LESS_OR_EQUAL stop code again, an attempt to access a memory location that is invalid (paged out or not allocated) whilst running at DISPATCH_LEVEL (a privileged mode).

The stack trace for the active thread - which was the idle thread (the thread running when there is no other work to do) - shows a nt!PpmIdleExecuteTransition+0x184d system function call immediately prior to a page fault (nt!KiPageFault+0x469). I don't know what transition was happening here, whether it was just transitioning from the idle state or whether this was a power transition (preparing to sleep of hibernate for example, or even sleeping a PCIe device) but I think it's clear I think that the transition failed because of a hardware problem - because it's the idle thread and nothing else was involved!

The list of driver calls for the active thread (the idle thread remember) shows three errors....
Code: 
fffff802`56868510  fffff802`90c90ba0 Unable to load image \SystemRoot\System32\DriverStore\FileRepository\u0365057.inf_amd64_c4eff47eaf88e53e\B364966\amdkmdag.sys, Win32 error 0n2
 amdkmdag+0x4d10ba0
This is part of the AMD chipset driver again and we've seen this driver fail before....

Code: 
fffff802`56869a48  fffff802`caf456f8 Unable to load image \SystemRoot\system32\drivers\wd\WdNisDrv.sys, Win32 error 0n2
 WdNisDrv+0x56f8
This is a Windows Defender driver and it's very unlikely there is a bug in here (otherwise we'd all know!). I think this driver has failed because another driver failed.

Code: 
fffff802`5686a3f8  fffff802`8380650e Unable to load image \SystemRoot\System32\drivers\rt640x64.sys, Win32 error 0n2
 rt640x64+0x2650e
The rt640x64.sys driver is the Realtek PCIe Adapter driver, and whilst it's possible there is a bug in this driver I'd guess that this driver failed because some PCIe device failed during whatever transition we see in the stack trace.

I have to say I'm still not 100% convinced you have a stable Windows system there - I would like to see another fully clean install with the AMD chipset drivers installed properly.

If we assume that you have done that (and I'd urge you to do a full reinstall to be sure) then I think you're looking at a hardware issue here.
 
A

AlbDel

Active member
ubuysa said:
This BSOD is an IRQL_NOT_LESS_OR_EQUAL stop code again, an attempt to access a memory location that is invalid (paged out or not allocated) whilst running at DISPATCH_LEVEL (a privileged mode).

The stack trace for the active thread - which was the idle thread (the thread running when there is no other work to do) - shows a nt!PpmIdleExecuteTransition+0x184d system function call immediately prior to a page fault (nt!KiPageFault+0x469). I don't know what transition was happening here, whether it was just transitioning from the idle state or whether this was a power transition (preparing to sleep of hibernate for example, or even sleeping a PCIe device) but I think it's clear I think that the transition failed because of a hardware problem - because it's the idle thread and nothing else was involved!

The list of driver calls for the active thread (the idle thread remember) shows three errors....
Code: 
fffff802`56868510  fffff802`90c90ba0 Unable to load image \SystemRoot\System32\DriverStore\FileRepository\u0365057.inf_amd64_c4eff47eaf88e53e\B364966\amdkmdag.sys, Win32 error 0n2
amdkmdag+0x4d10ba0
This is part of the AMD chipset driver again and we've seen this driver fail before....

Code: 
fffff802`56869a48  fffff802`caf456f8 Unable to load image \SystemRoot\system32\drivers\wd\WdNisDrv.sys, Win32 error 0n2
WdNisDrv+0x56f8
This is a Windows Defender driver and it's very unlikely there is a bug in here (otherwise we'd all know!). I think this driver has failed because another driver failed.

Code: 
fffff802`5686a3f8  fffff802`8380650e Unable to load image \SystemRoot\System32\drivers\rt640x64.sys, Win32 error 0n2
rt640x64+0x2650e
The rt640x64.sys driver is the Realtek PCIe Adapter driver, and whilst it's possible there is a bug in this driver I'd guess that this driver failed because some PCIe device failed during whatever transition we see in the stack trace.

I have to say I'm still not 100% convinced you have a stable Windows system there - I would like to see another fully clean install with the AMD chipset drivers installed properly.

If we assume that you have done that (and I'd urge you to do a full reinstall to be sure) then I think you're looking at a hardware issue here.
Click to expand...
I've already installed the driver properly using (as before) the AMD auto detect and install tool. I'll do a fresh install ASAP anyway.
Today I've been playing for a bit, and as already mentioned the laptop hasn't crashed yet.
 
A

AlbDel

Active member
Sadly nothing changed. Still BSOD which most of the times don't write a dump.
I've used the tool here https://www.amd.com/en/support to install the drivers (I've seen it install chipset drivers too), NVIDIA ones from GeForce Experience and the other drivers from PCS.
I've been using the Laptop after the latest installation and, as already mentioned in the first post, when I play (thus use the Dedicated GPU) it doesn't crash (I've been playing Sea of Thieves for 4 and a half hours straight with 0 problems). As soon as I stopped playing in a few minutes it crashed (blackscreen freeze, not even a BSOD).
 
ubuysa

ubuysa

The BSOD Doctor
AlbDel said:
Sadly nothing changed. Still BSOD which most of the times don't write a dump.
I've used the tool here https://www.amd.com/en/support to install the drivers (I've seen it install chipset drivers too), NVIDIA ones from GeForce Experience and the other drivers from PCS.
I've been using the Laptop after the latest installation and, as already mentioned in the first post, when I play (thus use the Dedicated GPU) it doesn't crash (I've been playing Sea of Thieves for 4 and a half hours straight with 0 problems). As soon as I stopped playing in a few minutes it crashed (blackscreen freeze, not even a BSOD).
Click to expand...
It's most likely a hardware issue then I'd think.

Your problem is going to be ensuring that it fails on PCS's test bench. I would suggest you experiment to find the best way to make it BSOD without running for many hours. In the previous dump it seemed to be a transition of some time (most likely a power transition) and in your latest crash it happened after the game and perhaps when transitions to the idle state were taking place or as device power transitions as devices went to sleep?

Rather than try to hammer it to death think about developing a procedure that involves transitions from one state to another; so staring games, ending games, waking devices from sleep etc. It's going to be in your own interestes to give PCS a procedure to follow that will make it fail. If they can't see it fail it's just likely to come back to you again...
 
A

AlbDel

Active member
No it never goes to sleep, just idle. I think the best way to make it crash is just turn it on and use it with things that don't require the Dedicated GPU.

If you're totally idle it's not guaranteed to crash.
 
ubuysa

ubuysa

The BSOD Doctor
AlbDel said:
No it never goes to sleep, just idle. I think the best way to make it crash is just turn it on and use it with things that don't require the Dedicated GPU.

If you're totally idle it's not guaranteed to crash.
Click to expand...
Well you know better than I the circumstances under which it will crash, so develop a procedure for PCS to follow to make it crash - or at least to give the highest probability of it crashing. Otherwise PCS will stress it for a few hours and if it doesn't crash you'll likely get it back as is.
 
ubuysa

ubuysa

The BSOD Doctor
This kernel dump is almost identical to minidumps of yours I've seen earlier.

The stop code for this dump (Wed Mar 24 21:46:32.986 2021) is a PAGE_FAULT_IN_NONPAGED_AREA which means that memory in a fixed (non-pageable) area was referenced and found to be invalid (paged out or not allocated). In this case the memory refenernced has not been allocated. These BSODs are almost always the fault of a third party driver.

In the stack trace for the active thread there is a call to exclusively obtain a pushlock (an internal serialisation mechanism) which is followed by a page fault. The problem then seems to be a driver attempting to access a pushlock (a memory structure) that doesn't exist.

In the list of driver calls for the active thread are two errors...

Code: 
ffffae03`7aedab78  fffff806`6027b45b Unable to load image \SystemRoot\System32\DriverStore\FileRepository\u0365057.inf_amd64_c4eff47eaf88e53e\B364966\amdkmdag.sys, Win32 error 0n2
amdkmdag+0x1cbb45b
This is an AMD chipset driver and of the two faults here this is the most likely cause of the BSOD. Check that the AMD chipset drivers are up to date using the AMD Driver & Support Tool.

Code: 
ffffae03`7aedce58  fffff806`24b3644fUnable to load image \SystemRoot\system32\drivers\wd\WdFilter.sys, Win32 error 0n2
WdFilter+0x3644f
This is a Windows Defender driver and is thus most unlikely to be at fault. It's more likely this driver failed due to the AMD driver failure above.

Assuming you are 100% certain you have a stable operating system platform (which really means clean installing Windows from bootable media, deleting partitions, running Windows Update, installing AMD chipset drivers, installing the latest Nvidia driver and then installing that absolute minimum software you need to test it) then I would strongly suspect a hardware issue. I would suggest you talk to PCS and make this (and other dumps) available to them. Also find out whether there is a BIOS (or AGESA) update for your build from PCS.
 
A

AlbDel

Active member
ubuysa said:
which really means clean installing Windows from bootable media, deleting partitions, running Windows Update, installing AMD chipset drivers, installing the latest Nvidia driver and then installing that absolute minimum software you need to test it
Click to expand...
Did everything on this list.
This morning I even tried to disable (From Device Manager) the Integrated GPU, but it still crashed (I'm assuming that disabling it doesn't completely disable it). I've searched for similar problems and lots of peoples had to disable C-States, but found nothing mentioning those in the bios (well that's maybe better as I didn't want to mess things up for the worse).
 
ubuysa

ubuysa

The BSOD Doctor
AlbDel said:
Did everything on this list.
This morning I even tried to disable (From Device Manager) the Integrated GPU, but it still crashed (I'm assuming that disabling it doesn't completely disable it). I've searched for similar problems and lots of peoples had to disable C-States, but found nothing mentioning those in the bios (well that's maybe better as I didn't want to mess things up for the worse).
Click to expand...
I would talk to PCS now then.
 
You must log in or register to reply here.
Top