Random Blue Screening (System_Service_Exception)

Toggle sidebar Toggle sidebar
M

megamidge11

Honorable
Jun 1, 2013
50
0
10,630
I keep getting bluescreen errors.... today, two happened within the same 30 mins...
its quite an annoyance. i can't think what it could be or what is causing it, as its completely random, but i think it might be RAM. Below is an entire WinDbg report....
icrosoft (R) Windows Debugger Version 6.12.0002.633 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Windows\Minidump\013114-33119-01.dmp]
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 (6 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7601.18247.amd64fre.win7sp1_gdr.130828-1532
Machine Name:
Kernel base = 0xfffff800`03012000 PsLoadedModuleList = 0xfffff800`032556d0
Debug session time: Fri Jan 31 17:45:20.596 2014 (UTC + 0:00)
System Uptime: 0 days 10:01:52.767
Loading Kernel Symbols
...............................................................
................................................................
.....................................
Loading User Symbols
Loading unloaded module list
........
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 3B, {c0000005, fffff9600019cd21, fffff88009f831c0, 0}

Probably caused by : win32k.sys ( win32k!ValidateHwnd+f1 )

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: fffff9600019cd21, Address of the instruction which caused the bugcheck
Arg3: fffff88009f831c0, 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!ValidateHwnd+f1
fffff960`0019cd21 498b9058010000 mov rdx,qword ptr [r8+158h]

CONTEXT: fffff88009f831c0 -- (.cxr 0xfffff88009f831c0)
rax=fffff900c08dac20 rbx=fffff900c0406720 rcx=000000000001044c
rdx=fffffa8008d294d0 rsi=000000000001044c rdi=fffff900c0e72700
rip=fffff9600019cd21 rsp=fffff88009f83ba0 rbp=fffff88009f83ca0
r8=f7fff900c08dac20 r9=0000000076ac0e10 r10=fffff9600016e21c
r11=fffff900c08dac20 r12=000000007efdb000 r13=000000000024fd20
r14=000000000024e710 r15=0000000074af2450
iopl=0 nv up ei pl nz na pe nc
cs=0010 ss=0018 ds=002b es=002b fs=0053 gs=002b efl=00010202
win32k!ValidateHwnd+0xf1:
fffff960`0019cd21 498b9058010000 mov rdx,qword ptr [r8+158h] ds:002b:f7fff900`c08dad78=????????????????
Resetting default scope

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT

BUGCHECK_STR: 0x3B

PROCESS_NAME: Steam.exe

CURRENT_IRQL: 0

LAST_CONTROL_TRANSFER: from fffff9600016e253 to fffff9600019cd21

STACK_TEXT:
fffff880`09f83ba0 fffff960`0016e253 : 00000000`0001044c 00000000`00000000 fffff880`09f83ca0 00000000`00000000 : win32k!ValidateHwnd+0xf1
fffff880`09f83bd0 fffff800`03086e53 : fffffa80`0a7a4b50 00000000`0636cb20 00000000`00000020 00000000`000012d4 : win32k!NtUserShowWindow+0x37
fffff880`09f83c20 00000000`74af2e09 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
00000000`0024e698 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x74af2e09


FOLLOWUP_IP:
win32k!ValidateHwnd+f1
fffff960`0019cd21 498b9058010000 mov rdx,qword ptr [r8+158h]

SYMBOL_STACK_INDEX: 0

SYMBOL_NAME: win32k!ValidateHwnd+f1

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: win32k

IMAGE_NAME: win32k.sys

DEBUG_FLR_IMAGE_TIMESTAMP: 529478c2

STACK_COMMAND: .cxr 0xfffff88009f831c0 ; kb

FAILURE_BUCKET_ID: X64_0x3B_win32k!ValidateHwnd+f1

BUCKET_ID: X64_0x3B_win32k!ValidateHwnd+f1

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

 
Sort by date Sort by votes
T

thicks083

Honorable
Jul 21, 2013
90
0
10,660
I would expect this to either be an issue with your RAM, or on the motherboard.

In my personal experience with the BSoD I have noticed that a majority of the time the problem is caused by blown capacitors on the motherboard. The capacitors either start to expand or even burst and bubble over, due to thermal events. Take a look inside that case to see if you have any of these symptoms!
 
Upvote 0 Downvote
M

megamidge11

Honorable
Jun 1, 2013
50
0
10,630
No, i always have the door off, as my aftermarket cooler doesnt fit (when i bought the cpu, the seller gave aftermarket cooler). im getting new case. None of these symptoms apply. thank you.
 
Upvote 0 Downvote
M

megamidge11

Honorable
Jun 1, 2013
50
0
10,630
Nope. It's a fairly new build too, i built it around a year ago. it is no gaming motherboard, was only 50 pounds, but yes, no blown capacitors, which are the ones that look like mini batteries?
 
Upvote 0 Downvote
You must log in or register to reply here.

TRENDING THREADS

Latest posts

Moderators online

Share this page

COMPANY
RESOURCES
FOLLOW
Top Bottom