Random BSODs almost daily, Bluescreenview blames ntoskrnl.exe

[jessicajoy13]

Hello. I'm not very tech savvy, so please bare with me while I try to explain my issue.

For about 2-3 weeks now, I've been experience random BSODs. After trying several things, I decided to reset to factory last week. All was well until a few days later, it continued with another BSOD. Ever since then, I've been getting them at random. Sometimes it'll happen 10 minutes after I boot my computer, other times it could take a day or so.

I download Bluescreenview in hopes that I could find what was causing this issue and get it resolved.
Bluescreenview stats that the bug check string is: KMODE_EXCEPTION_NOT_HANDLED
caused by driver: ntoskrnl.exe

There are other crashes where the driver was hal.dll and win32k.sys.

I'm not sure how to post my MiniDump files, I've tried accessing them, even with the Windows Debugging tool, but it says I don't have permission to open the file.

Information about my system :

Windows 7 Home Premium 64 bit
Acer Aspire X3400
4 GB ram (3.75 GB usable)
Processor: AMD Athlon(tm) II X3 435 Processor 2.90 GHz
Service Pack 1 is installed.


Any help, suggestions or assistance would be greatly appreciated.

 

[yowanvista]

http://www.sevenforums.com/crashes-debugging/96879-blue-screen-death-bsod-posting-instructions.html

Seems like hardware errors
Run a RAM test
http://www.sevenforums.com/tutorials/105647-ram-test-memtest86.html

Run Prime 95 to test your CPU. Carefully the instructions in this tutorial: CPU - Stress Test with Prime95. Run 3 separate tests, one on each of the settings (Blend, Small FFTs, Large FFTs). Post back with your results.
Note that this test may overheat the CPU, ensure proper cooling

 

[jessicajoy13]

Hey,

I ran the Memtest86 for 7 passes, took me about 7 hours but no errors were found.

I followed the steps listed and there should be an attached file that contains the System Health Report, including the Dump files.

I haven't done the Stress Tests yet, as I thought I'd give you these files first and see what you thought was the best course of action now that you have more details.

 

[jessicajoy13]

By the way, just thought I'd mention, if you find anything about a USB port being disabled, don't worry. I manually disabled it because it's damaged. I don't need it so I'm fine with leaving it as disabled.

 

[jessicajoy13]

Not sure if I have to bump the thread or not, sorry lol, I'm so new to this.

 

[ickymay]

For about 2-3 weeks now, I've been experience random BSODs.

What did you change do , add , or remove three weeks ago ?

Take look at your reliability history and see what clues you can offer for that time period three weeks ago ?

 

[jessicajoy13]

Update: I'm not sure if this is a related issue, but I'm also getting some random full black / full white screens where i can't do anything except reboot my computer. I made sure my NVIDIA Geforce 9200 is updated properly, and my monitor is plugged in correctly. Not sure what's going on.

 

[jessicajoy13]

Here's a screenshot of my Reliability history. I haven't made any changes other than Windows Updates and Driver Updates, and a few Game installations but they were all legitimate.

I can't go back to the original date it started happening as i reset to factory a couple of weeks ago.

 

[jessicajoy13]

-sigh- Another BSOD just happened. I'll post the new BOSD folder with the new Minidump.

 

[jessicajoy13]

and another one just happened....-sigh-. It said "SYSTEM_SERVICE_EXCEPTION". I'm now on my boyfriends laptop typing because it wouldn't boot up and is now going into start up repair. I'm about ready to throw this computer out lol

 

[jessicajoy13]

I won't post another BSOD folder unless requested, as I'm not sure if it's necessary. the latest BSOD stated in Bluescreenview that it was caused by Driver nvsmu.sys , which I'm pretty sure is the NVIDIA card, which i made sure was updated.

I hope I'm not discouraging anyone from assisting me further, I'm sorry for all of the updates but i thought it'd be easier for you to diagnose the issue if i told you everything that was happening.

 

[writhziden]

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


Loading Dump File [F:\BSODDmpFiles\jessicajoy13\Windows_NT6_BSOD_jcgriff2\020912-14866-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 (3 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506
Machine Name:
Kernel base = 0xfffff800`03212000 PsLoadedModuleList = 0xfffff800`03457670
Debug session time: Thu Feb  9 05:37:10.164 2012 (GMT-7)
System Uptime: 0 days 0:17:04.397
Loading Kernel Symbols
...............................................................
................................................................
............................
Loading User Symbols
Loading unloaded module list
.....
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 124, {0, fffffa8004206028, f602a000, 136}

Probably caused by : hardware

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

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

WHEA_UNCORRECTABLE_ERROR (124)
A fatal hardware error has occurred. Parameter 1 identifies the type of error
source that reported the error. Parameter 2 holds the address of the
WHEA_ERROR_RECORD structure that describes the error conditon.
Arguments:
Arg1: 0000000000000000, Machine Check Exception
Arg2: fffffa8004206028, Address of the WHEA_ERROR_RECORD structure.
Arg3: 00000000f602a000, High order 32-bits of the MCi_STATUS value.
Arg4: 0000000000000136, Low order 32-bits of the MCi_STATUS value.

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


BUGCHECK_STR:  0x124_AuthenticAMD

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

PROCESS_NAME:  dwm.exe

CURRENT_IRQL:  f

STACK_TEXT:  
fffff880`009f0a48 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KeBugCheckEx


STACK_COMMAND:  kb

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: hardware

IMAGE_NAME:  hardware

DEBUG_FLR_IMAGE_TIMESTAMP:  0

FAILURE_BUCKET_ID:  X64_0x124_AuthenticAMD_PROCESSOR_CACHE

BUCKET_ID:  X64_0x124_AuthenticAMD_PROCESSOR_CACHE

Followup: MachineOwner
---------
[*]
Loading Dump File [F:\BSODDmpFiles\jessicajoy13\Windows_NT6_BSOD_jcgriff2\020612-16442-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 (3 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506
Machine Name:
Kernel base = 0xfffff800`03208000 PsLoadedModuleList = 0xfffff800`0344d670
Debug session time: Mon Feb  6 07:29:28.560 2012 (GMT-7)
System Uptime: 0 days 0:06:56.042
Loading Kernel Symbols
...............................................................
................................................................
..........................
Loading User Symbols
Loading unloaded module list
....
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 1E, {ffffffffc000001d, fffff9600016fac1, 0, 0}

Probably caused by : win32k.sys ( win32k!LinkWindow+21 )

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

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

KMODE_EXCEPTION_NOT_HANDLED (1e)
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.
Arguments:
Arg1: ffffffffc000001d, The exception code that was not handled
Arg2: fffff9600016fac1, The address that the exception occurred at
Arg3: 0000000000000000, Parameter 0 of the exception
Arg4: 0000000000000000, Parameter 1 of the exception

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


EXCEPTION_CODE: (NTSTATUS) 0xc000001d - {EXCEPTION}  Illegal Instruction  An attempt was made to execute an illegal instruction.

FAULTING_IP: 
win32k!LinkWindow+21
fffff960`0016fac1 ce              ???

EXCEPTION_PARAMETER1:  0000000000000000

EXCEPTION_PARAMETER2:  0000000000000000

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

BUGCHECK_STR:  0x1E

PROCESS_NAME:  explorer.exe

CURRENT_IRQL:  0

LAST_CONTROL_TRANSFER:  from fffff800032d0588 to fffff80003284c40

FAILED_INSTRUCTION_ADDRESS: 
win32k!LinkWindow+21
fffff960`0016fac1 ce              ???

STACK_TEXT:  
fffff880`0c031c38 fffff800`032d0588 : 00000000`0000001e ffffffff`c000001d fffff960`0016fac1 00000000`00000000 : nt!KeBugCheckEx
fffff880`0c031c40 fffff800`032842c2 : fffff880`0c032418 00000000`00000000 fffff880`0c0324c0 fffff900`c0855250 : nt! ?? ::FNODOBFM::`string'+0x4977d
fffff880`0c0322e0 fffff800`0328241f : fffff880`0c0324c0 baa24011`baa75000 ba9e3811`ba9e3800 b9522717`00000000 : nt!KiExceptionDispatch+0xc2
fffff880`0c0324c0 fffff960`0016fac1 : 00000000`03570000 f900c00c`17280000 fa800607`e000ffff 00000000`0000ffff : nt!KiInvalidOpcodeFault+0x11f
fffff880`0c032656 fa800607`e0000000 : f880070f`b000ffff 00000000`0000ffff f8800f15`6c130000 f880009e`8180ffff : win32k!LinkWindow+0x21
fffff880`0c032696 f880070f`b000ffff : 00000000`0000ffff f8800f15`6c130000 f880009e`8180ffff f8800000`0000ffff : 0xfa800607`e0000000
fffff880`0c03269e 00000000`0000ffff : f8800f15`6c130000 f880009e`8180ffff f8800000`0000ffff 00000000`0357ffff : 0xf880070f`b000ffff
fffff880`0c0326a6 f8800f15`6c130000 : f880009e`8180ffff f8800000`0000ffff 00000000`0357ffff 00000000`00000000 : 0xffff
fffff880`0c0326ae f880009e`8180ffff : f8800000`0000ffff 00000000`0357ffff 00000000`00000000 00000000`00000000 : 0xf8800f15`6c130000
fffff880`0c0326b6 f8800000`0000ffff : 00000000`0357ffff 00000000`00000000 00000000`00000000 f900c00c`17280000 : 0xf880009e`8180ffff
fffff880`0c0326be 00000000`0357ffff : 00000000`00000000 00000000`00000000 f900c00c`17280000 00000000`0000ffff : 0xf8800000`0000ffff
fffff880`0c0326c6 00000000`00000000 : 00000000`00000000 f900c00c`17280000 00000000`0000ffff f8800c03`29900000 : 0x357ffff


STACK_COMMAND:  kb

FOLLOWUP_IP: 
win32k!LinkWindow+21
fffff960`0016fac1 ce              ???

SYMBOL_STACK_INDEX:  4

SYMBOL_NAME:  win32k!LinkWindow+21

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: win32k

IMAGE_NAME:  win32k.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  4ecdcd5a

FAILURE_BUCKET_ID:  X64_0x1E_BAD_IP_win32k!LinkWindow+21

BUCKET_ID:  X64_0x1E_BAD_IP_win32k!LinkWindow+21

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

[*]
Loading Dump File [F:\BSODDmpFiles\jessicajoy13\Windows_NT6_BSOD_jcgriff2\013112-27565-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 (3 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506
Machine Name:
Kernel base = 0xfffff800`03253000 PsLoadedModuleList = 0xfffff800`03498670
Debug session time: Tue Jan 31 10:05:07.595 2012 (GMT-7)
System Uptime: 1 days 13:31:45.078
Loading Kernel Symbols
...............................................................
................................................................
...............................
Loading User Symbols
Loading unloaded module list
...........
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 1E, {0, 0, 0, 0}

Unable to load image \SystemRoot\system32\DRIVERS\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
Probably caused by : hardware ( dxgmms1!VidSchDdiNotifyDpcWorker+f5 )

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

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

KMODE_EXCEPTION_NOT_HANDLED (1e)
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.
Arguments:
Arg1: 0000000000000000, The exception code that was not handled
Arg2: 0000000000000000, The address that the exception occurred at
Arg3: 0000000000000000, Parameter 0 of the exception
Arg4: 0000000000000000, Parameter 1 of the exception

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


EXCEPTION_CODE: (Win32) 0 (0) - The operation completed successfully.

FAULTING_IP: 
+0
00000000`00000000 ??              ???

EXCEPTION_PARAMETER1:  0000000000000000

EXCEPTION_PARAMETER2:  0000000000000000

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

BUGCHECK_STR:  0x1E

PROCESS_NAME:  System

CURRENT_IRQL:  2

EXCEPTION_RECORD:  fffff8800318b748 -- (.exr 0xfffff8800318b748)
ExceptionAddress: fffff8800ffa5d5d (dxgmms1!VidSchDdiNotifyDpcWorker+0x00000000000000f5)
   ExceptionCode: c0000005 (Access violation)
  ExceptionFlags: 00000000
NumberParameters: 2
   Parameter[0]: 0000000000000000
   Parameter[1]: ffffffffffffffff
Attempt to read from address ffffffffffffffff

TRAP_FRAME:  fffff8800318b7f0 -- (.trap 0xfffff8800318b7f0)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=fffffa8006765410 rbx=0000000000000000 rcx=0000000000000000
rdx=0000000000000000 rsi=0000000000000000 rdi=0000000000000000
rip=fffff8800ffa5d5d rsp=fffff8800318b980 rbp=fffffa8006764000
 r8=fffffa8006765420  r9=0000000000000000 r10=fffffa80066887d0
r11=0000000000000002 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei pl zr na po nc
dxgmms1!VidSchDdiNotifyDpcWorker+0xf5:
fffff880`0ffa5d5d 4a0fb194e5a0050000 cmpxchg qword ptr [rbp+r12*8+5A0h],rdx ss:0018:fffffa80`067645a0=????????????????
Resetting default scope

MISALIGNED_IP: 
dxgmms1!VidSchDdiNotifyDpcWorker+f5
fffff880`0ffa5d5d 4a0fb194e5a0050000 cmpxchg qword ptr [rbp+r12*8+5A0h],rdx

LAST_CONTROL_TRANSFER:  from fffff800032c75fe to fffff800032cfc10

STACK_TEXT:  
fffff880`0318a828 fffff800`032c75fe : fffffa80`0392f9b0 00000000`00000000 fffff880`0318afa0 fffff800`032fb830 : nt!KeBugCheck
fffff880`0318a830 fffff800`032fb4fd : fffff800`034d971c fffff800`03416c30 fffff800`03253000 fffff880`0318b748 : nt!KiKernelCalloutExceptionHandler+0xe
fffff880`0318a860 fffff800`032fa2d5 : fffff800`0341a0fc fffff880`0318a8d8 fffff880`0318b748 fffff800`03253000 : nt!RtlpExecuteHandlerForException+0xd
fffff880`0318a890 fffff800`0330b361 : fffff880`0318b748 fffff880`0318afa0 fffff880`00000000 fffffa80`00000004 : nt!RtlDispatchException+0x415
fffff880`0318af70 fffff800`032cf2c2 : fffff880`0318b748 fffffa80`06765910 fffff880`0318b7f0 fffffa80`06688010 : nt!KiDispatchException+0x135
fffff880`0318b610 fffff800`032cdbca : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiExceptionDispatch+0xc2
fffff880`0318b7f0 fffff880`0ffa5d5d : 00000000`00000000 00000000`001b4dba fffffa80`05c1b000 00000000`00000000 : nt!KiGeneralProtectionFault+0x10a
fffff880`0318b980 fffff880`0ffa5c4c : 00000000`00000000 fffffa80`06688010 00000000`00000000 00000000`00000000 : dxgmms1!VidSchDdiNotifyDpcWorker+0xf5
fffff880`0318b9d0 fffff880`0feac1cf : fffffa80`04dd9040 fffffa80`05025000 00000000`00000022 00000000`00000000 : dxgmms1!VidSchDdiNotifyDpc+0x94
fffff880`0318ba20 fffff880`0f308e90 : fffffa80`05025000 fffffa80`05025000 00000000`00000000 00000000`00000000 : dxgkrnl!DxgNotifyDpcCB+0x77
fffff880`0318ba50 fffffa80`05025000 : fffffa80`05025000 00000000`00000000 00000000`00000000 fffff880`0f308e23 : nvlddmkm+0xdbe90
fffff880`0318ba58 fffffa80`05025000 : 00000000`00000000 00000000`00000000 fffff880`0f308e23 fffffa80`05025000 : 0xfffffa80`05025000
fffff880`0318ba60 00000000`00000000 : 00000000`00000000 fffff880`0f308e23 fffffa80`05025000 00000000`00000000 : 0xfffffa80`05025000


STACK_COMMAND:  kb

FOLLOWUP_IP: 
dxgmms1!VidSchDdiNotifyDpcWorker+f5
fffff880`0ffa5d5d 4a0fb194e5a0050000 cmpxchg qword ptr [rbp+r12*8+5A0h],rdx

SYMBOL_STACK_INDEX:  7

SYMBOL_NAME:  dxgmms1!VidSchDdiNotifyDpcWorker+f5

FOLLOWUP_NAME:  MachineOwner

IMAGE_NAME:  hardware

DEBUG_FLR_IMAGE_TIMESTAMP:  0

MODULE_NAME: hardware

FAILURE_BUCKET_ID:  X64_IP_MISALIGNED_dxgmms1.sys

BUCKET_ID:  X64_IP_MISALIGNED_dxgmms1.sys

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


[/list]

1. Hardware stop. Possible causes are Hardware... Overheating... Bad hard disk sectors... BIOS... Drivers...
2. Possible causes are Memory problems... Viruses... Corrupted hard disk file system... Corrupted System Files... Lack of Windows updates... Drivers...
   Thanks to JMH for helping with my understanding of this crash.
3. Caused by DirectX, the display card, or the display card drivers. Other possible causes can be found in 2.

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 after each 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 are overclocking any hardware, please stop.
  
  
  
• http://www.sevenforums.com/crash-lockup-debug-how/35349-stop-0x124-what-means-what-try.html Many of the steps in that thread have been included below for convenience and specificity. I still recommend reading through that thread for useful steps that are not included below. Steps 2), 8), and 9) in particular (part of step 8 is included below).
  
  
  
• Check for and install all BIOS updates and driver updates for your computer from Acer Support: Downloads & Support Documents - Desktop / Aspire / Aspire X3400
  
  
  
• 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.
  
  
  
• Run Disk Check with both boxes checked for all HDDs and with Automatically fix file system errors checked for all SSDs. Post back your logs for the checks after finding them using http://www.sevenforums.com/tutorials/96938-check-disk-chkdsk-read-event-viewer-log.html
  
  
  
• To remove dust, follow the following general procedure. If you have a desktop bought from Dell, HP, Sony, Lenovo, etc. make sure removing the desktop casing will not void your warranty first. Call the company if you are still under warranty and ask if it is okay to remove the casing and blow dust out. The procedure described is fine for laptops; just make sure no stickers are on panels saying if you remove the panel it will void the warranty.
  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. Remove the casing for a desktop, or remove any screwed on panels and disc drives for laptops.
  5. Blow out the dust inside by using a can of compressed air or a low pressure compressor. You will want to put the computer on a desk or table so you can maintain the can in an upright position if using a can of air. Blow into all crevices on the motherboard, heat sinks, cards, modules, etc. for a desktop. Blow into vents, opened panels, disc drive areas, USB ports, and the keyboard if it is a laptop. You may also want to blow inside the disc drive by replacing the drive to the laptop, starting the computer, opening the drive, and then turning off the computer and removing all power as described above including the 30 second power button step. For a desktop, you may also want to blow inside the disc drive by starting the computer, opening the drive, and then turning off the computer and removing all power as described above including the 30 second power button step.
  6. Replace casing for the desktop. Replace panels and disc drive (if you have not already done so) for the laptop.
  7. Plug power supplies in. AC adapter for the desktop. Battery and then AC Adapter for the laptop.
  8. Start the computer and see if performance is better.
  
  
  
• Download and install the appropriate version of HWINFO: HWiNFO32 for 32-bit Windows 7 or HWiNFO64 for 64-bit Windows 7 to check hardware temperatures by running in sensor-only mode. Start logging the temperature through sensor-only mode when the computer first starts, and let it run during stress or until a crash occurs.
  
  Save the CSV file in a place you will remember, and then compress the CSV file to a zip file and upload to here for us to analyze by following the steps in http://www.sevenforums.com/tutorials/9733-screenshots-files-upload-post-seven-forums.html.
  
  
  
• Use FurMark: VGA Stress Test, Graphics Card and GPU Stability Test, Burn-in Test, OpenGL Benchmark and GPU Temperature | oZone3D.Net to test the graphics card GPU. Then use the |MG| Video Memory Stress Test 1.7.116 Download to test your graphics card memory.
  
  
  
• Run http://www.sevenforums.com/tutorials/100352-hardware-stress-test-prime95.html to determine any hardware problems. Run all three tests for a few hours each. If you get errors, stop the test and post back here.
  
  
  
• Install all Windows Updates.
  
  
  
• 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
  
  
  
• 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.​