Computer Lockup and Restarts- Bad Video Card (Again?)

zbook said:

There were no links in the above post.

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 zip > post a separate share link into the thread using one drive, drop box, or google drive

Run windows driver verifier after uninstalling the misbehaving/software.

If there are no BSOD for 48 hours then the tool can be turned off.

Drivers / software can be reinstalled after one week of computer stability (no BSOD or unexpected shutdowns / restarts).

My apologies for not getting back to you sooner. I tried last night but it appears my post didn't submit.

The crash logs and memory dumps are located in my OneDrive, in the shared folder. They are three files in the root of the folder... should be dated 2 nights ago. If you don't have the link, it is here: Microsoft OneDrive - Access files anywhere. Create docs with free Office Online. Please let me know if you have any access issues.

I presently uninstalled Steam from my computer. I rebooted and made sure to remove from Device Manager (deleting driver), Steam Streaming Speakers and Microphone. I checked and both drivers were WHQL'd, but I deleted them anyway.

So the plan is now, to enable ALL 19 tests, and run verifier until more dumps are created? Just want to be sure I understand.

I'm anxious to get Steam reinstalled - I can't play my games without it. Also in the past 3 or 4 days Steam has released an update to their program, and it heavily refined/modified Streaming, which it now refers to as Remote Play. I'm hoping that their update modified those drivers, too. But I doubt it. Probably I should just stick to the program and be patient.

If it is the Steam streaming drivers, this is a bad thing for me - I bought the Steamlink in order to use it... and it seemed to work perfectly with my AMD hardware... Then again, it would be nice to know that it isn't my faulty hardware or anything worse.

Let me know when you get a chance to look at the logs/dump. I'll run all 19 tests ASAP.

zbook said:

The debugging displayed the same misbehaving driver.


Uninstalling Steam will eliminate the software/hardware and its drivers as confounding factors.

The the troubleshooting can continue to look for other problems.

Steam can be reinstalled after one week of computer stability ( no BSOD or unexpected shutdowns / restarts).




Mon Jun 17 01:29:35.591 2019 (UTC - 5:00)

Code:

SteamStreamingMicrophone.sys Fri Jul 28 08:33:15 2017 (597B593B)

Code:

Name	Steam Streaming Microphone
Manufacturer	Valve Corporation Audio DDK
Status	OK
PNP Device ID	ROOT\STEAMSTREAMINGMICROPHONE\0000
Driver	c:\windows\system32\drivers\steamstreamingmicrophone.sys (, 39.78 KB (40,736 bytes), 04/30/19 08:30)

Code:

steamstreamingmicrophone	Steam Streaming Microphone	c:\windows\system32\drivers\steamstreamingmicrophone.sys	Kernel Driver	Yes	Manual	Running	OK	Normal	No	Yes

Code:

Start Menu\Programs\Steam	Public:Start Menu\Programs\Steam	Public

Ok so it's been running 18/19 tests for almost 36 hours straight:

Attachment 237900

I uninstalled Steam, but for those with this issue, I had to go into Device Manager and actually remove each device (choosing to delete the driver) itself - the Installer left behind the two drivers steamstreamingaudio.sys and steamstreamingmicrophone.sys.

I did not choose to enable the random low resources test because I didn't know what settings to choose. But regardless, for it to go this long without issue would seem to show my rig is pretty stable, correct? At this point, we can rule out any hardware issue like the video card or power supply, right? Side note, there is still an issue with the motherboard/BIOS updating, but that doesn't appear to be what we're seeing here.

What happens if in a week I install Steam and the same thing happens again? Should I submit a Support Ticket with Steam and let them know their drivers are crashing my system? Or do you think I should just look into trying to block that driver from loading? Do you think there could be any other cause? How confident are you that they as a company will do something? I bought the steamlink to stream my computer to the living room... if I can't do that without crashing, there's no point...

Select all 19 tests in the Microsoft link.

If there are no BSOD in 6 to 8 hours then run both V2 and DM.

Then turn off windows driver verifier.

Continue to use the computer to evaluate stability / instability so that there is a least one week of no BSOD and no unexpected shutdowns / restarts.

The above if completed without BSOD and unexpected shutdowns / restarts indicates that the tested drivers were stable under stress.

Make an updated backup image.

Consider upgrading to Windows 1903 and testing Steam with the new windows build.

To see whether the Steam hardware and software are causing computer instability:
After one week of stability (including windows driver verifier stress testing) reinstall the hardware / software and evaluate computer stability / instability.

If there are BSOD with Steam and Windows 1903 you can remain with 1903, revert to 1809, or try windows 1709 or1803.

Please make sure that you have one week of computer stability before making the other tests.

zbook said:

Select all 19 tests in the Microsoft link.

If there are no BSOD in 6 to 8 hours then run both V2 and DM.

Then turn off windows driver verifier.

Continue to use the computer to evaluate stability / instability so that there is a least one week of no BSOD and no unexpected shutdowns / restarts.

The above if completed without BSOD and unexpected shutdowns / restarts indicates that the tested drivers were stable under stress.

Make an updated backup image.

Consider upgrading to Windows 1903 and testing Steam with the new windows build.

To see whether the Steam hardware and software are causing computer instability:
After one week of stability (including windows driver verifier stress testing) reinstall the hardware / software and evaluate computer stability / instability.

If there are BSOD with Steam and Windows 1903 you can remain with 1903, revert to 1809, or try windows 1709 or1803.

Please make sure that you have one week of computer stability before making the other tests.

What settings should I set for the "Random Low Resources" test?

For windows driver verifier there are approximately 22 customized tests:

Code:

    [ ] 0x00000001 Special pool.
    [ ] 0x00000002 Force IRQL checking.
    [ ] 0x00000008 Pool tracking.
    [ ] 0x00000010 I/O verification.
    [ ] 0x00000020 Deadlock detection.
    [ ] 0x00000080 DMA checking.
    [ ] 0x00000100 Security checks.
    [ ] 0x00000800 Miscellaneous checks.
    [ ] 0x00020000 DDI compliance checking.

  Additional Flags:

    [ ] 0x00000004 Randomized low resources simulation.
    [ ] 0x00000200 Force pending I/O requests.
    [ ] 0x00000400 IRP logging.
    [ ] 0x00002000 Invariant MDL checking for stack.
    [ ] 0x00004000 Invariant MDL checking for driver.
    [ ] 0x00008000 Power framework delay fuzzing.
    [ ] 0x00010000 Port/miniport interface checking.
    [ ] 0x00040000 Systematic low resources simulation.
    [ ] 0x00080000 DDI compliance checking (additional).
    [ ] 0x00200000 NDIS/WIFI verification.
    [ ] 0x00800000 Kernel synchronization delay fuzzing.
    [ ] 0x01000000 VM switch verification.
    [ ] 0x02000000 Code integrity checks.

Select all tests to match the 19 tests in this link:
https://answers.microsoft.com/en-us/...3-c48669e4c983

zbook said:

For windows driver verifier there are approximately 22 customized tests:

Code:

    [ ] 0x00000001 Special pool.
    [ ] 0x00000002 Force IRQL checking.
    [ ] 0x00000008 Pool tracking.
    [ ] 0x00000010 I/O verification.
    [ ] 0x00000020 Deadlock detection.
    [ ] 0x00000080 DMA checking.
    [ ] 0x00000100 Security checks.
    [ ] 0x00000800 Miscellaneous checks.
    [ ] 0x00020000 DDI compliance checking.

  Additional Flags:

    [ ] 0x00000004 Randomized low resources simulation.
    [ ] 0x00000200 Force pending I/O requests.
    [ ] 0x00000400 IRP logging.
    [ ] 0x00002000 Invariant MDL checking for stack.
    [ ] 0x00004000 Invariant MDL checking for driver.
    [ ] 0x00008000 Power framework delay fuzzing.
    [ ] 0x00010000 Port/miniport interface checking.
    [ ] 0x00040000 Systematic low resources simulation.
    [ ] 0x00080000 DDI compliance checking (additional).
    [ ] 0x00200000 NDIS/WIFI verification.
    [ ] 0x00800000 Kernel synchronization delay fuzzing.
    [ ] 0x01000000 VM switch verification.
    [ ] 0x02000000 Code integrity checks.

Select all tests to match the 19 tests in this link:
https://answers.microsoft.com/en-us/...3-c48669e4c983

I have all of those selected except "[ ] 0x00000004 Randomized low resources simulation." The link you sent me to says to check all except "don't check "DDI compliance checking" and "randomized low resource simulation"". I will untick those tests, but that still leaves one in question I'm going to assume since they don't mention it and it isn't pictured, I will assume that they leave the "DDI compliance checking (additional)" unticked as well. That should leave me running 19 tests out of 22. Rather than the 21/22 I had.

I will run the tests for 3-4 hours and after that turn collect dm and v2 logs and post here. Then reset verifier (turn off) and use the computer for a bit. If I don't get the crashes/reboots like I had, I will go ahead and install build 1903 of Windows 10 (clean install). Then install Steam. If it crashes again like it has, I will open a support ticket with steam. In the mean time, if they don't offer me decent support, I will look into deleting or blocking that particular driver from loading.

The plan looks good.
If you don't have important files you can clean install.
If you have important files then make a backup image so that you have the option to restore.

zbook said:

The plan looks good.
If you don't have important files you can clean install.
If you have important files then make a backup image so that you have the option to restore.

I try not to keep anything I can just re-download again. This drive is just my OS and some programs. But we're not quite out of the woods yet.

I let verifier run overnight with the settings we agreed upon:
Attachment 237986

I rebooted the computer, ran verifier /reset. Powered off the computer and waited a bit. Maybe 2.5 hours.

I started the computer this morning, and it was still acting sluggishly, like the mouse cursor was lagging and Task Manager took a bit to come up. I ran verifier, and in the GUI I chose delete settings. It came back with "No changes made."

Whatever I thought. I rebooted the computer.

Within maybe 5 minutes, the entire screen went green. No keyboard input, no mouse input. I don't need to hold the power button down, just tap it, and the system turns off.

No memory dump was written out, but Everything revealed a WATCHDOG*.dmp file. I'm uploading that and the v2 and dm logs.

I'm scratching my head now.

I have an old 530 power supply sitting around. Maybe swapping that out is next.

Why would it not fail during hours and hours and hours of verifier, but crash within 4 or 5 minutes of desktop idle?

1) uninstall the Nvidia GPU driver using DDU (display driver uninstaller)

2) re-install the Nvidia GPU driver from the Nvidia website

3) make sure that you check the clean install box and if available install the physx driver.

Display Driver Uninstaller Download version 18.0.0.8 (or newer version if available)

Display Driver Uninstaller: How to use - Windows 7 Help Forums

Download Drivers | NVIDIA

Code:

Name	NVIDIA GeForce GTX 1070
PNP Device ID	PCI\VEN_10DE&DEV_1B81&SUBSYS_33011462&REV_A1\4&FC7F53B&0&0018
Adapter Type	GeForce GTX 1070, NVIDIA compatible
Adapter Description	NVIDIA GeForce GTX 1070
Adapter RAM	(1,048,576) bytes
Installed Drivers	C:\Windows\System32\DriverStore\FileRepository\nvmd.inf_amd64_c565f1ecc1f666f0\nvldumdx.dll,C:\Windows\System32\DriverStore\FileRepository\nvmd.inf_amd64_c565f1ecc1f666f0\nvldumdx.dll,C:\Windows\System32\DriverStore\FileRepository\nvmd.inf_amd64_c565f1ecc1f666f0\nvldumdx.dll,C:\Windows\System32\DriverStore\FileRepository\nvmd.inf_amd64_c565f1ecc1f666f0\nvldumdx.dll
Driver Version	25.21.14.1972
INF File	oem5.inf (Section001 section)
Color Planes	Not Available
Color Table Entries	4294967296
Resolution	3840 x 2160 x 60 hertz
Bits/Pixel	32
Memory Address	0xFA000000-0xFB0FFFFF
Memory Address	0xE0000000-0xF1FFFFFF
Memory Address	0xF0000000-0xF1FFFFFF
I/O Port	0x0000E000-0x0000EFFF
IRQ Channel	IRQ 40
Driver	c:\windows\system32\driverstore\filerepository\nvmd.inf_amd64_c565f1ecc1f666f0\nvlddmkm.sys (25.21.14.1972, 19.75 MB (20,704,968 bytes), 03/25/19 08:54)

Code:

nvlddmkm.sys Mon Mar 18 11:18:40 2019 (5C8FE100)