Windows 7: Blue Screen of Death, occuring fairly often

GHandy · 24 Apr 2012

Hi, I built a PC just over a month ago and last week I had a BSOD but thought nothing of it. Just restarted and everything was fine. But since last night they keep happening. I've been able to boot up fine after but it 'blue screened' shortly after booting up a few times.

Apologies if this isn't entirely correct. Tried to do this right

Computer Information

Windows 7 Home 64bit
Processor: Intel i3 2120
Processor Speed: 3292 MHz
Memory: 8175 MB
Platform: 64 Bit
Graphics Card: Nvidia GTX 550 Ti
Motherboard: Asrock H61M/U3S3

Is Windows 7 . . .
- x86 (32-bit) or x64 ? - 64
- the original installed OS on the system? - Installed after building it
- an OEM or full retail version? - full retail
- OEM = came pre-installed on system
- Full Retail = you purchased it from retailer

- What is the age of system (hardware)? Just over a month...
- What is the age of OS installation (have you re-installed the OS?) same as above, haven't tried reinstalling OS to fix BSOD

Last BSOD was about 20 mins ago, crashed right after I finished a match of league of legends. Other times I was just using google chrome on youtube and reddit. For some further info, a few weeks ago I got 2 random screen fracturing which quickly returned to normal. When they happened asus smart doctor popped up saying that the card wasn't working properly. I've rolled back the drivers for my graphics card and also performed disc check and a memory test (with programmes available on windows) and no problems.

Appreciate any help you guys can give

EDIT: Forgot to mention, I preformed a system health check and everything it seemed to check out (aside from 1 problem I'm aware of)

EDIT 2: 24/04 22:50
I removed one of my ram modules just to test to see if it had any effect. My PC was on for 2 hours and I was doing similar things when it BSOD before and it's been running well. No problems. I rebooted afterwards and tried to recreate what I was doing the last time it BSOD and still nothing (yet anyway). Could the ram be faulty or is it the slot that is ?

I did had a few more BSOD before removing 1 ram stick (one blue screen when I tried to start in safe mode with networking :s It blue screened after loading drivers/etc.) Also perhaps worth mentioning is my PC was quite sluggish after the second BSOD I had (last night) but has returned close to its previous speed since removing one of the two ram modules.

GHandy · 24 Apr 2012

bump

GHandy · 24 Apr 2012

Bump. Please help you if you can. Thank you!

GHandy · 25 Apr 2012

Bump

writhziden · 25 Apr 2012

I had this thread bookmarked to take a look. The more you reply to your own thread with unnecessary responses, the more likely you are to be missed for two reasons:

It appears your thread was already responded to and you are already receiving help.
It may lower you on the priority list for those who are helping who have seen your thread.

First, read 2) of : Forum Rules and info- Please Read!

Problem Devices:

Code:

Communications Port (COM2)	ACPI\PNP0501\2	This device is disabled.

Code:

Loading Dump File [D:\Kingston\BSODDmpFiles\GHandy\Windows_NT6_BSOD_jcgriff2\042412-31309-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*C:\SymCache*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 Personal
Built by: 7601.17790.amd64fre.win7sp1_gdr.120305-1505
Machine Name:
Kernel base = 0xfffff800`02e5e000 PsLoadedModuleList = 0xfffff800`030a2650
Debug session time: Tue Apr 24 07:39:15.736 2012 (UTC - 6:00)
System Uptime: 0 days 0:10:00.000
Loading Kernel Symbols
...............................................................
................................................................
...............................
Loading User Symbols
Loading unloaded module list
.....
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 109, {a3a039d8997dd7e0, b3b7465eebfaa736, fffff80003111010, 1}

*** WARNING: Unable to verify timestamp for win32k.sys
*** ERROR: Module load completed but symbols could not be loaded for win32k.sys
Probably caused by : memory_corruption

Followup: memory_corruption
---------

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

CRITICAL_STRUCTURE_CORRUPTION (109)
This bugcheck is generated when the kernel detects that critical kernel code or
data have been corrupted. There are generally three causes for a corruption:
1) A driver has inadvertently or deliberately modified critical kernel code
 or data. See http://www.microsoft.com/whdc/driver/kernel/64bitPatching.mspx
2) A developer attempted to set a normal kernel breakpoint using a kernel
 debugger that was not attached when the system was booted. Normal breakpoints,
 "bp", can only be set if the debugger is attached at boot time. Hardware
 breakpoints, "ba", can be set at any time.
3) A hardware corruption occurred, e.g. failing RAM holding kernel code or data.
Arguments:
Arg1: a3a039d8997dd7e0, Reserved
Arg2: b3b7465eebfaa736, Reserved
Arg3: fffff80003111010, Failure type dependent information
Arg4: 0000000000000001, Type of corrupted region, can be
	0 : A generic data region
	1 : Modification of a function or .pdata
	2 : A processor IDT
	3 : A processor GDT
	4 : Type 1 process list corruption
	5 : Type 2 process list corruption
	6 : Debug routine modification
	7 : Critical MSR modification

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


BUGCHECK_STR:  0x109

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  CODE_CORRUPTION

PROCESS_NAME:  System

CURRENT_IRQL:  0

LAST_CONTROL_TRANSFER:  from 0000000000000000 to fffff80002edac80

STACK_TEXT:  
fffff880`031c4498 00000000`00000000 : 00000000`00000109 a3a039d8`997dd7e0 b3b7465e`ebfaa736 fffff800`03111010 : nt!KeBugCheckEx


STACK_COMMAND:  kb

CHKIMG_EXTENSION: !chkimg -lo 50 -db !nt
2 errors : !nt (fffff80003111105-fffff80003111595)
fffff80003111100  87  d9  01  00  00 *4c  f7  c5  ff  0f  00  00  0f  84  ac  02 .....L..........
...
fffff80003111590  8d  54  24  21  49 *8f  ce  e8  c4  c1  dd  ff  48  85  c0  0f .T$!I.......H...

MODULE_NAME: memory_corruption

IMAGE_NAME:  memory_corruption

FOLLOWUP_NAME:  memory_corruption

DEBUG_FLR_IMAGE_TIMESTAMP:  0

MEMORY_CORRUPTOR:  STRIDE

FAILURE_BUCKET_ID:  X64_MEMORY_CORRUPTION_STRIDE

BUCKET_ID:  X64_MEMORY_CORRUPTION_STRIDE

Followup: memory_corruption
---------

The above crash indicates memory problems. Could also be due to a driver.

If you are overclocking any hardware, please stop.
Run the boot version of Memtest86+ paying close attention to Parts 2 and 3 of the tutorial. Also, in case Memtest86+ misses anything and comes up with no errors, run the extended version of the Windows Memory Diagnostics Tool for at least five passes. These you may want to run overnight since they take a long time to complete (run them an hour before bed each of the next two nights and check before going to sleep that they are still running).

For Part 3: If You Have Errors: If you swap any memory components, follow these steps for ESD safety:
1. Shut down and turn off your computer.
2. Unplug all power supplies to the computer (AC Power then battery for laptops, AC power for desktops)
3. Hold down the power button for 30 seconds to close the circuit and ensure all power drains from components.
4. Make sure you are grounded by using proper grounding techniques, i.e. work on an anti-static workbench, anti-static desk, or an anti-static pad. Hold something metallic while touching it to the anti-static surface, or use an anti-static wristband to attach to the anti-static material while working.
Once these steps have been followed, it is safe to remove and replace components within your computer.
An underlying driver may be incompatible\conflicting with your system. Run Driver Verifier to find any issues. To run Driver Verifier, do the following:
a. Backup your system and user files
b. Create a system restore point
c. If you do not have a Windows 7 DVD, Create a system repair disc
d. In Windows 7:
- Click the Start Menu
- Type verifier in Search programs and files (do not hit enter)
- Right click verifier and click Run as administrator
- Put a tick in Create custom settings (for code developers) and click next
- Put a tick in Select individual settings from a full list and click next
- Set up the individual settings as in the image and click next
- Put a tick in Select driver names from a list
- Put a tick next to all non-Microsoft drivers.
- Click Finish.
- Restart your computer.
If Windows cannot start in normal mode with driver verifier running, start in safe mode. If it cannot start in safe mode or normal mode, restore the system restore point using System Restore OPTION TWO.

Thanks to zigzag3143 for contributing to the Verifier steps.
If you are unable to start Windows with all drivers being verified or if the blue screen crashes fail to create .dmp files, run them in groups of 5 or 10 until you find a group that causes blue screen crashes and stores the blue screen .dmp files.
The idea with Verifier is to cause the system to crash, so do the things you normally do that cause crashes. After you have a few crashes, upload the crash reports for us to take a look and try to find patterns.

When you are ready to disable Verifier: Start Menu -> All Programs -> Accessories -> Right click Command Prompt -> Run as administrator -> Type the following command and then Enter:
verifier /reset
-> Restart your computer.

Windows 7: Blue Screen of Death, occuring fairly often

Blue Screen of Death, occuring fairly often problems?