Overclock.net › Forums › Software, Programming and Coding › Operating Systems › Windows › Random BSOD code 3b
New Posts  All Forums:Forum Nav:

Random BSOD code 3b - Page 2

post #11 of 22
You can do a clean install if you wish, I'd like to see that latest BSOD, though.
post #12 of 22
Quote:
Originally Posted by denial_ View Post

Well, maybe it as not only that driver, it did it again when I turned of my computer before going to work. Turning off my computer make it BSOD 3b about 1 time out of 10.
I recently upgraded my RAM from 8gb to 16gb : my computer would crash while playing BF3 because it was full. I ran memtest86 on the new modules for 8hours with no errors, so I can assume they are OK. Maybe it's just time for a clean install thumbsdownsmileyanim.gif.

Tried the program to read BSOD? Give it a try before doing a clean install. wink.gif
My System
(15 items)
 
  
CPUMotherboardGraphicsRAM
i7-4790k MSI Z97 Gaming 5 Sapphire R9 290X Tri-X 2x8gb ADATA 2133MHz CL10 
Hard DriveCoolingOSKeyboard
Mushkin 1 TB SSD & Samsung F3 spinpoint 1 TB MCP655A + 2 x MCP320 + EK supreme copper Win10 Corsair K70 Lux 
PowerCaseMouse
Corsair 750W Bitphenix Monstrous water cooling case Logitech G9X 
  hide details  
Reply
My System
(15 items)
 
  
CPUMotherboardGraphicsRAM
i7-4790k MSI Z97 Gaming 5 Sapphire R9 290X Tri-X 2x8gb ADATA 2133MHz CL10 
Hard DriveCoolingOSKeyboard
Mushkin 1 TB SSD & Samsung F3 spinpoint 1 TB MCP655A + 2 x MCP320 + EK supreme copper Win10 Corsair K70 Lux 
PowerCaseMouse
Corsair 750W Bitphenix Monstrous water cooling case Logitech G9X 
  hide details  
Reply
post #13 of 22
Thread Starter 
Quote:
Originally Posted by E-Peen View Post

You can do a clean install if you wish, I'd like to see that latest BSOD, though.

Here we go smile.gif. The clean install will not be for now anyway, too much stuff going on at the moment just don't have the time to do that.

I'll give it a try in a few minutes Just a nickname, just came back from work.

040412-21824-01.zip 28k .zip file

Edit: seems like, according to the software, 2 of the recent BSOD we caused by a software called Keyscrambler, so I uninstalled it and replaced with the latest version, and I won't let it run at startup to see if it helps resolve the problem smile.gif.
Edited by denial_ - 4/4/12 at 10:23pm
post #14 of 22
Hi, thanks for that info smile.gif

Keyscrambler was the process that crashed, but it may not have been the cause. The dump attached is an ntkrnlmp.exe (aka Windows has no idea what the cause was).

If you BSOD again, I'd like to you enable Driver Verifier. I noticed you have the ASUS hardware monitoring software installed, and I have analyzed dozens of BSOD cases with this as the case, so I'd like to just be sure it's not this, or any other offending third party driver.
Quote:
Driver Verifier:

Read the following to enable Driver Verifier. Use Driver Second if Memtest finds nothing, as it's likely a software / driver issue, we just aren't being told what it is, and hopefully Driver Verifier will than force a crash if it finds the violating driver.

Before enabling Driver Verifier, my recommendation is to set a backup / restore point as in severe cases Driver Verifier can break your Windows. If you have difficulty getting into Windows, boot into Safe Mode and disable Driver Verifier there.

I have also taken a look at your drivers list once again and it has the driver pcouffin.sys listed. This isn't a driver for one specific program, it's a driver that is used by a wide variety of cd/dvd burning programs. It's dated from 2006, which is a very.... long time ago, so I would recommend uninstalling or updating whatever cd/dvd burning programs you may be using.

Dump for reference:
Code:
Microsoft (R) Windows Debugger Version 6.12.0002.633 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Users\Icarus\Downloads\040412-21824-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: 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.17727.amd64fre.win7sp1_gdr.111118-2330
Machine Name:
Kernel base = 0xfffff800`03452000 PsLoadedModuleList = 0xfffff800`03696650
Debug session time: Wed Apr  4 13:44:14.852 2012 (UTC - 4:00)
System Uptime: 0 days 12:20:05.648
Loading Kernel Symbols
...............................................................
................................................................
.........................................................
Loading User Symbols
Loading unloaded module list
..............
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 3B, {c0000005, fffff800034d80b0, fffff8800a218b70, 0}

Probably caused by : ntkrnlmp.exe ( nt!IofCallDriver+50 )

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: fffff800034d80b0, Address of the instruction which caused the bugcheck
Arg3: fffff8800a218b70, 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!IofCallDriver+50
fffff800`034d80b0 49ff64c070      jmp     qword ptr [r8+rax*8+70h]

CONTEXT:  fffff8800a218b70 -- (.cxr 0xfffff8800a218b70)
rax=0000000000000012 rbx=fffffa800cad56a0 rcx=fffffa800f3d8930
rdx=fffffa800cad56a0 rsi=0000000000000000 rdi=fffffa800cad56a0
rip=fffff800034d80b0 rsp=fffff8800a219558 rbp=fffffa8011214b00
 r8=0000000000000000  r9=0000000000000012 r10=fffffa800c778f00
r11=fffffa8010b7f060 r12=0000000000000000 r13=fffffa800f3f1c20
r14=0000000000000000 r15=fffff8a004341c90
iopl=0         nv up ei ng nz na pe nc
cs=0010  ss=0018  ds=002b  es=002b  fs=0053  gs=002b             efl=00010282
nt!IofCallDriver+0x50:
fffff800`034d80b0 49ff64c070      jmp     qword ptr [r8+rax*8+70h] ds:002b:00000000`00000100=????????????????
Resetting default scope

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

BUGCHECK_STR:  0x3B

PROCESS_NAME:  KeyScrambler.e

CURRENT_IRQL:  0

LAST_CONTROL_TRANSFER:  from 0000000000000000 to fffff800034d80b0

STACK_TEXT:  
fffff880`0a219558 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!IofCallDriver+0x50


FOLLOWUP_IP: 
nt!IofCallDriver+50
fffff800`034d80b0 49ff64c070      jmp     qword ptr [r8+rax*8+70h]

SYMBOL_STACK_INDEX:  0

SYMBOL_NAME:  nt!IofCallDriver+50

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nt

IMAGE_NAME:  ntkrnlmp.exe

DEBUG_FLR_IMAGE_TIMESTAMP:  4ec79dd2

STACK_COMMAND:  .cxr 0xfffff8800a218b70 ; kb

FAILURE_BUCKET_ID:  X64_0x3B_nt!IofCallDriver+50

BUCKET_ID:  X64_0x3B_nt!IofCallDriver+50

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

3: kd> !thread
GetPointerFromAddress: unable to read from fffff80003700000
THREAD fffffa8010b7f060  Cid 0cc8.0d74  Teb: 0000000000000000 Win32Thread: 0000000000000000 RUNNING on processor 3
IRP List:
    Unable to read nt!_IRP @ fffffa800cad56a0
Not impersonating
GetUlongFromAddress: unable to read from fffff8000363fba4
Owning Process            fffffa8011214b30       Image:         KeyScrambler.e
Attached Process          N/A            Image:         N/A
fffff78000000000: Unable to get shared data
Wait Start TickCount      2846497      
Context Switch Count      758             
ReadMemory error: Cannot get nt!KeMaximumIncrement value.
UserTime                  00:00:00.000
KernelTime                00:00:00.000
Win32 Start Address 0x00000000773dfbc0
Stack Init fffff8800a219c70 Current fffff8800a2193a0
Base fffff8800a21a000 Limit fffff8800a214000 Call 0
Priority 12 BasePriority 8 UnusualBoost 0 ForegroundBoost 0 IoPriority 2 PagePriority 5
Child-SP          RetAddr           : Args to Child                                                           : Call Site
fffff880`0a2182a8 fffff800`034ce2e9 : 00000000`0000003b 00000000`c0000005 fffff800`034d80b0 fffff880`0a218b70 : nt!KeBugCheckEx
fffff880`0a2182b0 fffff800`034cdc3c : fffff880`0a219318 fffff880`0a218b70 00000000`00000000 fffff800`034f9f60 : nt!KiBugCheckDispatch+0x69
fffff880`0a2183f0 fffff800`034f9a6d : fffff800`036d540c fffff800`03617fc4 fffff800`03452000 fffff880`0a219318 : nt!KiSystemServiceHandler+0x7c
fffff880`0a218430 fffff800`034f8845 : fffff800`03618638 fffff880`0a2184a8 fffff880`0a219318 fffff800`03452000 : nt!RtlpExecuteHandlerForException+0xd
fffff880`0a218460 fffff800`035097c1 : fffff880`0a219318 fffff880`0a218b70 fffff880`00000000 fffffa80`00000004 : nt!RtlDispatchException+0x415
fffff880`0a218b40 fffff800`034ce3c2 : fffff880`0a219318 fffffa80`0cad56a0 fffff880`0a2193c0 00000000`00000000 : nt!KiDispatchException+0x135
fffff880`0a2191e0 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiExceptionDispatch+0xc2

post #15 of 22
Thread Starter 
My computer just crashed again after enabling Driver Verifier frown.gif. I booted in safemode and then reboot normal and now it's working, but the last BSOD code is now c4.
I'll uninstall my cd/dvd burner software if it can help smile.gif

Last minidump:
040512-23212-01.zip 24k .zip file

Hum maybe there's something here, in WhoCrashed I got this for the latest BSOD :

Bugcheck code: 0xC4 (0xF6, 0x118, 0xFFFFFA8011878060, 0xFFFFF880093DA122)
Error: DRIVER_VERIFIER_DETECTED_VIOLATION
file path: C:\Program Files (x86)\MSI Afterburner\RTCore64.sys

Since it's a Beta version maybe this is the problem
Edited by denial_ - 4/5/12 at 10:38pm
post #16 of 22
Hi smile.gif

Driver Verifier labeled the culprit as RTCore64.sys (RivaTuner/EVGA Precision/MSI Afterburner (known issues w/Win7), which is exactly why you crashed after enabling it, because MSI Afterburner is usually on start up, especially if you have it set that way to boot with certain fan speeds, or whatever it may be.

Please fully uninstall MSI Afterburner for now and see if the problem goes away by enabling Driver Verifier and testing a boot again. If it doesn't BSOD, Afterburner is your final culprit, if it does, please attach the new BSOD you get.

I would recommend as I said above fully uninstalling MSI Afterburner before attempting to install a new non-beta version to ensure that it actually is the issue here.

Dump for reference:
Code:
Microsoft (R) Windows Debugger Version 6.12.0002.633 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Users\Icarus\Downloads\040512-23212-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: 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.17727.amd64fre.win7sp1_gdr.111118-2330
Machine Name:
Kernel base = 0xfffff800`03462000 PsLoadedModuleList = 0xfffff800`036a6650
Debug session time: Thu Apr  5 12:43:47.025 2012 (UTC - 4:00)
System Uptime: 0 days 0:00:39.822
Loading Kernel Symbols
...............................................................
................................................................
.........................................................
Loading User Symbols
Loading unloaded module list
....
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck C4, {f6, 118, fffffa8011878060, fffff880093da122}

Unable to load image \??\C:\Program Files (x86)\MSI Afterburner\RTCore64.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for RTCore64.sys
*** ERROR: Module load completed but symbols could not be loaded for RTCore64.sys
Probably caused by : RTCore64.sys ( RTCore64+1122 )

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

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

DRIVER_VERIFIER_DETECTED_VIOLATION (c4)
A device driver attempting to corrupt the system has been caught.  This is
because the driver was specified in the registry as being suspect (by the
administrator) and the kernel has enabled substantial checking of this driver.
If the driver attempts to corrupt the system, bugchecks 0xC4, 0xC1 and 0xA will
be among the most commonly seen crashes.
Arguments:
Arg1: 00000000000000f6, Referencing user handle as KernelMode.
Arg2: 0000000000000118, Handle value being referenced.
Arg3: fffffa8011878060, Address of the current process.
Arg4: fffff880093da122, Address inside the driver that is performing the incorrect reference.

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


BUGCHECK_STR:  0xc4_f6

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VERIFIER_ENABLED_VISTA_MINIDUMP

PROCESS_NAME:  MSIAfterburner

CURRENT_IRQL:  0

LAST_CONTROL_TRANSFER:  from fffff800039673dc to fffff800034ded40

STACK_TEXT:  
fffff880`07b61488 fffff800`039673dc : 00000000`000000c4 00000000`000000f6 00000000`00000118 fffffa80`11878060 : nt!KeBugCheckEx
fffff880`07b61490 fffff800`0397cae4 : 00000000`00000118 fffffa80`11878060 00000000`00000002 00000000`00000001 : nt!VerifierBugCheckIfAppropriate+0x3c
fffff880`07b614d0 fffff800`037351e0 : 00000000`00000000 fffff880`07b61700 00000000`00000000 00000000`00000000 : nt!VfCheckUserHandle+0x1b4
fffff880`07b615b0 fffff800`037b8085 : 00000000`00000000 00000000`000f001f 00000000`00000000 fffff800`037b8000 : nt! ?? ::NNGAKEGL::`string'+0x212ce
fffff880`07b61680 fffff800`0397c878 : 00000000`00000004 00000000`00000002 fffff880`07b61770 fffff800`034da570 : nt!ObReferenceObjectByHandle+0x25
fffff880`07b616d0 fffff880`093da122 : 00000000`f7e20000 00000000`00000002 00000000`00000004 fffff800`037f87e7 : nt!VerifierObReferenceObjectByHandle+0x48
fffff880`07b61720 00000000`f7e20000 : 00000000`00000002 00000000`00000004 fffff800`037f87e7 fffff880`07b617a8 : RTCore64+0x1122
fffff880`07b61728 00000000`00000002 : 00000000`00000004 fffff800`037f87e7 fffff880`07b617a8 00000000`00000000 : 0xf7e20000
fffff880`07b61730 00000000`00000004 : fffff800`037f87e7 fffff880`07b617a8 00000000`00000000 fffffa80`0fefe0d8 : 0x2
fffff880`07b61738 fffff800`037f87e7 : fffff880`07b617a8 00000000`00000000 fffffa80`0fefe0d8 fffff800`0397fbcc : 0x4
fffff880`07b61740 fffff800`03983c16 : fffff980`1252aee0 fffff980`1252aee0 fffffa80`119fdf20 fffffa80`0c95f218 : nt!IopXxxControlFile+0x607
fffff880`07b61870 fffff800`037f87e7 : fffffa80`119fdf20 fffff880`07b61b60 fffffa80`119fdf20 fffffa80`11a525f0 : nt!IovCallDriver+0x566
fffff880`07b618d0 fffff800`037f9046 : fffffa80`11878060 00000000`00000000 00000000`00000000 00000000`00000000 : nt!IopXxxControlFile+0x607
fffff880`07b61a00 fffff800`034ddfd3 : 00000000`00000010 00000000`00010246 fffff880`07b61a90 00000000`00000018 : nt!NtDeviceIoControlFile+0x56
fffff880`07b61a70 00000000`73db2e09 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
00000000`0008ec08 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x73db2e09


STACK_COMMAND:  kb

FOLLOWUP_IP: 
RTCore64+1122
fffff880`093da122 85c0            test    eax,eax

SYMBOL_STACK_INDEX:  6

SYMBOL_NAME:  RTCore64+1122

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: RTCore64

IMAGE_NAME:  RTCore64.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  4e661112

FAILURE_BUCKET_ID:  X64_0xc4_f6_VRF_RTCore64+1122

BUCKET_ID:  X64_0xc4_f6_VRF_RTCore64+1122

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

post #17 of 22
Thread Starter 
Well, I still get some BSOD about one a day frown.gif. I uninstalled MSI Afterburner and Alcohol 120% but now, I get a new BSO code : 4e, PFN_FILE_CORRUPT.

Any Ideas now? tongue.gif

040712-20248-01.zip 23k .zip file
post #18 of 22
Hi smile.gif

Latest dump is a *4E bugcheck with the culprit pointed to memory corruption. Many things can cause memory corruption, but the most common are: bad drivers, bad memory, unstable overclock.

1. Stop all overclocking if you are and bring all clocks back to stock values via the BIOS. You're more than welcome to overclock after we solve your issues.

2. If the overclock is not the issue, enable Driver Verifier again and do as you normally would. Once you crash, please attach the latest verifier enabled dump it will generate.

Thanks.

Dump for reference:
Code:
Microsoft (R) Windows Debugger Version 6.12.0002.633 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Users\Icarus\Downloads\040712-20248-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: 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.17727.amd64fre.win7sp1_gdr.111118-2330
Machine Name:
Kernel base = 0xfffff800`03409000 PsLoadedModuleList = 0xfffff800`0364d650
Debug session time: Sat Apr  7 18:14:23.985 2012 (UTC - 4:00)
System Uptime: 0 days 7:23:16.782
Loading Kernel Symbols
...............................................................
................................................................
.......................................................
Loading User Symbols
Loading unloaded module list
........
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 4E, {99, 19cd18, 0, b8998}

Probably caused by : memory_corruption ( nt!MiBadShareCount+4c )

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

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

PFN_LIST_CORRUPT (4e)
Typically caused by drivers passing bad memory descriptor lists (ie: calling
MmUnlockPages twice with the same list, etc).  If a kernel debugger is
available get the stack trace.
Arguments:
Arg1: 0000000000000099, A PTE or PFN is corrupt
Arg2: 000000000019cd18, page frame number
Arg3: 0000000000000000, current page state
Arg4: 00000000000b8998, 0

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


BUGCHECK_STR:  0x4E_99

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

PROCESS_NAME:  bf3.exe

CURRENT_IRQL:  2

LAST_CONTROL_TRANSFER:  from fffff8000350e20c to fffff80003485d40

STACK_TEXT:  
fffff880`0a5fcf88 fffff800`0350e20c : 00000000`0000004e 00000000`00000099 00000000`0019cd18 00000000`00000000 : nt!KeBugCheckEx
fffff880`0a5fcf90 fffff800`0342df39 : 00000000`00000000 fffff680`0058f290 00000000`00000002 00000000`00000001 : nt!MiBadShareCount+0x4c
fffff880`0a5fcfd0 fffff800`03455873 : fffffa80`0edb9770 fffff700`00058f93 0000007f`fffffff8 fffff8a0`03e87de8 : nt! ?? ::FNODOBFM::`string'+0x32971
fffff880`0a5fd060 fffff800`03456942 : fffffa80`0edb9770 fffffa80`0000000a 00000000`0004acdb fffff800`00000000 : nt!MiDeleteAddressesInWorkingSet+0x307
fffff880`0a5fd910 fffff800`0375a81a : fffff8a0`17822a10 00000000`00000001 00000000`00000000 fffffa80`0cd22b60 : nt!MmCleanProcessAddressSpace+0x96
fffff880`0a5fd960 fffff800`0373c0d8 : 00000000`00000000 00000000`00000001 00000000`fffdb000 00000000`00000000 : nt!PspExitThread+0x56a
fffff880`0a5fda60 fffff800`03484fd3 : fffffa80`0edb9770 fffff880`00000000 fffffa80`0cd22b60 fffffa80`0cfc1ac0 : nt!NtTerminateProcess+0x138
fffff880`0a5fdae0 00000000`76e215da : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
00000000`0008e808 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x76e215da


STACK_COMMAND:  kb

FOLLOWUP_IP: 
nt!MiBadShareCount+4c
fffff800`0350e20c cc              int     3

SYMBOL_STACK_INDEX:  1

SYMBOL_NAME:  nt!MiBadShareCount+4c

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nt

DEBUG_FLR_IMAGE_TIMESTAMP:  4ec79dd2

IMAGE_NAME:  memory_corruption

FAILURE_BUCKET_ID:  X64_0x4E_99_nt!MiBadShareCount+4c

BUCKET_ID:  X64_0x4E_99_nt!MiBadShareCount+4c

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

2: kd> !thread
GetPointerFromAddress: unable to read from fffff800036b7000
THREAD fffffa800cd22b60  Cid 11b4.0924  Teb: 0000000000000000 Win32Thread: 0000000000000000 RUNNING on processor 2
Not impersonating
GetUlongFromAddress: unable to read from fffff800035f6ba4
Owning Process            fffffa800edb9770       Image:         bf3.exe
Attached Process          N/A            Image:         N/A
fffff78000000000: Unable to get shared data
Wait Start TickCount      1704910      
Context Switch Count      617231                 LargeStack
ReadMemory error: Cannot get nt!KeMaximumIncrement value.
UserTime                  00:00:00.000
KernelTime                00:00:00.000
Win32 Start Address 0x00000000024904e0
Stack Init fffff8800a5fdc70 Current fffff8800a5fccc0
Base fffff8800a5fe000 Limit fffff8800a5f4000 Call 0
Priority 8 BasePriority 8 UnusualBoost 0 ForegroundBoost 0 IoPriority 2 PagePriority 5
Child-SP          RetAddr           : Args to Child                                                           : Call Site
fffff880`0a5fcf88 fffff800`0350e20c : 00000000`0000004e 00000000`00000099 00000000`0019cd18 00000000`00000000 : nt!KeBugCheckEx
fffff880`0a5fcf90 fffff800`0342df39 : 00000000`00000000 fffff680`0058f290 00000000`00000002 00000000`00000001 : nt!MiBadShareCount+0x4c
fffff880`0a5fcfd0 fffff800`03455873 : fffffa80`0edb9770 fffff700`00058f93 0000007f`fffffff8 fffff8a0`03e87de8 : nt! ?? ::FNODOBFM::`string'+0x32971
fffff880`0a5fd060 fffff800`03456942 : fffffa80`0edb9770 fffffa80`0000000a 00000000`0004acdb fffff800`00000000 : nt!MiDeleteAddressesInWorkingSet+0x307
fffff880`0a5fd910 fffff800`0375a81a : fffff8a0`17822a10 00000000`00000001 00000000`00000000 fffffa80`0cd22b60 : nt!MmCleanProcessAddressSpace+0x96
fffff880`0a5fd960 fffff800`0373c0d8 : 00000000`00000000 00000000`00000001 00000000`fffdb000 00000000`00000000 : nt!PspExitThread+0x56a
fffff880`0a5fda60 fffff800`03484fd3 : fffffa80`0edb9770 fffff880`00000000 fffffa80`0cd22b60 fffffa80`0cfc1ac0 : nt!NtTerminateProcess+0x138
fffff880`0a5fdae0 00000000`76e215da : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13 (TrapFrame @ fffff880`0a5fdae0)
00000000`0008e808 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x76e215da


Edited by pjBSOD - 4/8/12 at 1:05pm
post #19 of 22
Thread Starter 
Alright I'll stop the overclock smile.gif.

This BSOD error, I had it when I was getting out of BF3, quitting the full screen mode. Half of the time I was getting 3b code when I was going to do something from idle (maybe my computer doesn't like Intel SpeedStep). I got a strong feeling toward AMD Catalyst however...
post #20 of 22
Run without the overclock for now and keep me updated with any further crashes, etc smile.gif
New Posts  All Forums:Forum Nav:
  Return Home
  Back to Forum: Windows
Overclock.net › Forums › Software, Programming and Coding › Operating Systems › Windows › Random BSOD code 3b