Windows 7 Forums
Welcome to Windows 7 Forums. Our forum is dedicated to helping you find support and solutions for any problems regarding your Windows 7 PC be it Dell, HP, Acer, Asus or a custom build. We also provide an extensive Windows 7 tutorial section that covers a wide range of tips and tricks.


Windows 7: Intermittent BSOD, trouble resuming Windows, Difficult to Diagnose


27 Jan 2012   #1

Windows 7 Professional 64 Bit
 
 
Intermittent BSOD, trouble resuming Windows, Difficult to Diagnose

System Spec:
- 64 bit
- I built the machine August 2010, I have not reinstalled the OS since.
- Full Retail Version of Windows 7
-

Hello Everyone,
I have been experiencing problems with this machine since about a month after I built it in August 2011. At first I would get a BSOD just every once in a while. I am at architecture school and I didn't have time to address the issue, so I just kept a diligent written log of every time I noticed it happening. I have included that as an attachment. You'll notice that there was not an obvious trigger - it would not crash as soon as I opened something, or as soon as I tried to use the sound card. It would happen both while I was working in Adobe Illustrator, and when I left my computer idle to go grab a cup of coffee or something like that. I have included all the dump files I have as attachments.
Recently, however, Windows has had trouble resuming. I can't figure out exactly what is happening because it hasn't happened while I was at my computer yet. But, pretty much every time I return to my computer after a 10 minute absence, I come back to a black screen with a blinking white underscore in the top left corner. I think it has something to do with the machine going to sleep and having trouble resuming windows.
Another clue, which I've researched a little bit, is that I think I heard a single beep the other day. Granted, I'm in a studio with 50 other people and there are cellphones, headphones tons of computer and all kinds of noise, but I'm sure enough about what I heard to include it here. The forums I checked suggested this was a problem with the RAM.
Here is a list of the components from the NewEgg invoice:
Motherboard:
13-128-498 MB GIGABYTE|GA-Z68X-UD3H-B3 Z68 R
Videocard:
14-133-273 VGA PNY|VCQFX580-PCIE-PB FX580 RT
Power Supply:
17-341-018 PSU OCZ|OCZ700MXSP 700W RT
Processor:
19-115-071 CPU INTEL|CORE I7 2600 3.4G 8M R
Card Reader:
20-223-103 CARD READ|ROSEWILL RCR-IC001 R
RAM
20-231-424 MEM 4Gx2|G.SKILL F3-10666CL9D-8GBNT
Hard Drive:
22-136-533 HD 1T|WD 7K 64M SATAIII WD1002FAEX
Cooling Unit:
35-118-003 CPU FAN ZALMAN|CNPS9500 AT RTL

My System SpecsSystem Spec
.

27 Jan 2012   #2

Windows 7 Professional 64 Bit
 
 
Forgot System Health Report

See attachment for system health report
My System SpecsSystem Spec
28 Jan 2012   #3

Windows 7 Home Premium 64 Bit
 
 

Code:
[*]
Loading Dump File [K:\BSODDmpFiles\AlexanderTheDan\Windows_NT6_BSOD_jcgriff2\012412-43087-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 (8 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506
Machine Name:
Kernel base = 0xfffff800`02e1a000 PsLoadedModuleList = 0xfffff800`0305f670
Debug session time: Tue Jan 24 14:55:49.340 2012 (GMT-7)
System Uptime: 0 days 6:51:41.072
Loading Kernel Symbols
...............................................................
................................................................
.............................
Loading User Symbols
Loading unloaded module list
............
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 7F, {8, 80050031, 406f8, fffff88004901033}

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 : dxgmms1.sys ( dxgmms1!VidSchDdiNotifyInterruptWorker+ab )

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

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

UNEXPECTED_KERNEL_MODE_TRAP (7f)
This means a trap occurred in kernel mode, and it's a trap of a kind
that the kernel isn't allowed to have/catch (bound trap) or that
is always instant death (double fault).  The first number in the
bugcheck params is the number of the trap (8 = double fault, etc)
Consult an Intel x86 family manual to learn more about what these
traps are. Here is a *portion* of those codes:
If kv shows a taskGate
        use .tss on the part before the colon, then kv.
Else if kv shows a trapframe
        use .trap on that value
Else
        .trap on the appropriate frame will show where the trap was taken
        (on x86, this will be the ebp that goes with the procedure KiTrap)
Endif
kb will then show the corrected stack.
Arguments:
Arg1: 0000000000000008, EXCEPTION_DOUBLE_FAULT
Arg2: 0000000080050031
Arg3: 00000000000406f8
Arg4: fffff88004901033

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


BUGCHECK_STR:  0x7f_8

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

PROCESS_NAME:  System

CURRENT_IRQL:  6

LAST_CONTROL_TRANSFER:  from fffff80002e961e9 to fffff80002e96c40

STACK_TEXT:  
fffff800`04450d28 fffff800`02e961e9 : 00000000`0000007f 00000000`00000008 00000000`80050031 00000000`000406f8 : nt!KeBugCheckEx
fffff800`04450d30 fffff800`02e946b2 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiBugCheckDispatch+0x69
fffff800`04450e70 fffff880`04901033 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiDoubleFaultAbort+0xb2
fffff880`0bb79000 fffff880`04900f76 : 00000000`00000000 00000000`00000000 fffffa80`1001b000 fffffa80`0f7e3000 : dxgmms1!VidSchDdiNotifyInterruptWorker+0xab
fffff880`0bb79050 fffff880`0480813f : fffffa80`0ea39480 00000000`00000000 00000000`00000000 00000000`00000000 : dxgmms1!VidSchDdiNotifyInterrupt+0x9e
fffff880`0bb79080 fffff880`0f13a9e2 : fffff880`0bb79270 fffff880`0bb79270 00000000`00000000 fffffa80`0ed31000 : dxgkrnl!DxgNotifyInterruptCB+0x83
fffff880`0bb790b0 fffff880`0bb79270 : fffff880`0bb79270 00000000`00000000 fffffa80`0ed31000 fffff880`0f13a972 : nvlddmkm+0xce9e2
fffff880`0bb790b8 fffff880`0bb79270 : 00000000`00000000 fffffa80`0ed31000 fffff880`0f13a972 fffffa80`0ed31000 : 0xfffff880`0bb79270
fffff880`0bb790c0 00000000`00000000 : fffffa80`0ed31000 fffff880`0f13a972 fffffa80`0ed31000 00000000`00000000 : 0xfffff880`0bb79270


STACK_COMMAND:  kb

FOLLOWUP_IP: 
dxgmms1!VidSchDdiNotifyInterruptWorker+ab
fffff880`04901033 e8f0020000      call    dxgmms1!VidSchiProcessIsrVSync (fffff880`04901328)

SYMBOL_STACK_INDEX:  3

SYMBOL_NAME:  dxgmms1!VidSchDdiNotifyInterruptWorker+ab

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: dxgmms1

IMAGE_NAME:  dxgmms1.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  4ce799c1

FAILURE_BUCKET_ID:  X64_0x7f_8_dxgmms1!VidSchDdiNotifyInterruptWorker+ab

BUCKET_ID:  X64_0x7f_8_dxgmms1!VidSchDdiNotifyInterruptWorker+ab

Followup: MachineOwner
---------
The problem is due to your graphics card/graphics card driver. These faults are usually hardware related, especially due to memory problems. It may also be that the graphics card or a RAM module is not seated properly. Another possible cause is an underlying driver that is incompatible with Windows.
Thanks to Dave76 for help understanding possible causes.

Your crashes could be a result of the BIOS needing an update, the graphics card drivers needing an update, or your chipset drivers needing an update. Begin with the following steps. Post back after each step and wait for a response from us before proceeding to the next step.
  • If you are overclocking anything, please stop.


  • Install/re-install your latest graphics card drivers. We ask that you re-install if you already have the latest drivers because the drivers on your system may be corrupt. Use the following steps for installing the drivers.
    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


  • Download and install HWiNFO64 Download to check hardware temperatures.


  • 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 Hardware - Stress Test With Prime95 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.


  • 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).


  • 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 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.

Also, when was the last time you blew dust out of your system? 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.
My System SpecsSystem Spec
.


Reply

 Intermittent BSOD, trouble resuming Windows, Difficult to Diagnose




Thread Tools



Similar help and support threads for2: Intermittent BSOD, trouble resuming Windows, Difficult to Diagnose
Thread Forum
BSOD, particularly upon resuming Windows, any help? BSOD Help and Support
trouble resuming from s3 sleep every single time. Performance & Maintenance
Windows crash while resuming from standby window's says it was a BSOD BSOD Help and Support
Very difficult to diagnose BSODs at random intervals. BSOD Help and Support
BSOD diagnose, thanks BSOD Help and Support
Please help diagnose this BSoD: 10d BSOD Help and Support
BSOD Windows 7 x64 when resuming from sleep BSOD Help and Support

Our Sites

Site Links

About Us

Find Us

Windows 7 Forums is an independent web site and has not been authorized, sponsored, or otherwise approved by Microsoft Corporation. "Windows 7" and related materials are trademarks of Microsoft Corp.

Designer Media Ltd

All times are GMT -5. The time now is 05:22 AM.
Twitter Facebook Google+



Windows 7 Forums

Seven Forums Android App Seven Forums IOS App
  

1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33