Solved Multiple BSOD... Driver IRQL error

[tstevens83]

Multiple BSOD with various programs running... even no programs and just background programs.

Windows 7 Professional - x64 - Full Retail version
system age varies - ~2-3 yrs
i have not reinstalled the OS and it's not the orginial

 

[writhziden]

Device Concerns:

High Definition Audio Device	HDAUDIO\FUNC_01&VEN_8086&DEV_2804&SUBSYS_80860101&REV_1000\4&35A89E12&0&0301	This device cannot start.

Hardware devices are not working or are not detected in Windows may resolve the above.​

Analysis:

All crashes blame NEOFLTR_650_16789.SYS which is part of your Juniper Networks software. Update the software or re-install it. It may be corrupted. If that does not resolve it, remove the software and test whether the crashes cease. If removing it resolves it but you need the software, contact Juniper support for help with the software.
Support - Juniper Networks​

 

[tstevens83]

how did you identify the file to blame for BSOD?

thank you for you support... i have a question: what information leads you to blame NEOFLTR_650_16789.SYS associated with Juniper Networks software? i looked at the dump files using BlueScreenView and it says ntoskrnl.exe caused the crashes. I went ahead and deleted the Juniper Networks software and i'm waiting to see if i get another crash.... so far so good.

 

[writhziden]

That is why we do not use BlueScreenView. The information it provides is vague at best and often just tells us that Windows is not working properly. If Windows were working properly, you would not need to use BlueScreenView.

Here is partial info from WinDbg (the software we use to debug the crashes). I have a tool I wrote that extracts the useful info from it. There is a similar tool provided by jcgriff2 and niemiro:

--------------------------------------------
--------------------START-------------------
--------------------------------------------
Loading Dump File [D:\Kingston\BSODDmpFiles\tstevens83\071012-26676-01.dmp]

Windows 7 Kernel Version 7601 (Service Pack 1) MP (4 procs) Free x64

System Uptime: 0 days 0:08:51.978

BugCheck D1, {0, 2, 8, 0}

*** WARNING: Unable to verify timestamp for NEOFLTR_650_16789.SYS

*** ERROR: Module load completed but symbols could not be loaded for NEOFLTR_650_16789.SYS

*** WARNING: Unable to verify timestamp for win32k.sys

*** ERROR: Module load completed but symbols could not be loaded for win32k.sys

[B][COLOR="Red"]Probably caused by : NEOFLTR_650_16789.SYS[/COLOR][/B] ( NEOFLTR_650_16789+d0c7 )

DRIVER_IRQL_NOT_LESS_OR_EQUAL (d1)

PROCESS_NAME:  System

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

STACK_TEXT:  
fffff800`04944878 fffff880`0122f0c7 : 00000000`000000cb 00000000`00000000 00000000`00000000 00000000`00000000 : 0x0
fffff800`04944880 00000000`000000cb : 00000000`00000000 00000000`00000000 00000000`00000000 fffffa80`09ba71c0 : NEOFLTR_650_16789+0xd0c7
fffff800`04944888 00000000`00000000 : 00000000`00000000 00000000`00000000 fffffa80`09ba71c0 00000000`00001000 : 0xcb


FAILURE_BUCKET_ID:  X64_0xD1_CODE_AV_NULL_IP_NEOFLTR_650_16789+d0c7

CPUID:        "Intel(R) Core(TM) i3 CPU         530  @ 2.93GHz"
MaxSpeed:     2930
CurrentSpeed: 2933

--------------------------------------------
---------------------END--------------------
--------------------------------------------

 

[tstevens83]

thank you for you patience and information... i did download WinDbg and got it to read the dump file... i saw the reference to NEOFLTR_650_16789.SYS. now... it will be interesting to see if i can decode a BSOD dump file if it happens again. thank you again for you help.

 

[writhziden]

You're welcome. Let us know if you the problem ends up being solved, and you may also mark the thread solved at that time.

You may also find the following of interest when debugging the blue screen crashes: http://www.sevenforums.com/crash-lockup-debug-how/232954-how-i-debug-blue-screen-crashes.html. Feel free to post again if you want help learning, or you can send me a PM with any questions.