Sign in with
Sign up | Sign in
Your question
Solved

Blue screen when shut down, psu or windows service pack update? plz help

Tags:
  • Blue Screen
  • windows service pace update
  • Components
  • psu
Last response: in Components
Share
April 21, 2014 8:25:06 AM

Sorry if this isn't in the correct category. My newly built pc blue screened on me while shutting down. I't has been running great, Ive played at least 5-6 hours of League of Legends on med high settings and have tested highest settings. All worked great, no hickups, nothing had gone wrong at all while under load. This makes me believe my psu is fine but I would like a second opinion. This morning when I booted my rig back up, windows started to configure a service pack update in three stages. This lead me to believe that the downloaded update had something to do with the seemingly random blue screen but idk. Any 2 cents or help would be greatly appreciated.

Here's my build specs
ASUS|M5A97 R2.0 970 AM3+
AMD|8-CORE FX-8350 @ 4.0Ghz w/ Cooler Master Hyper 212 EVO
PowerColor|Radeon R7 260X 1GB 128-Bit GDDR5
G.SKILL Ripjaws X Series 2 x 4GB DDR3
Kingston HyperX 3K 2.5" 120GB SATA III SSD
Rosewill Stallion Series RD600 600W ATX12V

More about : blue screen shut psu windows service pack update plz

April 21, 2014 10:13:32 AM

1 Rosewill Stallion Series RD600 ... not really good psu

2 Kingston HyperX 3K 2.5" 120GB SATA III SSD ....not the best ssd for sure

3 go in the bios screen at the really begining of system boot by tap the delete button and
see if everything is detected and normal , check if the boot options still in good configuration.

check if it still somes other updates to do with windows update and restart it maybe 2 or 3 times to correctly installed thoses updates

m
0
l
April 21, 2014 11:00:12 AM

If you are getting a blue screen then you can probably find out the cause from the crash dump.

* Right click on "Computer" and select "properties". Go to Advanced System Settings (which opens System Properties) > [Advanced] tab > under "Startup and Recovery" category, pick "Settings..."
* Make sure "Write an event to system log" is checked and "Kernal memory" dump is selected. The dump file location is probably listed as "%SystemRoot%\MEMORY.DMP ... which is the C:\Windows directory.
* If all of this is already turn on, then go looking for the C:\Windows\MEMORY.DMP file. If the date on the file is the same date as your last blue screen, then the system might have created a dump of the crash... which might be the key to finding the problem.

Once you have the crash dump, this page explains how to read it:
http://www.instructables.com/id/How-to-Analyze-a-BSOD-C...
After you get to the second page, and click on the analyze link and post the results.
m
0
l
Related resources
April 21, 2014 9:23:11 PM

completed any updates from WU and got the dump analysis.

Microsoft (R) Windows Debugger Version 6.3.9600.17029 X86
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Windows\MEMORY.DMP]
Kernel Summary Dump File: Only kernel address space is available


************* Symbol Path validation summary **************
Response Time (ms) Location
Deferred SRV*C:\Windows\symbol_cache*http://msdl.microsoft.com/download/symbols
Symbol search path is: SRV*C:\Windows\symbol_cache*http://msdl.microsoft.com/download/symbols
Executable search path is:
Windows 7 Kernel Version 7600 MP (8 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 7600.17273.amd64fre.win7_gdr.130318-1532
Machine Name:
Kernel base = 0xfffff800`02e01000 PsLoadedModuleList = 0xfffff800`0303de70
Debug session time: Mon Apr 21 01:54:51.148 2014 (UTC - 4:00)
System Uptime: 1 days 10:31:45.629
Loading Kernel Symbols
...............................................................
..............................................................Page 22015c not present in the dump file. Type ".hh dbgerr004" for details
..
.....................Page 14199d not present in the dump file. Type ".hh dbgerr004" for details
..
Loading User Symbols
PEB is paged out (Peb.Ldr = 000007ff`fffd3018). Type ".hh dbgerr001" for details
Loading unloaded module list
.......
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 3B, {c0000005, fffff960000d6483, fffff880035fe070, 0}

Page 222a4e not present in the dump file. Type ".hh dbgerr004" for details
Page 224cf8 not present in the dump file. Type ".hh dbgerr004" for details
Probably caused by : win32k.sys ( win32k!HmgLockEx+a3 )

Followup: MachineOwner
---------
m
0
l
April 21, 2014 11:40:23 PM

''3 go in the bios screen at the really begining of system boot by tap the delete button and
see if everything is detected and normal , check if the boot options still in good configuration.''

SO??
m
0
l
April 22, 2014 9:33:02 AM

Sorry about that I knew I should of got the details, here's the full analysis. My UEFI BIOS is fine, every thing checks out good and the system has been running smooth.


Microsoft (R) Windows Debugger Version 6.3.9600.17029 X86
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Windows\MEMORY.DMP]
Kernel Summary Dump File: Only kernel address space is available


************* Symbol Path validation summary **************
Response Time (ms) Location
Deferred SRV*C:\Windows\symbol_cache*http://msdl.microsoft.com/download/symbols
Symbol search path is: SRV*C:\Windows\symbol_cache*http://msdl.microsoft.com/download/symbols
Executable search path is:
Windows 7 Kernel Version 7600 MP (8 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 7600.17273.amd64fre.win7_gdr.130318-1532
Machine Name:
Kernel base = 0xfffff800`02e01000 PsLoadedModuleList = 0xfffff800`0303de70
Debug session time: Mon Apr 21 01:54:51.148 2014 (UTC - 4:00)
System Uptime: 1 days 10:31:45.629
Loading Kernel Symbols
...............................................................
..............................................................Page 22015c not present in the dump file. Type ".hh dbgerr004" for details
..
.....................Page 14199d not present in the dump file. Type ".hh dbgerr004" for details
..
Loading User Symbols
PEB is paged out (Peb.Ldr = 000007ff`fffd3018). Type ".hh dbgerr001" for details
Loading unloaded module list
.......
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 3B, {c0000005, fffff960000d6483, fffff880035fe070, 0}

Page 222a4e not present in the dump file. Type ".hh dbgerr004" for details
Page 224cf8 not present in the dump file. Type ".hh dbgerr004" for details
Probably caused by : win32k.sys ( win32k!HmgLockEx+a3 )

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

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

SYSTEM_SERVICE_EXCEPTION (3b)
An exception happened while executing a system service routine.
Arguments:
Arg1: 00000000c0000005, Exception code that caused the bugcheck
Arg2: fffff960000d6483, Address of the instruction which caused the bugcheck
Arg3: fffff880035fe070, Address of the context record for the exception that caused the bugcheck
Arg4: 0000000000000000, zero.

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


EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.

FAULTING_IP:
win32k!HmgLockEx+a3
fffff960`000d6483 0fb7430c movzx eax,word ptr [rbx+0Ch]

CONTEXT: fffff880035fe070 -- (.cxr 0xfffff880035fe070;r)
rax=fffff900c0200000 rbx=0000000000000000 rcx=fffffa8007466a20
rdx=fffff900c0200000 rsi=0000000000000000 rdi=fffff900c0200000
rip=fffff960000d6483 rsp=fffff880035fea40 rbp=0000000000000000
r8=0000000000000001 r9=0000000000000000 r10=0000000000000000
r11=fffff880035feaa8 r12=0000000003f69200 r13=0000000000000000
r14=0000000000000001 r15=0000000000000001
iopl=0 nv up ei pl zr na po nc
cs=0010 ss=0018 ds=002b es=002b fs=0053 gs=002b efl=00010246
win32k!HmgLockEx+0xa3:
fffff960`000d6483 0fb7430c movzx eax,word ptr [rbx+0Ch] ds:002b:00000000`0000000c=????
Last set context:
rax=fffff900c0200000 rbx=0000000000000000 rcx=fffffa8007466a20
rdx=fffff900c0200000 rsi=0000000000000000 rdi=fffff900c0200000
rip=fffff960000d6483 rsp=fffff880035fea40 rbp=0000000000000000
r8=0000000000000001 r9=0000000000000000 r10=0000000000000000
r11=fffff880035feaa8 r12=0000000003f69200 r13=0000000000000000
r14=0000000000000001 r15=0000000000000001
iopl=0 nv up ei pl zr na po nc
cs=0010 ss=0018 ds=002b es=002b fs=0053 gs=002b efl=00010246
win32k!HmgLockEx+0xa3:
fffff960`000d6483 0fb7430c movzx eax,word ptr [rbx+0Ch] ds:002b:00000000`0000000c=????
Resetting default scope

DEFAULT_BUCKET_ID: WIN7_DRIVER_FAULT

BUGCHECK_STR: 0x3B

PROCESS_NAME: dwm.exe

CURRENT_IRQL: 0

ANALYSIS_VERSION: 6.3.9600.17029 (debuggers(dbg).140219-1702) x86fre

LAST_CONTROL_TRANSFER: from fffff96000292620 to fffff960000d6483

STACK_TEXT:
fffff880`035fea40 fffff960`00292620 : fffff900`c2207e40 00000000`00000001 00000000`0d1212e5 fffff900`c235fcd0 : win32k!HmgLockEx+0xa3
fffff880`035feab0 fffff960`00291b1e : fffff900`c2207e40 00000000`00000000 000012e5`00000000 00000000`00000000 : win32k!SFMLOGICALSURFACE::o wnsSurfaceCleanup+0x40
fffff880`035feae0 fffff960`00292a23 : 00000000`00000000 00000000`0d1212e5 fffff900`c2207e40 00000000`03f6923c : win32k!SFMLOGICALSURFACE::D eInitialize+0x4e
fffff880`035feb20 fffff960`001ef197 : 00000000`00000000 fffff900`c00be010 fffff900`c2207e40 00000000`00000020 : win32k!bhLSurfDestroyLogicalSurfaceObject+0x4b
fffff880`035feb60 fffff960`002106e8 : 00000000`00000001 00000000`00000001 fffff880`035feca0 00000000`00000000 : win32k!GreSfmCloseCompositorRef+0x10f
fffff880`035feba0 fffff800`02e6fad3 : fffffa80`07466a20 fffff880`035feca0 00000000`00000008 00000000`03f6923c : win32k!NtGdiHLSurfSetInformation+0x1a8
fffff880`035fec20 000007fe`ff4b4efa : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
00000000`01cff248 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x000007fe`ff4b4efa


FOLLOWUP_IP:
win32k!HmgLockEx+a3
fffff960`000d6483 0fb7430c movzx eax,word ptr [rbx+0Ch]

SYMBOL_STACK_INDEX: 0

SYMBOL_NAME: win32k!HmgLockEx+a3

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: win32k

IMAGE_NAME: win32k.sys

DEBUG_FLR_IMAGE_TIMESTAMP: 5130212e

IMAGE_VERSION: 6.1.7600.17266

STACK_COMMAND: .cxr 0xfffff880035fe070 ; kb

FAILURE_BUCKET_ID: X64_0x3B_win32k!HmgLockEx+a3

BUCKET_ID: X64_0x3B_win32k!HmgLockEx+a3

ANALYSIS_SOURCE: KM

FAILURE_ID_HASH_STRING: km:x64_0x3b_win32k!hmglockex+a3

FAILURE_ID_HASH: {8f81bb6a-de67-bc4d-99db-3f117a68551c}

Followup: MachineOwner
---------
m
0
l

Best solution

April 22, 2014 10:51:20 AM

Thanks... well I'm not really certain from that, but here's a decent guess:
Quote:
Probably caused by : win32k.sys ( win32k!HmgLockEx+a3 )

It might be caused by a driver, since this file is related to handling drivers.
http://www.computerhope.com/cgi-bin/process.pl?p=win32k...
However, based on some forum post(s) I read, it could also be Windows itself (maybe it really was the update, like you said).

1. Update Windows to the latest version (get any service packs that are available; run windows update until it cannot find anything else to update)
http://www.tomshardware.com/answers/id-1990136/bsod-guy...

2. If there is a problem updating Windows, then rollback to an earlier date and then try to run the update again. I think your guess that the update may have caused the issue could be correct.

3. Test your memory:
http://www.howtogeek.com/howto/windows-vista/test-your-...

4. Download and install the latest drivers for all your parts:
* Video Card: http://support.amd.com/en-us/download
* Motherboard: (these include separate drivers for: "LAN, USB, AUDIO, Chipset, BIOS")
https://www.asus.com/us/Motherboards/
* SSD Firmware (if this is the right one?)
http://www.kingston.com/us/support/technical/downloads?...

5. It is possible that the update messed something up. If you can't get things to work again, you might have to consider a Windows re-install.
Share
April 22, 2014 11:10:20 AM

Thank you so much for your input. I will follow up with your advice and reply at a later date to confirm everything is still running smoothly.
m
0
l
April 22, 2014 1:54:00 PM

all of thoses treads to say the samethings i told you at the begining ????
funny things! HIHI!

''3 go in the bios screen at the really begining of system boot by tap the delete button and
see if everything is detected and normal , check if the boot options still in good configuration.

check if it still somes other updates to do with windows update and restart it maybe 2 or 3 times to correctly installed thoses updates''
m
0
l
April 23, 2014 8:05:02 AM

badboyrog2 said:
all of thoses treads to say the samethings i told you at the begining ????
funny things! HIHI!

''3 go in the bios screen at the really begining of system boot by tap the delete button and
see if everything is detected and normal , check if the boot options still in good configuration.

check if it still somes other updates to do with windows update and restart it maybe 2 or 3 times to correctly installed thoses updates''


There's nothing wrong with being thorough and I would like this to be helpful for others who might run into the same issue; providing more information will do that. Plus I learned about dump files which completely slipped my mind to check. Thank you for your input as well, every bit helps.
m
0
l
Related resources
!