Overclock.net › Forums › Intel › Intel CPUs › BSOD x101
New Posts  All Forums:Forum Nav:

BSOD x101

post #1 of 11
Thread Starter 
Problems have started to arise with my i3-550. I have it clocked at 4ghz @ 1.27v and it was tested in prime for about 30 hours with no issues. The other day I turned on the monitor to find that the SMP folding@home core had "stopped responding". I hit close program and FAH started up a new process and continued where it left off. This morning I awoke to find the same result. I hit close program, FAH continued on its merry way. I just came home from work to find a BSOD error x101.

vcore: 1.275v
IMC: Auto
DRAM: 1.5v
PLL: 1.80v
PCH: Auto
LLC: Enabled
CPU Spread Spectrum: Disabled
C1E: Disabled
MAX CPUID: Disabled
CPU TM: Disabled
A20M: Disabled


Does anyone know what might be causing this? I should also note that the PC had been on for about 4 Days before the first FAH core failure.
post #2 of 11
Just in case this is not overclock related:

Please navigate to C:/Windows/Minidump and zip up any dump files located there that you'd like to have analyzed, and then attach that zip here. If there are no dumps located in C:/Windows/Minump, you may be writing full memory dumps to C:/Windows, and it'll be called MEMORY.DMP.

If there are no dumps in either of those locations, but you know you have a page file set up, any "cleaner" programs such as TuneUp Utilities, CCleaner, etc, will delete this upon use.

If you cannot get into Windows, please try and get into Safe Mode and access the dump files this way.
post #3 of 11
Thread Starter 
The only DMP files I have in both C:\Windows and Minidump are both from 4/13/12. And Ive already checked the systems date and it is correct. It appears no dump file was made for this BSOD.

I guess I'll just wait and see if it happens again, and hope a dump file gets made.
Edited by Bryst - 5/3/12 at 9:14pm
post #4 of 11
Thread Starter 
PC did it again today at 3:03AM. This time it did make a minidump and dump file.

Minidump:
050412-13338-01.zip 29k .zip file
post #5 of 11
1e bugcheck with the culprit pointing to USBPORT.sys. It can be a device connected via USB and there's a driver issue with this device (unlikely), or Windows pointed that as the culprit and it is wrong.

The system crashed during FaHCore, which I can only assume is a folding client, and your system was under load, so your overclock is unstable or it may be hardware related. Loaded drivers look alright, no popular culprits or any out-of-date drivers from what I can see that would raise flags.

#1. Stop overclocking. Bring any and all overclocks back to stock settings for now to ensure this is the issue and you don't BSOD at stock settings.

#2. If you're still BSOD'ing afterwards, run Memtest to test your memory for errors.

I recommend 7 or 8 passes, no less.

#3. Test your GPU(s) with Furmark to ensure there's no artifacting or issues on load.

#4. Chkdsk:
Quote:
Open the "Computer" window
Right-click on the drive in question
Select the "Tools" tab
In the Error-checking area, click .

#5. Last but not least, if nothing's showing up hardware wise, enable Driver Verifier and attach the verifier enabled dump after you BSOD.

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\Cardbox\Downloads\050412-13338-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*C:\SymCache*http://msdl.microsoft.com/download/symbols
Executable search path is: 
Windows 7 Kernel Version 7600 MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Machine Name:
Kernel base = 0xfffff800`0324b000 PsLoadedModuleList = 0xfffff800`03488e50
Debug session time: Fri May  4 04:02:25.054 2012 (UTC - 4:00)
System Uptime: 0 days 4:54:50.162
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 : USBPORT.SYS ( USBPORT!USBPORT_Core_iCompleteDoneTransfer+45f )

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

3: 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: 
+6531623034336533
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:  FahCore_a4.exe

CURRENT_IRQL:  2

EXCEPTION_RECORD:  fffff880009b0a08 -- (.exr 0xfffff880009b0a08)
ExceptionAddress: fffff800033f029f (nt!ExFreePoolWithTag+0x00000000000001ef)
   ExceptionCode: c000001d (Illegal instruction)
  ExceptionFlags: 00000000
NumberParameters: 0

TRAP_FRAME:  fffff880009b0ab0 -- (.trap 0xfffff880009b0ab0)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=0000000000000200 rbx=0000000000000000 rcx=0000000000001c8e
rdx=fffff88002fd3180 rsi=0000000000000000 rdi=0000000000000000
rip=fffff800033f029f rsp=fffff880009b0c40 rbp=0000000000000000
 r8=000000000000e470  r9=00000000000000e0 r10=fffff8000324b000
r11=00000000000005b6 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei ng nz ac po cy
nt!ExFreePoolWithTag+0x1ef:
fffff800`033f029f 66833d612d100001 cmp     word ptr [nt!KeNumberNodes (fffff800`034f3008)],1 ds:ffff:fffff800`034f3008=????
Resetting default scope

LAST_CONTROL_TRANSFER:  from fffff800032b4c2e to fffff800032bced0

STACK_TEXT:  
fffff880`009afae8 fffff800`032b4c2e : fffff880`009afd00 00000000`00000002 fffff880`009b0260 fffff800`032e9e28 : nt!KeBugCheck
fffff880`009afaf0 fffff800`032e2bed : fffff800`034c9c24 fffff800`03402a3c fffff800`0324b000 fffff880`009b0a08 : nt!KiKernelCalloutExceptionHandler+0xe
fffff880`009afb20 fffff800`032ea250 : fffff800`0340aa88 fffff880`009afb98 fffff880`009b0a08 fffff800`0324b000 : nt!RtlpExecuteHandlerForException+0xd
fffff880`009afb50 fffff800`032f71b5 : fffff880`009b0a08 fffff880`009b0260 fffff880`00000000 00000000`00000000 : nt!RtlDispatchException+0x410
fffff880`009b0230 fffff800`032bc542 : fffff880`009b0a08 fffffa80`07e188e0 fffff880`009b0ab0 00000000`00000002 : nt!KiDispatchException+0x135
fffff880`009b08d0 fffff800`032ba69f : fffff880`009b0ab0 fffff880`0fd77402 fffffa80`04bf0700 00000000`00000000 : nt!KiExceptionDispatch+0xc2
fffff880`009b0ab0 fffff800`033f029f : fffffa80`05230250 fffff880`042a7d70 fffffa80`052303c0 fffff880`042a70d8 : nt!KiInvalidOpcodeFault+0x11f
fffff880`009b0c40 fffff800`03206865 : fffffa80`04d20010 00000000`000004a8 00000000`206c6148 fffffa80`04d20010 : nt!ExFreePoolWithTag+0x1ef
fffff880`009b0cf0 fffff880`0428d023 : fffffa80`0423c1a0 fffffa80`02e0de28 fffffa80`0423c050 fffffa80`0423c1a0 : hal!HalPutScatterGatherList+0x115
fffff880`009b0d50 fffff880`0428dab7 : fffffa80`02e0da02 fffffa80`0799ec60 00000000`ffffffff fffffa80`0423cea8 : USBPORT!USBPORT_Core_iCompleteDoneTransfer+0x45f
fffff880`009b0e30 fffff880`0428b64f : fffffa80`0423cea8 fffffa80`0423c1a0 fffffa80`0423d040 00000000`00000000 : USBPORT!USBPORT_Core_iIrpCsqCompleteDoneTransfer+0x3a7
fffff880`009b0e90 fffff880`0427cf89 : fffffa80`0423c050 00000000`00000000 fffffa80`0423ce02 fffffa80`0423cea8 : USBPORT!USBPORT_Core_UsbIocDpc_Worker+0xf3
fffff880`009b0ed0 fffff800`032c85dc : fffff880`02fd3180 fffffa80`0423cea8 fffffa80`0423cec0 00000000`00000000 : USBPORT!USBPORT_Xdpc_Worker+0x1d9
fffff880`009b0f00 fffff800`032c3065 : 01000001`00000100 fffffa80`07870060 00000000`00000000 fffff880`0427cdb0 : nt!KiRetireDpcList+0x1bc
fffff880`009b0fb0 fffff800`032c2e7c : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxRetireDpcList+0x5
fffff880`0841ebe0 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiDispatchInterruptContinue


STACK_COMMAND:  kb

FOLLOWUP_IP: 
USBPORT!USBPORT_Core_iCompleteDoneTransfer+45f
fffff880`0428d023 4533c0          xor     r8d,r8d

SYMBOL_STACK_INDEX:  9

SYMBOL_NAME:  USBPORT!USBPORT_Core_iCompleteDoneTransfer+45f

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: USBPORT

IMAGE_NAME:  USBPORT.SYS

DEBUG_FLR_IMAGE_TIMESTAMP:  4a5bcc07

FAILURE_BUCKET_ID:  X64_0x1E_0_USBPORT!USBPORT_Core_iCompleteDoneTransfer+45f

BUCKET_ID:  X64_0x1E_0_USBPORT!USBPORT_Core_iCompleteDoneTransfer+45f

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

3: kd> .trap 0xfffff880009b0ab0
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=0000000000000200 rbx=0000000000000000 rcx=0000000000001c8e
rdx=fffff88002fd3180 rsi=0000000000000000 rdi=0000000000000000
rip=fffff800033f029f rsp=fffff880009b0c40 rbp=0000000000000000
 r8=000000000000e470  r9=00000000000000e0 r10=fffff8000324b000
r11=00000000000005b6 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei ng nz ac po cy
nt!ExFreePoolWithTag+0x1ef:
fffff800`033f029f 66833d612d100001 cmp     word ptr [nt!KeNumberNodes (fffff800`034f3008)],1 ds:ffff:fffff800`034f3008=????
post #6 of 11
Thread Starter 
Awesome, thanks for your help. I am wondering, you say that it could be a device using a USB port? I am using a Edimax EW-7811Un mini USB card with the machine. Could that be causing the issue? I am going to default my clock and test my GPU, though I doubt its the GPU, eveytime FAH crashes its the CPU core.
post #7 of 11
Quote:
Originally Posted by Bryst View Post

Awesome, thanks for your help. I am wondering, you say that it could be a device using a USB port? I am using a Edimax EW-7811Un mini USB card with the machine. Could that be causing the issue?

It could be, but since you crashed during FaH, and it was the CPU cores that failed, it's most likely an unstable overclock and I'd like for you to take care of that first to make sure.
post #8 of 11
Thread Starter 
Okay, Ive reset my CPU to stock, but am going to keep the GPU overclocked. If it does it again, ill reset the GPU and test that way.

I find it odd that the CPU can pass 30 hours in prime, but now it cant handle 5 hours of folding without crashing.
post #9 of 11
Quote:
Originally Posted by Bryst View Post

Okay, Ive reset my CPU to stock, but am going to keep the GPU overclocked. If it does it again, ill reset the GPU and test that way.

Keep me updated.
post #10 of 11
Thread Starter 
Well the PC last the night and is still running. What would cause instability like that? Could it be the power supply? When the GPU is added to the power draw, there is a larger fluctuation in the voltage or something?
New Posts  All Forums:Forum Nav:
  Return Home
  Back to Forum: Intel CPUs
Overclock.net › Forums › Intel › Intel CPUs › BSOD x101