Take the 2-minute tour ×
Super User is a question and answer site for computer enthusiasts and power users. It's 100% free, no registration required.

I have an MSI laptop that runs Windows 7 32 bit version. Recently it has a tendency to reboot when I come back to use it after the screen has switched off. When I get back, there is the blue screen and then it asks whether I want to reboot as normal.

I have tried to look at the crash dump files, but I must admit I am not that much closer to understand what the problem is. It happens a few times a day. Could it be related to the HDMI cable that I have recently purchased and occasionally plug in/out during the day in order to watch movies over the TV?

Here is an example of the crash dump file:

I would be really thankful if someone could throw in a bit of guidance as I'm rather lost at the moment...

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 (4 procs) Free x86 compatible Product: WinNt, suite: TerminalServer SingleUserTS Personal Built by: 7601.17727.x86fre.win7sp1_gdr.111118-2330 Machine Name: Kernel base = 0x83445000 PsLoadedModuleList = 0x8358e4d0 Debug session time: Thu Mar 15 10:36:50.622 2012 (UTC + 1:00) System Uptime: 0 days 11:47:40.074 Loading Kernel Symbols ............................................................... ................................................................ ......................... Loading User Symbols Loading unloaded module list ......

  • *
  • Bugcheck Analysis *
  • *

Use !analyze -v to get detailed debugging information.

BugCheck 1000008E, {c0000005, 93a83e86, 8d7f4684, 0}

Probably caused by : dxgkrnl.sys ( dxgkrnl!DMMVIDPNSOURCEMODE::GetGraphicsInfo+9 )

Followup: MachineOwner

0: kd> !analyze -v

  • *
  • Bugcheck Analysis *
  • *

KERNEL_MODE_EXCEPTION_NOT_HANDLED_M (1000008e) This is a very common bugcheck. Usually the exception address pinpoints the driver/function that caused the problem. Always note this address as well as the link date of the driver/image that contains this address. Some common problems are exception code 0x80000003. This means a hard coded breakpoint or assertion was hit, but this system was booted /NODEBUG. This is not supposed to happen as developers should never have hardcoded breakpoints in retail code, but ... If this happens, make sure a debugger gets connected, and the system is booted /DEBUG. This will let us see why this breakpoint is happening. Arguments: Arg1: c0000005, The exception code that was not handled Arg2: 93a83e86, The address that the exception occurred at Arg3: 8d7f4684, Trap Frame Arg4: 00000000

Debugging Details:

EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - Instruktionen ved 0x%08lx refererede hukommelse ved 0x%08lx. Hukommelsen kunne ikke %s.

FAULTING_IP: dxgkrnl!DMMVIDPNSOURCEMODE::GetGraphicsInfo+9 93a83e86 837e2401 cmp dword ptr [esi+24h],1

TRAP_FRAME: 8d7f4684 -- (.trap 0xffffffff8d7f4684) ErrCode = 00000000 eax=00000010 ebx=00000000 ecx=00000000 edx=91971018 esi=00000000 edi=9196d1b0 eip=93a83e86 esp=8d7f46f8 ebp=8d7f4700 iopl=0 nv up ei pl zr na pe nc cs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000 efl=00010246 dxgkrnl!DMMVIDPNSOURCEMODE::GetGraphicsInfo+0x9: 93a83e86 837e2401 cmp dword ptr [esi+24h],1 ds:0023:00000024=???????? Resetting default scope




PROCESS_NAME: csrss.exe


LAST_CONTROL_TRANSFER: from 93afc8b0 to 93a83e86

8d7f4700 93afc8b0 8d7f4a24 00000000 9196d07e dxgkrnl!DMMVIDPNSOURCEMODE::GetGraphicsInfo+0x9 8d7f4740 93afbadb 00000000 8d7f48c0 8d7f4a24 dxgkrnl!VIDPN_MGR::AddFunctionalPathToVidPnTopology+0x374 8d7f4a8c 93ad03f2 ffffffff 00000001 9196d07e dxgkrnl!VIDPN_MGR::RestorePresentPathToActiveVidPn+0x30e 8d7f4ad4 93ad0624 88fa6000 ffffffff 00000000 dxgkrnl!VIDPN_MGR::_MonitorEventHandler+0x2e7 8d7f4b08 93afd20b ffffffff 00000002 00000000 dxgkrnl!MONITOR_MGR::_IssueMonitorEvent+0xa4 8d7f4b3c 93afcfb0 ffffffff 00000001 00000002 dxgkrnl!MONITOR_MGR::_EnableDisableMonitor+0x24f 8d7f4b64 93af2f77 88fa6000 ffffffff 00000001 dxgkrnl!MonitorEnableDisableMonitor+0xfb 8d7f4bec 93af24fd 88fe1040 87f1c2c8 00000004 dxgkrnl!DpiGdoDispatchInternalIoctl+0x620 8d7f4c10 8347c5be 88fe1040 87f1c2c8 87f1c2c8 dxgkrnl!DpiDispatchInternalIoctl+0x86 8d7f4c28 98373d40 9196d07e ffbb74f8 9196d1b0 nt!IofCallDriver+0x63 8d7f4c54 98437f18 88fe1040 0023200f 8d7f4c90 win32k!GreDeviceIoControlEx+0x97 8d7f4c94 983919ef 00000001 00000000 00000007 win32k!DrvSetMonitorPowerState+0xe3 8d7f4cac 98391775 0000001e 89d21ab8 98413da2 win32k!PowerOnMonitor+0x43 8d7f4cfc 9838ec56 89d21ad0 0112f710 00000000 win32k!xxxUserPowerEventCalloutWorker+0x109 8d7f4d18 98413dbd 0000001e 0112f710 8d7f4d34 win32k!xxxUserPowerCalloutWorker+0x2d 8d7f4d28 8348328a 0000001e 0112f71c 77ad7094 win32k!NtUserCallNoParam+0x1b 8d7f4d28 77ad7094 0000001e 0112f71c 77ad7094 nt!KiFastCallEntry+0x12a WARNING: Frame IP not in any known module. Following frames may be wrong. 0112f71c 00000000 00000000 00000000 00000000 0x77ad7094


FOLLOWUP_IP: dxgkrnl!DMMVIDPNSOURCEMODE::GetGraphicsInfo+9 93a83e86 837e2401 cmp dword ptr [esi+24h],1




MODULE_NAME: dxgkrnl

IMAGE_NAME: dxgkrnl.sys



BUCKET_ID: 0x8E_dxgkrnl!DMMVIDPNSOURCEMODE::GetGraphicsInfo+9

Followup: MachineOwner

share|improve this question
csrss.exe is unfortunately a fairly deep kernel mode process, so it could be a lot of things. I'd suspect drivers - did you run any updates around the time this all started? –  Shinrai Mar 15 '12 at 17:35
Have you tried updating your video driver and directx? –  Phillip R. Mar 15 '12 at 20:02
Where do I update directx? I have tried poking around in Device Manager, and everything seems to be updated. I don't recall doing any updates at the time. Do you think it is software or hardware related? Should I try wiping the CPU clean and reinstall everything? –  Larsen Mar 16 '12 at 16:58
add comment

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Browse other questions tagged or ask your own question.