Various BSODs all hinting towards drivers?

Hey guys, I did the clean boot and received a BSOD after ~24 hours.

Memory_dmp210502.zip - Google Drive

V2 log attached.

Please swap test hardware.

Latest bugcheck: 35

Prior bugchecks:

1
139
192
3B
50
7F
A
A0
C4
D1
FC

Hello ferchi

That new bugcheck is an interesting one:

Code:

NO_MORE_IRP_STACK_LOCATIONS (35)
A higher level driver has attempted to call a lower level driver through
the IoCallDriver() interface, but there are no more stack locations in the
packet, hence, the lower level driver would not be able to access its
parameters, as there are no parameters for it.  This is a disastrous
situation, since the higher level driver "thinks" it has filled in the
parameters for the lower level driver (something it MUST do before it calls
it), but since there is no stack location for the latter driver, the former
has written off of the end of the packet.  This means that some other memory
has probably been trashed at this point.
Arguments:
Arg1: ffff8d8dfcc212e0, Address of the IRP
Arg2: 0000000000000000
Arg3: 0000000000000000
Arg4: 0000000000000000

The usual cause is a driver but it can also point to a problem with the RAM. In your case I would be more inclined to a driver since you have had 100+ hours in safe mode with no problem.

The only 3rd party drivers active at the time of the crash were:
amdgpio2.sys Wed Mar 11 11:15:48 2020 (5E68C864)
AMDPCIDev.sys Wed Jan 13 09:54:28 2021 (5FFEC354)
amdpsp.sys Fri Mar 6 21:04:04 2020 (5E62BAC4)
ibtusb.sys Tue Feb 16 10:08:50 2021 (602B99B2)
inpoutx64.sys Sat Oct 18 00:01:16 2008 (48F9193C)
MsIo64.sys Mon Jan 20 03:35:15 2020 (5E251FF3)
Netwtw10.sys Tue Dec 1 21:58:14 2020 (5FC6BC76)
nvhda64v.sys Fri Oct 16 12:03:41 2020 (5F897E0D)
nvlddmkm.sys Tue Feb 23 21:51:02 2021 (603578C6)
rt640x64.sys Mon Jan 4 10:14:19 2021 (5FF2EA7B)
RTKVHD64.sys Tue Jan 12 10:18:34 2021 (5FFD777A)
ssgdio64.sys Fri Sep 9 19:40:54 2005 (4321D736)

I've highlighted two of the oldest drivers that might be worth removing or updating.

They are a driver for direct access to hardware ports and one from ATI diagnostics. I have no idea where these have come from!

Hope it gives you a pointer in the right direction.

philc43 said:

In your case I would be more inclined to a driver since you have had 100+ hours in safe mode with no problem.

The only 3rd party drivers active at the time of the crash were:
amdgpio2.sys Wed Mar 11 11:15:48 2020 (5E68C864)
AMDPCIDev.sys Wed Jan 13 09:54:28 2021 (5FFEC354)
amdpsp.sys Fri Mar 6 21:04:04 2020 (5E62BAC4)
ibtusb.sys Tue Feb 16 10:08:50 2021 (602B99B2)
inpoutx64.sys Sat Oct 18 00:01:16 2008 (48F9193C)
MsIo64.sys Mon Jan 20 03:35:15 2020 (5E251FF3)
Netwtw10.sys Tue Dec 1 21:58:14 2020 (5FC6BC76)
nvhda64v.sys Fri Oct 16 12:03:41 2020 (5F897E0D)
nvlddmkm.sys Tue Feb 23 21:51:02 2021 (603578C6)
rt640x64.sys Mon Jan 4 10:14:19 2021 (5FF2EA7B)
RTKVHD64.sys Tue Jan 12 10:18:34 2021 (5FFD777A)
ssgdio64.sys Fri Sep 9 19:40:54 2005 (4321D736)

I've highlighted two of the oldest drivers that might be worth removing or updating.

They are a driver for direct access to hardware ports and one from ATI diagnostics. I have no idea where these have come from!

Hope it gives you a pointer in the right direction.

See post #107.
The computer ran 1 week in normal boot without any BSOD.
The 100 hours of safe mode was < 1 week or 168 hours
So safe mode testing to be useful may need 2 weeks.


If you plan to uninstall and reinstall the two drivers then check WDV first:
Select only these two drivers for testing.
Select all customized tests including Randomized low resources simulation.
Run for 4 - 6 hours.

The WDV test will either be a true pos / neg or a false pos / neg.

There were multiple types of bugchecks.
Drivers were tested with WDV.
There were 6 memory dumps debugged.
When available please swap test CPU / Motherboard.

Hey guys,

sorry for my silence during the last month. I was very busy with finalizing my master thesis and had no time neither was I in the right frame of mind to rebuild my PC.

But in the last week, I ordered a new motherboard (same model: MSI x570 tomahawk wifi) and rebuild my PC from scratch.
It is up and running since 3 hours. Fingers crossed.
I updated the BIOS to the newest version and the NVIDIA drivers. I made no changes in BIOS, with fan curve adjustments as the only exception. XMP-profile NOT active, modules running @ 2666 MHz.

Any ideas on specific tests I could perform? Or just go with the day-to-day work case?

Nice.

Please monitor using:
Reliability Monitor is the Best Windows Troubleshooting Tool You Aren’t Using

For any BSOD:

a) run the V2 log collector to collect new log files

b) open file explorer> this PC > C: > in the right upper corner search for: C:\Windows\memory.dmp
> if the file size is < 1.5 GB then > save to the downloads folder > zip > post a separate share link into the thread using one drive, drop box, or google drive

Right-click on the Start button --> Windows PowerShell
Run the following line of commands to put "memory.dmp" into a ZIP on the desktop.

Code:

Compress-Archive -Path "$env:homeDrive\Windows\MEMORY.DMP" -DestinationPath "$env:homeDrive$env:homePath\Desktop\Memory_dmp"

Hey,

unfortunately I just received a BSOD while light gaming.
Memory_dmp210615.zip - Google Drive

V2 log attached.

- - - Updated - - -

and another one while idle...

dmp: Memory_dmp210615_2.zip - Google Drive

V2 log attached.
Looks to me like the same old problem.. replace CPU next?.. Or maybe PSU?

- - - Updated - - -

Looked into the two drivers inpoutx64.sys and ssgdio64.sys..

I found inpoutx64.dll as constituent of "ZenTimings" which I used while testing my RAM modules. Deleted the folder and deleted the .sys in system32/drivers in safemode.

I was not able to find ssgdio64.sys anywhere.

- - - Updated - - -

And another BSOD while idle. This time there is an additional driver listed "netio.sys".

dmp: Memory_dmp210616.zip - Google Drive

Are this BSODs looking the same as before or is this new stuff? A confirmation would be really great so I would swap out CPU next I guess.. If no other suggestions.

"ssgdio64.sys"
A google search gets this info, you may have to uninstall it ( ATI )

What is ssgdio64.sys?
What is ssgdio64.sys from ATI Technologies Inc.?

- - - Updated - - -

Autoruns may make it easier to find that driver remnants.

Autoruns for Windows requires no installation. Right click on it & run as Admin, then navigate to the Drivers tab, clear the checkmark next to the driver you wish to disable, then reboot the computer.
https://docs.microsoft.com/en-us/sys...loads/autoruns

Thank you. I disabled both with "autoruns".