Jump to content


 


Register a free account to unlock additional features at BleepingComputer.com
Welcome to BleepingComputer, a free community where people like yourself come together to discuss and learn how to use their computers. Using the site is easy and fun. As a guest, you can browse and view the various discussions in the forums, but can not create a new topic or reply to an existing one unless you are logged in. Other benefits of registering an account are subscribing to topics and forums, creating a blog, and having no ads shown anywhere on the site.


Click here to Register a free account now! or read our Welcome Guide to learn how to use this site.

Photo

Win 7 x64 Stop Error


  • Please log in to reply
29 replies to this topic

#1 Snelk

Snelk

  • Members
  • 21 posts
  • OFFLINE
  •  
  • Local time:10:15 PM

Posted 25 July 2013 - 08:11 PM

About a week ago I started experiencing the exact same stop error intermittently and at random intervals (it has happened four times now, once a day for the first three days, but then no error at all for three days). 

 

I have tried checking my RAM using memtest 86+, which found no issues.  I have also tried testing my video RAM using a program called OCCT, also with no error.  I will be running a disc check, and will update this post accordingly.

 

At the time the error begin appearing, I had not installed any new hardware for quite some time, and the last software was installed about a week prior. 

 

I have contacted my hardware manufacturer and they immediately recommended that I do a clean install.  I would rather not do this for obvious reasons, so if anyone can help me it would be most appreciated. 

 

My system specs (mostly from dxdiag) as well as the contents of the stop error mini-dump will follow.

 

Edit: chkdsk found no issues on my primary drive.  Also, I forgot to mention it but as far as I can tell all my drivers are up to date.

------------------
System Information
------------------
Time of this report: 7/25/2013, 18:45:39
Operating System: Windows 7 Professional 64-bit (6.1, Build 7601) Service Pack 1 (7601.win7sp1_gdr.130318-1533)
Language: English (Regional Setting: English)
System Manufacturer: ASUSTeK Computer Inc.
System Model: G74Sx
BIOS: BIOS Date: 08/15/11 10:49:00 Ver: 04.06.03
Processor: Intel® Core™ i7-2630QM CPU @ 2.00GHz (8 CPUs), ~2.0GHz

Storage: Intel SSDSA2CW160G3
Memory: 16384MB RAM
Available OS Memory: 16362MB RAM
Page File: 5854MB used, 11304MB available
Windows Dir: C:\Windows
DirectX Version: DirectX 11
DX Setup Parameters: Not found
User DPI Setting: Using System DPI
System DPI Setting: 96 DPI (100 percent)
DWM DPI Scaling: Disabled
DxDiag Version: 6.01.7601.17514 64bit Unicode

 

Microsoft ® Windows Debugger Version 6.2.9200.20512 AMD64
Copyright © Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Windows\Minidump\072113-11856-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.18113.amd64fre.win7sp1_gdr.130318-1533
Machine Name:
Kernel base = 0xfffff800`03804000 PsLoadedModuleList = 0xfffff800`03a47670
Debug session time: Sun Jul 21 15:37:28.121 2013 (UTC - 6:00)
System Uptime: 1 days 5:19:01.074
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, fffff88004b6d344}

*** 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!VidSchiProcessIsrVSync+10 )

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: fffff88004b6d344

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


BUGCHECK_STR:  0x7f_8

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT

PROCESS_NAME:  System

CURRENT_IRQL:  a

LAST_CONTROL_TRANSFER:  from fffff800038791a9 to fffff80003879c00

STACK_TEXT:  
fffff800`00ba4d28 fffff800`038791a9 : 00000000`0000007f 00000000`00000008 00000000`80050031 00000000`000406f8 : nt!KeBugCheckEx
fffff800`00ba4d30 fffff800`03877672 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiBugCheckDispatch+0x69
fffff800`00ba4e70 fffff880`04b6d344 : fffff880`139ef290 fffff880`04b6d044 00000000`00673b62 00000000`00000000 : nt!KiDoubleFaultAbort+0xb2
fffff880`139ef000 fffff880`04b6d044 : 00000000`00673b62 00000000`00000000 00000000`028a0000 c1d00000`3fff64bf : dxgmms1!VidSchiProcessIsrVSync+0x10
fffff880`139ef010 fffff880`04b6cf82 : 3c59ad30`3ecc422a 3ace860a`3b13aa41 fffffa80`12ba9000 fffffa80`0fc1ed60 : dxgmms1!VidSchDdiNotifyInterruptWorker+0xb0
fffff880`139ef060 fffff880`04a7413f : fffffa80`0fbbe040 00000000`00000000 00000000`00000000 00000000`00000000 : dxgmms1!VidSchDdiNotifyInterrupt+0x9e
fffff880`139ef090 fffff880`0598d02a : fffff880`139ef290 fffff880`139ef290 fffff880`139ef140 fffffa80`0fc1e000 : dxgkrnl!DxgNotifyInterruptCB+0x83
fffff880`139ef0c0 fffff880`139ef290 : fffff880`139ef290 fffff880`139ef140 fffffa80`0fc1e000 fffff880`0598cfbd : nvlddmkm+0xb902a
fffff880`139ef0c8 fffff880`139ef290 : fffff880`139ef140 fffffa80`0fc1e000 fffff880`0598cfbd fffffa80`0fc1e000 : 0xfffff880`139ef290
fffff880`139ef0d0 fffff880`139ef140 : fffffa80`0fc1e000 fffff880`0598cfbd fffffa80`0fc1e000 00000000`00000000 : 0xfffff880`139ef290
fffff880`139ef0d8 fffffa80`0fc1e000 : fffff880`0598cfbd fffffa80`0fc1e000 00000000`00000000 00000000`00000000 : 0xfffff880`139ef140
fffff880`139ef0e0 fffff880`0598cfbd : fffffa80`0fc1e000 00000000`00000000 00000000`00000000 00000000`00000000 : 0xfffffa80`0fc1e000
fffff880`139ef0e8 fffffa80`0fc1e000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nvlddmkm+0xb8fbd
fffff880`139ef0f0 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 fffffa80`0fbbe040 : 0xfffffa80`0fc1e000


STACK_COMMAND:  kb

FOLLOWUP_IP:
dxgmms1!VidSchiProcessIsrVSync+10
fffff880`04b6d344 57              push    rdi

SYMBOL_STACK_INDEX:  3

SYMBOL_NAME:  dxgmms1!VidSchiProcessIsrVSync+10

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: dxgmms1

IMAGE_NAME:  dxgmms1.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  5164dc13

FAILURE_BUCKET_ID:  X64_0x7f_8_dxgmms1!VidSchiProcessIsrVSync+10

BUCKET_ID:  X64_0x7f_8_dxgmms1!VidSchiProcessIsrVSync+10

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


Edited by Snelk, 25 July 2013 - 08:57 PM.


BC AdBot (Login to Remove)

 


#2 hamluis

hamluis

    Moderator


  • Moderator
  • 56,295 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:Killeen, TX
  • Local time:11:15 PM

Posted 26 July 2013 - 07:14 AM

First thing I would try...uninstall the graphics drivers, then reinstall same.

 

You might want to read http://www.sevenforums.com/bsod-help-support/211855-bsod-dxgmms1-sys.html .

 

Louis

 



#3 Snelk

Snelk
  • Topic Starter

  • Members
  • 21 posts
  • OFFLINE
  •  
  • Local time:10:15 PM

Posted 26 July 2013 - 11:06 AM

Alright

 

First thing I would try...uninstall the graphics drivers, then reinstall same.

 

You might want to read http://www.sevenforums.com/bsod-help-support/211855-bsod-dxgmms1-sys.html .

 

Louis

 

Alright, I'll give it a shot.  Given the amount of time between the errors it might be a while before I can be sure if it worked or not.



#4 hamluis

hamluis

    Moderator


  • Moderator
  • 56,295 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:Killeen, TX
  • Local time:11:15 PM

Posted 26 July 2013 - 12:40 PM

Well...someone will be around to try to help...if you post :).

 

Louis



#5 Snelk

Snelk
  • Topic Starter

  • Members
  • 21 posts
  • OFFLINE
  •  
  • Local time:10:15 PM

Posted 26 July 2013 - 10:04 PM

Alright, so I removed and reinstalled my graphics driver about ten hours ago, I just had another stop error occur, but this one was different.

 

For one thing I had no idea it was a stop error at first because the computer just froze for a few seconds and then the screen went black.  I was forced to do a hard shutdown and when I rebooted there was an entry in the event viewer:

     "The computer has rebooted from a bugcheck.  The bugcheck was: 0x00000116 (0xfffffa800cf5a4e0, 0xfffff88005a21e30, 0x0000000000000000, 0x000000000000000d). A dump was saved in: C:\Windows\Minidump\072613-14258-01.dmp. Report Id: 072613-14258-01."

 

At the time of the error I wasn't doing anything that would be considrered graphically "strenuous" (ie. browsing/word processing). 

 

The following is the contents of the minidump:

Microsoft ® Windows Debugger Version 6.2.9200.20512 AMD64
Copyright © Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Windows\Minidump\072613-14258-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.18113.amd64fre.win7sp1_gdr.130318-1533
Machine Name:
Kernel base = 0xfffff800`0381d000 PsLoadedModuleList = 0xfffff800`03a60670
Debug session time: Fri Jul 26 20:47:06.829 2013 (UTC - 6:00)
System Uptime: 0 days 9:49:26.782
Loading Kernel Symbols
...............................................................
................................................................
................................................................
.........
Loading User Symbols
Loading unloaded module list
..............
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 116, {fffffa800cf5a4e0, fffff88005a21e30, 0, d}

Unable to load image 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+13be30 )

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

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

VIDEO_TDR_FAILURE (116)
Attempt to reset the display driver and recover from timeout failed.
Arguments:
Arg1: fffffa800cf5a4e0, Optional pointer to internal TDR recovery context (TDR_RECOVERY_CONTEXT).
Arg2: fffff88005a21e30, The pointer into responsible device driver module (e.g. owner tag).
Arg3: 0000000000000000, Optional error code (NTSTATUS) of the last failed operation.
Arg4: 000000000000000d, Optional internal context dependent data.

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


FAULTING_IP:
nvlddmkm+13be30
fffff880`05a21e30 ??              ???

DEFAULT_BUCKET_ID:  GRAPHICS_DRIVER_TDR_FAULT

CUSTOMER_CRASH_COUNT:  1

BUGCHECK_STR:  0x116

PROCESS_NAME:  System

CURRENT_IRQL:  0

STACK_TEXT:  
fffff880`097c9888 fffff880`04afa054 : 00000000`00000116 fffffa80`0cf5a4e0 fffff880`05a21e30 00000000`00000000 : nt!KeBugCheckEx
fffff880`097c9890 fffff880`04af9ddb : fffff880`05a21e30 fffffa80`0cf5a4e0 00000000`00000000 fffffa80`12bf9010 : dxgkrnl!TdrBugcheckOnTimeout+0xec
fffff880`097c98d0 fffff880`04ba0f13 : fffffa80`0cf5a4e0 00000000`00000000 00000000`00000000 fffffa80`12bf9010 : dxgkrnl!TdrIsRecoveryRequired+0x21f
fffff880`097c9900 fffff880`04bcad50 : fffffa80`00000000 00000000`00229729 00000000`00000000 00000000`00000002 : dxgmms1!VidSchiReportHwHang+0x40b
fffff880`097c99e0 fffff880`04bc9437 : 00000000`00000102 00000000`00000000 00000000`00229729 00000000`00000000 : dxgmms1!VidSchiCheckHwProgress+0xd0
fffff880`097c9a10 fffff880`04b9c2d2 : ffffffff`ff676980 fffffa80`12bf9010 00000000`00000000 00000000`00000000 : dxgmms1!VidSchiWaitForSchedulerEvents+0x1fb
fffff880`097c9ab0 fffff880`04bc8ff6 : 00000000`00000000 fffffa80`17528010 00000000`00000080 fffffa80`12bf9010 : dxgmms1!VidSchiScheduleCommandToRun+0x1da
fffff880`097c9bc0 fffff800`03b30ede : 00000000`fffffc32 fffffa80`12c051e0 fffffa80`0c7961d0 fffffa80`12c051e0 : dxgmms1!VidSchiWorkerThread+0xba
fffff880`097c9c00 fffff800`03883906 : fffff800`03a0de80 fffffa80`12c051e0 fffff800`03a1bcc0 00000000`00000000 : nt!PspSystemThreadStartup+0x5a
fffff880`097c9c40 00000000`00000000 : fffff880`097ca000 fffff880`097c4000 fffff880`065aed70 00000000`00000000 : nt!KiStartSystemThread+0x16


STACK_COMMAND:  .bugcheck ; kb

FOLLOWUP_IP:
nvlddmkm+13be30
fffff880`05a21e30 ??              ???

SYMBOL_NAME:  nvlddmkm+13be30

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nvlddmkm

IMAGE_NAME:  nvlddmkm.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  51c41788

FAILURE_BUCKET_ID:  X64_0x116_IMAGE_nvlddmkm.sys

BUCKET_ID:  X64_0x116_IMAGE_nvlddmkm.sys

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



#6 Anshad Edavana

Anshad Edavana

  • Members
  • 2,805 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:India
  • Local time:09:45 AM

Posted 27 July 2013 - 09:27 AM

Hi

 

Please follow the below steps to collect the necessary data required to analyze the reason behind the crash.

 

:step1: Upload the crash dumps for analysis
 
Open C:\Windows\Minidump folder. Copy and  zip the entire contents of that folder and upload to any free file hosting site of your choice. You may have to disable UAC to copy them.
 
   Example file hosting sites :
 
 
 
 
Post the download link to the dumps in next reply.
 
 
:step2: A Speccy snapshot of your system
 
  Generate a report about your system using Speccy by reading the guide below. 
 
 
 Post the web link displayed by Speccy in next reply.
 
:step3: A Minitoolbox log
 
  Download Minitoolbox from the below link.
 
 
  Run the tool and only select the following tick boxes.
 
    -List last 10 Event viewer errors
    -List installed programs
    -List devices
    -List users, partition and memory size
 
Now click "Go" and post the output in next reply  (or upload the result.txt with dump files)

Edited by Anshad Edavana, 27 July 2013 - 09:28 AM.


#7 Snelk

Snelk
  • Topic Starter

  • Members
  • 21 posts
  • OFFLINE
  •  
  • Local time:10:15 PM

Posted 27 July 2013 - 09:53 PM

Crash dumps & minitoolbox results: here (there were more, but my computer apears to have deleted them, attempts to recover them were unsuccessful, it looks like where ever they were on the drive was overwritten.)

 

Specy: here



#8 Anshad Edavana

Anshad Edavana

  • Members
  • 2,805 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:India
  • Local time:09:45 AM

Posted 27 July 2013 - 10:11 PM

Hi

 

Thanks for providing the requested info. I will keep you posted after analyzing the dumps and logs. 



#9 Snelk

Snelk
  • Topic Starter

  • Members
  • 21 posts
  • OFFLINE
  •  
  • Local time:10:15 PM

Posted 27 July 2013 - 11:18 PM

Hi

 

Thanks for providing the requested info. I will keep you posted after analyzing the dumps and logs. 

 

Alright, thanks for the help ^^.



#10 Anshad Edavana

Anshad Edavana

  • Members
  • 2,805 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:India
  • Local time:09:45 AM

Posted 28 July 2013 - 04:45 AM

Hi

 

You are getting video related crashes.


VIDEO_TDR_FAILURE (116)
Attempt to reset the display driver and recover from timeout failed.
Arguments:
Arg1: fffffa800cf5a4e0, Optional pointer to internal TDR recovery context (TDR_RECOVERY_CONTEXT).
Arg2: fffff88005a21e30, The pointer into responsible device driver module (e.g. owner tag).
Arg3: 0000000000000000, Optional error code (NTSTATUS) of the last failed operation.
Arg4: 000000000000000d, Optional internal context dependent data.

This simply means video driver crashed and to an unrecoverable state. 

 

http://msdn.microsoft.com/en-us/library/windows/hardware/ff557263(v=vs.85).aspx

 

Usual causes :  Overclocking , overheating graphics card , driver error and faulty graphic card.

 

 

Please try the below steps. Make sure to reset any overclocking or tweaking applied to the system before proceeding. Entering the BIOS setup and loading optimized defaults is also highly recommended.

 

:step1: Clean install video driver

 

1. Uninstall existing video driver and it's associated components. While uninstalling, remove Nvidia graphics driver at last. For example, in the following order.

 

    NVIDIA Update

   

    NVIDIA 3D Vision

 

    NVIDIA HD Audio Driver

 

    NVIDIA PhysX

 

    Remaining Nvidia components ...

 

    NVIDIA Graphics Driver

 

2. Download and install the latest driver.

 

    Get the latest driver from the below link. While installing choose custom (advanced ) and unselect everything except Nvidia graphics driver and Physx.

 

    http://www.nvidia.com/object/notebook-win8-win7-64bit-320.49-whql-driver.html

 

    cleaninstallnvidia.jpg 

 

:step2: Set graphics card power management to maximum performance.

 

      Read instructions from the below link carefully and set Nvidia power management to "Maximum performance".

 

      http://nvidia.custhelp.com/app/answers/detail/a_id/3130/~/setting-%22power-management-mode%22-from-adaptive-to-maximum-performance

 

:step3: Turn off PCI Express link state power management.

 

      http://www.sevenforums.com/tutorials/292971-pcie-link-state-power-management-turn-off-windows.html

 

:step4: Update chipset drivers.

 

      Download latest driver from the below link.

 

      https://downloadcenter.intel.com/confirm.aspx?httpDown=http://downloadmirror.intel.com/20775/eng/infinst_autol.exe&lang=eng&Dwnldid=20775&ProductID=816&ProductFamily=Software+Products&ProductLine=Chipset+Software&ProductProduct=Intel%C2%AE+Chipset+Software+Installation+Utility

 

:step5: Uninstall known problematic softwares.

 

      Uninstall the following bloatwares. They are not directly related to the issue you are facing but i highly advice to uninstall them for smooth system operation.

 

      ASUS USB Charger Plus

 

      ASUS Power4Gear Hybrid

 

      ASUS AI Recovery

 

     Also uninstall the following softwares.

 

     Advanced SystemCare 6  : It may cause serious damage to the system registry by deleting needed keys. BC highly advice to not using any kind of                                                      registry cleaners.

 

     Zone Alarm : This will cause conflict with Avast Pro antivirus. In fact, Windows doesn't need a third party firewall programs. Windows firewall is itself                               capable.

 

                            http://www.howtogeek.com/165203/why-you-dont-need-to-install-a-third-party-firewall-and-when-you-do/

 

 

:step6: Update Direct X

 

     http://www.microsoft.com/en-in/download/details.aspx?id=35

 

 

Follow the steps exactly as i described and post your findings in next reply.


Edited by Anshad Edavana, 28 July 2013 - 04:49 AM.


#11 Snelk

Snelk
  • Topic Starter

  • Members
  • 21 posts
  • OFFLINE
  •  
  • Local time:10:15 PM

Posted 29 July 2013 - 07:34 PM

Alright, I will get started on all that.  A few things though:

 

1)  I don't use the registry cleaning or "optimization" functions of ASC 6 because, as you pointed out, it can be dangerous if used improperly. 

2) As far as I know as long as only the firewall is enabled/installed for ZoneAlarm it does not conflict with Avast.  I will still remove it though, since I doubt I'll ever use any of the more advanced features.

3) I will be happy to remove all the bloatware except power4gear, doing so would disable a button on my computer that is dedicated to cycling through power settings.

 

Other, than that I will follow your recommendations to the letter, I will probably have an updated in an hour or two.  Although, since as previously stated, the stop errors have a fair amount of time between them, the update will likely just be a notice that I have completed the above troubleshooting steps.

 

Edit:

:step1: Clean install video driver

 

    NVIDIA Update - Uninstalled

    NVIDIA 3D Vision - Uninstalled

    NVIDIA HD Audio Driver - Uninstalled

    NVIDIA PhysX - Unable to uninstall, could not find program in installed programs list

    NVIDIA Graphics Driver - Uninstalled & reinstalled

 

:step2: Set graphics card power management to maximum performance. - Done

 

:step3: Turn off PCI Express link state power management. - Already off for primary use power settings

 

:step4: Update chipset drivers. - Done, fairly sure these were already up to date but ran installer anyway

 

:step5: Uninstall known problematic software.

 

      ASUS USB Charger Plus - Uninstalled

      ASUS Power4Gear Hybrid - Removal would disable some hardware

      ASUS AI Recovery - Uninstalled

 

     Advanced SystemCare 6  - In use (all registry modification features disabled)

     Zone Alarm - Uninstalled

 

:step6: Update Direct X - Done, already up to date (installer confirmed this)

 

Edit 2:

Another stop error.  Computer was idling at the time Dump is here.  At this point I will probably follow my manufacturers advice and do a clean install.  Not until sometime next week though, when my summer course ends.  And if THAT doesn't work.... its pretty much a 100% certainty its a hardware issue..... sigh

 

Anyway, If there is anything else I could try before then, please let me know.  Thanks. 


Edited by Snelk, 29 July 2013 - 08:49 PM.


#12 Anshad Edavana

Anshad Edavana

  • Members
  • 2,805 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:India
  • Local time:09:45 AM

Posted 29 July 2013 - 11:32 PM

Hi

 

New dump also still blames Nvidia video driver.

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

Unable to load image 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+f6d49 )

On the software part your system looks clean. Video driver is already up to dated and no conflicting driver can be seen in the dumps. However, i recommend doing the below steps as a last resort before re-installing Windows.

 

:step1: Update system BIOS.

 

 Check in the Asus support site for an updated BIOS. If there any, install it first.

 

:step2: Install known stable graphic driver.

 

Uninstall the currently installed latest driver as i described in my previous post. Then install the below driver. We are downgrading the driver but so far, this version is known to be stable and crash free.

 

http://www.nvidia.in/object/win8-win7-winvista-64bit-306.23-whql-driver-in.html

 

 

If that doesn't helps, we don't have much choice other than to re-install the OS and check.



#13 Snelk

Snelk
  • Topic Starter

  • Members
  • 21 posts
  • OFFLINE
  •  
  • Local time:10:15 PM

Posted 30 July 2013 - 12:23 AM

:step1: Update system BIOS.
 
Tried upgrading from BIOS version 202 to 203, WinFlash reported that "The BIOS file version does not match the BIOS ROM version"
 
:step2: Install known stable graphic driver. - 306.23 incompatible with the 560 M, using 306.97 instead - installed

Edited by Snelk, 30 July 2013 - 12:46 AM.


#14 Anshad Edavana

Anshad Edavana

  • Members
  • 2,805 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:India
  • Local time:09:45 AM

Posted 30 July 2013 - 01:42 AM

Hi

 

BIOS update error seems to be strange to me. Try Asus EZflash which can be located on the BIOS setup itself.

 

Also, if you encounter further blue screens, please enable Driver Verifier. This will stress test all third party drivers and create a blue screen when it detects a driver violation.

 

http://www.sevenforums.com/tutorials/101379-driver-verifier-enable-disable.html

 

Play some high definition movies continuously to stress test the system. Analyzing those dumps will let us know whether the issue is hardware related or software related.



#15 Snelk

Snelk
  • Topic Starter

  • Members
  • 21 posts
  • OFFLINE
  •  
  • Local time:10:15 PM

Posted 30 July 2013 - 04:12 PM

Got the following error when trying to use Asus EZFlash, I opted not to potentially turn my computer into a very expensive brick.

 

https://www.dropbox.com/s/5m3b1l18ccwaitj/IMAG0029.jpg

 

Will be enabling driver verifier next.

Edit:

 

1) first start up after enabling verifier....  BSOD before login.

2) BSOD due to smart defrag, removed smart defrag, BSOD goes away

3) verifier apparently using 90% cpu, before all startup processes can load (which is taking much longer than normal) BSOD due to some HID*.sys driver, computer is so hosed it can't even produce a minidump

 

I can't even try to stress test the important stuff, because all this little probably not affiliated stuff is causing BSOD's before I can, suggestions?


Edited by Snelk, 30 July 2013 - 07:41 PM.





0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users