jcgriff2 - Blue Screen of Death

"Failed to Repair," restarts, and other woes

Monday, August 19, 2019

BSOD Kernel Dump Expert
1,235 posts
ONLINE

Gender:Male
Location:New Jersey Shore
Local time:11:16 AM

Posted Today, 10:56 AM

Hi. . .

On the current system first, activate the Hidden Admin user account and see if you can see and access the files you are after -

https://www.sysnative.com/forums/threads/enable-disable-the-hidden-administrator-user-account-windows-10-8-1-8-7-vista.25824/

If no-go, place the HDD back into the system as primary, boot-up and activate the Hidden Admin user account.

There is only 1 Hidden Administrator user account and since you will be using it
only temporarily, I would advise NOT password protecting it right now. If you were to lose control/access of the Hidden Admin account (it is the account that comes up when the UAC screen appears), you will more than likely have to reinstall Windows.

What you describe to me sounds like permission setting issues. As far as the no-boot situation, I don't know what to tell you right now. It may have something to do with the upgraded RAM.

When you increased the RAM to 32 GB, did you install ALL new RAM sticks or did you just add 2 or so RAM sticks to the existing RAM that was already installed?

If you added to the existing, does all of the RAM match?

Regards. . .

jcgriff2

Edited by jcgriff2, Today, 10:57 AM.

Windows 10 "Failed to Repair," restarts, and other woes - WMIC Memorychip HTML Report

WMIC Memorychip HTML Report

BC thread - https://www.bleepingcomputer.com/forums/t/702707/failed-to-repair-restarts-and-other-woes/#entry4852195

BSOD Kernel Dump Expert

1,235 posts

ONLINE

Gender:Male
Location:New Jersey Shore
Local time:11:16 AM

Posted Today, 11:16 AM

Also, I'd like to see your RAM configuration and info.

Run #24 from this WMI tutorial - https://www.sysnative.com/forums/threads/windows-management-instrumentation-wmi-windows-10-8-1-8-7-vista.12294/

Start with the WMI RAM memorychip HTML batch script - http://www.sysnative.com/SysnativeTutorials/wmi/batch/memorychip_h.bat

The output should look like this - http://www.sysnative.com/SysnativeTutorials/wmi/html/memorychip.html

If not, run the TEXT output batch file - http://www.sysnative.com/SysnativeTutorials/wmi/batch/memorychip_t.bat

The output should look like this - http://www.sysnative.com/SysnativeTutorials/wmi/txt/memorychip.txt

I'd prefer the HTML output. You can run it on the current system as the RAM hardware is the same as the previous non-boot RAM.

Regardless of which you run, please zip up the file and attach it to your next post.

Also, please run systeminfo from a CMD Prompt/Screen.

Then paste it into your post using a BB code CODE BOX.

To copy the CMD screen, RIGHT-click anywhere on the CMD screen, select "select all"; then hit ENTER. This will select and copy the entire contents of your CMD screen. The CODE BB brackets are necessary to keep the spacing from the systeminfo report aligned.

You can also click on

in the menu and then paste the CMD screen contents between the CODE brackets.

If you find an email address in the systeminfo output after pasting into your post, simply remove it. If it is in systeminfo, it will be ~ 5-10 lines down from the top of the report.

Good luck to you!

Regards. . .

jcgriff2

BSOD: Driver Power State Failure

Friday, August 16, 2019

https://www.bleepingcomputer.com/forums/t/702378/bsod-driver-power-state-failure/?p=4849725

NVIDIA Roll back.

BSOD - DRIVER_POWER_STATE_FAILURE - 0x0000009f

Monday, August 12, 2019

Posted Today, 02:50 PM

Hi. . .

2 of the 5 dumps you submitted were zero (-0-) bytes in size. This means that Windows came down so fast that it did not have time to write a dump or an "unknown" hardware problem exists and the computer literally shut off/lost power before it could write the dump (akin to someone pulling out the electrical plug on a desktop PC.

BSOD Kernel memory dumps are created to help software developers debug their code, not really to help us with hardware issues. In fact, dump files are incapable of telling us which piece of hardware is/has failed. At best, dumps can point us in a general direction, for example, telling us that an I/O error occurred, which to me means that the system encountered trouble with a hard drive. Again, that was just an example and I was NOT referring to your system.

Of the 3 remaining dumps, 2 of them had bugchecks = 0xc4 which means that Driver Verifier flagged a driver. The driver named was the Microsoft Windows Network I/O Subsystem driver netio.sys

This presents at least 2 problems. The Driver Verifier instructions state to only select 3rd party drivers (non-Microsoft drivers). Did you do this step correctly?

If so, having Driver Verifier list a Microsoft driver leas us to the direction of unknown hardware failure as the probable cause. netio.sys being a Microsoft driver means that it is sacrosanct and could not possibly be the actual cause of the BSOD. If it were, many millions of other people would also be experiencing BSODs because they have the exact same version of that driver that you do.

The 3rd dump had a bugcheck = [0x9f (0x3,,,)[/b] = DRIVER_POWER_STATE_FAILURE; A device has been blocking an IRP for too long a time. (IRP = Input/Output request packets)

Digging deeper into the 0x9f dump reveals the blocked IRP -

>[IRP_MJ_POWER(16), IRP_MN_SET_POWER(2)]
            0 e1 ffff8f8a2f2aa030 00000000 fffff8002ab6f520-ffff8f8a329a9ee8 Success Error Cancel pending
        \Driver\nvlddmkm nt!PopRequestCompletion
   Args: 00000000 00000001 00000001 00000000

If you look carefully through that seemingly jumbled mess, you'll see nvlddmkm after the word \driver

nvlddmkm.sys is your NVIDIA video card driver. Your driver is relatively new - just about 1 month old. From your dump file -

nvlddmkm.sys Wed Jul 17 14:04:33 2019 (5D2F8D61)

https://www.sysnative.com/drivers/driver.php?id=nvlddmkm.sys

I would suggest rolling the driver back, but we also need to test your video card.

Run FurMark - https://www.sysnative.com/forums/threads/furmark-display-card-stress-test.3907/

Please post the results.

If Furmark passes, then run Driver Verifier - https://www.bleepingcomputer.com/forums/t/576333/driver-verifier-bsod-related-windows-10-81-8-7-vista/

Driver Verifier must run for at least 24 hours and it's job is to stress-test your 3rd party drivers and force a BSOD if it detects a violation.

Please use these settings - https://www.bleepingcomputer.com/forums/t/576333/driver-verifier-bsod-related-windows-10-81-8-7-vista/

I must admit that after seeing netio.sys, finding NVIDIA in the 0x9f dump threw me for a loop as I was expecting to see either your wifi or Ethernet driver (a networking driver), not your video driver.

And of course, the 2 dumps showing zero bytes in size is bothersome. Also, every file in the Sysnative zip file shows as 1/1/1980 12:00 AM, which I have no idea why the files would display like that (but I have seen this phenomenon before) as I wrote the Sysnative app.

Screenshot of the 5 dump files showing the date and time (timestamp) as well as the two dumps that are -0- bytes in size -

Regards. . .

jcgriff2

p.s. ntoskrnl.exe (that you mentioned WhoCrashed said was the cause of the 0x9f dump) is the Windows kernel and could not possibly be the cause of your BSODs. ntoskrnl.exe is often named as a default of sorts when the real cause cannot be determined.

Edited by jcgriff2, Today, 02:51 PM.

BSOD 0x000007e - Atheros wifi

Sysnative Forums - https://www.sysnative.com/forums/threads/bsod-stop-0x0000007e-error-on-startup.29010/#post-266648

Atheros USB wifi driver is the cause - athurx.sys

If the BSODs do get to a point where you can no longer tolerate them, you can replace the USB wifi adapter.

I would recommend Netgear brand or perhaps TP-Link brand USB wifi adapters as they do generally keep their drivers updated.

Netgear USB wifi adapters at Amazon - Amazon.com: usb wifi adapter - NETGEAR

Netgear drivers - download | Support | NETGEAR

Also, TP-Link seems to have drivers available too -

TP-Link USB devices - Amazon.com: tp-link usb wifi adapter

TP-Link driver downloads - TP-Link Product Support - Download Center

Good luck to you!

Regards. . .

jcgriff2

0x116 BSOD VIDEO_TDR_ ERROR - Video TDR Timeout

Saturday, August 10, 2019

Hi. . .

There were in fact 3 BSOD dumps.

The bugcheck on all 3 dumps was 0x116 = Video TDR Timeout - the video driver attempted to reset itself but could not do so within the time allotted (30 seconds).

The probable cause on all 3 dumps listed as your ATI video driver -

atikmpag.sys Mon Apr 15 20:17:47 2019 (5CB5495B)

Check ATI for a driver update - https://www.sysnative.com/drivers/driver.php?id=atikmpag.sys

You're looking for a driver newer than 15 April 2019.

If after the driver update you are still having issues, swap out the video card for another, even if just temporarily to see if the system stabilizes.

0x116 bugcheck BSODs generally have two causes - (1) video driver or (2) video card

Regards. . .

jcgriff2

Edited by jcgriff2, Today, 01:59 PM.

WHEA_UNCORRECTABLE_ERROR

https://www.bleepingcomputer.com/forums/t/702241/whea-uncorrectable-error/?p=4846443

So a generic BUS error has occurred
BUSLG_SRC_ERR_I_NOTIMEOUT_ERR (Proc 0 Bank 22)
Thus, the BUS logic has detected an error in the source on processor 0 and MCA bank 22.
BUS errors are usually due to two causes
-> overclocking including mismatch CPU -> Memory
-> overheating of the CPU

Fault bucket 0xEF_csrss.exe_BUGCHECK_CRITICAL_PROCESS_c0000005_nt!PspCatchCriticalBreak, type 0

Check SSD + HDDs

Caused by Bitdefender - bddci.sys

https://www.sysnative.com/forums/threads/reading-on-line-news-got-bsod-windows-7-sp1-x64.28204/#post-257598

Same thread - BIOS Update - https://www.sysnative.com/forums/threads/reading-on-line-news-got-bsod-windows-7-sp1-x64.28204/#post-257607

https://www.techsupportforum.com/forums/f299/win7-crashing-before-i-can-use-sysnativefilecollectionapp-1235666.html#post7732918

The first is your Atheros wifi driver - https://www.sysnative.com/drivers/dr...?id=athurx.sys

cmdguard.sys - uninstall COMODO. Driver verifier flagged this driver.

amdxhc31.sys - this appears to be an AMD chipset driver. Go to your system manufacturer's site.

MVP Logo

Recent Post

Sysnative Forums

jcgriff2 Links

Text

Search This Blog

Popular Posts

About Me

Labels

Archives

About

Blogroll

Archive