|15 Jun 2011||#2|
Welcome to Seven Forums.
The BSoD is STOP 0x0000003B: SYSTEM_SERVICE_EXCEPTION
Usual causes: System service, Device driver, graphics driver, ?memory
If you're using a Fire wire device check this link.
STOP 0x0000003B" Stop error on a computer that is running Windows 7 when you use some IEEE 1394 devices
Have you installed a new Graphics Card driver recently?
If you have then un-install the driver and install a known good driver.
******************************************************************************* * * * 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: fffff960002b6189, Address of the instruction which caused the bugcheck Arg3: fffff8800a5622b0, 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!DEVLOCKBLTOBJ::vClearRenderState+55 fffff960`002b6189 c6804001000000 mov byte ptr [rax+140h],0 CONTEXT: fffff8800a5622b0 -- (.cxr 0xfffff8800a5622b0) rax=fffff900c1ebec30 rbx=fffff8800a562f60 rcx=fffff8800a562f10 rdx=fffff8800a562f60 rsi=fffff900c20593d0 rdi=fffff900c01f2a10 rip=fffff960002b6189 rsp=fffff8800a562c90 rbp=0000000000000000 r8=0000000000000000 r9=fffff900c21db630 r10=fffff900000004c0 r11=fffff900c20503b0 r12=0000000000000000 r13=fffff960003a72e0 r14=0000000000000001 r15=fffff900c200c670 iopl=0 nv up ei ng nz na po nc cs=0010 ss=0018 ds=002b es=002b fs=0053 gs=002b efl=00210286 win32k!DEVLOCKBLTOBJ::vClearRenderState+0x55: fffff960`002b6189 c6804001000000 mov byte ptr [rax+140h],0 ds:002b:fffff900`c1ebed70=?? 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 fffff9600015816d to fffff960002b6189 STACK_TEXT: fffff880`0a562c90 fffff960`0015816d : fffff880`0a562f10 fffff900`c20593d0 00000000`00000000 00000000`00ffffff : win32k!DEVLOCKBLTOBJ::vClearRenderState+0x55 fffff880`0a562cc0 fffff960`00157fda : fffff960`003a72e0 fffff900`c01f2a10 fffff900`c20593d0 00000000`00000000 : win32k!DEVLOCKBLTOBJ::bDisposeTrgDco+0x41 fffff880`0a562cf0 fffff960`0026102c : 00000000`00000000 fffff900`c200c670 00000000`746c7847 fffff900`c200c670 : win32k!DEVLOCKBLTOBJ::~DEVLOCKBLTOBJ+0xaa fffff880`0a562d20 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : win32k!NtGdiAlphaBlend+0x1900 FOLLOWUP_IP: win32k!DEVLOCKBLTOBJ::vClearRenderState+55 fffff960`002b6189 c6804001000000 mov byte ptr [rax+140h],0 SYMBOL_STACK_INDEX: 0 SYMBOL_NAME: win32k!DEVLOCKBLTOBJ::vClearRenderState+55 FOLLOWUP_NAME: MachineOwner MODULE_NAME: win32k IMAGE_NAME: win32k.sys DEBUG_FLR_IMAGE_TIMESTAMP: 4d6f104c STACK_COMMAND: .cxr 0xfffff8800a5622b0 ; kb FAILURE_BUCKET_ID: X64_0x3B_win32k!DEVLOCKBLTOBJ::vClearRenderState+55 BUCKET_ID: X64_0x3B_win32k!DEVLOCKBLTOBJ::vClearRenderState+55 Followup: MachineOwner ---------
This is an old driver that is known to cause BSoDs.
RTCore64 RTCore64.sys Wed May 25 14:39:12 2005
Check here for a newer driver, preferably 2009 or later: RivaTuner
There are a lot of Bug Checks in your Events Log.
STOP 0x00000101: CLOCK_WATCHDOG_TIMEOUT
Usual causes: Device driver, BIOS bug, hardware defect
Event: Log Name: System Source: Microsoft-Windows-WER-SystemErrorReporting Date: 2011-06-12T15:27:42.000 Event ID: 1001 Task: N/A Level: Error Opcode: N/A Keyword: Classic User: N/A User Name: N/A Computer: AnthonyDoan-PC Description: The computer has rebooted from a bugcheck. The bugcheck was: 0x00000101 (0x0000000000000031, 0x0000000000000000, 0xfffff880033d5180, 0x0000000000000003). A dump was saved in: C:\Windows\MEMORY.DMP. Report Id: 061211-12402-01.
STOP 0x0000000A: IRQL_NOT_LESS_OR_EQUAL
Usual causes: Kernel mode driver, System Service, BIOS, Windows, Virus scanner, Backup tool, compatibility
This bug check is issued if paged memory (or invalid memory) is accessed when the IRQL is too high.
The error that generates this bug check usually occurs after the installation of a faulty device driver, system service, or BIOS.
If you encounter bug check 0xA while upgrading to a later version of Windows, this error might be caused by a device driver, a system service, a virus scanner, or a backup tool that is incompatible with the new version.
Event: Log Name: System Source: Microsoft-Windows-WER-SystemErrorReporting Date: 2011-06-12T03:19:08.000 Event ID: 1001 Task: N/A Level: Error Opcode: N/A Keyword: Classic User: N/A User Name: N/A Computer: AnthonyDoan-PC Description: The computer has rebooted from a bugcheck. The bugcheck was: 0x0000000a (0x0000000000000003, 0x0000000000000002, 0x0000000000000001, 0xfffff800030e9d4b). A dump was saved in: C:\Windows\MEMORY.DMP. Report Id: 061211-11778-01.
STOP 0x00000124: WHEA_UNCORRECTABLE_ERROR
Usual causes: Hardware, Incompatibility, May be driver corruption
The WHEA_UNCORRECTABLE_ERROR bug check has a value of 0x00000124. This bug check indicates that a fatal hardware error has occurred. This bug check uses the error data that is provided by the Windows Hardware Error Architecture (WHEA).
Several of these.
Event: Log Name: System Source: Microsoft-Windows-WER-SystemErrorReporting Date: 2011-06-12T00:00:11.000 Event ID: 1001 Task: N/A Level: Error Opcode: N/A Keyword: Classic User: N/A User Name: N/A Computer: AnthonyDoan-PC Description: The computer has rebooted from a bugcheck. The bugcheck was: 0x00000124 (0x0000000000000000, 0xfffffa8006804028, 0x00000000f2000000, 0x0000000000000014). A dump was saved in: C:\Windows\MEMORY.DMP. Report Id: 061211-12058-01.
Startup Repair Failed.
Any details on this?
Event: Log Name: System Source: Microsoft-Windows-StartupRepair Date: 2011-06-11T15:05:46.307 Event ID: 1002 Task: N/A Level: Information Opcode: Info Keyword: N/A User: S-1-5-18 User Name: NT AUTHORITY\SYSTEM Computer: AnthonyDoan-PC Description: Startup Repair failed.
First try the Fire wire fix, un-install the graphics driver then install a known good one.
Get new driver for RivaTuner/EVGA Precision/MSI Afterburner, or uninstall these programs for testing purposes.
|My System Specs|
|15 Jun 2011||#3|
Thanks for the reply! I don't believe I am using any firewire devices so not sure if that can be the problem.
I have since updated my video card drivers and I haven't run into the 3b problem again (yet anyway). I am running EVGA Precision, but it is the newest version. I'm guessing the on screen overlay that comes with it (which I believe is part of rivatuner) is the old driver, but I don't think I can update that. I'll try turning off the onscreen overlay as well.
As for the other problems, I was in the process of overclocking and I knew those were related to that (at least I hope so).
Once again, thanks for the help! I'll see how far I get with the new nvidia drivers and having the onscreen overlay turned off.
|My System Specs|
|16 Jun 2011||#4|
The new graphics drivers should help.
For the Rivatuner driver, check the website listed above for a new driver and install it if turning it off doesn't stop it from crashing your system.
Thanks for the info on OC'ing, next time you should mention that in your initial post, it will help us understand what is affecting your crashes.
Good luck and let us know if you have any questions or get any more crashes.
If you can, post back in 4-7 days and let us know your status.
|My System Specs|
|Thread Tools||Search this Thread|
Windows 7 Forums is an independent web site and has not been authorized, sponsored, or otherwise approved by Microsoft Corporation. "Windows 7" and related materials are trademarks of Microsoft Corp.
© Designer Media Ltd
All times are GMT -5. The time now is 08:29.