brand new computer, still got bsod
Here is the cause of your problem: Company: Fresco Logic Description: xHCI Hub Driver *1 Regards Milos
January 8th, 2012 3:35pm

I went into device manager and tried to update the driver thru it's auto online search, but it says the best driver software for the device is already installed. Is there a better version than my current one? If so, where can I find it? I did some search online but had no luck finding it. -Vincent
Free Windows Admin Tool Kit Click here and download it now
January 8th, 2012 5:57pm

P1 = c0000005 is not conclusive in this case, but the dump seems to be pointing to FLxHCIc.sys. Since you identified that this driver is not available via Windows Update, you may want to see if there is a newer (or older) version on the manufacturer's web site to try. 6: kd> !analyze -v ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M (1000007e) 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. Some common problems are exception code 0x80000003. This means a hard coded breakpoint or assertion was hit, but this system was booted /NODEBUG. This is not supposed to happen as developers should never have hardcoded breakpoints in retail code, but ... If this happens, make sure a debugger gets connected, and the system is booted /DEBUG. This will let us see why this breakpoint is happening. Arguments: Arg1: ffffffffc0000005, The exception code that was not handled Arg2: fffff88004c76370, The address that the exception occurred at Arg3: fffff880035770d8, Exception Record Address Arg4: fffff88003576930, Context Record Address Debugging Details: ------------------ EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s. FAULTING_IP: FLxHCIc+3370 fffff880`04c76370 48897818 mov qword ptr [rax+18h],rdi EXCEPTION_RECORD: fffff880035770d8 -- (.exr 0xfffff880035770d8) ExceptionAddress: fffff88004c76370 (FLxHCIc+0x0000000000003370) ExceptionCode: c0000005 (Access violation) ExceptionFlags: 00000000 NumberParameters: 2 Parameter[0]: 0000000000000001 Parameter[1]: 0000000000000018 Attempt to write to address 0000000000000018 CONTEXT: fffff88003576930 -- (.cxr 0xfffff88003576930) rax=0000000000000000 rbx=fffff88003577710 rcx=fffffa8010537390 rdx=fffffa8010537390 rsi=0000000000000000 rdi=fffffa8010537390 rip=fffff88004c76370 rsp=fffff88003577310 rbp=fffff88004cb8308 r8=0000000000000000 r9=0000000000000000 r10=0000000000000002 r11=0000000000000000 r12=fffff88004cb8308 r13=fffff88004cb8308 r14=0000000000000001 r15=0000000000000006 iopl=0 nv up ei pl nz ac po nc cs=0010 ss=0018 ds=002b es=002b fs=0053 gs=002b efl=00010216 FLxHCIc+0x3370: fffff880`04c76370 48897818 mov qword ptr [rax+18h],rdi ds:002b:00000000`00000018=???????????????? Resetting default scope CUSTOMER_CRASH_COUNT: 1 PROCESS_NAME: System CURRENT_IRQL: 0 ERROR_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s. EXCEPTION_PARAMETER1: 0000000000000001 EXCEPTION_PARAMETER2: 0000000000000018 WRITE_ADDRESS: GetPointerFromAddress: unable to read from fffff800034cd100 0000000000000018 FOLLOWUP_IP: FLxHCIc+3370 fffff880`04c76370 48897818 mov qword ptr [rax+18h],rdi BUGCHECK_STR: 0x7E DEFAULT_BUCKET_ID: NULL_CLASS_PTR_DEREFERENCE LAST_CONTROL_TRANSFER: from 0000000000000001 to fffff88004c76370 STACK_TEXT: fffff880`03577310 00000000`00000001 : 00000000`00000003 00000000`00000021 fffffa80`10537390 fffffa80`10488370 : FLxHCIc+0x3370 fffff880`03577318 00000000`00000003 : 00000000`00000021 fffffa80`10537390 fffffa80`10488370 fffff880`04c76455 : 0x1 fffff880`03577320 00000000`00000021 : fffffa80`10537390 fffffa80`10488370 fffff880`04c76455 fffffa80`10537390 : 0x3 fffff880`03577328 fffffa80`10537390 : fffffa80`10488370 fffff880`04c76455 fffffa80`10537390 fffff880`03577710 : 0x21 fffff880`03577330 fffffa80`10488370 : fffff880`04c76455 fffffa80`10537390 fffff880`03577710 00000000`00000000 : 0xfffffa80`10537390 fffff880`03577338 fffff880`04c76455 : fffffa80`10537390 fffff880`03577710 00000000`00000000 00000000`00000000 : 0xfffffa80`10488370 fffff880`03577340 fffffa80`10537390 : fffff880`03577710 00000000`00000000 00000000`00000000 fffff880`03577710 : FLxHCIc+0x3455 fffff880`03577348 fffff880`03577710 : 00000000`00000000 00000000`00000000 fffff880`03577710 fffff880`04c95807 : 0xfffffa80`10537390 fffff880`03577350 00000000`00000000 : 00000000`00000000 fffff880`03577710 fffff880`04c95807 00000000`00000000 : 0xfffff880`03577710 SYMBOL_STACK_INDEX: 0 SYMBOL_NAME: FLxHCIc+3370 FOLLOWUP_NAME: MachineOwner MODULE_NAME: FLxHCIc IMAGE_NAME: FLxHCIc.sys DEBUG_FLR_IMAGE_TIMESTAMP: 4d661e08 STACK_COMMAND: .cxr 0xfffff88003576930 ; kb FAILURE_BUCKET_ID: X64_0x7E_FLxHCIc+3370 BUCKET_ID: X64_0x7E_FLxHCIc+3370 Followup: MachineOwner --------- 6: kd> lmvm FLxHCIc start end module name fffff880`04c73000 fffff880`04cc3000 FLxHCIc T (no symbols) Loaded symbol image file: FLxHCIc.sys Image path: \SystemRoot\system32\DRIVERS\FLxHCIc.sys Image name: FLxHCIc.sys Timestamp: Thu Feb 24 01:59:52 2011 (4D661E08) CheckSum: 0004C3F2 ImageSize: 00050000 Translations: 0000.04b0 0000.04e4 0409.04b0 0409.04e4 -- Mike Burr Technology
January 8th, 2012 9:09pm

I just bought a brand new computer about a month ago, windows 7 home premium pre-installed with manufacture warranty, but still got bsod twice this weekend. I was running windows backup and virus scan and left the computer on over night. When I come back in the morning, I got the same error message twice. Please have a look at the error message and the dump files below and let me know what I should do to fix this problem, thank you. Problem signature: Problem Event Name: BlueScreen OS Version: 6.1.7601.2.1.0.768.3 Locale ID: 1033 Additional information about the problem: BCCode: 1000007e BCP1: FFFFFFFFC0000005 BCP2: FFFFF88004D24370 BCP3: FFFFF880035770D8 BCP4: FFFFF88003576930 OS Version: 6_1_7601 Service Pack: 1_0 Product: 768_1 Files that help describe the problem: C:\Windows\Minidump\010812-23524-01.dmp C:\Users\fuzzybear\AppData\Local\Temp\WER-65754-0.sysdata.xml Read our privacy statement online: http://go.microsoft.com/fwlink/?linkid=104288&clcid=0x0409 If the online privacy statement is not available, please read our privacy statement offline: C:\Windows\system32\en-US\erofflps.txt http://www.mediafire.com/?ba2110sf0q9cdn8 http://www.mediafire.com/?b31v9ihrju3arpb
Free Windows Admin Tool Kit Click here and download it now
January 9th, 2012 3:42am

1. If it is new computer with preinstalled operating system, the you have an option to address svendor's support 2. Unfortunately you heve not specified more your computer. If you have NVIDIA graphic card, the try to install new driver. 3. Test your hardware, namely RAM with memtest and hard disc with disc vendor testing tools. 4. Download minidump viewer from Nirsoft and analyze your minidump file. Regards Milos
January 9th, 2012 4:56am

P1 = c0000005 is not conclusive in this case, but the dump seems to be pointing to FLxHCIc.sys. Since you identified that this driver is not available via Windows Update, you may want to see if there is a newer (or older) version on the manufacturer's web site to try. 6: kd> !analyze -v ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M (1000007e) 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. Some common problems are exception code 0x80000003. This means a hard coded breakpoint or assertion was hit, but this system was booted /NODEBUG. This is not supposed to happen as developers should never have hardcoded breakpoints in retail code, but ... If this happens, make sure a debugger gets connected, and the system is booted /DEBUG. This will let us see why this breakpoint is happening. Arguments: Arg1: ffffffffc0000005, The exception code that was not handled Arg2: fffff88004c76370, The address that the exception occurred at Arg3: fffff880035770d8, Exception Record Address Arg4: fffff88003576930, Context Record Address Debugging Details: ------------------ EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s. FAULTING_IP: FLxHCIc+3370 fffff880`04c76370 48897818 mov qword ptr [rax+18h],rdi EXCEPTION_RECORD: fffff880035770d8 -- (.exr 0xfffff880035770d8) ExceptionAddress: fffff88004c76370 (FLxHCIc+0x0000000000003370) ExceptionCode: c0000005 (Access violation) ExceptionFlags: 00000000 NumberParameters: 2 Parameter[0]: 0000000000000001 Parameter[1]: 0000000000000018 Attempt to write to address 0000000000000018 CONTEXT: fffff88003576930 -- (.cxr 0xfffff88003576930) rax=0000000000000000 rbx=fffff88003577710 rcx=fffffa8010537390 rdx=fffffa8010537390 rsi=0000000000000000 rdi=fffffa8010537390 rip=fffff88004c76370 rsp=fffff88003577310 rbp=fffff88004cb8308 r8=0000000000000000 r9=0000000000000000 r10=0000000000000002 r11=0000000000000000 r12=fffff88004cb8308 r13=fffff88004cb8308 r14=0000000000000001 r15=0000000000000006 iopl=0 nv up ei pl nz ac po nc cs=0010 ss=0018 ds=002b es=002b fs=0053 gs=002b efl=00010216 FLxHCIc+0x3370: fffff880`04c76370 48897818 mov qword ptr [rax+18h],rdi ds:002b:00000000`00000018=???????????????? Resetting default scope CUSTOMER_CRASH_COUNT: 1 PROCESS_NAME: System CURRENT_IRQL: 0 ERROR_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s. EXCEPTION_PARAMETER1: 0000000000000001 EXCEPTION_PARAMETER2: 0000000000000018 WRITE_ADDRESS: GetPointerFromAddress: unable to read from fffff800034cd100 0000000000000018 FOLLOWUP_IP: FLxHCIc+3370 fffff880`04c76370 48897818 mov qword ptr [rax+18h],rdi BUGCHECK_STR: 0x7E DEFAULT_BUCKET_ID: NULL_CLASS_PTR_DEREFERENCE LAST_CONTROL_TRANSFER: from 0000000000000001 to fffff88004c76370 STACK_TEXT: fffff880`03577310 00000000`00000001 : 00000000`00000003 00000000`00000021 fffffa80`10537390 fffffa80`10488370 : FLxHCIc+0x3370 fffff880`03577318 00000000`00000003 : 00000000`00000021 fffffa80`10537390 fffffa80`10488370 fffff880`04c76455 : 0x1 fffff880`03577320 00000000`00000021 : fffffa80`10537390 fffffa80`10488370 fffff880`04c76455 fffffa80`10537390 : 0x3 fffff880`03577328 fffffa80`10537390 : fffffa80`10488370 fffff880`04c76455 fffffa80`10537390 fffff880`03577710 : 0x21 fffff880`03577330 fffffa80`10488370 : fffff880`04c76455 fffffa80`10537390 fffff880`03577710 00000000`00000000 : 0xfffffa80`10537390 fffff880`03577338 fffff880`04c76455 : fffffa80`10537390 fffff880`03577710 00000000`00000000 00000000`00000000 : 0xfffffa80`10488370 fffff880`03577340 fffffa80`10537390 : fffff880`03577710 00000000`00000000 00000000`00000000 fffff880`03577710 : FLxHCIc+0x3455 fffff880`03577348 fffff880`03577710 : 00000000`00000000 00000000`00000000 fffff880`03577710 fffff880`04c95807 : 0xfffffa80`10537390 fffff880`03577350 00000000`00000000 : 00000000`00000000 fffff880`03577710 fffff880`04c95807 00000000`00000000 : 0xfffff880`03577710 SYMBOL_STACK_INDEX: 0 SYMBOL_NAME: FLxHCIc+3370 FOLLOWUP_NAME: MachineOwner MODULE_NAME: FLxHCIc IMAGE_NAME: FLxHCIc.sys DEBUG_FLR_IMAGE_TIMESTAMP: 4d661e08 STACK_COMMAND: .cxr 0xfffff88003576930 ; kb FAILURE_BUCKET_ID: X64_0x7E_FLxHCIc+3370 BUCKET_ID: X64_0x7E_FLxHCIc+3370 Followup: MachineOwner --------- 6: kd> lmvm FLxHCIc start end module name fffff880`04c73000 fffff880`04cc3000 FLxHCIc T (no symbols) Loaded symbol image file: FLxHCIc.sys Image path: \SystemRoot\system32\DRIVERS\FLxHCIc.sys Image name: FLxHCIc.sys Timestamp: Thu Feb 24 01:59:52 2011 (4D661E08) CheckSum: 0004C3F2 ImageSize: 00050000 Translations: 0000.04b0 0000.04e4 0409.04b0 0409.04e4 -- Mike Burr Technology
Free Windows Admin Tool Kit Click here and download it now
January 9th, 2012 5:07am

Hello, here is a starting point for blue screen analysis http://mikemstech.blogspot.com/2011/11/windows-crash-dump-analysis.html parameter 1 indicates memory corruption (c0000005), please enable driver verifier, wait for a few crashes, and upload the dumps from c:\windows\minidump to skydrive and post a link http://mikemstech.blogspot.com/2011/12/enable-driver-verifier-to-help-identify.html http://mikemstech.blogspot.com/2010/08/skydrive-uploading-files-for-community.html -- Mike Burr Technology
January 9th, 2012 5:19am

Thank you ver much for your info. I just got another BSOD. This time it happened when I was working on the computer, not from leaving it running over night. Please have a look at the dump file below. Should I stop backing up windows to my external hard drive? Is that the cause for the 3 BSODs I had over the weekend? http://www.mediafire.com/?4k7dce4ae4q0buc -Vincent
Free Windows Admin Tool Kit Click here and download it now
January 9th, 2012 6:13am

This topic is archived. No further replies will be accepted.

Other recent topics Other recent topics