Intel HD 2000 (i5-2400) locks up entire system?

[RChew1]

Hi All,

Ever since I've been using the integrated graphics on my motherboard, I've been experiencing weird lock-ups that happens seemingly randomly. Previously, I was using a Radeon 5850 dedicated graphics card, but decided to hook up a secondary monitor to the onboard graphics to aid in my work.

When the system locks up, I cannot do anything at all, everything just freezes, mouse cursor and all. Even the reset button doesn't work--I have to press and hold the power button for 4 seconds to turn it off. The HDD LED dies.

Only once was I able to get a BSOD, and here is my minidump:

*******************************************************************************

* *

* Bugcheck Analysis *

* *

*******************************************************************************

DPC_WATCHDOG_VIOLATION (133)

The DPC watchdog detected a prolonged run time at an IRQL of DISPATCH_LEVEL

or above.

Arguments:

Arg1: 0000000000000001, The system cumulatively spent an extended period of time at

DISPATCH_LEVEL or above. The offending component can usually be

identified with a stack trace.

Arg2: 0000000000000780, The watchdog period.

Arg3: 0000000000000000

Arg4: 0000000000000000

Debugging Details:

------------------

DPC_TIMEOUT_TYPE: DPC_QUEUE_EXECUTION_TIMEOUT_EXCEEDED

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: WIN8_DRIVER_FAULT

BUGCHECK_STR: 0x133

PROCESS_NAME: firefox.exe

CURRENT_IRQL: d

LAST_CONTROL_TRANSFER: from fffff800da5da19b to fffff800da481340

STACK_TEXT:

fffff880`06b14d38 fffff800`da5da19b : 00000000`00000133 00000000`00000001 00000000`00000780 00000000`00000000 : nt!KeBugCheckEx

fffff880`06b14d40 fffff800`da4ac011 : 00000000`00000002 fffff880`02cd1180 fffff880`06b14ef0 fffff780`00000320 : nt! ?? ::FNODOBFM::`string'+0x13ca8

fffff880`06b14dc0 fffff800`da4ace97 : ffffffff`ffd0d9a0 fffffa80`06c0050c fffff880`06b14ef0 00000000`00000000 : nt!KeUpdateRunTime+0x51

fffff880`06b14df0 fffff800`dab71eca : ffffffff`ffd0d9a0 fffffa80`06c0050c 00000000`34ed466d 00000000`c0000002 : nt!KeUpdateTime+0x3f9

fffff880`06b14fe0 fffff800`da47a7ee : 0000000f`b7c520e4 00000000`36b10ff5 fffffa80`06c00580 fffff880`046ea08f : hal!HalpTimerClockInterrupt+0x86

fffff880`06b15010 fffff800`da537bc1 : 00000000`00000050 00000000`00000001 00000000`00000242 00000000`00000000 : nt!KiInterruptDispatchLBControl+0x1ce

fffff880`06b151a0 fffff800`da53b65a : fffffa80`044c9700 00000000`00000002 00000000`00000001 fffff880`06b15211 : nt!KeInvalidateRangeAllCaches+0x96

fffff880`06b151e0 fffff800`da4c9f97 : 00000000`00000002 fffff880`06b15280 00000000`00000380 fffff880`1faedd6c : nt!MiChangePageAttribute+0x16a

fffff880`06b15230 fffff800`da4cb5cb : 00000000`00000001 00000000`1dfc1000 fffff880`06b15611 fffff880`06b15548 : nt!MiResolveDemandZeroFault+0xa67

fffff880`06b15350 fffff800`da4bba28 : fffffa80`093f4080 00000000`1dfc1000 fffffa80`093f4080 fffff880`06b15500 : nt!MiDispatchFault+0xae6

fffff880`06b15490 fffff800`da4d386a : 00000000`00000001 ffffffff`ffffffff 00000000`00000000 fffff880`06b15611 : nt!MmAccessFault+0x288

fffff880`06b155d0 fffff800`da4d332e : 00000000`00000000 fffffa80`093f4080 fffffa80`0ceff5b0 fffff800`da690e70 : nt!MiProbeLeafFrame+0x24a

fffff880`06b156d0 fffff880`0364b3ec : fffff880`06b15901 fffff880`06b15700 00000000`00000000 00000000`1dfc1000 : nt!MmProbeAndLockPages+0x14e

fffff880`06b15790 fffff880`0364a4f8 : fffff8a0`051eabf0 fffff8a0`051ead50 fffffa80`06ae6000 fffff880`00000002 : dxgmms1!VIDMM_SEGMENT::SafeProbeAndLockPages+0x1bc

fffff880`06b15840 fffff880`036450d0 : fffffa80`06ae6000 fffff8a0`051eabf0 fffff8a0`051eabf0 00000000`00000000 : dxgmms1!VIDMM_SEGMENT::LockAllocationBackingStore+0xf4

fffff880`06b158c0 fffff880`03638289 : fffff8a0`051eabf0 00000000`00000000 fffffa80`06ae6c68 fffff880`03637f83 : dxgmms1!VIDMM_APERTURE_SEGMENT::CommitResource+0xcc

fffff880`06b15910 fffff880`0363bdba : fffffa80`06ae6000 fffff880`06b159d8 00000000`00000000 00000000`00000000 : dxgmms1!VIDMM_GLOBAL::PageInAllocations+0xb9

fffff880`06b15970 fffff880`03636361 : fffff8a0`051eabf0 fffffa80`0731ff70 fffffa80`06ae6000 fffff880`0361ac66 : dxgmms1!VIDMM_GLOBAL::PageInOneAllocation+0x102

fffff880`06b159d0 fffff880`036358e3 : 00000000`00000000 fffffa80`099053e0 00000000`0000000f 00000000`0000000f : dxgmms1!VIDMM_GLOBAL::ProcessDeferredCommand+0x395

fffff880`06b15b40 fffff880`03650909 : 00000000`00000000 fffff880`0361f875 fffffa80`0c1f7750 fffff880`03652f0f : dxgmms1!VidMmiProcessSystemCommand+0x23

fffff880`06b15b70 fffff880`0364fb47 : fffffa80`06aabbf0 fffff880`0364f57c fffff780`00000320 fffff800`da406000 : dxgmms1!VidSchiSubmitSystemCommand+0x71

fffff880`06b15ba0 fffff880`0364f662 : fffffa80`06aadc70 fffffa80`06aabbf0 fffffa80`0af0cb90 fffffa80`09905010 : dxgmms1!VidSchiSubmitQueueCommand+0x73

fffff880`06b15bd0 fffff800`da428551 : fffffa80`093f4080 fffffa80`09905010 fffff800`da756880 00000000`0414d156 : dxgmms1!VidSchiWorkerThread+0xe6

fffff880`06b15c10 fffff800`da466dd6 : fffff800`da6fc180 fffffa80`093f4080 fffff800`da756880 fffffa80`069a0680 : nt!PspSystemThreadStartup+0x59

fffff880`06b15c60 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiStartSystemThread+0x16

STACK_COMMAND: kb

FOLLOWUP_IP:

dxgmms1!VIDMM_SEGMENT::SafeProbeAndLockPages+1bc

fffff880`0364b3ec 90 nop

SYMBOL_STACK_INDEX: d

SYMBOL_NAME: dxgmms1!VIDMM_SEGMENT::SafeProbeAndLockPages+1bc

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: dxgmms1

IMAGE_NAME: dxgmms1.sys

DEBUG_FLR_IMAGE_TIMESTAMP: 505ab2a9

BUCKET_ID_FUNC_OFFSET: 1bc

FAILURE_BUCKET_ID: 0x133_ISR_dxgmms1!VIDMM_SEGMENT::SafeProbeAndLockPages

BUCKET_ID: 0x133_ISR_dxgmms1!VIDMM_SEGMENT::SafeProbeAndLockPages

Followup: MachineOwner

---------

I have tried the following:

- Reinstalling Windows 8

- Reinstalling the Intel HD drivers

- Uninstalling AMD Catalyst drivers and running solely on Intel HD

It happens on random occasions, once while I was browsing the web, and another time while in MS Word. Most oftenly, it happens while playing an Adobe Flash video. I have not overclocked or under/overvolted my CPU. Temperatures seem to be fine. It does not happen at all while I am hooked up to my dedicated graphics card, leading me to think that the problem lies with my Intel HD graphics. I am running on VGA input on my Intel graphics and DVI on my Radeon 5850.

Any help would be greatly appreciated!

Here are my system specs:

Intel i5-2400 w/ Asrock Z68 Extreme4 2.23 BIOS (latest)

2x4GB DDR-1333 Value RAMs (memtested to be fine)

Sapphire Radeon 5850

Crucial m4 128GB SSD (updated to latest firmware)

Samsung SpinPoint F3 1TB

WD Green 500GB

Seagate Barracuda 7200.11 320GB

Creative Sound Blaster Audigy 2 ZS

[Fred_D_Intel]

Hi Reuben,

You can try using the latest graphics driver we have available in our website. This is the link to the driver http://downloadcenter.intel.com/Detail_Desc.aspx?agr=Y&DwnldID=22375&lang=eng&OSVersion=Windows%208%2C%2064-bit*&DownloadType=%0A%09%09%09%09%09%09%09Drivers%0A%09%09%09%09%09%09

You can run the Intel Processor Diagnostic Tool in order to check if the issue is being caused by the processor itself or not. This is the link to the tool http://www.intel.com/support/processors/sb/CS-031726.htm http://www.intel.com/support/processors/sb/CS-031726.htm

Thanks!