Solved BSOD during regular use, Various Errors

[Spa178]

I am currently experiencing BSOD issues with my PC during regular use.

The BSOD does not seem to be associated with any particular task, as it has occurred while the computer is idle or in use, with or without any extraneous programs. After each BSOD, there are issues in restarting and it will occasionally either refuse to boot correctly and simply spin the fans, or it will crash mid-boot and attempt to restart. The PC only boots properly once turned off completely and restarted through the use of the On/Off button, as the restart button simply begins the cycle of boot/crash again.
Each BSOD has also caused issues with programs, managing to either corrupt or remove files that are integral to their operation. For instance, my attempts to run Path of Exile are thwarted due to some missing audio files, and Mechwarrior Online is missing some files related to the engine. This is fixable, of course, through re-installing or repairing them, but the issue reappears after another BSOD.

Any help in resolving this issue would be greatly appreciated.

 

[Spa178]

Issues are still continuing.

Turns out that the issues with corrupt game files are separate to the BSOD issue.
The BSOD's seem to occur most often when either gaming, watching youtube, or both, with either program spontaneously failing 2-3 times in quick succession before the actual BSOD occurs.
Have attempted a GPU driver rollback, uninstall, and update to no avail.

Here are some newer .dmp files from the Minidump folder.

oh, and *bump*.

 

[Golden]

fffff880`01fb0338  fffff880`01fb0890
fffff880`01fb0340  00000000`00000000
fffff880`01fb0348  fffff880`02b36193Unable to load image \SystemRoot\system32\drivers\aswSP.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for[B][COLOR="Red"] aswSP.sys[/COLOR][/B]
*** ERROR: Module load completed but symbols could not be loaded for aswSP.sys
 aswSP+0x1f193
fffff880`01fb0350  00000000`c0000503
fffff880`01fb0358  fffff880`02b2297e aswSP+0xb97e
fffff880`01fb0360  fffff8a0`05c94948
fffff880`01fb0368  fffff880`01fb03e8

Please uninstall Avast using this tool:
Avast Software Uninstall Utility Download

Replace it with MSE (known to never cause BSOD's).
Microsoft Security Essentials - Microsoft Windows

Now reboot and do the following please:

Run Driver Verifier for 24 hours or the occurrence of the next crash, whichever is earlier.
http://www.sevenforums.com/tutorials/101379-driver-verifier-enable-disable.html

Driver Verifier will cause your computer to run very sluggishly - this is normal. What it is trying to do is force your system to BSOD and isolate the offending driver/s. When it does, reboot, disable driver verifier, reboot as normal and upload the new dmp file/s here.

I recommend creating a system restore point before turning on driver verifier:
http://www.sevenforums.com/tutorials/697-system-restore-point-create.html

If your system fails to boot to desktop once driver verifier is enabled, turn it off by booting into Safe Mode:
http://www.sevenforums.com/tutorials/69585-safe-mode.html

 

[Spa178]

I did as you said, and directly after logging on with verifier active, I receive a BSOD.
Unfortunately, there is an issue with the .dmp files. They won't compress, and they seem to have dissapeared from c/windows/minidump after being copied. They are also not being picked up by the automatic debug program that is recommended by the site.

I can still open it with WinDBG though, and this was the result:


Microsoft (R) Windows Debugger Version 6.3.9600.17298 X86
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Users\Daniel\Desktop\Latest Dump\021515-23041-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 7 Kernel Version 7601 (Service Pack 1) MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7601.18717.amd64fre.win7sp1_gdr.150113-1808
Machine Name:
Kernel base = 0xfffff800`02c57000 PsLoadedModuleList = 0xfffff800`02e9b890
Debug session time: Sun Feb 15 21:21:57.747 2015 (UTC + 9:30)
System Uptime: 0 days 0:01:05.980
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 C4, {40, 0, fffff980059fec50, 0}

*** WARNING: Unable to verify timestamp for ndisrd.sys
*** ERROR: Module load completed but symbols could not be loaded for ndisrd.sys
Probably caused by : ndisrd.sys ( ndisrd+2716 )

Followup: MachineOwner
---------

3: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

DRIVER_VERIFIER_DETECTED_VIOLATION (c4)
A device driver attempting to corrupt the system has been caught. This is
because the driver was specified in the registry as being suspect (by the
administrator) and the kernel has enabled substantial checking of this driver.
If the driver attempts to corrupt the system, bugchecks 0xC4, 0xC1 and 0xA will
be among the most commonly seen crashes.
Arguments:
Arg1: 0000000000000040, Acquiring a spinlock at IRQL < DISPATCH_LEVEL.
Arg2: 0000000000000000, Current IRQL
Arg3: fffff980059fec50, Spinlock address
Arg4: 0000000000000000

Debugging Details:
------------------


BUGCHECK_STR: 0xc4_40

CURRENT_IRQL: 0

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: VERIFIER_ENABLED_VISTA_MINIDUMP

PROCESS_NAME: NetSvcHelp.exe

ANALYSIS_VERSION: 6.3.9600.17298 (debuggers(dbg).141024-1500) x86fre

LAST_CONTROL_TRANSFER: from fffff8000315b4ec to fffff80002ccbec0

STACK_TEXT:
fffff880`0abbd688 fffff800`0315b4ec : 00000000`000000c4 00000000`00000040 00000000`00000000 fffff980`059fec50 : nt!KeBugCheckEx
fffff880`0abbd690 fffff800`0316c2df : 00000000`00000002 fffffa80`0c6d6dc8 00000000`00000000 fffff800`031696bb : nt!VerifierBugCheckIfAppropriate+0x3c
fffff880`0abbd6d0 fffff880`03f49716 : fffffa80`10c955c0 fffff980`059fec00 fffff980`16d5efb0 fffff880`0abbd798 : nt!VerifierKeAcquireSpinLockAtDpcLevel+0xa0
fffff880`0abbd730 fffffa80`10c955c0 : fffff980`059fec00 fffff980`16d5efb0 fffff880`0abbd798 00000000`00000000 : ndisrd+0x2716
fffff880`0abbd738 fffff980`059fec00 : fffff980`16d5efb0 fffff880`0abbd798 00000000`00000000 fffff880`03f4ab99 : 0xfffffa80`10c955c0
fffff880`0abbd740 fffff980`16d5efb0 : fffff880`0abbd798 00000000`00000000 fffff880`03f4ab99 00000000`00010001 : 0xfffff980`059fec00
fffff880`0abbd748 fffff880`0abbd798 : 00000000`00000000 fffff880`03f4ab99 00000000`00010001 fffff980`16d6aff0 : 0xfffff980`16d5efb0
fffff880`0abbd750 00000000`00000000 : fffff880`03f4ab99 00000000`00010001 fffff980`16d6aff0 00000000`00000000 : 0xfffff880`0abbd798


STACK_COMMAND: kb

FOLLOWUP_IP:
ndisrd+2716
fffff880`03f49716 ?? ???

SYMBOL_STACK_INDEX: 3

SYMBOL_NAME: ndisrd+2716

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: ndisrd

IMAGE_NAME: ndisrd.sys

DEBUG_FLR_IMAGE_TIMESTAMP: 4fc6df85

FAILURE_BUCKET_ID: X64_0xc4_40_VRF_ndisrd+2716

BUCKET_ID: X64_0xc4_40_VRF_ndisrd+2716

ANALYSIS_SOURCE: KM

FAILURE_ID_HASH_STRING: km:x64_0xc4_40_vrf_ndisrd+2716

FAILURE_ID_HASH: {30bca9d7-111a-da6d-af09-4e1e9b7679e4}

Followup: MachineOwner
---------


I am going to attempt to obtain a .dmp file to upload by running the verifier again.

 

[Spa178]

Alright, here's the latest dump from Driver Verifier.

 

[Spa178]

Quick Update:

Issue seems to be solved.
I noticed that the file that resulted in the error for the most recent dump was one of my Nvidia drivers. So, I booted into Safe Mode and uninstalled my Nvidia drivers through Device Manager, deleted the Nvidia folder in Local Disk (C) and reinstalled the latest driver.
I have only experienced a single BSOD since then, which was virus related, and have been able to perform CPU and GPU intensive tasks for hours at a time without a single issue.

Thanks for your help Golden.

 

[Golden]

Sorry for not replying earlier...been a bit burnt out and taking some time for myself.