Random BSODs Popping Up

[Nucstorm]

Hello SevenForums,

I got this laptop in May 2012, and about a month ago it started to randomly pull BSODs up on the screen. Some days it won't do it, but then others it will occur. Hopefully you guys can find out what the problem is and I can fix it.


Windows 7 Home Premium 64 bit
6 GB RAM
NVIDIA GeForce GTX 660M
Intel Core i7-3610QM @ 2.30 GHz

Attaching the dump files I have as well. Thanks in advanced for the help!

 

[Nucstorm]

Bump

 

[Nucstorm]

Bump

 

[x BlueRobot]

[COLOR="Red"]BugCheck 109[/COLOR], {a3a039d89f0e65b2, b3b7465ef18ca1c8, fffff88003370640, 3}

Probably caused by : Unknown_Image ( ANALYSIS_INCONCLUSIVE )

Usual causes:  Device driver, Breakpoint set with no debugger attached, Hardware (Memory in particular)

The BSOD descripton indicates that something has corrupted kernel code, this could be due to a corrupted driver or a form of hardware which holding kernel code, for instance RAM which is failing and therefore is causing the data stored to appear corrupted to the operating system.

Follow these steps:

Remove:

Start Menu\Programs\NirSoft RegScanner

Windows 7 doesn't require any programs which make changes to the operating system and registry, these programs tend to cause problems by modifying and deleting files.

Scan for any missing, modified or corrupted protected Windows files with:

• http://www.sevenforums.com/tutorials/1538-sfc-scannow-command-system-file-checker.html

Run Driver Verifier to scan for any corrupted drivers which may be causing problems, this program works by running various stress tests on drivers, in order to produce a BSOD which will locate the driver; run for least 24 hours:

• http://www.sevenforums.com/tutorials/101379-driver-verifier-enable-disable.html

:info: Additional Help - http://www.sevenforums.com/crash-lo...-driver-verifier-identify-issues-drivers.html

Memory:

• http://www.sevenforums.com/tutorials/105647-ram-test-memtest86.html

Run Memtest86+ for least 9-10 passes, and preferably overnight as it can take a while to fully complete.

Test each RAM stick individually, if an error is found then move the same RAM stick into the next DIMM slot and test again, if errors are found for the same RAM stick in every available slot then you have a faulty RAM module. On the other hand, if no errors are found in the next slot or the other slots for the same RAM module, then you have a faulty DIMM slot.

Test each RAM stick and every motherboard DIMM slot available.

 

[Nucstorm]

I ran the Device Verifier, and I got a BSOD within 5-10 minutes. Here is the dump file from that BSOD.

 

[x BlueRobot]

[COLOR="red"]BugCheck D5[/COLOR], {fffff98014028f10, 1, fffff88008c7514a, 0}

*** WARNING: Unable to verify timestamp for HD-Hypervisor-amd64.sys
*** ERROR: Module load completed but symbols could not be loaded for HD-Hypervisor-amd64.sys

Could not read faulting driver name
Probably caused by : [COLOR="Red"]HD-Hypervisor-amd64.sys[/COLOR] ( HD_Hypervisor_amd64+314a )

Usual causes:  Device driver

The driver referenced seems to be causing some issues, and seems to be linked to your BlueStacks program:

Start Menu\Programs\BlueStacks

I would try and find a updated version of the program, or remove the program completely if it is not needed.

Check for any program or driver compatibility issues:

• Windows 7 Upgrade Advisor - Download - Microsoft Windows

:info: More Information - DRT - HD-Hypervisor-amd64.sys

You may disable Driver Verifier now; use the link provided in my first post for instructions.