Windows 7 Forums
Welcome to Windows 7 Forums. Our forum is dedicated to helping you find support and solutions for any problems regarding your Windows 7 PC be it Dell, HP, Acer, Asus or a custom build. We also provide an extensive Windows 7 tutorial section that covers a wide range of tips and tricks.


Windows 7: BSOD playing Skyrim, error 0x0000003B

23 Jan 2012   #1

Win7 x64 Ultimate
 
 
BSOD playing Skyrim, error 0x0000003B

Hello

This happens a fair bit whilst playing Skyrim. Any help is appreciated

My System SpecsSystem Spec
.

24 Jan 2012   #2

Windows 7 Home Premium 64 Bit
 
 

Code:
  1. Microsoft (R) Windows Debugger Version 6.12.0002.633 AMD64 Copyright (c) Microsoft Corporation. All rights reserved. Loading Dump File [J:\BSODDmpFiles\Milamber\Windows_NT6_BSOD_jcgriff2\012412-10202-01.dmp] Mini Kernel Dump File: Only registers and stack trace are available Symbol search path is: SRV*c:\users\mike\documents\symbols*http://msdl.microsoft.com/download/symbols Executable search path is: Windows 7 Kernel Version 7601 (Service Pack 1) MP (4 procs) Free x64 Product: WinNt, suite: TerminalServer SingleUserTS Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506 Machine Name: Kernel base = 0xfffff800`03400000 PsLoadedModuleList = 0xfffff800`03645670 Debug session time: Mon Jan 23 15:57:08.714 2012 (UTC - 7:00) System Uptime: 0 days 1:49:14.869 Loading Kernel Symbols ............................................................... ................................................................ ............................................................... Loading User Symbols Loading unloaded module list ......... ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* Use !analyze -v to get detailed debugging information. BugCheck 3B, {c0000005, fffff80003481faa, fffff8800f0affd0, 0} Probably caused by : ntkrnlmp.exe ( nt!KiCommitThreadWait+24a ) Followup: MachineOwner --------- 1: 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: fffff80003481faa, Address of the instruction which caused the bugcheck Arg3: fffff8800f0affd0, 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: nt!KiCommitThreadWait+24a fffff800`03481faa f00fba2e07 lock bts dword ptr [rsi],7 CONTEXT: fffff8800f0affd0 -- (.cxr 0xfffff8800f0affd0) rax=000007fffffae000 rbx=fffffa8013419790 rcx=fffff8800f0b0970 rdx=00000000000007ff rsi=00fffa0013419850 rdi=0000000000000102 rip=fffff80003481faa rsp=fffff8800f0b09b0 rbp=0000000000000000 r8=fffffa8011bd8bb8 r9=0000000000000000 r10=fffffffffffffffd r11=0000000000000000 r12=0000000000000000 r13=0000000000000000 r14=0000000000000000 r15=fffff78000000008 iopl=0 nv up ei ng nz na pe cy cs=0010 ss=0018 ds=002b es=002b fs=0053 gs=002b efl=00010283 nt!KiCommitThreadWait+0x24a: fffff800`03481faa f00fba2e07 lock bts dword ptr [rsi],7 ds:002b:00fffa00`13419850=???????? Resetting default scope CUSTOMER_CRASH_COUNT: 1 DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT BUGCHECK_STR: 0x3B PROCESS_NAME: svchost.exe CURRENT_IRQL: 2 LAST_CONTROL_TRANSFER: from 0000000000000000 to fffff80003481faa STACK_TEXT: fffff880`0f0b09b0 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiCommitThreadWait+0x24a FOLLOWUP_IP: nt!KiCommitThreadWait+24a fffff800`03481faa f00fba2e07 lock bts dword ptr [rsi],7 SYMBOL_STACK_INDEX: 0 SYMBOL_NAME: nt!KiCommitThreadWait+24a FOLLOWUP_NAME: MachineOwner MODULE_NAME: nt IMAGE_NAME: ntkrnlmp.exe DEBUG_FLR_IMAGE_TIMESTAMP: 4e02aaa3 STACK_COMMAND: .cxr 0xfffff8800f0affd0 ; kb FAILURE_BUCKET_ID: X64_0x3B_nt!KiCommitThreadWait+24a BUCKET_ID: X64_0x3B_nt!KiCommitThreadWait+24a Followup: MachineOwner ---------
  2. Loading Dump File [J:\BSODDmpFiles\Milamber\Windows_NT6_BSOD_jcgriff2\012312-10998-01.dmp] Mini Kernel Dump File: Only registers and stack trace are available Symbol search path is: SRV*c:\users\mike\documents\symbols*http://msdl.microsoft.com/download/symbols Executable search path is: Windows 7 Kernel Version 7601 (Service Pack 1) MP (4 procs) Free x64 Product: WinNt, suite: TerminalServer SingleUserTS Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506 Machine Name: Kernel base = 0xfffff800`0344a000 PsLoadedModuleList = 0xfffff800`0368f670 Debug session time: Mon Jan 23 04:00:32.931 2012 (UTC - 7:00) System Uptime: 0 days 13:00:27.713 Loading Kernel Symbols .........................................................Unable to load image Unknown_Module_00000000`00000000, Win32 error 0n2 *** WARNING: Unable to verify timestamp for Unknown_Module_00000000`00000000 Unable to add module at 00000000`00000000 Loading User Symbols Loading unloaded module list ......... ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* Use !analyze -v to get detailed debugging information. BugCheck 124, {0, fffffa800f054028, be200000, 5110a} Probably caused by : hardware Followup: MachineOwner --------- 3: kd> !analyze -v ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* WHEA_UNCORRECTABLE_ERROR (124) A fatal hardware error has occurred. Parameter 1 identifies the type of error source that reported the error. Parameter 2 holds the address of the WHEA_ERROR_RECORD structure that describes the error conditon. Arguments: Arg1: 0000000000000000, Machine Check Exception Arg2: fffffa800f054028, Address of the WHEA_ERROR_RECORD structure. Arg3: 00000000be200000, High order 32-bits of the MCi_STATUS value. Arg4: 000000000005110a, Low order 32-bits of the MCi_STATUS value. Debugging Details: ------------------ BUGCHECK_STR: 0x124_GenuineIntel CUSTOMER_CRASH_COUNT: 1 DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT PROCESS_NAME: Ruse.exe CURRENT_IRQL: f STACK_TEXT: fffff880`03ddfa58 fffff800`03413a3b : 00000000`00000124 00000000`00000000 fffffa80`0f054028 00000000`be200000 : nt!KeBugCheckEx fffff880`03ddfa60 fffff800`035d7513 : 00000000`00000001 fffffa80`0f055d30 00000000`00000000 fffffa80`0f055d80 : hal!HalBugCheckSystem+0x1e3 fffff880`03ddfaa0 fffff800`03413700 : 00000000`00000728 fffffa80`0f055d30 fffff880`03ddfe30 fffff880`03ddfe00 : nt!WheaReportHwError+0x263 fffff880`03ddfb00 fffff800`03413052 : fffffa80`0f055d30 fffff880`03ddfe30 fffffa80`0f055d30 00000000`00000000 : hal!HalpMcaReportError+0x4c fffff880`03ddfc50 fffff800`03412f0d : 00000000`00000004 00000000`00000001 fffff880`03ddfeb0 00000000`00000000 : hal!HalpMceHandler+0x9e fffff880`03ddfc90 fffff800`03406e88 : 00000000`00000002 00000000`14594380 00000000`00000000 00000000`00000000 : hal!HalpMceHandlerWithRendezvous+0x55 fffff880`03ddfcc0 fffff800`034c552c : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : hal!HalHandleMcheck+0x40 fffff880`03ddfcf0 fffff800`034c5393 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxMcheckAbort+0x6c fffff880`03ddfe30 00000000`627269f1 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiMcheckAbort+0x153 00000000`0e2cfda0 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x627269f1 STACK_COMMAND: kb FOLLOWUP_NAME: MachineOwner MODULE_NAME: hardware IMAGE_NAME: hardware DEBUG_FLR_IMAGE_TIMESTAMP: 0 FAILURE_BUCKET_ID: X64_0x124_GenuineIntel_PROCESSOR_CACHE BUCKET_ID: X64_0x124_GenuineIntel_PROCESSOR_CACHE Followup: MachineOwner ---------
  3. Loading Dump File [J:\BSODDmpFiles\Milamber\Windows_NT6_BSOD_jcgriff2\012112-11497-01.dmp] Mini Kernel Dump File: Only registers and stack trace are available Symbol search path is: SRV*c:\users\mike\documents\symbols*http://msdl.microsoft.com/download/symbols Executable search path is: Windows 7 Kernel Version 7601 (Service Pack 1) MP (4 procs) Free x64 Product: WinNt, suite: TerminalServer SingleUserTS Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506 Machine Name: Kernel base = 0xfffff800`03418000 PsLoadedModuleList = 0xfffff800`0365d670 Debug session time: Sat Jan 21 00:30:10.176 2012 (UTC - 7:00) System Uptime: 0 days 1:15:49.957 Loading Kernel Symbols ............................................................... ................................................................ ........................................................... Loading User Symbols Loading unloaded module list .............. ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* Use !analyze -v to get detailed debugging information. BugCheck A, {10, f, 0, fffff800034bf805} Probably caused by : ntkrnlmp.exe ( nt!RtlLookupFunctionEntry+b5 ) Followup: MachineOwner --------- 3: kd> !analyze -v ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* IRQL_NOT_LESS_OR_EQUAL (a) An attempt was made to access a pageable (or completely invalid) address at an interrupt request level (IRQL) that is too high. This is usually caused by drivers using improper addresses. If a kernel debugger is available get the stack backtrace. Arguments: Arg1: 0000000000000010, memory referenced Arg2: 000000000000000f, IRQL Arg3: 0000000000000000, bitfield : bit 0 : value 0 = read operation, 1 = write operation bit 3 : value 0 = not an execute operation, 1 = execute operation (only on chips which support this level of status) Arg4: fffff800034bf805, address which referenced memory Debugging Details: ------------------ READ_ADDRESS: GetPointerFromAddress: unable to read from fffff800036c7100 0000000000000010 CURRENT_IRQL: f FAULTING_IP: nt!RtlLookupFunctionEntry+b5 fffff800`034bf805 4084ff test dil,dil CUSTOMER_CRASH_COUNT: 1 DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT BUGCHECK_STR: 0xA PROCESS_NAME: TESV.exe TRAP_FRAME: fffff88017c1f6c0 -- (.trap 0xfffff88017c1f6c0) NOTE: The trap frame does not contain all registers. Some register values may be zeroed or incorrect. rax=0000000000000000 rbx=0000000000000000 rcx=0000000000000001 rdx=fffff800034c25ec rsi=0000000000000000 rdi=0000000000000000 rip=fffff800034bf805 rsp=fffff88017c1f850 rbp=fffff88003dd7180 r8=fffff80003418000 r9=0000000000000000 r10=fffff800037855f3 r11=fffff88017c1faa0 r12=0000000000000000 r13=0000000000000000 r14=0000000000000000 r15=0000000000000000 iopl=0 nv up ei pl zr na po nc nt!RtlLookupFunctionEntry+0xb5: fffff800`034bf805 4084ff test dil,dil Resetting default scope LAST_CONTROL_TRANSFER: from fffff800034941e9 to fffff80003494c40 STACK_TEXT: fffff880`17c1f578 fffff800`034941e9 : 00000000`0000000a 00000000`00000010 00000000`0000000f 00000000`00000000 : nt!KeBugCheckEx fffff880`17c1f580 fffff800`03492e60 : 00000000`00000000 00000000`00000000 00000000`00000000 fffff800`03499faa : nt!KiBugCheckDispatch+0x69 fffff880`17c1f6c0 fffff800`034bf805 : fffff880`17c1ffc0 fffff880`17c20060 00000000`00000001 fffff880`0163de28 : nt!KiPageFault+0x260 fffff880`17c1f850 fffff800`034bef90 : fffff800`03499faa fffff880`17c1f908 fffff880`00000003 fffff880`01624000 : nt!RtlLookupFunctionEntry+0xb5 fffff880`17c1f8c0 fffff800`034d0361 : fffff880`17c20778 fffff880`17c1ffd0 fffff880`00000000 00000000`00000102 : nt!RtlDispatchException+0xd0 fffff880`17c1ffa0 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiDispatchException+0x135 STACK_COMMAND: kb FOLLOWUP_IP: nt!RtlLookupFunctionEntry+b5 fffff800`034bf805 4084ff test dil,dil SYMBOL_STACK_INDEX: 3 SYMBOL_NAME: nt!RtlLookupFunctionEntry+b5 FOLLOWUP_NAME: MachineOwner MODULE_NAME: nt IMAGE_NAME: ntkrnlmp.exe DEBUG_FLR_IMAGE_TIMESTAMP: 4e02aaa3 FAILURE_BUCKET_ID: X64_0xA_nt!RtlLookupFunctionEntry+b5 BUCKET_ID: X64_0xA_nt!RtlLookupFunctionEntry+b5 Followup: MachineOwner ---------
  4. Loading Dump File [J:\BSODDmpFiles\Milamber\Windows_NT6_BSOD_jcgriff2\011412-12308-01.dmp] Mini Kernel Dump File: Only registers and stack trace are available Symbol search path is: SRV*c:\users\mike\documents\symbols*http://msdl.microsoft.com/download/symbols Executable search path is: Windows 7 Kernel Version 7601 (Service Pack 1) MP (4 procs) Free x64 Product: WinNt, suite: TerminalServer SingleUserTS Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506 Machine Name: Kernel base = 0xfffff800`03864000 PsLoadedModuleList = 0xfffff800`03aa9670 Debug session time: Sat Jan 14 04:01:40.398 2012 (UTC - 7:00) System Uptime: 0 days 5:11:13.179 Loading Kernel Symbols ............................................................... ................................................................ .......................................................... Loading User Symbols Loading unloaded module list ......... ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* Use !analyze -v to get detailed debugging information. BugCheck 3B, {c0000005, fffff800038e3847, fffff8800db5ee50, 0} *** WARNING: Unable to verify timestamp for win32k.sys *** ERROR: Module load completed but symbols could not be loaded for win32k.sys Probably caused by : memory_corruption Followup: memory_corruption --------- 1: 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: fffff800038e3847, Address of the instruction which caused the bugcheck Arg3: fffff8800db5ee50, 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: nt!SwapContext_PatchXSave+46 fffff800`038e3847 4983be1801000000 cmp qword ptr [r14+118h],0 CONTEXT: fffff8800db5ee50 -- (.cxr 0xfffff8800db5ee50) rax=0000000000000004 rbx=fffff880009ee180 rcx=fffff88003d1bcc0 rdx=0000000000000000 rsi=fffffa80113f33f0 rdi=fffff880009f8fc0 rip=fffff800038e3847 rsp=fffff8800db5f830 rbp=fffff88003d1bc70 r8=0000000000000000 r9=0000000000000f44 r10=fffff80003864000 r11=0000000000000000 r12=0000000000000000 r13=0000000000000000 r14=59fffa8011fe1060 r15=fffff880009f2f40 iopl=0 nv up ei pl zr na po nc cs=0010 ss=0018 ds=002b es=002b fs=0053 gs=002b efl=00010246 nt!SwapContext_PatchXSave+0x46: fffff800`038e3847 4983be1801000000 cmp qword ptr [r14+118h],0 ds:002b:59fffa80`11fe1178=???????????????? Resetting default scope CUSTOMER_CRASH_COUNT: 1 DEFAULT_BUCKET_ID: CODE_CORRUPTION BUGCHECK_STR: 0x3B PROCESS_NAME: TESV.exe CURRENT_IRQL: 2 LAST_CONTROL_TRANSFER: from 0000000000000000 to fffff800038e3847 STACK_TEXT: fffff880`0db5f830 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!SwapContext_PatchXSave+0x46 CHKIMG_EXTENSION: !chkimg -lo 50 -d !nt fffff800038e3803 - nt!SwapContext_PatchXSave+2 [ 01:21 ] fffff800038e38e4 - nt!SwapContext_PatchXRstor+2 (+0xe1) [ 09:29 ] fffff800038e3aa3 - nt!EnlightenedSwapContext_PatchXSave+2 (+0x1bf) [ 01:21 ] fffff800038e3b86 - nt!EnlightenedSwapContext_PatchXRstor+2 (+0xe3) [ 09:29 ] 4 errors : !nt (fffff800038e3803-fffff800038e3b86) MODULE_NAME: memory_corruption IMAGE_NAME: memory_corruption FOLLOWUP_NAME: memory_corruption DEBUG_FLR_IMAGE_TIMESTAMP: 0 MEMORY_CORRUPTOR: ONE_BIT_LARGE STACK_COMMAND: .cxr 0xfffff8800db5ee50 ; kb FAILURE_BUCKET_ID: X64_MEMORY_CORRUPTION_ONE_BIT_LARGE BUCKET_ID: X64_MEMORY_CORRUPTION_ONE_BIT_LARGE Followup: memory_corruption ---------
  1. Possible causes are Memory problems... Corrupted hard disk system files... Corrupted System Files... Graphics Driver...
  2. Hardware stop 0x124.
  3. Possible causes are Memory problems... Corrupted hard disk system files... Corrupted System Files... Lack of Windows updates... Antivirus Software...
  4. Possible causes are Memory problems... Corrupted hard disk system files... Corrupted System Files... Graphics Driver...

Thanks to Dave76 for help understanding possible causes.

We will start with the common problems first (see bold possible causes). Do the following steps and test after each to see if stability increases (the memory tests you can run concurrently as they will not increase stability unless you are forced to move modules around). Post back your results after each step, and if you get a blue screen crash, upload the files again and await further instructions after we are able to analyze the crash.
My System SpecsSystem Spec
24 Jan 2012   #3

Win7 x64 Ultimate
 
 

Thanks very much.

I have downloaded a bootable version of memtest86 and will run this tonight and then the Windows 7 Memory test.

Will be in touch!
My System SpecsSystem Spec
.


25 Jan 2012   #4

Win7 x64 Ultimate
 
 

I have tested my memory for 7.5 hours and it appears to be fine.

http://i.imgur.com/kbfnI.jpg

My temps at idle:

GTX580: 45
GTX580: 38
CPU: 34
Mobo: 25

My temps at load:

GTX580: 82
GTX580: 79
CPU: 41
Mobo: 27
My System SpecsSystem Spec
25 Jan 2012   #5

Windows 7 Home Premium 64 Bit
 
 

Quote   Quote: Originally Posted by Milamber View Post
I have tested my memory for 7.5 hours and it appears to be fine.

http://i.imgur.com/kbfnI.jpg

My temps at idle:

GTX580: 45
GTX580: 38
CPU: 34
Mobo: 25

My temps at load:

GTX580: 82
GTX580: 79
CPU: 41
Mobo: 27
Your memtest should run for 7 passes, and we recommend at least 5. Yours only ran for 4, so it would be best if you test again.


Did you ever run the Memtest86+ for 7 passes (or more)? More is better in this instance.
My System SpecsSystem Spec
16 Feb 2012   #6

Win7 x64 Ultimate
 
 

Hello

yes I did but forgot to take a photo with my phone.. I did 9 passes without errors.
My System SpecsSystem Spec
16 Feb 2012   #7

Windows 7 Home Premium 64 Bit
 
 

How are things running at this time? Any change? Also, do you have your graphics card linked via an SLI bridge?
My System SpecsSystem Spec
16 Feb 2012   #8

Win7 x64 Ultimate
 
 

hi

I still get the error from time to time... My gpus are connected via sli bridge as my pc is used for 3d gaming.
My System SpecsSystem Spec
16 Feb 2012   #9

Windows 7 Home Premium 64 Bit
 
 

Have you tried removing the bridge and testing each card individually? If you do this, try running them just without the bridge and see if the crashes still occur. There have been many cases where the bridge or motherboard were to blame for graphics SLI not working properly. If no crashes occur with just the bridge removed, contact nVidia and Gigabyte for troubleshooting steps for your bridge.

If you still crash with the bridge removed, continue to testing each card individually. It is possible one of the cards or slots is bad. Post back how things go with these steps. Best of luck!
My System SpecsSystem Spec
16 Feb 2012   #10

Win7 x64 Ultimate
 
 

Is my sli bridge faulty?

what indicators are there?

thanks !
My System SpecsSystem Spec
Reply

 BSOD playing Skyrim, error 0x0000003B




Thread Tools



Similar help and support threads for2: BSOD playing Skyrim, error 0x0000003B
Thread Forum
BSOD playing LoL/SC2/Skyrim/ARMA2 error 0x124 BSOD Help and Support
BSOD playing Skyrim and other games, error 0x0000001a BSOD Help and Support
BSOD playing Skyrim, error 0x00000116 BSOD Help and Support
BSOD playing Skyrim, error 0x0000007A BSOD Help and Support
BSOD playing Skyrim, now won't stop; error 1000007e BSOD Help and Support
BSOD Playing Skyrim, BF3 and SW:ToR error 0x0000001e and 0x0000003b BSOD Help and Support
Solved BSOD playing Skyrim, error code 116 BSOD Help and Support

Our Sites

Site Links

About Us

Find Us

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 09:22 PM.
Twitter Facebook Google+



Windows 7 Forums

Seven Forums Android App Seven Forums IOS App
  

1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33