BSOD while gaming

Page 2 of 2 FirstFirst 12

  1. dleslie
    Posts : 12
    Win 7 Home 64 6.1.7600
    Thread Starter
       New #11

    Hi,

    I have uninstalled AVG, using the uninstaller that was linked. I went with MSE instead. I ran memtest 86+ before posting here for three full passes, so I'm going to assume that things are alright in the memory department.

    I set up the driver verifier according to the instructions in the post and, sure enough, the MSI afterburner driver caused a crash on the first reboot. I managed to get into windows normally after another crash with no driver info attached to it. I uninstalled Afterburner and then restarted and so far so good.

    Will this driver verifier continue to run after every restart until I turn it off?

    Thanks for the help again!!!!

    Dave
      My Computer
    Quote Quote

  3. DeanP
    Posts : 2,566
    Win 7 Pro x64 SP1 OS X Snow Leopard 10.6.7
       New #12

    Hello Dave,

    Run at least 7 passes for Memtest (you won't find any errors occurring around 3 or 4 passes).

    As said, uninstall MSI Afterburner - because it is using an old driver, causing issues on some Windows 7 system and Driver Verifier is blaming it.

    What to do when Driver Verifier is on?
    Reboot the system and wait for it to crash to the Blue Screen. Continue to use your system normally, and if you know what causes the crash, do that repeatedly. The objective here is to get the system to crash because Driver Verifier is stressing the drivers out. If it doesn't crash for you, then let it run for at least 36 hours of continuous operation (an estimate on my part).

    Reboot into Windows (after the crash) and turn off Driver Verifier by going back in and selecting "Delete existing settings" on the first page, then locate and zip up the memory dump file and upload it with your next post.
      My Computer
    Quote Quote

  4. dleslie
    Posts : 12
    Win 7 Home 64 6.1.7600
    Thread Starter
       New #13

    Hi,

    After rebooting a crash occurred before Windows could boot up. Here is the dump file.

    Thanks again!

    Dave
      My Computer
    Quote Quote

  6. dleslie
    Posts : 12
    Win 7 Home 64 6.1.7600
    Thread Starter
       New #14

    I should have mentioned that verifier was running at the time of the crash, but, there was no indication of a specific driver at fault at the blue screen.

    Dave
      My Computer
    Quote Quote

  7. DeanP
    Posts : 2,566
    Win 7 Pro x64 SP1 OS X Snow Leopard 10.6.7
       New #15

       Warning
    Before you do anything - turn off Driver Verifier. (type in verifier.exe in Start Search Box and select Delete existing settings)


    Dump blames the driver of your Zotac Graphics card, please do the following...

    - Boot into safe mode with networking
    - Uninstall the Display drivers
    - Use driver sweeper to remove leftover ATI display driver files Guru3D - Driver Sweeper (This step is important)
    - Reboot into safe mode with networking
    - Install the latest drivers ZOTAC - It's time to play! - Downloads | Windows 7 and Vista 64-bit | Graphics Card Drivers
    - Reboot into normal mode
    Code:
    *******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 1000007E, {ffffffffc0000005, fffff80002a69634, fffff880033bc5b8, fffff880033bbe20}

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 : nvlddmkm.sys ( nvlddmkm+92ad0 )

Followup: MachineOwner
---------
      My Computer
    Quote Quote

  8. dleslie
    Posts : 12
    Win 7 Home 64 6.1.7600
    Thread Starter
       New #16

    Hi,

    Seven passes of memtest with no errors. The video drivers have been cleared and reinstalled in safe mode. Fingers crossed.

    Thanks for the help,

    Dave
      My Computer
    Quote Quote

  10. dleslie
    Posts : 12
    Win 7 Home 64 6.1.7600
    Thread Starter
       New #17

    Hi,

    After taking the above measures, I got another crash during startup while using driver verifier.

    Here's the file. Thanks again!

    Dave
      My Computer
    Quote Quote

  11. dleslie
    Posts : 12
    Win 7 Home 64 6.1.7600
    Thread Starter
       New #18

    Hi,

    Things seemed to be running smoothly for a while, until I was playing Starcraft 2 today. I got two bluescreens within 20 minute of each other. I have followed the advise given to me by the generous gentlemen who have responded to the thread. But, here I am, back again.

    If anyone could take some time to peek at these dumps and see what could be causing my problems I would appreciate it. Thanks.

    Dave
      My Computer
    Quote Quote

  12. DeanP
    Posts : 2,566
    Win 7 Pro x64 SP1 OS X Snow Leopard 10.6.7
       New #19

    [warn2]Turn off Driver Verifier. Go to verifier.exe and select "Delete existing settings"[/warn2]

    Dump blames hardware. See this thread: Stop 0x124 - what it means and what to try

    If you are overclocking anything. Stop and return to default values, please.

    Regards...
    Code:
    *******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 124, {0, fffffa80087cc028, be000000, 800400}

Probably caused by : hardware

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

0: 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: fffffa80087cc028, Address of the WHEA_ERROR_RECORD structure.
Arg3: 00000000be000000, High order 32-bits of the MCi_STATUS value.
Arg4: 0000000000800400, Low order 32-bits of the MCi_STATUS value.

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


BUGCHECK_STR:  0x124_GenuineIntel

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

PROCESS_NAME:  System

CURRENT_IRQL:  f

STACK_TEXT:  
fffff800`00ba8a98 fffff800`02ff5903 : 00000000`00000124 00000000`00000000 fffffa80`087cc028 00000000`be000000 : nt!KeBugCheckEx
fffff800`00ba8aa0 fffff800`02b8c5a3 : 00000000`00000001 fffffa80`08016470 00000000`00000000 fffffa80`080164c0 : hal!HalBugCheckSystem+0x1e3
fffff800`00ba8ae0 fffff800`02ff55c8 : 00000000`00000728 fffffa80`08016470 fffff800`00ba8e70 fffff800`00ba8e00 : nt!WheaReportHwError+0x263
fffff800`00ba8b40 fffff800`02ff4f1a : fffffa80`08016470 fffff800`00ba8e70 fffffa80`08016470 00000000`00000000 : hal!HalpMcaReportError+0x4c
fffff800`00ba8c90 fffff800`02ff4dd5 : 00000000`00000004 00000000`00000001 fffff800`00ba8ef0 00000000`00000000 : hal!HalpMceHandler+0x9e
fffff800`00ba8cd0 fffff800`02fe8e88 : fffff800`02bf0e80 fffff800`02bf0e80 00000000`00000000 00000000`00000000 : hal!HalpMceHandlerWithRendezvous+0x55
fffff800`00ba8d00 fffff800`02a74fec : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : hal!HalHandleMcheck+0x40
fffff800`00ba8d30 fffff800`02a74e53 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxMcheckAbort+0x6c
fffff800`00ba8e70 fffff800`02a83dbb : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiMcheckAbort+0x153
fffff800`00b9cca0 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!PoIdle+0xab


STACK_COMMAND:  kb

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: hardware

IMAGE_NAME:  hardware

DEBUG_FLR_IMAGE_TIMESTAMP:  0

FAILURE_BUCKET_ID:  X64_0x124_GenuineIntel_PROCESSOR_MAE

BUCKET_ID:  X64_0x124_GenuineIntel_PROCESSOR_MAE

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

0: 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: fffffa80087cc028, Address of the WHEA_ERROR_RECORD structure.
Arg3: 00000000be000000, High order 32-bits of the MCi_STATUS value.
Arg4: 0000000000800400, Low order 32-bits of the MCi_STATUS value.

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


BUGCHECK_STR:  0x124_GenuineIntel

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

PROCESS_NAME:  System

CURRENT_IRQL:  f

STACK_TEXT:  
fffff800`00ba8a98 fffff800`02ff5903 : 00000000`00000124 00000000`00000000 fffffa80`087cc028 00000000`be000000 : nt!KeBugCheckEx
fffff800`00ba8aa0 fffff800`02b8c5a3 : 00000000`00000001 fffffa80`08016470 00000000`00000000 fffffa80`080164c0 : hal!HalBugCheckSystem+0x1e3
fffff800`00ba8ae0 fffff800`02ff55c8 : 00000000`00000728 fffffa80`08016470 fffff800`00ba8e70 fffff800`00ba8e00 : nt!WheaReportHwError+0x263
fffff800`00ba8b40 fffff800`02ff4f1a : fffffa80`08016470 fffff800`00ba8e70 fffffa80`08016470 00000000`00000000 : hal!HalpMcaReportError+0x4c
fffff800`00ba8c90 fffff800`02ff4dd5 : 00000000`00000004 00000000`00000001 fffff800`00ba8ef0 00000000`00000000 : hal!HalpMceHandler+0x9e
fffff800`00ba8cd0 fffff800`02fe8e88 : fffff800`02bf0e80 fffff800`02bf0e80 00000000`00000000 00000000`00000000 : hal!HalpMceHandlerWithRendezvous+0x55
fffff800`00ba8d00 fffff800`02a74fec : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : hal!HalHandleMcheck+0x40
fffff800`00ba8d30 fffff800`02a74e53 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxMcheckAbort+0x6c
fffff800`00ba8e70 fffff800`02a83dbb : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiMcheckAbort+0x153
fffff800`00b9cca0 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!PoIdle+0xab


STACK_COMMAND:  kb

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: hardware

IMAGE_NAME:  hardware

DEBUG_FLR_IMAGE_TIMESTAMP:  0

FAILURE_BUCKET_ID:  X64_0x124_GenuineIntel_PROCESSOR_MAE

BUCKET_ID:  X64_0x124_GenuineIntel_PROCESSOR_MAE

Followup: MachineOwner
---------
      My Computer
    Quote Quote

 
Page 2 of 2 FirstFirst 12

  Related Discussions
Hi all! About 5 months ago I bought all new parts and assembled a PC for gaming / school work. The goal was to buy parts that are instantly available (sold older PC to a friend and I needed a replacement fast) and the price range was about 1000-1200€ (in Finland). I ended up with the following...
Hi guys, This is my first post in this forum since I have not received any help from elswhere. You guys are my only hope. Okay, so I recently bought two G1 Gaming GTX970 graphics cards. The first driver install went bad by windows using its own drivers, so I got the Display Driver...
Hello Forum, I have build a Gaming PC and i was trying to use the MSI Gaming app. It worked but nowadays when i change the mode it gives me an instant BSOD. i have uploaded the BSOD .zip file as instructed. Thank you for your help, Kind regards, Jan L
So over the past couple of weeks i've been getting alot of BSoD while gaming on my laptop, the most common being failure to reset display drivers. It seems to be a driver problem but I've tried re-installing them and it hasn't had an effect. I wasn't sure how to properly do a fresh install so if...
I dont know why. I recently bought a new computer and it has been doing this since i first got it. I dont know why but hopefully you can help me. :D My Computer Stats: -Intel® Core™ i7-3770K -GIGABYTE GA-Z77X-UD3H Z77 - NVIDIA GeForce GTX 660 Ti 2GB -Corsair Vengeance 8GB -2TB Hard Drive...
Our Sites
Site Links
About 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 19:37.
Find Us