Possible PSU Failure?

Indianatone said:

Have asked the BSOD guys to run the files thru the grinder so to speak. Someone will post the results and if it is inconclusive I would suspect the PSU.

Thanks Indianatone! I really appreciate all your help with this.

Did you have a look at voltages in your BIOS/UEFI?

I have one more request for you before you replace the PSU. I have had a machine that has been doing weird things since the last NVidia driver came out. A new one dated 21st October just been released. Try that and see if the problem goes away. Unlikely but humour me. I thought my wife's machine had a bad motherboard or cpu so swapped them both out. That machine started to go wrong after running for nearly 3 years a month ago after I upgraded the video driver. FWIW https://www.sevenforums.com/bsod-help...uescreens.html
Free is also cheaper. The suspect driver is this one
GeForce 327.23 Driver

https://forums.geforce.com/default/t...fset=9#3949966

x BlueRobot said:

Code:

BugCheck 116, {fffffa80098a34e0, fffff88009910f50, ffffffffc000009a, 4}
 
Unable to load image \SystemRoot\system32\DRIVERS\nvlddmkm.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for nvlddmkm.sys
*** ERROR: Module load completed but symbols could not be loaded for nvlddmkm.sys
Probably caused by : nvlddmkm.sys ( nvlddmkm+8f0f50 )

Code:

6: kd> !error ffffffffc000009a
Error code: (NTSTATUS) 0xc000009a (3221225626) - Insufficient system resources exist to complete the API.

The NTSTATUS error code is usually related to pool leaks caused by graphics card drivers, however, reading through the thread and looking at the stack, I think it may be a PSU issue too.

Code:

6: kd> !stack
Call Stack : 7 frames
## Stack-Pointer Return-Address Call-Site 
00 fffff8800296fa48 fffff88007c71054 nt!KeBugCheckEx+0 
01 fffff8800296fa50 fffff88007c44867 dxgkrnl!TdrBugcheckOnTimeout+ec 
02 fffff8800296fa90 fffff88007c70e63 dxgkrnl!DXGADAPTER::Reset+2a3 
03 fffff8800296fb40 fffff88007d4003d dxgkrnl!TdrResetFromTimeout+23 
04 fffff8800296fbc0 fffff8000391abae dxgmms1!VidSchiWorkerThread+101 
05 fffff8800296fc00 fffff8000366d8c6 nt!PspSystemThreadStartup+5a 
06 fffff8800296fc40 0000000000000000 nt!KxStartSystemThread+16

The stack indicates that the graphics card driver has attempted to reset the graphics card, but failed to do so within the allocated time interval, and therefore caused a timeout with the following Stop Code 0x116. More Information - Timeout Detection and Recovery (TDR) (Windows Drivers)

So it is my graphics card? Is the PSU causing it to malfunction which triggers the crash? My GPU is only 5 months old so I can't imagine it being the one causing all this.

Britton30 said:

Did you have a look at voltages in your BIOS/UEFI?

I just got home and was able to get these when I booted up the computer. Not sure if it is good or bad, but this is what I found.

CPU Voltage - 1.12V / 1.20V (It would fluctuate back and forth)
3.3V Voltage - 3.296V
5V Voltage - 5.080V
12V Voltage - 12.288V

I don't know if this was the information you were looking for exactly but just let me know if there were any other readings you needed.

Indianatone said:

I have one more request for you before you replace the PSU. I have had a machine that has been doing weird things since the last NVidia driver came out. A new one dated 21st October just been released. Try that and see if the problem goes away. Unlikely but humour me. I thought my wife's machine had a bad motherboard or cpu so swapped them both out. That machine started to go wrong after running for nearly 3 years a month ago after I upgraded the video driver. FWIW https://www.sevenforums.com/bsod-help...uescreens.html
Free is also cheaper. The suspect driver is this one
GeForce 327.23 Driver

https://forums.geforce.com/default/t...fset=9#3949966

That is funny because my current driver is the 327.23. I will update to the new driver (331.58) and test it to see if there are any changes. Thanks for catching this!

Those voltages are perfect. It is normal for the CPU voltage to go up and down as the speed changes or cores go on or off (power saving when idle).

x BlueRobot said:

The PSU most likely seems to be causing the GPU to crash.

I think so too, but that driver gave me the runaround on one of my machines so its worth a try since it free.