Display randomly freezes/distorts

#21
Is your video card or CPU overclocked?



Debugging :

Code:
Microsoft (R) Windows Debugger Version 6.11.0001.404 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [M:\Desktop\081210-25849-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*c:\websymbols*http://msdl.microsoft.com/download/symbols
Executable search path is: 
Windows 7 Kernel Version 7600 MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Machine Name:
Kernel base = 0xfffff800`02c0d000 PsLoadedModuleList = 0xfffff800`02e4ae50


...............................................................
................................................................
..........
Loading User Symbols
Loading unloaded module list
....
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 124, {0, fffffa8003a84028, b2000040, 800}

Unable to load image \SystemRoot\system32\DRIVERS\intelppm.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for intelppm.sys
*** ERROR: Module load completed but symbols could not be loaded for intelppm.sys
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: fffffa8003a84028, Address of the WHEA_ERROR_RECORD structure.
Arg3: 00000000b2000040, High order 32-bits of the MCi_STATUS value.
Arg4: 0000000000000800, 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:  
fffff880`009f1a58 fffff800`031fb903 : 00000000`00000124 00000000`00000000 fffffa80`03a84028 00000000`b2000040 : nt!KeBugCheckEx
fffff880`009f1a60 fffff800`02d93593 : 00000000`00000001 fffffa80`03adbb40 00000000`00000000 fffffa80`03adbb90 : hal!HalBugCheckSystem+0x1e3
fffff880`009f1aa0 fffff800`031fb5c8 : 00000000`00000728 fffffa80`03adbb40 fffff880`009f1e30 fffff880`009f1e00 : nt!WheaReportHwError+0x263
fffff880`009f1b00 fffff800`031faf1a : fffffa80`03adbb40 fffff880`009f1e30 fffffa80`03adbb40 00000000`00000000 : hal!HalpMcaReportError+0x4c
fffff880`009f1c50 fffff800`031fadd5 : 00000000`00000004 00000000`00000001 fffff880`009f1eb0 00000000`00000000 : hal!HalpMceHandler+0x9e
fffff880`009f1c90 fffff800`031eee88 : 00000000`00000000 fffff880`009e9180 00000000`00000000 00000000`00000000 : hal!HalpMceHandlerWithRendezvous+0x55
fffff880`009f1cc0 fffff800`02c7bfec : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : hal!HalHandleMcheck+0x40
fffff880`009f1cf0 fffff800`02c7be53 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxMcheckAbort+0x6c
fffff880`009f1e30 fffff880`0416c9c2 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiMcheckAbort+0x153
fffff880`02f1bc98 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : intelppm+0x39c2


STACK_COMMAND:  kb

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: hardware

IMAGE_NAME:  hardware

DEBUG_FLR_IMAGE_TIMESTAMP:  0

FAILURE_BUCKET_ID:  X64_0x124_GenuineIntel_PROCESSOR_BUS

BUCKET_ID:  X64_0x124_GenuineIntel_PROCESSOR_BUS

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

1: kd> analyze ~v
1. intelppm.sys - Processor Device Driver belongs to the software Intel Processor Driver or Microsoft Windows Operating System by Microsoft Corporation.

In some cases, malware processes camouflage themselves as intelppm.sys.

Do system scan for malware.




2. 0x124_GenuineIntel

0x124 error, msdn reference:

Download and install updates and device drivers for your computer from Windows Update.

Scan your computer for computer viruses.

Check your hard disk for errors.






3. nvlddmkm.sys - something wrong with your card, or the forceware version.

Code:
Microsoft (R) Windows Debugger Version 6.11.0001.404 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [M:\Desktop\081210-36987-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*c:\websymbols*http://msdl.microsoft.com/download/symbols
Executable search path is: 
Windows 7 Kernel Version 7600 MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Machine Name:
Kernel base = 0xfffff800`02c15000 PsLoadedModuleList = 0xfffff800`02e52e50

...............................................................
................................................................
......
Loading User Symbols
Loading unloaded module list
....
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 116, {fffffa8004fde010, fffff880048f9140, 0, 2}

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+e1140 )

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

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

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

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


FAULTING_IP: 
nvlddmkm+e1140
fffff880`048f9140 803d51b4970000  cmp     byte ptr [nvlddmkm+0xa5c598 (fffff880`05274598)],0

DEFAULT_BUCKET_ID:  GRAPHICS_DRIVER_TDR_FAULT

CUSTOMER_CRASH_COUNT:  1

BUGCHECK_STR:  0x116

PROCESS_NAME:  System

CURRENT_IRQL:  0

STACK_TEXT:  
fffff880`03d809c8 fffff880`05342ef8 : 00000000`00000116 fffffa80`04fde010 fffff880`048f9140 00000000`00000000 : nt!KeBugCheckEx
fffff880`03d809d0 fffff880`05342c02 : fffff880`048f9140 fffffa80`04fde010 fffffa80`04dd0d50 fffffa80`04aab410 : dxgkrnl!TdrBugcheckOnTimeout+0xec
fffff880`03d80a10 fffff880`0418bf07 : fffffa80`04fde010 00000000`00000000 fffffa80`04dd0d50 fffffa80`04aab410 : dxgkrnl!TdrIsRecoveryRequired+0x1a2
fffff880`03d80a40 fffff880`041b5b75 : 00000000`ffffffff 00000000`000005a4 00000000`00000000 00000000`00000002 : dxgmms1!VidSchiReportHwHang+0x40b
fffff880`03d80b20 fffff880`041b42bb : 00000000`00000102 00000000`00000000 00000000`000005a4 00000000`00000000 : dxgmms1!VidSchiCheckHwProgress+0x71
fffff880`03d80b50 fffff880`041872c6 : ffffffff`ff676980 fffffa80`04aab410 00000000`00000000 00000000`00000000 : dxgmms1!VidSchiWaitForSchedulerEvents+0x1fb
fffff880`03d80bf0 fffff880`041b3e7a : 00000000`00000000 00000000`0000000f 00000000`00000080 fffffa80`0411dc68 : dxgmms1!VidSchiScheduleCommandToRun+0x1da
fffff880`03d80d00 fffff800`02f29c06 : 00000000`02e98f75 fffffa80`04aaf770 fffffa80`024b9040 fffffa80`04aaf770 : dxgmms1!VidSchiWorkerThread+0xba
fffff880`03d80d40 fffff800`02c63c26 : fffff800`02dffe80 fffffa80`04aaf770 fffff800`02e0dc40 fffff880`01268534 : nt!PspSystemThreadStartup+0x5a
fffff880`03d80d80 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxStartSystemThread+0x16


STACK_COMMAND:  .bugcheck ; kb

FOLLOWUP_IP: 
nvlddmkm+e1140
fffff880`048f9140 803d51b4970000  cmp     byte ptr [nvlddmkm+0xa5c598 (fffff880`05274598)],0

SYMBOL_NAME:  nvlddmkm+e1140

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nvlddmkm

IMAGE_NAME:  nvlddmkm.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  4a5ce19c

FAILURE_BUCKET_ID:  X64_0x116_IMAGE_nvlddmkm.sys

BUCKET_ID:  X64_0x116_IMAGE_nvlddmkm.sys

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

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

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

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


FAULTING_IP: 
nvlddmkm+e1140
fffff880`048f9140 803d51b4970000  cmp     byte ptr [nvlddmkm+0xa5c598 (fffff880`05274598)],0

DEFAULT_BUCKET_ID:  GRAPHICS_DRIVER_TDR_FAULT

CUSTOMER_CRASH_COUNT:  1

BUGCHECK_STR:  0x116

PROCESS_NAME:  System

CURRENT_IRQL:  0

STACK_TEXT:  
fffff880`03d809c8 fffff880`05342ef8 : 00000000`00000116 fffffa80`04fde010 fffff880`048f9140 00000000`00000000 : nt!KeBugCheckEx
fffff880`03d809d0 fffff880`05342c02 : fffff880`048f9140 fffffa80`04fde010 fffffa80`04dd0d50 fffffa80`04aab410 : dxgkrnl!TdrBugcheckOnTimeout+0xec
fffff880`03d80a10 fffff880`0418bf07 : fffffa80`04fde010 00000000`00000000 fffffa80`04dd0d50 fffffa80`04aab410 : dxgkrnl!TdrIsRecoveryRequired+0x1a2
fffff880`03d80a40 fffff880`041b5b75 : 00000000`ffffffff 00000000`000005a4 00000000`00000000 00000000`00000002 : dxgmms1!VidSchiReportHwHang+0x40b
fffff880`03d80b20 fffff880`041b42bb : 00000000`00000102 00000000`00000000 00000000`000005a4 00000000`00000000 : dxgmms1!VidSchiCheckHwProgress+0x71
fffff880`03d80b50 fffff880`041872c6 : ffffffff`ff676980 fffffa80`04aab410 00000000`00000000 00000000`00000000 : dxgmms1!VidSchiWaitForSchedulerEvents+0x1fb
fffff880`03d80bf0 fffff880`041b3e7a : 00000000`00000000 00000000`0000000f 00000000`00000080 fffffa80`0411dc68 : dxgmms1!VidSchiScheduleCommandToRun+0x1da
fffff880`03d80d00 fffff800`02f29c06 : 00000000`02e98f75 fffffa80`04aaf770 fffffa80`024b9040 fffffa80`04aaf770 : dxgmms1!VidSchiWorkerThread+0xba
fffff880`03d80d40 fffff800`02c63c26 : fffff800`02dffe80 fffffa80`04aaf770 fffff800`02e0dc40 fffff880`01268534 : nt!PspSystemThreadStartup+0x5a
fffff880`03d80d80 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxStartSystemThread+0x16


STACK_COMMAND:  .bugcheck ; kb

FOLLOWUP_IP: 
nvlddmkm+e1140
fffff880`048f9140 803d51b4970000  cmp     byte ptr [nvlddmkm+0xa5c598 (fffff880`05274598)],0

SYMBOL_NAME:  nvlddmkm+e1140

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nvlddmkm

IMAGE_NAME:  nvlddmkm.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  4a5ce19c

FAILURE_BUCKET_ID:  X64_0x116_IMAGE_nvlddmkm.sys

BUCKET_ID:  X64_0x116_IMAGE_nvlddmkm.sys

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


#22
My recommendation based on what I see:

Clean install Windows while formatting. First thing after getting to desktop: Install latest video driver normally.

Then Windows Update to install all patches. This still may not do well since there may be a hardware fault. This is best chances to sort it though.
 


#23
Thanks, I'll try that this evening.
 


#24
You're welcome.

I also advise, somewhere in there either before or after the clean install (doesn't matter much as long as it's done - before is probably best) -

Use CPU-Z to find out your exact motherboard model. Look at mainboard tab. Then visit Asus' page for it to obtain the latest bios. Install.
 


#26
Just a small note here... "Newer" is not synonymous with "Better".

Updates and revisions are as prone to introduce problems as they are to solve them.

As I noted above the answer in my case (same video card) was to backdate the drivers and uninstall the 3D software.

For example: NVidia has moved beyond the 8000 series architecture. Newer versions of their drivers will be optomized for the newer hardware they are producing. The most optimal drivers for 8000 series cards would be the last version before the next level of hardware was introduced.
 


#27
So true, I too used to experience just this with my older cards,

CommonTater said:
Newer versions of their drivers will be optomized for the newer hardware they are producing.

The most optimal drivers for 8000 series cards would be the last version before the next level of hardware was introduced.
This must sure be taken into consideration.


Also, upgrade bios and clean install 7 as suggested. Then please write back on how it gets on.
 


#28
WEll i was able to have the pc on all night in safe mode w/ networking.
- i downloaded malware bytes and CPU-Z.
- I rebooted the PC into normal mode without a problem (graphics card is still uninstalled).
- Installed/Updated Malware Bytes
- Ran CPU-Z. (screenshot below)

cpu-z screenshot.jpg

- I went to Asus's website but after running their wizard app they determined that they did not have support for my model of Mobo.

- Did a google search for "Asus Berkley" and it brought me to an HP webpage, but HP does not have windows 7 support for my model desktop (Elite Pavillion m90490n) or MoBo.
- Went to American Megatrends to see if they had bios updates but on their website they say they do not update the bios and i would have to go to the OEM in order to do that.

I will begin the clean install of 7 shortly because seeking a bios update is not going to work.


EDIT

I will try installing the older version of nvidia's graphic driver (196.21) and see if that works. If not, clean install here I come. W00t!
 


Last edited:
#29
couldnt install version 196.21. That is for XP & Win2000 operating system.
 


#31
Nothing against the previous advice as I'm 100% sure that all of it is made in honest supportive help.

I always recommend the latest driver for video to be installed, based on thousands or 10s of thousands of crash dump analysis' I've made, along with making customized video driver installs for many years.

His problem to being with is partially but not fully due to having the old 2009 video driver. Latest available driver installed instead would be best for him, as it would be for any video card it supports.
 


#32
I did a clean install. Reformatted the C:\ drive (excluding the factory image) then performed the install of win7 ultimate. Went through the entire installation process fine. After its reboot and it gets to the first screen where you have to create a username it locks up. Screen starts to distort and the keyboard/mouse are not responding (basically, a normal day here at home... FML) and then it rebooted itself to an all black screen. i've turned off the pc and am working from my wife's desktop.
 


#33
Ok... is this computer still under warranty?

I'm thinking you got some hardware problems --bad memory, blown chipset, or such. If I were in your shoes I would pack it up and send it in to be serviced. You are entitled to a working machine for at least the length of the manufacturer's warranty...
 


#34
no, it is no longer under warranty. i rebooted it a few minutes ago and was able to get through the final setup steps fine. it is sitll on and has not gone crazy....yet. will head over to nvidia now to get the older driver.

i just want to be able to play starcraft 2 in peace *sigh*
 


#35
If the motherboard has an onboard video, remove the video card, plug the monitor into the motherboard and boot to Windows.

If it runs well, then the video card itself is defective. (That would be what 0x124 stops mean - as I said, something in the system is likely defective.)

If the mobo doesn't have onboard video, borrow a friend's card if you can to test with that.
 


#36
If it runs well, then the video card itself is defective.
You may be right on this one TorrentG... I've had a couple of ASUS 8400gs cards go bad on me of late. These are the passively cooled ones with the BIG heatsink held on by two small plastic pins... the pins break, the thermal grease gaps and the chips overheat to self-destruction.

If you're right, our friend has a simple and cheap fix... just use the onboard video.
 


#37
Ya, ya true. I hear that. More often than the chips overheating and being destroyed, it's the capacitors that fail due to being cheap, misformulated and from China.

a.k.a capacitor plague

My 6200A-Le on my family machine had the blown caps. Replaced them with low esr type caps a few years ago when the card failed and it's been fine ever since.
 


#38
so far so good. i was able to install the updated drivers for the RealTek audio device, Intel's wireless network card, the LG Monitor, and the older version of the Nvidia card. i am currently running the windows updates and will reboot it again shortly.
 


#39
You may be right on this one TorrentG... I've had a couple of ASUS 8400gs cards go bad on me of late. These are the passively cooled ones with the BIG heatsink held on by two small plastic pins... the pins break, the thermal grease gaps and the chips overheat to self-destruction.

If you're right, our friend has a simple and cheap fix... just use the onboard video.
There is no other external video port...there is 1 port that has a plastic cap which is screwed over it towards the lower back end of the tower. i'll check it out tonight when i return home.


By the way, thanks for all the support.
 


#40
so far so good. i was able to install the updated drivers for the RealTek audio device, Intel's wireless network card, the LG Monitor, and the older version of the Nvidia card. i am currently running the windows updates and will reboot it again shortly.
Well here's the bad news... Windows updates is probably going to replace all those drivers on you. Be ready to uninstall then re-install each device in turn to get them working again. Right after you put windows updates on manual ... so that you can select what it does and does not foist upon you.

(Straight up... Automatic updates is/are the computer industry's biggest ever screw up. At one time 50% of my service calls came the day after windows updates... )
 


This website is not affiliated, owned, or endorsed by Microsoft Corporation. It is a member of the Microsoft Partner Program.
Top