Random BSOD Kernel-Power 41 (63) bugcheckcode 126, 26, 278, 0, 59, 80

Adam Wilkin · 29 Jan 2016

Hello, i have been experiencing random restarts at the beginning of January. The 2 restart i remember the most at the beginning of the month was when Just Cause 3 was loading up and when i was updating Nvidia drivers. These did not come up with a BSOD. But after that the restarts have been much more frequent happening around once a day and now i have a BSOD, and i don't have an explanation for these resent problems. Looking up on the internet at first i thought my graphics card or PSU was the problem but i now think it might be a software issue with drivers or something.

I have linked a ZIP file with all the files you need!

Anyone could help i would really appreciate it. If you have any questions about anything please ask and i will try and explain as much as i can. Thank You!

**cluberti** · 29 Jan 2016

Note that if you're having issues with problems starting in January, the restarts are not producing bugchecks (the only dump files here are from June 2015 and December 2015). I did see you've been having power issues since June, though, although it was most frequently reported in December. I decided to look at the dump from December and found your video driver is from May of 2015 - given this is an nVidia chipset, there's bound to be a newer driver (the latest driver for the GTX 960 appears to have been released just 2 days ago):

Code:

2: kd> lmvm nvlddmkm
start             end                 module name
fffff880`05c8e000 fffff880`06751000   nvlddmkm T (no symbols)           
    Loaded symbol image file: nvlddmkm.sys
    Image path: nvlddmkm.sys
    Image name: nvlddmkm.sys
    Timestamp:        Wed May 27 19:49:51 2015 (5566824F)
    CheckSum:         00A7E4BD
    ImageSize:        00AC3000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4

Adam Wilkin · 30 Jan 2016

Yes in December i had bought a new graphics card and it was a faulty one, but i got a new one back that worked. That probably explains the problems in December. Also i have updated the nivida drivers, and 2 days ago when i did it crashed with no BSOD.

i dont know why windows is not creating dump files then, there is a screenshot of my cirtical errors

Maybe its a hardware thing, as it seems windows cant record what it it?

**cluberti** · 31 Jan 2016

If the system is set to crash, you can actually test it by using NotMyFault from sysinternals - if it bugchecks when using that tool (you would crash the system on purpose), then you can be certain that at least the BSOD works (and validate it creates a memory.dmp file after coming back up). If so, then yes, the unclean shutdowns would likely NOT be bugchecks. That would indeed indicate hardware issues instead.

Adam Wilkin · 15 Feb 2016

sorry for the late reply, i updated lots of programs and drivers and it seemed to work but its now just come back! i just tried that program and still not dump files were created. what do you suggest now?