Overclock.net › Forums › Intel › Intel - General › BlueScreen: 3b error code
New Posts  All Forums:Forum Nav:

BlueScreen: 3b error code

post #1 of 8
Thread Starter 
Before I hear, need moar voltage etc. Let me detail the stuff:

I am running @ 160x21 which is 3.3GHz. Signature is for gaming only, I don't feel quite well running 1.4v when web browsing, waste of electricity.

Voltage is quite low:
1.05vcore, 1.125VTT

I never had a single BSOD with this even on starcraft 2, benching (stress testing the signature video card clock) or normal use. It only happens on start-up, the mobo post and then re-post a couple of seconds later (3-4 sec I would say). Windows isn't even loaded up!
It's not the first time it happens, but it does sometimes, randomly though it's really not frequent.

So yea, I am looking for another explanation than "need more voltage", could this be instead related to software? Drivers?

BTW: I did stress test with Linx. I don't remember exactly how long, but it handled 1-2h no error.
I don't think it's related to low voltage, it's possible however but I am looking for an other explanation first smile.gif

Here is the codes:
Code:
Signature du problème :
  Nom d’événement de problème:  BlueScreen
  *sips*
Informations supplémentaires sur le problème :
  BCCode:       3b
  BCP1: 00000000C000001D
  BCP2: FFFFF80001FFA49F
  BCP3: FFFFF8800B06C130
  BCP4: 0000000000000000
  OS Version:   6_1_7601
  Service Pack: 1_0
  Product:      768_1

Fichiers aidant à décrire le problème :
  C:\Windows\Minidump\040212-9718-01.dmp
  C:\Windows\Temp\WER-11921-0.sysdata.xml

Lire notre déclaration de confidentialité en ligne :
  http://go.microsoft.com/fwlink/?linkid=104288&clcid=0x040c

Si la déclaration de confidentialité en ligne n’est pas disponible, lisez la version hors connexion :
  C:\Windows\system32\fr-FR\erofflps.txt
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 #2 of 8
The best way to diagnose whether or not this is software related is to bring your entire overclock back to stock. If it's unstable, it doesn't matter anyway and you can just re-overclock and hopefully get it stable this time.

Also, I'd like to take a look at your dump files just in case there is something else. Can you please navigate to C:/Windows/Minidump and zip / rar up your latest dump files? Once you've done that, please attach the zip / rar to your post by clicking the paperclip icon in the reply / post box.

If there are no files there, you may have it set to writing Kernel Memory Dumps rather than Small. If so, the DMP will be located in C:/Windows itself and named MEMORY.DMP.
post #3 of 8
Thread Starter 
Latest:
022812-10171-01.zip 24k .zip file

I have some other related to overclocking to 4.8+GHz, there is this one that I am not sure, could be the same BlueScreen type but couldn't certify since I sometimes play with my CPU.

040212-9718-01.zip 27k .zip file
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 #4 of 8
Latest dump attached is a *1E bugcheck, points to the culprit usbuhci.sys, which is the UHCI USB Miniport Driver. Very unlikely this is the cause, however it could be a peripheral or something related attached to a hub that's producing these crashes. An example would be a Razer device with bad drivers as they've been reported to have major issues, specifically Lachesis drivers.

The second dump attached is a *3B bugcheck with the culprit as memory corruption, many things can cause memory corruption: bad drivers, bad memory, unstable OC, etc.

With that being said, as I said earlier, it's very likely you just have an unstable OC here. As I said earlier, please reset it to stock and play around for a bit as usual, if you get no crashes, you know it was the OC. If you DO get crashes after bringing everything to default values via the bios, please attach the latest dump you receive and we'll work from there.

Few extra things to mention, after checking your drivers list, I have noticed you have dtsoftbus01.sys listed, which is the Daemon Tools driver. Daemon Tools is a very large cause of BSODs in Windows, so please fully uninstall Daemon Tools. A virutalization program that doesn't cause said issues or use sptd.sys as an example is Power ISO, etc.

Dumps 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\022812-10171-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 Personal
Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506
Machine Name:
Kernel base = 0xfffff800`01c14000 PsLoadedModuleList = 0xfffff800`01e59670
Debug session time: Tue Feb 28 09:52:04.789 2012 (UTC - 4:00)
System Uptime: 0 days 0:09:07.289
Loading Kernel Symbols
...............................................................
................................................................
......................
Loading User Symbols
Loading unloaded module list
......
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 1E, {0, 0, 0, 0}

Probably caused by : usbuhci.sys ( usbuhci!UhciPollAsyncEndpoint+114 )

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

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

KMODE_EXCEPTION_NOT_HANDLED (1e)
This is a very common bugcheck.  Usually the exception address pinpoints
the driver/function that caused the problem.  Always note this address
as well as the link date of the driver/image that contains this address.
Arguments:
Arg1: 0000000000000000, The exception code that was not handled
Arg2: 0000000000000000, The address that the exception occurred at
Arg3: 0000000000000000, Parameter 0 of the exception
Arg4: 0000000000000000, Parameter 1 of the exception

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


EXCEPTION_CODE: (Win32) 0 (0) - The operation completed successfully.

FAULTING_IP: 
+3139623530343132
00000000`00000000 ??              ???

EXCEPTION_PARAMETER1:  0000000000000000

EXCEPTION_PARAMETER2:  0000000000000000

ERROR_CODE: (NTSTATUS) 0 - STATUS_WAIT_0

BUGCHECK_STR:  0x1E_0

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

PROCESS_NAME:  System

CURRENT_IRQL:  2

EXCEPTION_RECORD:  fffff880009fa8e8 -- (.exr 0xfffff880009fa8e8)
ExceptionAddress: fffff8800526f2fc (usbuhci!UhciPollAsyncEndpoint+0x0000000000000114)
   ExceptionCode: c0000005 (Access violation)
  ExceptionFlags: 00000000
NumberParameters: 2
   Parameter[0]: 0000000000000000
   Parameter[1]: ffffffffffffffff
Attempt to read from address ffffffffffffffff

TRAP_FRAME:  fffff880009fa990 -- (.trap 0xfffff880009fa990)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=ff9ff880045e3b80 rbx=0000000000000000 rcx=fffffa8006cb47d0
rdx=fffff880045e3b40 rsi=0000000000000000 rdi=0000000000000000
rip=fffff8800526f2fc rsp=fffff880009fab20 rbp=fffff880045e3b00
 r8=000000004f444648  r9=000000007f64ab80 r10=00000000ffffffff
r11=fffffa8006c85c30 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei ng nz na pe nc
usbuhci!UhciPollAsyncEndpoint+0x114:
fffff880`0526f2fc 0fba600417      bt      dword ptr [rax+4],17h ds:8b40:ff9ff880`045e3b84=????????
Resetting default scope

LAST_CONTROL_TRANSFER:  from fffff80001c885fe to fffff80001c90c10

STACK_TEXT:  
fffff880`009f99c8 fffff800`01c885fe : fffffa80`05751a70 00000000`00000200 fffff880`009fa140 fffff800`01cbc830 : nt!KeBugCheck
fffff880`009f99d0 fffff800`01cbc4fd : fffff800`01e9a71c fffff800`01dd7c30 fffff800`01c14000 fffff880`009fa8e8 : nt!KiKernelCalloutExceptionHandler+0xe
fffff880`009f9a00 fffff800`01cbb2d5 : fffff800`01ddb0fc fffff880`009f9a78 fffff880`009fa8e8 fffff800`01c14000 : nt!RtlpExecuteHandlerForException+0xd
fffff880`009f9a30 fffff800`01ccc361 : fffff880`009fa8e8 fffff880`009fa140 fffff880`00000000 fffff880`045e3b80 : nt!RtlDispatchException+0x415
fffff880`009fa110 fffff800`01c902c2 : fffff880`009fa8e8 00000000`00000002 fffff880`009fa990 fffffa80`06cb4728 : nt!KiDispatchException+0x135
fffff880`009fa7b0 fffff800`01c8ebca : fffffa80`0637c330 00000000`00000000 fffff880`009e7180 fffffa80`0751f601 : nt!KiExceptionDispatch+0xc2
fffff880`009fa990 fffff880`0526f2fc : 00000000`00000002 fffffa80`06cb4728 fffffa80`06cb4728 fffffa80`06cb47e8 : nt!KiGeneralProtectionFault+0x10a
fffff880`009fab20 fffff880`0526c2d6 : 00000000`00000002 fffffa80`06cb44e0 00000000`00000000 fffffa80`0627a1a0 : usbuhci!UhciPollAsyncEndpoint+0x114
fffff880`009fab80 fffff880`050d4e8b : fffffa80`0627a1a0 00000000`00000002 00000000`00000000 00000000`00000040 : usbuhci!UhciPollEndpoint+0x1a
fffff880`009fabb0 fffff880`050d99d1 : 00000000`00000040 00000000`00000004 fffffa80`06cb44e0 fffffa80`0627a050 : USBPORT!MPf_PollEndpoint+0x9b
fffff880`009fabe0 fffff880`050e5077 : fffffa80`0627a1a0 00000000`00000040 fffffa80`0000000e 00000000`00000000 : USBPORT!USBPORT_iSetGlobalEndpointStateTx+0x7c1
fffff880`009fac40 fffff880`050d5f89 : fffffa80`0627a050 00000000`00000000 fffffa80`0627aa02 fffffa80`0627aa18 : USBPORT!USBPORT_Core_UsbHcIntDpc_Worker+0x1c3
fffff880`009faca0 fffff800`01c9c0ac : fffff880`009e7180 fffffa80`0627aa18 fffffa80`0627aa30 00000000`00000000 : USBPORT!USBPORT_Xdpc_Worker+0x1d9
fffff880`009facd0 fffff800`01c8896a : fffff880`009e7180 fffff880`009f1fc0 00000000`00000000 fffff880`050d5db0 : nt!KiRetireDpcList+0x1bc
fffff880`009fad80 00000000`00000000 : fffff880`009fb000 fffff880`009f5000 fffff880`009fad40 00000000`00000000 : nt!KiIdleLoop+0x5a


STACK_COMMAND:  kb

FOLLOWUP_IP: 
usbuhci!UhciPollAsyncEndpoint+114
fffff880`0526f2fc 0fba600417      bt      dword ptr [rax+4],17h

SYMBOL_STACK_INDEX:  7

SYMBOL_NAME:  usbuhci!UhciPollAsyncEndpoint+114

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: usbuhci

IMAGE_NAME:  usbuhci.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  4a5bcc03

FAILURE_BUCKET_ID:  X64_0x1E_0_usbuhci!UhciPollAsyncEndpoint+114

BUCKET_ID:  X64_0x1E_0_usbuhci!UhciPollAsyncEndpoint+114

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



Microsoft (R) Windows Debugger Version 6.12.0002.633 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Users\Icarus\Downloads\040212-9718-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 Personal
Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506
Machine Name:
Kernel base = 0xfffff800`01c66000 PsLoadedModuleList = 0xfffff800`01eab670
Debug session time: Mon Apr  2 17:08:29.524 2012 (UTC - 4:00)
System Uptime: 0 days 0:00:15.071
Loading Kernel Symbols
...............................................................
................................................................
..................
Loading User Symbols
Loading unloaded module list
.....
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 3B, {c000001d, fffff80001ffa49f, fffff8800b06c130, 0}

Probably caused by : memory_corruption

Followup: memory_corruption
---------

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

SYSTEM_SERVICE_EXCEPTION (3b)
An exception happened while executing a system service routine.
Arguments:
Arg1: 00000000c000001d, Exception code that caused the bugcheck
Arg2: fffff80001ffa49f, Address of the instruction which caused the bugcheck
Arg3: fffff8800b06c130, Address of the context record for the exception that caused the bugcheck
Arg4: 0000000000000000, zero.

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


EXCEPTION_CODE: (NTSTATUS) 0xc000001d - {EXCEPTION}  Illegal Instruction  An attempt was made to execute an illegal instruction.

FAULTING_IP: 
nt!MiUnmapViewOfSection+42f
fffff800`01ffa49f 82              ???

CONTEXT:  fffff8800b06c130 -- (.cxr 0xfffff8800b06c130)
rax=0000000000000030 rbx=fffffa80071eb9a0 rcx=0000000000000030
rdx=000000000000002e rsi=fffffa8007200060 rdi=fffffa8006854060
rip=fffff80001ffa49f rsp=fffff8800b06cb10 rbp=0000000000000002
 r8=fffff88001ece180  r9=0000000000000100 r10=fffffa8006cfc580
r11=fffff80001e6b900 r12=0007ffffffffffff r13=0000000000000000
r14=000000007706efff r15=0000000076f50000
iopl=0         nv up ei ng nz na po cy
cs=0010  ss=0018  ds=002b  es=002b  fs=0053  gs=002b             efl=00010287
nt!MiUnmapViewOfSection+0x42f:
fffff800`01ffa49f 82              ???
Resetting default scope

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  CODE_CORRUPTION

BUGCHECK_STR:  0x3B

PROCESS_NAME:  SDCleaner.exe

CURRENT_IRQL:  0

LAST_CONTROL_TRANSFER:  from fffff80001ffa623 to fffff80001ffa49f

STACK_TEXT:  
fffff880`0b06cb10 fffff800`01ffa623 : 0000007f`00000000 00000000`76f50000 fffffa80`00000001 fffffa80`068df910 : nt!MiUnmapViewOfSection+0x42f
fffff880`0b06cbd0 fffff800`01ce1ed3 : 00000000`00000000 00000000`76ff449c fffffa80`07200060 00000000`76ff161c : nt!NtUnmapViewOfSection+0x5f
fffff880`0b06cc20 00000000`771c15ba : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
00000000`0008e698 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x771c15ba


CHKIMG_EXTENSION: !chkimg -lo 50 -d !nt
    fffff80001ffa49f - nt!MiUnmapViewOfSection+42f
        [ 8b:82 ]
1 error : !nt (fffff80001ffa49f)

MODULE_NAME: memory_corruption

IMAGE_NAME:  memory_corruption

FOLLOWUP_NAME:  memory_corruption

DEBUG_FLR_IMAGE_TIMESTAMP:  0

MEMORY_CORRUPTOR:  ONE_BYTE

STACK_COMMAND:  .cxr 0xfffff8800b06c130 ; kb

FAILURE_BUCKET_ID:  X64_MEMORY_CORRUPTION_ONE_BYTE

BUCKET_ID:  X64_MEMORY_CORRUPTION_ONE_BYTE

Followup: memory_corruption
---------



post #5 of 8
Thread Starter 
Woa, you sir is a pro.
What else did you see? biggrin.gif

I indeed have a razer keyboard... I will check how I can put it up to date.
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 #6 of 8
Razer drivers can be downloaded / updated here. Keep me updated.
post #7 of 8
Thread Starter 
Thanks for your help again.
Updated driver or the keyboard and uninstalled daemon tool on my other disk. Weird thing is that I don't have it on my SSD but it does load from the HDD (which also have windows installed on it) when I am booting from the SSD.
We'll see if it happens again, hope not!

Edit: I just searched on the net. I have a lycosa keyboard. I hope the driver update won't also cause BSOD.
http://www.sevenforums.com/crashes-debugging/170569-cant-figure-out-whats-causing-bsod.html
Edited by Just a nickname - 4/2/12 at 6:34pm
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 #8 of 8
I'll ask you to enable verifier if you do keep BSOD'ing, this will show us if the driver that is causing BSODs is in fact the Lycosa driver. We'll worry about that when and if we have to smile.gif
New Posts  All Forums:Forum Nav:
  Return Home
  Back to Forum: Intel - General
Overclock.net › Forums › Intel › Intel - General › BlueScreen: 3b error code