X79 Blue Screen Registry Fix Won't Stick

[bradly1101]

I made a post a while ago about IRQ_NOT_LESS_OR_EQUAL blue screens I was getting on a pretty rare basis. In running Driver Verifier I drilled down on the specific error by Googling and found an answer that worked. "If there is a Network Interface listed with no values in this key (HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\services\Tcpip\Parameters\Interfaces) just delete it."

That worked! The Driver Verifier error no longer came up, and I went months without an IRQ_NOT_LESS_OR_EQUAL blue screen (or any BSOD's).

The problem is that the registry entry keeps coming back and results in a BSOD.

Any thoughts?

 

[Ketchup]

Does it save to a dump file? If so, have you looked at it with a program like Whocrashed?

 

[bradly1101]

Does it save to a dump file? If so, have you looked at it with a prosram like Whocrashed?

Yes that's what led me to driver verifier and the fix. It just won't stick.

 

[Ketchup]

What does whocrashed say about the error?

 

[bradly1101]

What does whocrashed say about the error?

On Sat 12/10/2016 7:25:45 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\121016-24492-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x70400)
Bugcheck code: 0x9F (0x3, 0xFFFFFA800FBFA060, 0xFFFFF80000B9A3D8, 0xFFFFFA801C7F4010)
Error: DRIVER_POWER_STATE_FAILURE
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This bug check indicates that the driver is in an inconsistent or invalid power state.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.

 

[Ketchup]

Figures. But it's free. Sometimes they do have helpful tips. What OS?

 

[bradly1101]

7. I know how to fix the error, I just need the phantom registry entry to stop coming back.

 

[Ketchup]

You know, a virus will do something like that. What AV are you running?

 

[bradly1101]

MSE. I'm doing a scan now. Thanks.

 

[bradly1101]

Nothing found after a full scan.

 

[Ketchup]

I guess my next question is, how do you know the registry entry causes the blue screen? It may been a needed field on your install, and Windows restores it from the backup registry on the next reboot.

Glad to know you are virus free in any event. The virus I was referring to is about 2 years old, so MSE would have caught it if it was there.

 

[bradly1101]

I guess my next question is, how do you know the registry entry causes the blue screen? It may been a needed field on your install, and Windows restores it from the backup registry on the next reboot.

Glad to know you are virus free in any event. The virus I was referring to is about 2 years old, so MSE would have caught it if it was there.

The troubleshooting included using Driver Verifier since the BSOD indicated a driver problem. The error led me to this fix:
https://support.microsoft.com/en-us/kb/2550576

"c. Find the following registry key, and if the Data value is empty, remove the registry key.

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\services\Tcpip\Parameters\Interfaces\<your-adapter-interface>"

I checked and it does come back with every reboot. I originally posted this as a possible power problem here. There's a strange symptom when the PC is running fine the CD drive will cycle like it just received power. So despite MS's recommendation, I think that key is supposed to stay there, and I'm beginning to suspect the CD drive. It's a cheap Sony unit left over from another build.

 

[Ketchup]

But according to that, simply turning off driver verifier would fix your problem.

 

[bradly1101]

Driver Verifier is something you do turn off. I only get the Driver Verifier error when running Verifier, and that led me to this fix. If I delete the empty interface in the Registry, then run Verifier, it makes it past that error. I'm not sure why since it requires a reboot in between, so the registry entry must be back, but it works. If I get a blue screen (once in a few months) then delete this, I don't see the error or BSOD's in a long time. But I do get that strange CD power cycling.

 

[bradly1101]

I have disconnected the CD drive to test. Still getting Verifier error though.