Random BSoD's

[raisanbran]

I have a random BSoD happens when I game, Idle, the amount of time for the BSoD to occur differs sometimes right after I boot and startup or sometimes it will be an hour or two etc..

I have tried memory test and got 7 passes with no errors, sfc scans/chkdsk, fresh install on windows and drivers but the problem still occurs.

I came to a conclusion and narrowed down the BSoD related to either a driver or my graphics card please look at the dumps and give me insight! (I used driver verifier following sevenforums guide to create the dumps inside the zip)

(My system is non-overclocked all Bios settings are factory default)

 

[Arc]

Uninstall Hotspot Shield.

fffff800`03722a40  fffff880`035dabd0Unable to load image hssdrv6.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for hssdrv6.sys
*** ERROR: Module load completed but symbols could not be loaded for hssdrv6.sys
 hssdrv6+0x14bd0

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.

Killer Network is failing.

fffff800`03721e20  fffff880`0440781aUnable to load image e22w7x64.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for e22w7x64.sys
*** ERROR: Module load completed but symbols could not be loaded for e22w7x64.sys
 e22w7x64+0x781a

Search for driver updates in Killer Gaming :: Support :: Driver Downloads

Intel XHCI driver is failing, too.

fffff800`03722d18  fffff880`045251a4Unable to load image iusb3xhc.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for iusb3xhc.sys
*** ERROR: Module load completed but symbols could not be loaded for iusb3xhc.sys
 iusb3xhc+0x7b1a4

Update drivers from https://downloadcenter.intel.com/default.aspx

SteelSeried engine (recently got I guess?) Is in total failure.

fffff800`03724580  fffff880`043d1c10Unable to load image SteelBus64.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for SteelBus64.sys
*** ERROR: Module load completed but symbols could not be loaded for SteelBus64.sys
 SteelBus64+0x1c10
-------------------------------------------------------------------------------------------
fffff800`03724218  fffff880`05a3a210Unable to load image SAlpham64.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for SAlpham64.sys
*** ERROR: Module load completed but symbols could not be loaded for SAlpham64.sys
 SAlpham64+0x3210

Try not using those keyboard and mouse .... there cannot be any driver updated than that is installed there.

Free up the startup. Windows does not need any other program to auto start with it, but the auto start programs often conflicts and causes various problems including BSODs.

1. Click on the Start button
2. Type “msconfig (without quotes), click the resulting link. It will open the System Configuration window.
3. Select the “Startup” tab.
4. Deselect all items other than the antivirus.
5. Apply > OK
6. Accept then restart.

Let us know the results.

 

[raisanbran]

I have uninstalled Hotspot Shield, installed the Microsoft Security Essentials and scanned with no threats or viruses etc (It is a clean install of windows with a formatted Corsair SSD no real files as of yet except for drivers and a few programs)

Updated the said drivers and still got a BSoD (0xA)

New dump attached...

The types of BSoD I get are inconsistent and the variables keep changing

*Edit
To update the drivers I first uninstalled them completely and installed it as the latest version manually by going to the sites driver downloads & support

 

[Arc]

It is the display driver this time.

fffff880`0664d828  fffff880`05af7541Unable to load image nvlddmkm.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for nvlddmkm.sys
*** ERROR: Module load completed but symbols could not be loaded for nvlddmkm.sys
 nvlddmkm+0xb8541

And the driver is not up-to-date.

fffff880`05a3f000 fffff880`064ea000   nvlddmkm T (no symbols)           
    Loaded symbol image file: nvlddmkm.sys
    Image path: nvlddmkm.sys
    Image name: nvlddmkm.sys
    Timestamp:        Thu Mar 14 12:59:32 2013 (51417C5C)
    CheckSum:         00A90E70
    ImageSize:        00AAB000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4

Install the latest WHQL only.

• Uninstall All nvidia items in Control Panel > Programs and features
  • 3D Vision Control Driver
  • 3D Vision Driver
  • Graphics Driver
  • HD Audio Driver
  • PhysX
  • nvidia Update
  (Are you using nvidia chipset drivers? If so, dont uninstall anything other than those are listed).
• Now follow Drivers - Clean Left over Files after Uninstalling
• Boot normally now. Go to Drivers - Download NVIDIA Drivers, Download 320.49 WHQL. While installing, Select Custom (Advanced) install. In the next page, follow this settings:
  
  

Let us know the results.

 

[raisanbran]

I updated to the latest driver by uninstalling and completely removing it with DriverSweeper and left my computer running for 6 - 7 hours to see if a BSoD reproduces and in that time 3 more dumps showed up.

 

[Skylais]

I updated to the latest driver by uninstalling and completely removing it with DriverSweeper and left my computer running for 6 - 7 hours to see if a BSoD reproduces and in that time 3 more dumps showed up.

Those last ones don't help much, i would try this
Driver verifier: http://www.sevenforums.com/tutorials/101379-driver-verifier-enable-disable.html
and then upload any more dumps so arc can help you further

 

[raisanbran]

After a BSoD while idling for an hour on boot-up the SteelSeries Driver stopped working or crashed and here is the dump.

I have uninstalled the SteelSeries Driver to see if I get a new BSoD these new dumps has the Driver Verifier enabled on all non-microsoft drivers.

 

[raisanbran]

These new dumps are probably more accurate the other ones I posted have the wrong verifier settings but the current ones have the corrected ones.

 

[Arc]

The BSODs are not Driver enabled. But those are worthy.

*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 1A, {8887, fffffa800005f820, fffffa8009b61b40, 500}

Probably caused by : [COLOR=Red]hardware_ram ( ZEROED_PAGE_CORRUPTED )[/COLOR]

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

Either the RAM timings are not right, or those are mismatch, or misfitted or corrupted.

First, If those are overclocked or voltages were increased, put them to stock settings. Re-seat them properly. And 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.

First run it with all the existing/installed RAM modules. If it comes with no error, all is good.

But if it starts showing errors, Stop testing. Errors/red lines means one or more RAM is faulty. But the fault may occur due to a faulty DIMM slot, too, which is a motherboard component. Using memtest86+, you can discriminate between a faulty RAM and a faulty motherboard.

How? Say you have two RAM sticks and two DIMM slots. You obtained errors at the test with all RAM sticks installed. Now, remove all the sticks but one. Test it in all the available slots, one by one. Continue the same procedure for all the available sticks.
How to make the inference that is it a RAM issue or it is a motherboard issue? Suppose you have got the result like that:

test|Slot1|Slot2
RAM1| Error | Error
RAM2|Good|Good

It is a RAM, a bad RAM.

But if you have got a result like that:

test|Slot1|Slot2
RAM1| Error |Good
RAM2| Error |Good

It is a motherboard issue. The particular slot is bad.

 

[raisanbran]

I tested the ram it had 7 passes with no errors, After I re-seated all the cards/cables/ram my system ran fine for around 8 - 9 hours without crashing then all in the same hour I had 3 crashes with BSoD dumps in the attached file with this post.