- tactlessbastard
- Feb 4, 2001
-
Godspeed, post
-
Fun Shoe
|
Problem description: I built a PC with the below specs. I'll walk away from it and when I come back, it won't wake up at a key touch or mouse movement, and seems to be powered down. When I press the main power button, the Windows login screen will quickly come up, but when I log in, after briefly flashing to the desktop, I get a blue screen with a loving emoticon on it and it says Windows needs to collect information and then it reboots. The error it cites is I think VIDEO_SCHEDULER_INTERNAL_ERROR but once it's gone on reboot, there's no bringing it back. After that, it works fine, until the next time I leave it alone. I've googled about event logging and found the Windows event viewer, and I've got 11 incidences in the past week of "Critical, Kernel-Power, Event ID: 41"
During normal use, the computer has given me no other problems.
Attempted fixes: I googled the error message but it didn't make sense to me, most results were about fixing this error during upgrades from 7 --> 8
Recent changes: New build.
Operating system: Windows 8.1 Pro 64bit. I should add that I am brand spanking new to Windows 8.1, my last PC was vista home version.
System specs:
**CPU** | [Intel Core i5-4590 3.3GHz Quad-Core Processor]
**Motherboard** | [MSI H97M-G43 Micro ATX LGA1150 Motherboard]
**Memory** | [Corsair Vengeance 8GB (2 x 4GB) DDR3-1600 Memory]
**Storage** | [Samsung 840 EVO 120GB 2.5" Solid State Drive]
**Storage** | [Western Digital Caviar Blue 1TB 3.5" 7200RPM Internal Hard Drive]
**Video Card** | [MSI Radeon R9 270 2GB TWIN FROZR Video Card]
**Case** | [Cooler Master N200 MicroATX Mid Tower Case]
**Power Supply** | [Corsair CSM 550W 80+ Gold Certified Semi-Modular ATX Power Supply]
**Optical Drive** | [Samsung SH-224DB/BEBE DVD/CD Writer]
**Wireless Network Adapter** | [Intel 62205ANHMWDTX1 802.11a/b/g/n PCI-Express x1 Wi-Fi Adapter]
Location: US
I have Googled and read the FAQ: Yes
I appreciate any advice.
|
#
?
Nov 21, 2014 03:01
|
|
- Adbot
-
ADBOT LOVES YOU
|
|
|
#
?
Apr 25, 2024 11:30
|
|
- Zarc
- Jul 25, 2014
-
|
Have done the usual stuff like making sure you have the latest mb bios and drivers for mb/graphics card? Are you overclocking the cpu at all? How's the airflow in your case? That vid card will dump most of the heat into the case. Have you checked what the temps are?
|
|
#
?
Nov 21, 2014 03:18
|
|
- tactlessbastard
- Feb 4, 2001
-
Godspeed, post
-
Fun Shoe
|
Have done the usual stuff like making sure you have the latest mb bios and drivers for mb/graphics card? Are you overclocking the cpu at all? How's the airflow in your case? That vid card will dump most of the heat into the case. Have you checked what the temps are?
I have updated the drivers for my graphics card and SSD, I had not done the motherboard. Will do so.
I am not overclocking. Airflow is good, temps are good. I keep the PC in a fairly cool room and the fans rarely spin up to full speed. They do, however when I'm stressing it.
|
|
#
?
Nov 21, 2014 03:34
|
|
- Zarc
- Jul 25, 2014
-
|
Do you happen to have Cyberlink installed by chance? I found references to it being very buggy and causing the video error. The power event is just windows detecting an improper shutdown. It's also quite possible you have a bad video card. I found a reference to cards using this particular ati chip having some out of box failures. (more than normal)
|
|
#
?
Nov 21, 2014 03:46
|
|
- tactlessbastard
- Feb 4, 2001
-
Godspeed, post
-
Fun Shoe
|
Do you happen to have Cyberlink installed by chance? I found references to it being very buggy and causing the video error. The power event is just windows detecting an improper shutdown. It's also quite possible you have a bad video card. I found a reference to cards using this particular ati chip having some out of box failures. (more than normal)
No Cyberlink. I don't think it's a bad graphics card, games are playing fine and there are no visual defects. I got the MSI MB program, updated my bios from 2.2 to 2.6, and am downloading all the various other MB drivers which I did not get initially because I am a big smelly moron.
|
|
#
?
Nov 21, 2014 03:50
|
|
- Zarc
- Jul 25, 2014
-
|
I found this link on microsoft's site
http://answers.microsoft.com/en-us/...67-761cfa58ee05
I'm not that great at looking at .dmp files, but if you can get one, somebody here might be able to give more insight as well.
|
|
#
?
Nov 21, 2014 03:57
|
|
- tactlessbastard
- Feb 4, 2001
-
Godspeed, post
-
Fun Shoe
|
I'm downloading the SDK so I can get .dmp files, it's going to take a while. Meanwhile, i've updated a lot of drivers on the motherboard so hopefully that got it. I'll report back if it happens again. Thanks, Zarc.
|
|
#
?
Nov 21, 2014 04:24
|
|
- tactlessbastard
- Feb 4, 2001
-
Godspeed, post
-
Fun Shoe
|
The error happened again during the night. I searched for .dmp and found only memory.dmp on the C: drive. I opened it with WinDbg (after copying it to the desktop, I didn't have permission to open it when it was in it's folder (thanks, google!)).
Here's the contents:
code:
Microsoft (R) Windows Debugger Version 6.3.9600.17298 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [C:\Users\A\Desktop\MEMORY.DMP]
Kernel Bitmap Dump File: Only kernel address space is available
Symbol search path is: *** Invalid ***
****************************************************************************
* Symbol loading may be unreliable without a symbol search path. *
* Use .symfix to have the debugger choose a symbol path. *
* After setting your symbol path, use .reload to refresh symbol locations. *
****************************************************************************
Executable search path is:
*********************************************************************
* Symbols can not be loaded because symbol path is not initialized. *
* *
* The Symbol Path can be set by: *
* using the _NT_SYMBOL_PATH environment variable. *
* using the -y <symbol_path> argument when starting the debugger. *
* using .sympath and .sympath+ *
*********************************************************************
*** ERROR: Symbol file could not be found. Defaulted to export symbols for ntkrnlmp.exe -
Windows 8 Kernel Version 9600 MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 9600.17328.amd64fre.winblue_r3.140827-1500
Machine Name:
Kernel base = 0xfffff803`3c07a000 PsLoadedModuleList = 0xfffff803`3c350370
Debug session time: Fri Nov 21 08:21:27.802 2014 (UTC - 6:00)
System Uptime: 0 days 11:07:40.447
*********************************************************************
* Symbols can not be loaded because symbol path is not initialized. *
* *
* The Symbol Path can be set by: *
* using the _NT_SYMBOL_PATH environment variable. *
* using the -y <symbol_path> argument when starting the debugger. *
* using .sympath and .sympath+ *
*********************************************************************
*** ERROR: Symbol file could not be found. Defaulted to export symbols for ntkrnlmp.exe -
Loading Kernel Symbols
...............................................................
................................................................
..................
Loading User Symbols
PEB is paged out (Peb.Ldr = 00007ff7`e5b4a018). Type ".hh dbgerr001" for details
Loading unloaded module list
...................
************* Symbol Loading Error Summary **************
Module name Error
ntkrnlmp The system cannot find the file specified
You can troubleshoot most symbol related issues by turning on symbol loading diagnostics (!sym noisy) and repeating the command that caused symbols to be loaded.
You should also verify that your symbol search path (.sympath) is correct.
*** ERROR: Symbol file could not be found. Defaulted to export symbols for watchdog.sys -
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 10E, {2, 0, 0, 0}
*** ERROR: Symbol file could not be found. Defaulted to export symbols for dxgmms1.sys -
*** ERROR: Symbol file could not be found. Defaulted to export symbols for dxgkrnl.sys -
Page 107bb8 not present in the dump file. Type ".hh dbgerr004" for details
*** ERROR: Symbol file could not be found. Defaulted to export symbols for win32k.sys -
***** Kernel symbols are WRONG. Please fix symbols to do analysis.
*************************************************************************
*** ***
*** ***
*** Either you specified an unqualified symbol, or your debugger ***
*** doesn't have full symbol information. Unqualified symbol ***
*** resolution is turned off by default. Please either specify a ***
*** fully qualified symbol module!symbolname, or enable resolution ***
*** of unqualified symbols by typing ".symopt- 100". Note that ***
*** enabling unqualified symbol resolution with network symbol ***
*** server shares in the symbol path may cause the debugger to ***
*** appear to hang for long periods of time when an incorrect ***
*** symbol name is typed or the network symbol server is down. ***
*** ***
*** For some commands to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!_KPRCB ***
*** ***
*************************************************************************
code:
Probably caused by : dxgmms1.sys ( dxgmms1!VidMmInterface+34d2a )
Followup: MachineOwner
---------
tactlessbastard fucked around with this message at 15:38 on Nov 21, 2014
|
|
#
?
Nov 21, 2014 15:36
|
|
- tactlessbastard
- Feb 4, 2001
-
Godspeed, post
-
Fun Shoe
|
Ok, sorry about that, I got my symbols figured out.
code:Microsoft (R) Windows Debugger Version 6.3.9600.17298 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [C:\Windows\MEMORY.DMP]
Kernel Bitmap Dump File: Only kernel address space is available
************* Symbol Path validation summary **************
Response Time (ms) Location
Deferred SRV*C:\Windows\symbol_cache*[url]http://msdl.microsoft.com/download/symbols[/url]
Symbol search path is: SRV*C:\Windows\symbol_cache*[url]http://msdl.microsoft.com/download/symbols[/url]
Executable search path is:
Windows 8 Kernel Version 9600 MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 9600.17328.amd64fre.winblue_r3.140827-1500
Machine Name:
Kernel base = 0xfffff803`3c07a000 PsLoadedModuleList = 0xfffff803`3c350370
Debug session time: Fri Nov 21 08:21:27.802 2014 (UTC - 6:00)
System Uptime: 0 days 11:07:40.447
Loading Kernel Symbols
...............................................................
................................................................
..................
Loading User Symbols
PEB is paged out (Peb.Ldr = 00007ff7`e5b4a018). Type ".hh dbgerr001" for details
Loading unloaded module list
...................
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 10E, {2, 0, 0, 0}
Page 107bb8 not present in the dump file. Type ".hh dbgerr004" for details
Probably caused by : dxgmms1.sys ( dxgmms1!VIDMM_PROCESS_HEAP::~VIDMM_PROCESS_HEAP+1406a )
Followup: MachineOwner
---------
|
|
#
?
Nov 21, 2014 15:43
|
|
- r0ck0
- Sep 12, 2004
-
r0ck0s p0zt m0d3rn lyf
|
quote:Probably caused by : dxgmms1.sys ( dxgmms1!VIDMM_PROCESS_HEAP::~VIDMM_PROCESS_HEAP+1406a )
Blue screen in dxgmms1.sys
http://answers.microsoft.com/en-us/windows/forum/windows_7-system/blue-screen-in-dxgmms1sys/db3f0576-976f-4401-8793-40f01942fb9d
|
|
#
?
Nov 21, 2014 16:21
|
|
- tactlessbastard
- Feb 4, 2001
-
Godspeed, post
-
Fun Shoe
|
I have updated the MB and GPU drivers.
code:Microsoft (R) Windows Debugger Version 6.3.9600.17298 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [C:\Windows\MEMORY.DMP]
Kernel Bitmap Dump File: Only kernel address space is available
************* Symbol Path validation summary **************
Response Time (ms) Location
Deferred SRV*C:\Windows\symbol_cache*[url]http://msdl.microsoft.com/download/symbols[/url]
Symbol search path is: SRV*C:\Windows\symbol_cache*[url]http://msdl.microsoft.com/download/symbols[/url]
Executable search path is:
Windows 8 Kernel Version 9600 MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 9600.17328.amd64fre.winblue_r3.140827-1500
Machine Name:
Kernel base = 0xfffff802`d5617000 PsLoadedModuleList = 0xfffff802`d58ed370
Debug session time: Fri Nov 21 17:52:53.777 2014 (UTC - 6:00)
System Uptime: 0 days 4:57:55.423
Loading Kernel Symbols
...............................................................
................................................................
.........................
Loading User Symbols
PEB is paged out (Peb.Ldr = 00007ff7`4bdec018). Type ".hh dbgerr001" for details
Loading unloaded module list
...............
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 10E, {2, 0, 0, 0}
Page 11e1e2 not present in the dump file. Type ".hh dbgerr004" for details
Probably caused by : dxgmms1.sys ( dxgmms1!VIDMM_PROCESS_HEAP::~VIDMM_PROCESS_HEAP+1406a )
Followup: MachineOwner
---------
3: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
VIDEO_MEMORY_MANAGEMENT_INTERNAL (10e)
The video memory manager encountered a condition that it can't recover from. By crashing,
the video memory manager is attempting to get enough information into the minidump such that
somebody can pinpoint what lead to this condition.
Arguments:
Arg1: 0000000000000002, Process heap being destroyed isn't empty.
Arg2: 0000000000000000
Arg3: 0000000000000000
Arg4: 0000000000000000
Debugging Details:
------------------
BUGCHECK_STR: 0x10e_2
DEFAULT_BUCKET_ID: WIN8_DRIVER_FAULT
PROCESS_NAME: LogonUI.exe
CURRENT_IRQL: 0
ANALYSIS_VERSION: 6.3.9600.17298 (debuggers(dbg).141024-1500) amd64fre
LAST_CONTROL_TRANSFER: from fffff800abbb99ca to fffff802d57661a0
STACK_TEXT:
ffffd000`21250638 fffff800`abbb99ca : 00000000`0000010e 00000000`00000002 00000000`00000000 00000000`00000000 : nt!KeBugCheckEx
ffffd000`21250640 fffff800`abcdacea : ffffe000`d5877df0 00000000`00000002 00000000`00000004 fffff800`6d4d6956 : watchdog!WdLogEvent5_WdCriticalError+0xce
ffffd000`21250680 fffff800`abcc6c66 : ffffe000`d5877df0 ffffd000`212507c9 ffffe000`d1bf9cc0 ffffe000`d4af7580 : dxgmms1!VIDMM_PROCESS_HEAP::~VIDMM_PROCESS_HEAP+0x1406a
ffffd000`212506b0 fffff800`abc9651e : ffffc000`c1eeb010 ffffc000`c10a90e0 ffffc000`c10a90e0 ffffd000`212507c9 : dxgmms1!VIDMM_PROCESS::~VIDMM_PROCESS+0x52
ffffd000`212506e0 fffff800`abc9650a : ffffc000`c10a9148 ffffc000`c10a90e0 ffffd000`21250770 fffff802`68536956 : dxgmms1!VIDMM_PROCESS::`scalar deleting destructor'+0xe
ffffd000`21250710 fffff800`aba3c215 : ffffe000`d181d7d0 00000000`00000000 00000000`00000400 fffff802`d5670efb : dxgmms1!VidMmTerminateProcess+0xe
ffffd000`21250740 fffff800`abaa6722 : ffffc000`c10a90e0 00000000`00000400 ffffc000`c10a90e0 fffff960`004c0f60 : dxgkrnl!VIDMM_EXPORT::VidMmTerminateProcess+0x3d
ffffd000`21250770 fffff800`aba92655 : ffffd001`7e5c0180 ffffc000`c10a90e0 fffff901`400c3108 00000000`00000000 : dxgkrnl!DXGPROCESS::Destroy+0xce
ffffd000`21250830 fffff960`00177e83 : 00000000`00000414 ffffd000`21250a20 fffff901`400c3010 ffffe000`d65a86c0 : dxgkrnl!DxgkProcessCallout+0x135
ffffd000`21250890 fffff960`00179353 : fffff901`400c3010 ffffe000`d65a86c0 ffffd000`212509c0 ffffe000`d4074740 : win32k!GdiProcessCallout+0x1f7
ffffd000`21250910 fffff802`d59fa40a : ffffd000`21250a20 ffffd000`212509c0 00000000`00000000 00060030`00010002 : win32k!W32pProcessCallout+0x53
ffffd000`21250940 fffff802`d59f9620 : ffffe000`d2fb4e40 00000000`00000000 00000000`00000000 ffffe000`d65a8988 : nt!PsInvokeWin32Callout+0x42
ffffd000`21250980 fffff802`d59bc9fd : 00000000`00000000 00000000`00000000 ffffe000`d65a86c0 ffffe000`d4074740 : nt!PspExitThread+0x518
ffffd000`21250a90 fffff802`d57719b3 : ffffe000`d65a86c0 ffffe000`d4074740 ffffd000`21250b80 00000032`fb3e1d90 : nt!NtTerminateProcess+0xfd
ffffd000`21250b00 00007ff8`7fb6193a : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
00000032`fb16fb38 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x00007ff8`7fb6193a
STACK_COMMAND: kb
FOLLOWUP_IP:
dxgmms1!VIDMM_PROCESS_HEAP::~VIDMM_PROCESS_HEAP+1406a
fffff800`abcdacea 90 nop
SYMBOL_STACK_INDEX: 2
SYMBOL_NAME: dxgmms1!VIDMM_PROCESS_HEAP::~VIDMM_PROCESS_HEAP+1406a
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: dxgmms1
IMAGE_NAME: dxgmms1.sys
DEBUG_FLR_IMAGE_TIMESTAMP: 53183e46
IMAGE_VERSION: 6.3.9600.17041
BUCKET_ID_FUNC_OFFSET: 1406a
FAILURE_BUCKET_ID: 0x10e_2_dxgmms1!VIDMM_PROCESS_HEAP::_VIDMM_PROCESS_HEAP
BUCKET_ID: 0x10e_2_dxgmms1!VIDMM_PROCESS_HEAP::_VIDMM_PROCESS_HEAP
ANALYSIS_SOURCE: KM
FAILURE_ID_HASH_STRING: km:0x10e_2_dxgmms1!vidmm_process_heap::_vidmm_process_heap
FAILURE_ID_HASH: {e0ffb3d2-60cf-6759-819f-14e8b85f5be5}
Followup: MachineOwner
---------
|
|
#
?
Nov 22, 2014 00:57
|
|
- Adbot
-
ADBOT LOVES YOU
|
|
|
#
?
Apr 25, 2024 11:30
|
|
- Zarc
- Jul 25, 2014
-
|
I found this link.
http://msdn.microsoft.com/en-us/library/windows/hardware/ff557275%28v=vs.85%29.aspx
With the dmp seeming to point to an issue in video memory process heap, I strongly suspect some of the onboard video ram on your graphics card is bad.
If you can borrow another card to test with (and make sure you clean the drivers appropriately), that could confirm it. I'm unaware of a reliable gpu memory tester (only one I've heard about has a very high false positive rate), though if anybody else can recommend one, you can try that to confirm it as well. Short of that, RMA the card.
|
|
#
?
Nov 22, 2014 04:56
|
|
#
?
Nov 21, 2014 03:01
