I exclude normal solutions like faulty RAM or HDD...
Google queries:
* symbol search path windows 8.1
* ndis.sys bsod windows 8.1
* BSOD - IRQL_NOT_LESS_OR_EQUAL
* Module load completed but symbols could not be loaded for Neo_VPN123.sys
* symfix
* ndis.sys fffff880`01c9f000
* trace bsod file verification
Useless official link:
http://msdn.microsoft.com/en-us/library/windows/desktop/ee416349(v=vs.85).aspxMost helpful link ever:
http://www.instructables.com/id/How-to-Analyze-a-BSOD-Crash-Dump/Link to start with:
http://www.reviversoft.com/blog/2013/09/using-driver-verifier-to-fix-a-blue-screen-of-death/http://www.sevenforums.com/tutorials/101379-driver-verifier-enable-disable.htmlMost important and helpful part of that article:
Paste the following text into the Symbol Search Path Dialog
SRV*C:\Windows\symbol_cache*http://msdl.microsoft.com/download/symbols
This will take a little while. Be patient.
What did I solve with it?
Well, I was having BSOD's for a LONG time now. Almost always after system restore. I replaced / unplugged many hardwares but even after my new computer, I kept having this problem. Surely I was repeating my errors and I suspected "some" VPN tool. But hunting them down for years, I have quite a few ;-) So which one? I always ignored it, but 2 days ago (new video card) I had it.
Time to solve!
I first enabled driver verification for all non-Microsoft drivers.
That resulted in immediate BSOD. I booted into safe mode, without network, and disabled windows 8 driver verification again (with verifier.exe).
Now I had (yet another) dump report (C:\Windows\minidump\*.dmp).
Analyzing it with 'WinDbg (x64).exe' (don't forget to set Symbol Path! Why MS makes this so complicated... Sigh), gave:
************* Symbol Path validation summary **************
Response Time (ms) Location
Deferred SRV*C:\Windows\symbol_cache*http://msdl.microsoft.com/download/symbols
Microsoft (R) Windows Debugger Version 6.3.9600.16384 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [C:\Windows\Minidump\030714-70465-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available
************* Symbol Path validation summary **************
Response Time (ms) Location
Deferred SRV*C:\Windows\symbol_cache*http://msdl.microsoft.com/download/symbols
Symbol search path is: SRV*C:\Windows\symbol_cache*http://msdl.microsoft.com/download/symbols
Executable search path is:
Windows 8 Kernel Version 9200 MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 9200.16628.amd64fre.win8_gdr.130531-1504
Machine Name:
Kernel base = 0xfffff802`a0001000 PsLoadedModuleList = 0xfffff802`a02cda20
Debug session time: Fri Mar 7 09:19:20.139 2014 (UTC + 1:00)
System Uptime: 0 days 0:00:40.992
Loading Kernel Symbols
.
Press ctrl-c (cdb, kd, ntsd) or ctrl-break (windbg) to abort symbol loads that take too long.
Run !sym noisy before .reload to track down problems loading symbols.
..............................................................
................................................................
............................
Loading User Symbols
Loading unloaded module list
...
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck C2, {9b, 204, 580, fffff88001c94d47}
*** WARNING: Unable to verify timestamp for Neo_VPN123.sys
*** ERROR: Module load completed but symbols could not be loaded for Neo_VPN123.sys
Probably caused by : Neo_VPN123.sys ( Neo_VPN123+1113 )
Followup: MachineOwner
---------
I did not find a way to add Neo_VPN123 symbol set, BUT a quick google search showed me this belonged to my beloved (but not working anymore) SoftEther. So I just removed it, should be solved now. If not: next dmp analysis on its way. I should have learned this long ago but always failed on Symbols...
Anyways, enjoy - a non-coin article for once again
Devvie
