Jump to content


 


Register a free account to unlock additional features at BleepingComputer.com
Welcome to BleepingComputer, a free community where people like yourself come together to discuss and learn how to use their computers. Using the site is easy and fun. As a guest, you can browse and view the various discussions in the forums, but can not create a new topic or reply to an existing one unless you are logged in. Other benefits of registering an account are subscribing to topics and forums, creating a blog, and having no ads shown anywhere on the site.


Click here to Register a free account now! or read our Welcome Guide to learn how to use this site.

Photo

BSOD error


  • Please log in to reply
No replies to this topic

#1 pdee

pdee

  • Members
  • 1 posts
  • OFFLINE
  •  
  • Local time:07:28 AM

Posted 22 October 2014 - 08:33 AM

Hello, I've been getting this error for the last 2 months. I'm pasting the analysis from Online crash dump analysis service. 

I hope it helps; I just want to know what I can do to fix this. 

Thank you! 

 

Crash Dump Analysis provided by OSR Open Systems Resources, Inc. (http://www.osr.com)
Online Crash Dump Analysis Service
See http://www.osronline.com for more information
Windows 7 Kernel Version 7600 MP (2 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Machine Name:
Kernel base = 0xfffff800`0325e000 PsLoadedModuleList = 0xfffff800`0349be50
Debug session time: Wed Oct 22 08:25:55.812 2014 (UTC - 4:00)
System Uptime: 1 days 13:43:32.265
*******************************************************************************
* *
* 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: fffff96000124377, Address of the instruction which caused the bugcheck
Arg3: fffff8800833c030, Address of the context record for the exception that caused the bugcheck
Arg4: 0000000000000000, zero.

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

TRIAGER: Could not open triage file : e:\dump_analysis\program\triage\modclass.ini, error 2

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`00124377 0fb7430c movzx eax,word ptr [rbx+0Ch]

CONTEXT: fffff8800833c030 -- (.cxr 0xfffff8800833c030)
rax=fffff900c0200000 rbx=0000000000000000 rcx=fffffa80077fab60
rdx=fffff900c0200000 rsi=0000000000000000 rdi=fffff900c0200000
rip=fffff96000124377 rsp=fffff8800833ca00 rbp=0000000000000000
r8=0000000000000001 r9=0000000000000000 r10=0000000000000000
r11=fffff8800833ca68 r12=0000000000499d00 r13=0000000000000000
r14=0000000000000001 r15=0000000000000000
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`00124377 0fb7430c movzx eax,word ptr [rbx+0Ch] ds:002b:00000000`0000000c=????
Resetting default scope

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: WIN7_DRIVER_FAULT

BUGCHECK_STR: 0x3B

PROCESS_NAME: dwm.exe

CURRENT_IRQL: 0

LAST_CONTROL_TRANSFER: from fffff960002dc8a0 to fffff96000124377

STACK_TEXT:
fffff880`0833ca00 fffff960`002dc8a0 : fffff900`c078b1d0 00000000`00000001 ffffffff`e3121271 fffff900`c0167bf0 : win32k!HmgLockEx+0xa3
fffff880`0833ca70 fffff960`002dbd9e : fffff900`c078b1d0 00000000`00000000 00001271`624d4653 00000000`0000001d : win32k!SFMLOGICALSURFACE::OwnsSurfaceCleanup+0x40
fffff880`0833caa0 fffff960`002dcca3 : 00000000`00000000 ffffffff`e3121271 fffff900`c078b1d0 00000000`00499d60 : win32k!SFMLOGICALSURFACE::DeInitialize+0x4e
fffff880`0833cae0 fffff960`00239777 : 00000000`00000000 fffff900`c00bf010 fffff900`c078b1d0 00000000`00000020 : win32k!bhLSurfDestroyLogicalSurfaceObject+0x4b
fffff880`0833cb20 fffff960`0025aa50 : 00000800`00000001 00000000`00000001 fffff880`0833cc60 00000000`00000000 : win32k!GreSfmCloseCompositorRef+0x10f
fffff880`0833cb60 fffff800`032cd993 : fffffa80`077fab60 00000000`0694f800 000007fe`f7d3d610 00000000`00000000 : win32k!NtGdiHLSurfSetInformation+0x1a8
fffff880`0833cbe0 000007fe`fd704efa : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
00000000`0694f258 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x7fe`fd704efa


FOLLOWUP_IP:
win32k!HmgLockEx+a3
fffff960`00124377 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: 4c1c483f

STACK_COMMAND: .cxr 0xfffff8800833c030 ; kb

FAILURE_BUCKET_ID: X64_0x3B_win32k!HmgLockEx+a3

BUCKET_ID: X64_0x3B_win32k!HmgLockEx+a3

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



BC AdBot (Login to Remove)

 





0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users