Solved BSOD occurs intermittently during use, and when idle

[1977chevy]

Thank you for any help.

This problem began perhaps 4 or 5 months ago at first happening a couple of times a week, until more recently (last month or two) has become, often, several times a day. The BSOD will sometimes complete, and reboot, but more often will hang on the BSOD screen. If I leave the computer on at night, it will very often be in this state in the morning, and the same if I leave it idle during the day.

When in use, the problem may happen at any time, but seems to occur most frequently when I'm using Eclipse, and also when working in a 3D application called Daz Studio, which uses OpenGL for its interface. It has also frequently happened when browsing in Firefox. It's hard to say if these are particularly vulnerable, or if this is just because these are my most frequently used applications.

Things I have tried which have not helped, or provided information to me:

• Memcheck - Ran for hours, all memory checks out
• Recreated Pagefile, defragging hard drive in between
• Disk Check and Defrag on all Hard drives
• Reinstalled most recent Nvidia drivers
• Installed beta Nvidia drivers
• Checked for driver updates for other hardware, including MB, BIOS, Network, etc. (none found)

Things I have tried which have seem to have helped a little:

• Uninstalled Nvidia drivers, and installed older version from before crashes

I've used BlueScreenView to look at the dump files and found that most are either due to hal.dll or directx. Reverting to the older Nvidia drivers seems to have stopped the directx ones, and now I see all hal.dll.

The components making up this computer were in use together for at least two years without issue before this started.

Thank you for your time.

 

[Arc]

Your crash dumps are not showing any finite probable cause.

Test your RAM modules for possible errors.
How to Test and Diagnose RAM Issues with Memtest86+
Run memtest for at least 8 passes, preferably overnight.

Stress test the Graphics Card using Furmark.
Video Card - Stress Test with Furmark

Stress test the CPU.
Hardware - Stress Test With Prime95

If alol the tests come free of errors, enable Driver Verifier to monitor the drivers.
Driver Verifier - Enable and Disable
Run Driver Verifier for 24 hours or the occurrence of the next crash, whichever is earlier.

   Information

Why Driver Verifier:
It puts a stress on the drivers, ans so it makes the unstable drivers crash. Hopefully the driver that crashes is recorded in the memory dump.

How Can we know that DV is enabled:
It will make the system bit of slow, laggy.

   Warning

Before enabling DV, make it sure that you have earlier System restore points made in your computer. You can check it easily by using CCleaner looking at Tools > System Restore.

If there is no points, make a System Restore Point manually before enabling DV.

   Tip

• If you fail to get on the Desktop because of DV, Boot into Advanced Boot Options > Safe mode. Disable DV there. Now boot normally again, and try following the instruction of enabling DV again.
• If you cannot boot in Safe mode too, do a System Restore to a point you made earlier.

Let us know the results, with the subsequent crash dumps, if any.
______________________________________________________________________________

BugCheck A, {1d2, 2, 0, fffff800032e8474}

Probably caused by : ntkrnlmp.exe ( nt!RtlDispatchException+354 )

Followup: MachineOwner
-----------------------------------------------------------------------
BugCheck 1, {7705144a, 0, ffff0000, fffff88006cceca0}

Probably caused by : ntkrnlmp.exe ( nt!KiSystemServiceExit+245 )

Followup: MachineOwner
-------------------------------------------------------------------------
BugCheck 3B, {c0000005, fffff8000358d1fa, fffff8800bf9b0e0, 0}

Probably caused by : ntkrnlmp.exe ( nt!ObpDecrementHandleCount+2a )

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

 

[1977chevy]

I knew I'd forget some things... I have been working on this off and on for a few months now. I did do the memtest overnight a couple of different times with no problems. I also did the CPU test with no errors and I did do furmark, though not for very long because I heard some scary things about it cooking your hardware. No problems or crashes with it, though.

I was never able to identify any cause from the logs, so I'm not surprised there's no obvious probable cause, though I had hoped. I'll try the Driver Verifier.

Thanks for your help!

 

[1977chevy]

I started getting crashes fairly regularly with Drive Verifier running, and then recently got into a state where it crashed on login, so I booted into safe mode and ran verifier again, choosing to delete the settings.

During one early crash, the BSOD indicated CI.dll did something with pageable instead of non-pageable memory (Sorry I don't recall the exact message - not sure if it's in the dmp files). I booted with a win7 cd and replaced CI.dll from it, but that did not seem to help.

I've attacked the new zip file with SF Diagnostic Tool output.

 

[Arc]

There are three driver verifier enabled crash dumps.

Yesterday ..... Symantec/ Norton NIS/ N360 driver

BugCheck A, {476c, 2, 0, fffff800032b5018}

*** WARNING: Unable to verify timestamp for [URL="http://www.carrona.org/drivers/driver.php?id=SYMNETS.SYS"]SYMNETS.SYS[/URL]
*** ERROR: Module load completed but symbols could not be loaded for [URL="http://www.carrona.org/drivers/driver.php?id=SYMNETS.SYS"]SYMNETS.SYS[/URL]
Probably caused by : [URL="http://www.carrona.org/drivers/driver.php?id=SYMNETS.SYS"]SYMNETS.SYS[/URL] ( SYMNETS+5b900 )

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

Description here: Driver Reference Table - SYMNETS.SYS

Today ... the first one .... nothing at all. But giving the hint of memory corruption.

BugCheck A, {fffff6fb4010e5c8, 0, 0, fffff8000329af6b}

[COLOR=Red]Probably caused by : memory_corruption [/COLOR]( nt!MiCompleteProtoPteFault+7b )

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

Though we have noticed plenty of such memory corruptions caused by Symentec. In that case it might not be a physical memory corruption.

Today ... the latest one .... same. Nothing apparently.

BugCheck D1, {0, c, 8, 0}

Probably caused by : ntkrnlmp.exe ( nt!KiPageFault+260 )

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

But a deeper search reveals Symentec as the crasher.

fffff880`027d2850  fffff880`046ac400[COLOR=Red]Unable to load image \??\C:\ProgramData\Norton[/COLOR]\{0C55C096-0F1D-4F28-AAA2-85EF591126E7}\N360_20.1.0.24\Definitions\BASHDefs\20130924.001\BHDrvx64.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for [URL="http://www.carrona.org/drivers/driver.php?id=BHDrvx64.sys"]BHDrvx64.sys[/URL]
*** ERROR: Module load completed but symbols could not be loaded for [URL="http://www.carrona.org/drivers/driver.php?id=BHDrvx64.sys"]BHDrvx64.sys[/URL]
 BHDrvx64+0xa1400

Description here: Driver Reference Table - BHDrvx64.sys

So, the first attempt should be testing how the computer is running minus Symentec.

Uninstall Norton and all Symentec products using Norton Removal tool. Use Microsoft Security Essentials as your antivirus with windows inbuilt firewall, and free MBAM as the on demand scanner.
Download, install and update those, and then run full system scans with both of them, one by one.

Let us know the results.

** And disable Driver Verifier. It is not any more needed at this point of time.

 

[1977chevy]

Just an update. On 10/2 I uninstalled the Comcast Norton, and installed Windows' Virus scanner and Malware Bytes and did scans with each.

My computer continues to crash multiple times each day, but now it never finishes the blue screen (it freezes while counting up, and never restarts, then there is no dump file when I force reboot). This used to be the case for 75% of the crashes or so, but now it's 100%.

 

[Arc]

The problem is if we suggest anything without seeing the crash dumps, it will not be any proper suggestion but will be some guesswork only.

If things are really getting bad, you should go for a clean install, as it will take less time than troubleshooting the issue in this darkness. Moreover, it will almost nullify the chance of a driver caused BSOD.

 

[1977chevy]

Apparently this didn't add my comments when I marked solved. I replaced my power supply with an old, but good one, and did a couple other things I think are likely unrelated (such as switching out a hard drive). Have not had a BSOD since!

Thanks for all your help.

 

[Arc]

Good to know that the computer is running good now