Solved BSOD under several different situations, see details.

[BinaryZael]

I just put this computer together a few days ago and blew like a grand out of my tax money on it, everything was going dandy till my first of three BSoDs, all under different situations.

I'm running Windows 7 Home Premium 64bit (retail) and there is VERY little installed, no more than WoW, Minecraft and some ancient Blizzard games.

The following events are not as rapid as they seem, they are spread out over a couple days and some hours.

My first BSoD happened during a flash game, at which point two things happened. First I did some research and found somewhere that Adobe flash has caused a BSoD for several people, something to do with hardware acceleration. Second, I decided it was probably a good idea to update my drivers and bios. I did those things and figured all was well.

I then decided to move my Minecraft server from my previous computer to this one, rewrote the batch file and allocated 2GB of ram to it, hopped in and started playing. Not 10 minutes into it I experienced another BSoD. Setting that aside, I decided some WoW might clear my mind and help me think about what's going on here, shortly after I had yet another BSoD. I ran two passes of an extended Physical Memory test which came back with zero errors and threw my hands in the air and decided to seek help.

Here I am.

Attached are both the minidump files collected via Windows_NT6_BSOD_v3.03_jcgriff2_ and the .html from perfmon.

I'm headed to work now, but I'll be back to hopefully check responses in about 10 hours. Thanks.

 

[zigzag3143]

These were related to netio.sys and usually when that happens it is because of your malware app. In your case AVG

I note you have AVG.
AVG can be a contributing cause of BSOD'S .
Please remove and replace with Microsoft Security Essentials AT LEAST TO TEST

Download tools and utilities | AVG Worldwide

Microsoft Security Essentials - Free Antivirus for Windows

 

[BinaryZael]

I'll give that a shot and play stuff over the weekend and try to trigger a BSOD. I've had ancient computers forever and used AVG back when it was new, and since have become partial to it, but if it's going to start doing this business I'l drop it in favor of something else. I'll post back as to whether or not this solves my issue.

 

[BinaryZael]

So I had another BSoD just now, and things were just looking up too. I was playing WoW and dxgmms1.sys seemed to be the culprit this time. After some research, all I could find were older posts about DX10, while I'm running DX11. At the time of Blue Screening, The game was running perfectly smooth, no hang, no lag. Attatched is the updated logs from the recent crash, as well as a .txt of dxdiag, I don't know if it provides any additional useful information, but it's there nonetheless.

 

[zigzag3143]

So I had another BSoD just now, and things were just looking up too. I was playing WoW and dxgmms1.sys seemed to be the culprit this time. After some research, all I could find were older posts about DX10, while I'm running DX11. At the time of Blue Screening, The game was running perfectly smooth, no hang, no lag. Attatched is the updated logs from the recent crash, as well as a .txt of dxdiag, I don't know if it provides any additional useful information, but it's there nonetheless.

Are you by chance overclocking?

 

[BinaryZael]

I am not, I don't have the cooling for it, however my system runs very cool.

 

[BinaryZael]

So, its been a few days and I just experienced another Blue Screen. This time during Minecraft, not doing anything special, just whizzing around aimlessly. I haven't messed with any voltages or BIOS settings in any way, nothing is clocked. The computer does randomly hang for a second once in a while with a buzz from the speakers as if it's about to crash but usually doesn't. Getting more and more concerned at this point where the hanging becomes more frequent and the BSoDs happen at lower and lower load levels. If anyone has any more suggestions I would love to hear them. Thanks in advance, as I'm headed off to work in a few.

 

[BinaryZael]

So it happened again, just now... Playing Skyrim, not even in combat or doing anything that might cause any additional load. I was literally just sitting there for not even a few moments while I got my bearing. The sound buzzed for a moment while the game hung, then BSoD. The stop error was only there for a moment, as usual. I couldn't read the screen fast enough to see anything defining. While the Blue Screens do seem random, the only thing I see linking them is that they are triggered under situations of higher than normal load, meaning that the computer is not idling. I can browse just fine as far as I can tell. I have noted that I no longer get the BSoD related to netio.sys, and Microsoft Security Essentials is installed and running with AVG out if the picture, so that much has worked, but the problem persists.
Attached is the usual.

 

[writhziden]

Possible outdated driver:

gdrv	fffff880`06ea3000	fffff880`06eac000	Thu Mar 12 21:22:29 2009 (49b9d175)	000105ce		gdrv.sys

gdrv.sys
Remove Gigabyte Easy Saver - mobo power utility, it is known to cause crashes when it is out of date on Windows 7.

[list=1]
[*]
Microsoft (R) Windows Debugger Version 6.12.0002.633 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.


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

Symbol search path is: SRV*c:\symbols*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.17640.amd64fre.win7sp1_gdr.110622-1506
Machine Name:
Kernel base = 0xfffff800`03016000 PsLoadedModuleList = 0xfffff800`0325b670
Debug session time: Thu Mar  8 23:41:56.577 2012 (UTC - 6:00)
System Uptime: 0 days 13:34:25.200
Loading Kernel Symbols
...............................................................
................................................................
...................
Loading User Symbols
Loading unloaded module list
.....
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 50, {fffff88008e19c78, 1, fffff80003050ab4, 1}


Could not read faulting driver name
Probably caused by : ntkrnlmp.exe ( nt!KeEnumerateKernelStackSegments+28 )

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

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

PAGE_FAULT_IN_NONPAGED_AREA (50)
Invalid system memory was referenced.  This cannot be protected by try-except,
it must be protected by a Probe.  Typically the address is just plain bad or it
is pointing at freed memory.
Arguments:
Arg1: fffff88008e19c78, memory referenced.
Arg2: 0000000000000001, value 0 = read operation, 1 = write operation.
Arg3: fffff80003050ab4, If non-zero, the instruction address which referenced the bad memory
	address.
Arg4: 0000000000000001, (reserved)

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


Could not read faulting driver name

WRITE_ADDRESS: GetPointerFromAddress: unable to read from fffff800032c5100
 fffff88008e19c78 

FAULTING_IP: 
nt!KeEnumerateKernelStackSegments+28
fffff800`03050ab4 48894508        mov     qword ptr [rbp+8],rax

MM_INTERNAL_CODE:  1

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

BUGCHECK_STR:  0x50

PROCESS_NAME:  System

CURRENT_IRQL:  0

TRAP_FRAME:  fffff8800331d850 -- (.trap 0xfffff8800331d850)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=fffff88008e12000 rbx=0000000000000000 rcx=fffffa80075278e0
rdx=fffff80003050458 rsi=0000000000000000 rdi=0000000000000000
rip=fffff80003050ab4 rsp=fffff8800331d9e0 rbp=fffff88008e19c70
 r8=fffff8800331da90  r9=0000000000000001 r10=0000000000000000
r11=fffff800030a24c0 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei ng nz na pe nc
nt!KeEnumerateKernelStackSegments+0x28:
fffff800`03050ab4 48894508        mov     qword ptr [rbp+8],rax ss:0018:fffff880`08e19c78=fffff88008e12000
Resetting default scope

LAST_CONTROL_TRANSFER:  from fffff80003025b24 to fffff80003092c40

STACK_TEXT:  
fffff880`0331d6e8 fffff800`03025b24 : 00000000`00000050 fffff880`08e19c78 00000000`00000001 fffff880`0331d850 : nt!KeBugCheckEx
fffff880`0331d6f0 fffff800`03090d6e : 00000000`00000001 fffff880`08e19c78 fffff880`0331d800 00000000`00000000 : nt! ?? ::FNODOBFM::`string'+0x461e2
fffff880`0331d850 fffff800`03050ab4 : fffff880`0331da98 00000001`00000001 fffff880`0331da90 fffff880`03782000 : nt!KiPageFault+0x16e
fffff880`0331d9e0 fffff800`03050a5c : 00000000`00000000 00000000`00000001 fffff880`0331db78 fffffa80`075278e0 : nt!KeEnumerateKernelStackSegments+0x28
fffff880`0331da70 fffff800`03050a00 : 00000000`00000000 00000000`000000c8 00000000`00000000 fffff800`030363c3 : nt!MmOutPageKernelStack+0x34
fffff880`0331db50 fffff800`030c72f8 : 00000000`00000000 00000000`00000080 fffffa80`0697b890 fffffa80`0697b800 : nt!KiOutSwapKernelStacks+0x11c
fffff880`0331dbc0 fffff800`0332dfee : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KeSwapProcessOrStack+0x48
fffff880`0331dc00 fffff800`030845e6 : fffff880`02f65180 fffffa80`06a99040 fffff880`02f6ffc0 00000000`00000000 : nt!PspSystemThreadStartup+0x5a
fffff880`0331dc40 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxStartSystemThread+0x16


STACK_COMMAND:  kb

FOLLOWUP_IP: 
nt!KeEnumerateKernelStackSegments+28
fffff800`03050ab4 48894508        mov     qword ptr [rbp+8],rax

SYMBOL_STACK_INDEX:  3

SYMBOL_NAME:  nt!KeEnumerateKernelStackSegments+28

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nt

IMAGE_NAME:  ntkrnlmp.exe

DEBUG_FLR_IMAGE_TIMESTAMP:  4e02aaa3

FAILURE_BUCKET_ID:  X64_0x50_nt!KeEnumerateKernelStackSegments+28

BUCKET_ID:  X64_0x50_nt!KeEnumerateKernelStackSegments+28

Followup: MachineOwner
---------
[*]
Loading Dump File [D:\Kingston\BSODDmpFiles\BinaryZael\Windows_NT6_BSOD_jcgriff2\030712-17908-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*c:\symbols*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.17640.amd64fre.win7sp1_gdr.110622-1506
Machine Name:
Kernel base = 0xfffff800`0300b000 PsLoadedModuleList = 0xfffff800`03250670
Debug session time: Wed Mar  7 10:59:03.680 2012 (UTC - 6:00)
System Uptime: 0 days 0:56:05.288
Loading Kernel Symbols
...............................................................
................................................................
...................
Loading User Symbols
Loading unloaded module list
.....
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 109, {a3a039d8993ef7d0, 0, ea40e4e7deafb4bb, 101}

Probably caused by : Unknown_Image ( ANALYSIS_INCONCLUSIVE )

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

2: 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: a3a039d8993ef7d0, Reserved
Arg2: 0000000000000000, Reserved
Arg3: ea40e4e7deafb4bb, Failure type dependent information
Arg4: 0000000000000101, 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:  VISTA_DRIVER_FAULT

PROCESS_NAME:  System

CURRENT_IRQL:  0

LAST_CONTROL_TRANSFER:  from 0000000000000000 to fffff80003087c40

STACK_TEXT:  
fffff880`031b6498 00000000`00000000 : 00000000`00000109 a3a039d8`993ef7d0 00000000`00000000 ea40e4e7`deafb4bb : nt!KeBugCheckEx


STACK_COMMAND:  kb

SYMBOL_NAME:  ANALYSIS_INCONCLUSIVE

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: Unknown_Module

IMAGE_NAME:  Unknown_Image

DEBUG_FLR_IMAGE_TIMESTAMP:  0

BUCKET_ID:  BAD_STACK

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

[*]
Loading Dump File [D:\Kingston\BSODDmpFiles\BinaryZael\Windows_NT6_BSOD_jcgriff2\030312-24819-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*c:\symbols*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.17640.amd64fre.win7sp1_gdr.110622-1506
Machine Name:
Kernel base = 0xfffff800`02e63000 PsLoadedModuleList = 0xfffff800`030a8670
Debug session time: Sat Mar  3 11:44:21.480 2012 (UTC - 6:00)
System Uptime: 0 days 13:20:02.713
Loading Kernel Symbols
...............................................................
................................................................
..................
Loading User Symbols
Loading unloaded module list
....
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 1000007E, {ffffffffc0000005, fffff88013dd1cee, fffff8800389e568, fffff8800389ddc0}

Probably caused by : dxgmms1.sys ( dxgmms1!VIDMM_GLOBAL::ReferenceAllocationForPreparation+22 )

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

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

SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M (1000007e)
This is a very common bugcheck.  Usually the exception address pinpoints
the driver/function that caused the problem.  Always note this address
as well as the link date of the driver/image that contains this address.
Some common problems are exception code 0x80000003.  This means a hard
coded breakpoint or assertion was hit, but this system was booted
/NODEBUG.  This is not supposed to happen as developers should never have
hardcoded breakpoints in retail code, but ...
If this happens, make sure a debugger gets connected, and the
system is booted /DEBUG.  This will let us see why this breakpoint is
happening.
Arguments:
Arg1: ffffffffc0000005, The exception code that was not handled
Arg2: fffff88013dd1cee, The address that the exception occurred at
Arg3: fffff8800389e568, Exception Record Address
Arg4: fffff8800389ddc0, Context Record Address

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


EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.

FAULTING_IP: 
dxgmms1!VIDMM_GLOBAL::ReferenceAllocationForPreparation+22
fffff880`13dd1cee 488b18          mov     rbx,qword ptr [rax]

EXCEPTION_RECORD:  fffff8800389e568 -- (.exr 0xfffff8800389e568)
ExceptionAddress: fffff88013dd1cee (dxgmms1!VIDMM_GLOBAL::ReferenceAllocationForPreparation+0x0000000000000022)
   ExceptionCode: c0000005 (Access violation)
  ExceptionFlags: 00000000
NumberParameters: 2
   Parameter[0]: 0000000000000000
   Parameter[1]: ffffffffffffffff
Attempt to read from address ffffffffffffffff

CONTEXT:  fffff8800389ddc0 -- (.cxr 0xfffff8800389ddc0)
rax=0f809e3e350e33b7 rbx=0000000000000000 rcx=fffffa8009b51000
rdx=fffffa8007eadd20 rsi=fffffa80080ee7d8 rdi=fffffa8009b51000
rip=fffff88013dd1cee rsp=fffff8800389e7a0 rbp=fffffa800b747790
 r8=fffffa8007afc401  r9=0000000000000000 r10=0000000000000000
r11=00000000000001cd r12=00000000000000d2 r13=0000000000000001
r14=0000000000000000 r15=0000000000000001
iopl=0         nv up ei ng nz na po nc
cs=0010  ss=0000  ds=002b  es=002b  fs=0053  gs=002b             efl=00010286
dxgmms1!VIDMM_GLOBAL::ReferenceAllocationForPreparation+0x22:
fffff880`13dd1cee 488b18          mov     rbx,qword ptr [rax] ds:002b:0f809e3e`350e33b7=????????????????
Resetting default scope

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

PROCESS_NAME:  System

CURRENT_IRQL:  0

ERROR_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.

EXCEPTION_PARAMETER1:  0000000000000000

EXCEPTION_PARAMETER2:  ffffffffffffffff

READ_ADDRESS: GetPointerFromAddress: unable to read from fffff80003112100
 ffffffffffffffff 

FOLLOWUP_IP: 
dxgmms1!VIDMM_GLOBAL::ReferenceAllocationForPreparation+22
fffff880`13dd1cee 488b18          mov     rbx,qword ptr [rax]

BUGCHECK_STR:  0x7E

LAST_CONTROL_TRANSFER:  from fffff88013dceed3 to fffff88013dd1cee

STACK_TEXT:  
fffff880`0389e7a0 fffff880`13dceed3 : 00000000`00000000 fffffa80`080ee7d8 00000000`000000d2 00000000`00000000 : dxgmms1!VIDMM_GLOBAL::ReferenceAllocationForPreparation+0x22
fffff880`0389e7d0 fffff880`13de965d : 00000000`00000000 fffff8a0`0d526c30 fffffa80`00000000 fffffa80`07afc4e0 : dxgmms1!VIDMM_GLOBAL::PrepareDmaBuffer+0x43f
fffff880`0389e9a0 fffff880`13de9398 : fffff800`043a3080 fffff880`13de8d00 fffffa80`00000000 fffffa80`00000000 : dxgmms1!VidSchiSubmitRenderCommand+0x241
fffff880`0389eb90 fffff880`13de8e96 : 00000000`00000000 fffffa80`076b7410 00000000`00000080 fffffa80`09abd010 : dxgmms1!VidSchiSubmitQueueCommand+0x50
fffff880`0389ebc0 fffff800`0317afee : 00000000`04ca85d7 fffffa80`09b508c0 fffffa80`0697b890 fffffa80`09b508c0 : dxgmms1!VidSchiWorkerThread+0xd6
fffff880`0389ec00 fffff800`02ed15e6 : fffff800`03055e80 fffffa80`09b508c0 fffff800`03063cc0 fffff880`01228384 : nt!PspSystemThreadStartup+0x5a
fffff880`0389ec40 00000000`00000000 : fffff880`0389f000 fffff880`03899000 fffff880`0389e540 00000000`00000000 : nt!KxStartSystemThread+0x16


SYMBOL_STACK_INDEX:  0

SYMBOL_NAME:  dxgmms1!VIDMM_GLOBAL::ReferenceAllocationForPreparation+22

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: dxgmms1

IMAGE_NAME:  dxgmms1.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  4ce799c1

STACK_COMMAND:  .cxr 0xfffff8800389ddc0 ; kb

FAILURE_BUCKET_ID:  X64_0x7E_dxgmms1!VIDMM_GLOBAL::ReferenceAllocationForPreparation+22

BUCKET_ID:  X64_0x7E_dxgmms1!VIDMM_GLOBAL::ReferenceAllocationForPreparation+22

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


[/list]

1. Possible causes are Memory problems... Graphics card memory problems... BIOS... Corrupted hard disk file system... Corrupted System Files... Missing Windows Updates... Drivers...
2. A windows system process was terminated unexpectedly. Possible causes are hard disk errors... System file corruption... Viruses... Lack of Windows updates... Drivers...
3. Caused by DirectX/Graphics Card/Graphics Card Drivers

Thanks to Dave76 for help understanding possible causes.



We will start with the common problems first (see bold possible causes). Do the following steps and test by doing your normal routine after each step to see if stability increases (the memory tests you can run concurrently as they will not increase stability unless you are forced to move modules around). Post back your results after each step, and if you get a blue screen crash, upload the files again and await further instructions after we are able to analyze the crash.

If you can do your normal routine for a few weeks without a crash, and your crashes are usually more frequent than that, then the problem is likely solved.

• If you are overclocking any hardware, please stop.
  
  
• Download and install Malwarebytes. Update the software and run it, but do not start the free trial. Run a full scan of the system with Malwarebytes and with Microsoft Security Essentials. Post back your results.
  
  
• Try re-installing DirectX using the Download: DirectX Redist (June 2010) - Microsoft Download Center - Download Details and see how the system responds.
  
  Follow the steps for Diagnosing basic problems with DirectX. To re-install your display card drivers as outlined in the DirectX link, use the following steps.
  
  1. Download the latest drivers for your display card(s)
  2. Click Start Menu
  3. Right Click My Computer/Computer
  4. Click Manage
  5. Click Device Manager from the list on the left
  6. Expand Display adapters
  7. Do the following for each adapter (in case you have multiple display cards)
     • Right click the adapter
     • Click Uninstall (do not click OK in the dialog box that pops up after hitting Uninstall)
     • Put a tick in Delete driver software for this device (if this option is available, otherwise just hit OK) and hit OK
  8. Restart your computer after uninstalling drivers for all display cards
  9. Install the latest driver for the display cards once Windows starts
  
  Alternatively:
  1. Login as an adminstrative user
  2. Download the latest drivers for your display card(s)
  3. Click Start Menu
  4. Click Control Panel
  5. Click Hardware and Sound
  6. Click Device Manager (the last link under Devices and Printers)
  7. Expand Display adapters
  8. Do the following for each adapter (in case you have multiple display cards)
     • Right click the adapter
     • Click Uninstall (do not click OK in the dialog box that pops up after hitting Uninstall)
     • Put a tick in Delete driver software for this device (if this option is available, otherwise just hit OK) and hit OK
  9. Restart your computer after uninstalling drivers for all display cards
  10. Install the latest driver for the display cards once Windows starts
  
  
• Use the |MG| Video Memory Stress Test 1.7.116 Download to test your graphics card memory. Let the memory test run for at least seven passes; the more the better.
  
  
• 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).
  
  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. Run Driver Verifier
  
  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 http://www.sevenforums.com/tutorials/700-system-restore.html 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.

 

[BinaryZael]

Alrighty, that's an impressive response. I didn't honestly thing anyone was working on it, but I had my hopes up, good thing too.

I've removed Gigabyte Easy Saver, wasn't using it anyway.
I'm not overclocking, no problems there.
Downloaded, updated and ran the full scan in Malwarebytes with one return of "Adware.GamePlayLab". Removed that. Log attached.
Re-installed DriectX
Uninstalled, deleted and re-installed my graphics drivers

There was an update, in spite of the fact that I had recently updated. (Old ver.285.66 -> New ver.295.73)
I'm running vmt as we speak and it's currently at pass 3 with no errors, but I will let it run. I've downloaded memtest and plan to run that while I'm at work tomorrow and if necessary I will be swapping RAM, not my favorite activity but I'll do what must be done. I'm not overly concerned about ESD. I've got the static prevention tools and experience.
After the (potentially) coming days of physically minmaxing my RAM I'll download and run Driver Verifier and attempt to collect dumps and post with more information when I have it.
Thank you, all of you involved in this response for the information and detailed instructions. I'll be posting again in a few days.

 

[writhziden]

Adware is not too serious, so probably not a concern with your issue unless it was only happening while browsing, which it appears it was not. It is good that you removed it anyway to rule it out as an issue and also to remove an adware pest. Let us know how the other steps go.

Best of luck!

 

[BinaryZael]

Thanks for the confidence. I didn't think adware or any kind of minor malware was going to give me a blue screen error, but as a measure of good computer health, and to rule out any kind of off the wall chances, I followed your given directions verbatim. I've run more than enough passes with memtest and come to a single obvious conclusion. With varying addresses, a single bit kept returning with the same variation. "00080000"
Now, I have two sticks of 4GB each in my computer. I'm not sure which of them, or if it's even the RAM and not a faulty slot is to blame.
I just had a rough day at work and I'm not about to clear off my work area and get gritty twenty minutes before bed, so I'll handle this another time and attempt to rule out the source.
After this is all said and done, if I still crash, I'll proceed to the last steps and run Verifier.

 

[writhziden]

Viruses can cause crashes; see: http://www.sevenforums.com/crashes-...-randomly-driver-irql-irql-4.html#post1835493

Let us know how the RAM slot swapping goes and whether you are able to determine if it is the RAM, a slot, or both. Best of luck!

 

[BinaryZael]

Sorry for the HUGE delay on an update. A mix of heavy overtime at work, responsibilities to my guild and my Fiance having some serious computer issues of her own had consumed any time I had to play musical RAM.

I did however get some time this weekend, did our shopping early Saturday and didn't have to stay late at work for any reason. I pulled out all but the first stick and ran Memtest with no errors, moved it to the second slot (The slot that I had removed the previous stick from) and ran again with no errors, and placed a third unused stick in the first slot and ran with no errors. each run I allowed for at least a few passes. I didn't have time for a set of seven, however after 3-4 I felt it was safe to move on to a new stick, given I only had a day to do this in.

I followed up by doing EVERYTHING that could cause my computer to BSoD. I played WoW on the highest settings, Skyrim in the same way and flash games for a few hours in Chrome to just go ahead and let it eat up as much of my 8 GB as it could. No BSoDs so far. I'm a little hesitant to click 'solved' just for the fact that it's only been a day and it could just be that my computer is in a good mood and this is a fluke. Should the problem go away by the end of the week I'll solve and close this thread.

 

[writhziden]

Sounds like you did good steps. I agree that you should be hesitant at this time, and I look forward to hearing back when you have had more time to test out the system.

No worries about delayed responses. I will stay subscribed to this thread for some time, and if I remove my subscription, I check through threads that have not been answered and rarely miss my own. Best of luck!

 

[BinaryZael]

Seems good so far. Had a little bit of a hiccup playing flash. Buzzed and locked up for like 3 seconds and recovered, but I'm gonna call it solved. That seemed like an isolated incident. Thanks for the help. Solved

 

[writhziden]

You're welcome. Glad it is solved.