BSOD after overclocking HELP

Toggle sidebar Toggle sidebar
S

s1nk0

Honorable
Dec 18, 2013
105
0
10,690
This is my mini dump log:

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 8 Kernel Version 9600 MP (6 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 9600.17736.amd64fre.winblue_r9.150322-1500
Machine Name:
Kernel base = 0xfffff800`90a7a000 PsLoadedModuleList = 0xfffff800`90d53850
Debug session time: Tue Apr 21 15:14:08.837 2015 (UTC - 4:00)
System Uptime: 0 days 3:51:28.535
*******************************************************************************
* *
* 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: fffff80090b647a0, Address of the instruction which caused the bugcheck
Arg3: ffffd00021a5a930, 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:
nt!KxWaitForLockOwnerShipWithIrql+14
fffff800`90b647a0 48890a mov qword ptr [rdx],rcx

CONTEXT: ffffd00021a5a930 -- (.cxr 0xffffd00021a5a930)
rax=0000000000000000 rbx=0000000000000000 rcx=ffffd00021a5b3e0
rdx=0020000000000000 rsi=0000000000000000 rdi=ffffd00021a5b3e0
rip=fffff80090b647a0 rsp=ffffd00021a5b360 rbp=ffffd00021a5b490
r8=ffffd00021a5b4e0 r9=ffffe001215de3c0 r10=ffffd00021a5b5c0
r11=fffff9014014a010 r12=0000000000000000 r13=fffff90140f52b00
r14=fffff90141299700 r15=ffffe0011e904780
iopl=0 nv up di pl zr na po nc
cs=0010 ss=0018 ds=002b es=002b fs=0053 gs=002b efl=00010046
nt!KxWaitForLockOwnerShipWithIrql+0x14:
fffff800`90b647a0 48890a mov qword ptr [rdx],rcx ds:002b:00200000`00000000=????????????????
Resetting default scope

DEFAULT_BUCKET_ID: WIN8_DRIVER_FAULT

BUGCHECK_STR: 0x3B

PROCESS_NAME: vegas130.exe

CURRENT_IRQL: 0

LAST_CONTROL_TRANSFER: from fffff80090b3d2af to fffff80090b647a0

STACK_TEXT:
ffffd000`21a5b360 fffff800`90b3d2af : ffffe001`215de3c0 00000000`00000000 ffffd000`21a5b728 00000000`00000000 : nt!KxWaitForLockOwnerShipWithIrql+0x14
ffffd000`21a5b390 fffff800`90b3c8a2 : fffff901`40f52b00 ffffd000`21a5bb80 ffffd000`21a5bb02 fffff901`41299770 : nt!ExpReleaseResourceForThreadLite+0x48f
ffffd000`21a5b4d0 fffff960`0008569c : fffff901`41244a10 fffff800`90b3b4fb ffffd000`21a5bb02 ffffe001`215de3c0 : nt!ExReleaseResourceAndLeaveCriticalRegion+0x12
ffffd000`21a5b500 fffff960`0004a042 : ffffe001`215de3c0 ffffd000`21a5b640 ffffd000`21a5b728 ffffd000`21a5b600 : win32k!SEMOBJ::vUnlock+0x2c
ffffd000`21a5b540 fffff960`0004bae2 : 00000000`00000011 ffffd000`21a5b7a0 00000000`00000000 00000000`00000004 : win32k!RFONTOBJ::bInit+0x832
ffffd000`21a5b690 fffff960`000bf89f : 00000000`00000000 00000000`00000000 ffffd000`21a5bcc0 00000000`00000000 : win32k!GreExtTextOutWLocked+0x322
ffffd000`21a5bb20 fffff960`000bfea9 : ffffd000`21a5bce8 ffffd000`21a5bcc8 ffffd000`21a5bcb0 00000000`00000001 : win32k!GreExtTextOutWInternal+0xdf
ffffd000`21a5bbf0 fffff800`90bd64b3 : 00000000`00000000 ffffd000`21a5bec0 00000000`00000000 00000000`00bfd828 : win32k!NtGdiExtTextOutW+0x309
ffffd000`21a5bdd0 00007ff8`72ae476a : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
00000000`00bfcf88 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x7ff8`72ae476a


FOLLOWUP_IP:
win32k!SEMOBJ::vUnlock+2c
fffff960`0008569c ff15beee3000 call qword ptr [win32k!_imp_PsLeavePriorityRegion (fffff960`00394560)]

SYMBOL_STACK_INDEX: 3

SYMBOL_NAME: win32k!SEMOBJ::vUnlock+2c

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: win32k

IMAGE_NAME: win32k.sys

DEBUG_FLR_IMAGE_TIMESTAMP: 54ee5a22

STACK_COMMAND: .cxr 0xffffd00021a5a930 ; kb

FAILURE_BUCKET_ID: X64_0x3B_win32k!SEMOBJ::vUnlock+2c

BUCKET_ID: X64_0x3B_win32k!SEMOBJ::vUnlock+2c

Followup: MachineOwner
---------
Click to expand...

I made sure my OC's are stable with Intel Burn Test and Afterburner, yet I'm still crashing. Someone please help. Thank you.
JavaScript:
 
Solution
hftvhftv


Never disable thermal throttling, that can save your CPU and board. There are also many other settings to change besides the core clock in order for it to be stable such as turbo, but all in all, I heavily do not recommend you do even the slightest overclock to your chip as your board is an extremely low end model with not heatsink on the MOSFET or VRMs as well as I see some Chinese capacitors. I'm sorry...
Sort by date Sort by votes
hftvhftv

hftvhftv

Distinguished
Ambassador
May 26, 2014
966
148
19,390

First off, the definition of stable is not blue screening, so you are not stable. What CPU, motherboard, etc and what settings do you have set in the BIOS?
 
Upvote 0 Downvote
S

s1nk0

Honorable
Dec 18, 2013
105
0
10,690
Hi, sorry.

My specs:
AMD FX 6300
Hyper 212 Evo
ASRock 960GM/U3S3
GTX 770 2GB
Rosewill CHALLENGER Black Gaming ATX Mid Tower
EVGA 600W 80PLUSB
G.SKILL Value Series 8GB (2 x 4GB)
Kingston 120GB V300 SSD
WD Blue 1 TB HD
Windows 8.1 64bit

Default BIOS settings except for CPU multiplier (3.8) and CPU Thermal Throttle disabled.
 
Upvote 0 Downvote
hftvhftv

hftvhftv

Distinguished
Ambassador
May 26, 2014
966
148
19,390


Never disable thermal throttling, that can save your CPU and board. There are also many other settings to change besides the core clock in order for it to be stable such as turbo, but all in all, I heavily do not recommend you do even the slightest overclock to your chip as your board is an extremely low end model with not heatsink on the MOSFET or VRMs as well as I see some Chinese capacitors. I'm sorry to say this, but your board is not fit for overclocking.
 
Upvote 0 Downvote
Solution
S

s1nk0

Honorable
Dec 18, 2013
105
0
10,690


That's rather unfortunate. :( Thank you, anyway.
 
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