Black screen... No device found...

[dorchen]

Hi my packard bell iExtreme that i bought a couple of days ago has this problem especially when i play CoD Black ops. The computer goes in to some kinda sleep mode (i dont really know how to describe it) The screen and audio dissapears and the only way (exept ripping the cable from it) to shut it down, is manually on the start up button.
Is it hardware or a software problem?
Is there a reason it only happpens when i play CoD?

 

[TrainableMan]

Drop into a command prompt and run "powercfg /requests" and paste the results back here please.

 

[dorchen]

Drop into a command prompt and run "powercfg /requests" and paste the results back here please.

It says: C:\System32>powercfg/requests
DISPLAY:
None.

SYSTEM:
None.

AWAYMODE:
None.

 

[TrainableMan]

Basically it says nothing is preventing sleep. So you can either turn off sleep in Control Panel\Power Options ... Advanced settings. Or you can try a little program like Don't Sleep. I did the first option so mine never sleeps but to save energy, especially for laptop users, you might be better off leaving it on and then just running that program when you run the old game; just remember to shut it off once you end the game or use it's timer function.

 

[Thrax]

This is not a sleep issue. This is a "your computer is crashing" issue.

Can you please link me to the specs of this computer?

 

[dorchen]

Packar bell iExtreme M860
Intel core i7 2600 3.40ghz
ram 8gb
64 bit
nvidiaGT 530

 

[dorchen]

This is not a sleep issue. This is a "your computer is crashing" issue.

Can you please link me to the specs of this computer?

it happened again like a minute ago, i started a game and the fans started going really loud, my screen told me no input and the lights on the chassi were light as they are when the computer is on.

 

[Thrax]

When is the last time you updated the drivers for this PC? When in doubt, get the newest Windows 64-bit drivers from their site. Reboot after they're installed, and see what happens.

Your PC is definitely crashing when the GPU is being activated for a game.

 

[dorchen]

When is the last time you updated the drivers for this PC? When in doubt, get the newest Windows 64-bit drivers from their site. Reboot after they're installed, and see what happens.

Your PC is definitely crashing when the GPU is being activated for a game.

ive downloaded them like a few days ago, and it has crashed after ive downloaded...

 

[dorchen]

Still crashing......

 

[TrainableMan]

Enable minidumps and see if you get DMP files, if so then start a BSOD thread and include the zipped DMP files.

See BSOD instructions and link to instructions for enabling minidumps HERE.

 

[dorchen]

Enable minidumps and see if you get DMP files, if so then start a BSOD thread and include the zipped DMP files.

See BSOD instructions and link to instructions for enabling minidumps HERE.

Here are my minidumps, what do you mean by enabling them??

 

[TrainableMan]

Here are my minidumps, what do you mean by enabling them??

Some machines have dumps disabled but since you have DMP files yours are already enabled so not an issue there.

And I see your system specs are:
Packard Bell iExtreme M860
Intel core i7 2600 3.40ghz
ram 8gb
64 bit
nvidiaGT 530

I will move this over to the BSODs section.

 

[Ace]

The crash dumps show that you've been encountering BSOD's for around a month now, i'll take a look at them and post my results here.

 

[Ace]

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

Use !analyze -v to get detailed debugging information.

BugCheck 116, {fffffa80151ea4e0, fffff8800fc2efa4, ffffffffc000009a, 4}

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

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

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

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

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


FAULTING_IP:
nvlddmkm+7fefa4
fffff880`0fc2efa4 4883ec28 sub rsp,28h

DEFAULT_BUCKET_ID: GRAPHICS_DRIVER_TDR_FAULT

CUSTOMER_CRASH_COUNT: 1

BUGCHECK_STR: 0x116

PROCESS_NAME: System

CURRENT_IRQL: 0

STACK_TEXT:
fffff880`0555aa48 fffff880`100f3000 : 00000000`00000116 fffffa80`151ea4e0 fffff880`0fc2efa4 ffffffff`c000009a : nt!KeBugCheckEx
fffff880`0555aa50 fffff880`100c6867 : fffff880`0fc2efa4 fffffa80`0c307000 00000000`00000000 ffffffff`c000009a : dxgkrnl!TdrBugcheckOnTimeout+0xec
fffff880`0555aa90 fffff880`100f2e0f : fffffa80`ffffd84d ffffffff`fffe7960 fffffa80`151ea4e0 00000000`00000000 : dxgkrnl!DXGADAPTER::Reset+0x2a3
fffff880`0555ab40 fffff880`101c1ec1 : fffffa80`14d34190 00000000`00000080 00000000`00000000 fffffa80`0c25f010 : dxgkrnl!TdrResetFromTimeout+0x23
fffff880`0555abc0 fffff800`03332fee : 00000000`02f554ca fffffa80`0c3234d0 fffffa80`06d0aae0 fffffa80`0c3234d0 : dxgmms1!VidSchiWorkerThread+0x101
fffff880`0555ac00 fffff800`030895e6 : fffff800`0320de80 fffffa80`0c3234d0 fffff800`0321bcc0 00000000`00000000 : nt!PspSystemThreadStartup+0x5a
fffff880`0555ac40 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxStartSystemThread+0x16


STACK_COMMAND: .bugcheck ; kb

FOLLOWUP_IP:
nvlddmkm+7fefa4
fffff880`0fc2efa4 4883ec28 sub rsp,28h

SYMBOL_NAME: nvlddmkm+7fefa4

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: nvlddmkm

IMAGE_NAME: nvlddmkm.sys

DEBUG_FLR_IMAGE_TIMESTAMP: 4e391010

FAILURE_BUCKET_ID: X64_0x116_IMAGE_nvlddmkm.sys

BUCKET_ID: X64_0x116_IMAGE_nvlddmkm.sys

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

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

VIDEO_TDR_FAILURE (0x116)

This indicates that an attempt to reset the display driver and recover from a timeout had failed. The default timeout value should be around 5 seconds.

Every one of your crash dumps points to the same error. You don't seem to be overclocking anything, your cpu cycles in at around 3.4 Ghz which is where it should be. I would check for updates to your NVidea driver firstly.

Overheating and powersupply issues could be possible causes. I would check your internal core temps to make sure that they aren't too high. To check for heating problems on your GPU I would suggest a program called CPU-Z which is available here: http://www.cpuid.com/softwares/cpu-z.html

You can also do a GPU Stress test here: http://www.ozone3d.net/benchmarks/fur/

Check for any warnings in device manager under the display area, and also your event viewer.

If we don't find an issue here, I would suggest that you also try running System File Checker to see if there's any corrupt system files. To use it, open command prompt and type this in:

sfc /scannow

Let it finish, and attempt to repair any corrupt or missing entries.

Last resort would be to try to reinstall your Nvidia Graphic driver using the Clean Install feature.

fffff880`0f430000 fffff880`10094000   nvlddmkm nvlddmkm.sys
    Loaded symbol image file: nvlddmkm.sys
    Symbol file: nvlddmkm.sys
    Image path: \SystemRoot\system32\DRIVERS\nvlddmkm.sys
    Timestamp:        Wed Aug 03 03:08:32 2011 (4E391010)
    CheckSum:         00C5B5DF
    ImageSize:        00C64000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4

------------------------------------------------------------------------------------------------------
If you want some extra information on it you can take a look here: http://msdn.microsoft.com/en-us/windows/hardware/gg487368

 

[dorchen]

VIDEO_TDR_FAILURE (0x116)

This indicates that an attempt to reset the display driver and recover from a timeout had failed. The default timeout value should be around 5 seconds.

Every one of your crash dumps points to the same error. You don't seem to be overclocking anything, your cpu cycles in at around 3.4 Ghz which is where it should be. I would check for updates to your NVidea driver firstly.

Overheating and powersupply issues could be possible causes. I would check your internal core temps to make sure that they aren't too high. To check for heating problems on your GPU I would suggest a program called CPU-Z which is available here: http://www.cpuid.com/softwares/cpu-z.html

You can also do a GPU Stress test here: http://www.ozone3d.net/benchmarks/fur/

Check for any warnings in device manager under the display area, and also your event viewer.

If we don't find an issue here, I would suggest that you also try running System File Checker to see if there's any corrupt system files. To use it, open command prompt and type this in:

sfc /scannow

Let it finish, and attempt to repair any corrupt or missing entries.

Last resort would be to try to reinstall your Nvidia Graphic driver using the Clean Install feature.

fffff880`0f430000 fffff880`10094000   nvlddmkm nvlddmkm.sys
    Loaded symbol image file: nvlddmkm.sys
    Symbol file: nvlddmkm.sys
    Image path: \SystemRoot\system32\DRIVERS\nvlddmkm.sys
    Timestamp:        Wed Aug 03 03:08:32 2011 (4E391010)
    CheckSum:         00C5B5DF
    ImageSize:        00C64000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4

------------------------------------------------------------------------------------------------------
If you want some extra information on it you can take a look here: http://msdn.microsoft.com/en-us/windows/hardware/gg487368

How do i solve heating problems?

 

[Ace]

You might want to look into some new fans for your system, or make sure the ones you have are working at least, and that they direct sufficient airflow to your CPU and GPU specifically. Otherwise you could go with an entirely new water cooling system, if you're willing to do some work there.

What did the other tests say? What did you try from my post above? Is it a confirmed heating issue? In this case you want to cool down your GPU somehow. If you don't have any fans for now, you could try opening the case, and pointing a big external fan directly at the area, and see if that helps at all. Make sure your computer is in a room with a window open so that the room temperatures aren't too warm for your computer to operate in as well.