HP crashes while asleep, restarts to BSOD once with ID:4105 BC Code 9f

Welcome to SevenForums

Apparently it looks like the BSOD-s were caused by ATI drivers.

Code:

*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 100000EA, {86f45a60, 0, 0, 0}

Unable to load image \SystemRoot\system32\DRIVERS\atikmdag.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for atikmdag.sys
*** ERROR: Module load completed but symbols could not be loaded for atikmdag.sys
*** WARNING: Unable to verify timestamp for atikmpag.sys
*** ERROR: Module load completed but symbols could not be loaded for atikmpag.sys
Probably caused by : dxgkrnl.sys ( dxgkrnl!TdrTimedOperationBugcheckOnTimeout+2c )

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

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

THREAD_STUCK_IN_DEVICE_DRIVER_M (100000ea)
The device driver is spinning in an infinite loop, most likely waiting for
hardware to become idle. This usually indicates problem with the hardware
itself or with the device driver programming the hardware incorrectly.
If the kernel debugger is connected and running when watchdog detects a
timeout condition then DbgBreakPoint() will be called instead of KeBugCheckEx()
and detailed message including bugcheck arguments will be printed to the
debugger. This way we can identify an offending thread, set breakpoints in it,
and hit go to return to the spinning code to debug it further. Because
KeBugCheckEx() is not called the .bugcheck directive will not return bugcheck
information in this case. The arguments are already printed out to the kernel
debugger. You can also retrieve them from a global variable via
"dd watchdog!g_WdBugCheckData l5" (use dq on NT64).
On MP machines it is possible to hit a timeout when the spinning thread is
interrupted by hardware interrupt and ISR or DPC routine is running at the time
of the bugcheck (this is because the timeout's work item can be delivered and
handled on the second CPU and the same time). If this is the case you will have
to look deeper at the offending thread's stack (e.g. using dds) to determine
spinning code which caused the timeout to occur.
Arguments:
Arg1: 86f45a60, Pointer to a stuck thread object.  Do .thread then kb on it to find
	the hung location.
Arg2: 00000000, Pointer to a DEFERRED_WATCHDOG object.
Arg3: 00000000, Pointer to offending driver name.
Arg4: 00000000, Number of times "intercepted" bugcheck 0xEA was hit (see notes).

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


FAULTING_THREAD:  86f45a60

DEFAULT_BUCKET_ID:  GRAPHICS_DRIVER_FAULT

CUSTOMER_CRASH_COUNT:  1

BUGCHECK_STR:  0xEA

PROCESS_NAME:  csrss.exe

CURRENT_IRQL:  0

LAST_CONTROL_TRANSFER:  from 8febf1f7 to 82f20bdc

STACK_TEXT:  
8d0b46b8 8febf1f7 000000ea 86f45a60 00000000 nt!KeBugCheckEx+0x1e
8d0b46fc 8feb7bc0 8d0b4748 00000000 8feba51e dxgkrnl!TdrTimedOperationBugcheckOnTimeout+0x2c
8d0b4724 8f85c35b 8d0b4748 00000000 00000000 dxgkrnl!TdrTimedOperationDelay+0xc9
WARNING: Stack unwind information not available. Following frames may be wrong.
8d0b4774 8f855ae7 8fa33adb 8d0b4814 ffffffff atikmdag+0x2935b
8d0b4794 8fa30a3b 86086001 8d0b47b0 1fff1fff atikmdag+0x22ae7
8d0b47f0 8fa33c54 86a91004 8fa33adb 8d0b4814 atikmdag+0x1fda3b
8d0b482c 8fa66317 86387000 00000000 00000001 atikmdag+0x200c54
8d0b4848 8f99bc63 86387000 00000000 00000001 atikmdag+0x233317
8d0b4868 8f9b2b86 86a91000 86a99f7e 00000000 atikmdag+0x168c63
8d0b488c 8f9b2c1c 86a91000 86a99658 00000001 atikmdag+0x17fb86
8d0b48ac 8f983f4d 86a912c0 00000000 00000001 atikmdag+0x17fc1c
8d0b48c0 8f982b74 00000000 00000001 8d0b48e4 atikmdag+0x150f4d
8d0b48d0 8f86d5dd 869850d0 00000000 00000001 atikmdag+0x14fb74
8d0b48e4 8f882464 00000000 8d0b4900 8f883a51 atikmdag+0x3a5dd
8d0b48f0 8f883a51 8d0b4a00 860a7540 8d0b495c atikmdag+0x4f464
8d0b4900 8f875268 00000000 8d0b4a0c 863c0840 atikmdag+0x50a51
8d0b495c 8f8432d9 8d0b4a0c 863c0840 00000000 atikmdag+0x42268
8d0b4974 8eda9dde 00000001 8d0b4a0c 82e106ee atikmdag+0x102d9
8d0b49b0 8feede50 863c0840 8d0b4a0c 00000000 atikmpag+0x5dde
8d0b49dc 8ff2e659 8d0b4a0c 898e81b0 898e807e dxgkrnl!DXGADAPTER::DdiSetVidPnSourceVisibility+0x48
8d0b4a40 8ff00346 ffffffff 898e807e 96db37f0 dxgkrnl!VIDPN_MGR::RemovePresentPathFromActiveVidPn+0x274
8d0b4a84 8ff00624 86109000 ffffffff 00000000 dxgkrnl!VIDPN_MGR::_MonitorEventHandler+0x23b
8d0b4ab8 8ff2d20b ffffffff 00000002 00000001 dxgkrnl!MONITOR_MGR::_IssueMonitorEvent+0xa4
8d0b4aec 8ff2cfb0 ffffffff 00000000 00000002 dxgkrnl!MONITOR_MGR::_EnableDisableMonitor+0x24f
8d0b4b14 8ff22c16 86109000 ffffffff 00000000 dxgkrnl!MonitorEnableDisableMonitor+0xfb
8d0b4b9c 8ff224fd 867189c8 852c29f8 00000004 dxgkrnl!DpiGdoDispatchInternalIoctl+0x2be
8d0b4bc0 82e78c0e 867189c8 852c29f8 852c29f8 dxgkrnl!DpiDispatchInternalIoctl+0x86
8d0b4bd8 971545e2 898e807e ffb92610 898e81b0 nt!IofCallDriver+0x63
8d0b4c04 97218b21 867189c8 0023200f 8d0b4c40 win32k!GreDeviceIoControlEx+0x97
8d0b4c44 97217669 00000001 ffbbd70c 00000001 win32k!DrvSetMonitorPowerState+0xe3
8d0b4c6c 97217fa4 971f48d8 0000001e 879a8070 win32k!PowerOffMonitor+0xaa
8d0b4d00 9716f516 0187f78c 00000000 879a8070 win32k!xxxUserPowerStateCalloutWorker+0x7b
8d0b4d18 971f48f3 0000001e 0187f78c 8d0b4d34 win32k!xxxUserPowerCalloutWorker+0x34
8d0b4d28 82e7f89a 0000001e 0187f798 778d7094 win32k!NtUserCallNoParam+0x1b
8d0b4d28 778d7094 0000001e 0187f798 778d7094 nt!KiFastCallEntry+0x12a
0187f798 00000000 00000000 00000000 00000000 0x778d7094


STACK_COMMAND:  .thread 0xffffffff86f45a60 ; kb

FOLLOWUP_IP: 
dxgkrnl!TdrTimedOperationBugcheckOnTimeout+2c
8febf1f7 cc              int     3

SYMBOL_STACK_INDEX:  1

SYMBOL_NAME:  dxgkrnl!TdrTimedOperationBugcheckOnTimeout+2c

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: dxgkrnl

IMAGE_NAME:  dxgkrnl.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  4ce78ffe

FAILURE_BUCKET_ID:  0xEA_IMAGE_dxgkrnl.sys

BUCKET_ID:  0xEA_IMAGE_dxgkrnl.sys

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

0: kd> lmvm atikmpag
start    end        module name
8eda4000 8ede1000   atikmpag T (no symbols)           
    Loaded symbol image file: atikmpag.sys
    Image path: \SystemRoot\system32\DRIVERS\atikmpag.sys
    Image name: atikmpag.sys
    Timestamp:        Wed Sep 29 07:14:29 2010 (4CA292F5)
    CheckSum:         00044628
    ImageSize:        0003D000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4

Sometimes drivers remain, not completely uninstalled. Follow this tutorial for complete removal of drivers of the particular program:

• How to Clean Left Over Driver Files with Driver Sweeper
• HP and Windows® 7

NFO:

Please upload your msinfo32.nfo file. To get this: Start Menu -> Type msinfo32 into the Search programs and files box

-> When it opens, go to File, Save -> Save as msinfo32.nfo and save in a place you will remember
-> Let it finish the process of gathering and saving the system info
-> Right click the .nfo file, click send to compressed (zipped) folder
-> Upload the .zip file here.

Please upload your msinfo32.txt file. To get this: Start Menu -> Type msinfo32 into the Search programs and files box

-> When it opens, go to File, Export -> Save as msinfo32.txt and save in a place you will remember
-> Let it finish the process of gathering and saving the system info
-> Right click the .txt file, click send to compressed (zipped) folder
-> Upload the .zip file here.

Go through this link:

• How to troubleshoot video card problems

AVG contributes in BSOD-s. Please uninstall it with its removal tool: AVG | Download tools and utilities

Microsoft Security Essentials.

Recommended from a strict BSOD perspective, compatibility & stability compared to other antiviruses/internet security software. It is free and lightweight:-

• Microsoft Security Essentials, Free antivirus for windows.
• Malwarebytes Anti-Malware Free
• Good and Free system security combination
  
  

   Warning

Do not start the free trial of Malware Bytes; remember to deselect that option when prompted.

Run a full scan with both (separately) once downloaded, installed and updated.

---

Disk Check on your hard drive for file system errors and bad sectors on it.

• How to run Disk Check on Windows 7

Perform a System File Check to check the integrity of all protected Windows 7 :

1. Click on the start
2. Type CMD on Search
3. Left click and Run as Administrator
4. Type
   Code:

   SFC /scannow

Full tutorial here:

• SFC /Scannow Command - System File Checker

Let us know the results.

Check for a BIOS update.

Code:

BIOS Version/Date	Hewlett-Packard 68MVD Ver. F.15, 02/12/2008

Your BIOS dates from 2008. Please check at the manufacturer's website to see if there are any BIOS updates available for your system. Also check the readme file to see if they apply to the problems that you are having. Please be advised that flashing the BIOS is a very unforgiving process - and one mistake can physically damage your motherboard.

Number down items at start-up. Keep only your anti-virus, this also improves the time for logging into windows.

• Startup Programs - Change
• Troubleshoot Application Conflicts by Performing a Clean Startup

Update the thread if you get a BSOD again.

The display driver is not the latest, till now.

Code:

8cad9000 8cb25000   atikmpag T (no symbols)           
    Loaded symbol image file: atikmpag.sys
    Image path: \SystemRoot\system32\DRIVERS\atikmpag.sys
    Image name: atikmpag.sys
    Timestamp:        Sat Nov 17 01:08:49 2012 (50A69649)
    CheckSum:         0004C882
    ImageSize:        0004C000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4

Update your ATI/AMD display driver.
You can get it from the link in our forum, Latest AMD Catalyst Video Driver for Windows 7, or you may go to AMD Graphics Driver and Software and opt for Automatically Detect and Install the appropriate driver for your card.


During installation, you may opt for advanced installation, and install the display driver only, not the Catalyst Control Center.

Pay attention to the BIOS, as koolkat77 suggested earlier.

Code:

BiosMajorRelease = 15
BiosMinorRelease = 21
FirmwareMajorRelease = 113
FirmwareMinorRelease = 54
BiosVendor = Hewlett-Packard
BiosVersion = 68MVD Ver. F.15
BiosReleaseDate = 12/02/2008

It is really old.

Also, make it sure that the computer is getting enough power .... check that all the BIOS timing\clock settings of CPU, GPU and RAM are set to default.

Code:

CPUID:        "Intel(R) Core(TM)2 Duo CPU     T7300  @ 2.00GHz"
MaxSpeed:     2000
CurrentSpeed: 1995

It seems to be getting some less power.

BTW, there is no 9F crash dump as you stated. Post it following the Blue Screen of Death (BSOD) Posting Instructions so that we can obtain all the information required, and upload your MSINFO32.nfo file.

1. Click on the start button
2. Type "msinfo32" (without quotes) in the search bar of the start menu, click the resulting link. It will open the System Information window.
3. File>Save. In the "File Name" filed, put "MSINFO32" (without Quote), give the save location to desktop, and click the "save" button.
4. Give the time for processing, it will save a .nfo file on your desktop.
5. Zip it, and upload it following the instruction.