-
×InformationNeed Windows 11 help?Check documents on compatibility, FAQs, upgrade information and available fixes.
Windows 11 Support Center. -
-
×InformationNeed Windows 11 help?Check documents on compatibility, FAQs, upgrade information and available fixes.
Windows 11 Support Center. -
- HP Community
- Desktops
- Desktop Boot and Lockup
- Intermittent BSOD each day tixhci.sys

Create an account on the HP Community to personalize your profile and ask a question
06-14-2012 05:59 PM
Hi All,
Have HPE h8-1120a Desktop PC and is crashing every once a day or so. Mini dump is created and have run an analysis against them and see there is an access violation occuring on tixhci driver.
I checked the HP drivers for the PC and there is only the original Texas Instruments USB driver available for download - is there an updated version available?
Is there any workaround or known porblems regarding this driver and HPE PC'S?
BugCheck 1000007E, {ffffffffc0000005, fffff880054dbbbf, fffff880034bb838, fffff880034bb090} Probably caused by : tixhci.sys ( tixhci+43bbf ) Followup: MachineOwner --------- 1: 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: fffff880054dbbbf, The address that the exception occurred at Arg3: fffff880034bb838, Exception Record Address Arg4: fffff880034bb090, 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: tixhci+43bbf fffff880`054dbbbf 498b4208 mov rax,qword ptr [r10+8] EXCEPTION_RECORD: fffff880034bb838 -- (.exr 0xfffff880034bb838) ExceptionAddress: fffff880054dbbbf (tixhci+0x0000000000043bbf) ExceptionCode: c0000005 (Access violation) ExceptionFlags: 00000000 NumberParameters: 2 Parameter[0]: 0000000000000000 Parameter[1]: 0000000000000008 Attempt to read from address 0000000000000008 CONTEXT: fffff880034bb090 -- (.cxr 0xfffff880034bb090) rax=0000000000000025 rbx=fffffa800aa9a540 rcx=fffffa800aa9a540 rdx=fffffa80056d4e60 rsi=fffffa800aa9a6d0 rdi=fffffa800ae98210 rip=fffff880054dbbbf rsp=fffff880034bba70 rbp=fffffa800aa9a540 r8=fffffa800ae98020 r9=fffffa800ae98148 r10=0000000000000000 r11=fffffa800ae77de8 r12=fffffa800ae40002 r13=0000000000000001 r14=0000000000000001 r15=fffff800044ab080 iopl=0 nv up ei ng nz na po nc cs=0010 ss=0018 ds=002b es=002b fs=0053 gs=002b efl=00010286 tixhci+0x43bbf: fffff880`054dbbbf 498b4208 mov rax,qword ptr [r10+8] ds:002b:00000000`00000008=???????????????? 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: 0000000000000000 EXCEPTION_PARAMETER2: 0000000000000008 READ_ADDRESS: GetPointerFromAddress: unable to read from fffff80002ecb100 0000000000000008 FOLLOWUP_IP: tixhci+43bbf fffff880`054dbbbf 498b4208 mov rax,qword ptr [r10+8] BUGCHECK_STR: 0x7E DEFAULT_BUCKET_ID: NULL_CLASS_PTR_DEREFERENCE LAST_CONTROL_TRANSFER: from fffffa800ae77de8 to fffff880054dbbbf STACK_TEXT: fffff880`034bba70 fffffa80`0ae77de8 : fffffa80`0aa9ac58 00000000`00000000 fffff880`054e1100 00000000`00000000 : tixhci+0x43bbf fffff880`034bba78 fffffa80`0aa9ac58 : 00000000`00000000 fffff880`054e1100 00000000`00000000 fffff880`054da1d2 : 0xfffffa80`0ae77de8 fffff880`034bba80 00000000`00000000 : fffff880`054e1100 00000000`00000000 fffff880`054da1d2 fffffa80`0ae77de8 : 0xfffffa80`0aa9ac58 SYMBOL_STACK_INDEX: 0 SYMBOL_NAME: tixhci+43bbf FOLLOWUP_NAME: MachineOwner MODULE_NAME: tixhci IMAGE_NAME: tixhci.sys DEBUG_FLR_IMAGE_TIMESTAMP: 4db0823b STACK_COMMAND: .cxr 0xfffff880034bb090 ; kb FAILURE_BUCKET_ID: X64_0x7E_tixhci+43bbf BUCKET_ID: X64_0x7E_tixhci+43bbf Followup: MachineOwner ---------
Solved! Go to Solution.
Accepted Solutions
06-15-2012 02:16 PM - edited 06-15-2012 02:38 PM
Hmmm, unable to install the fix, get error dialog box popup 259. However, I have changed the power save options to High Performance and BSOD hasn't re-occured!!!
06-14-2012 06:07 PM
http://h30434.www3.hp.com/t5/Desktop-Lockups-Freezes-Hangs/Driver-update-for-Win7-USB-issue-on-nVidi...
I'll see how this goes,...
06-15-2012 02:16 PM - edited 06-15-2012 02:38 PM
Hmmm, unable to install the fix, get error dialog box popup 259. However, I have changed the power save options to High Performance and BSOD hasn't re-occured!!!
06-01-2016 11:48 AM
I received this same minidump on an HP Z820 Workstation. I had previously turned off the Hibernation option (cmd /C powercfg -h off) and had not changed my Sleep settings in the Advanced Power Settings. When it went to sleep and began to hibernate after a certain amount of time, it failed horribly (as it should have).
To change this so it won't happen again, you can either switch to the "High Performance" setting or the much more correct, make sure hibernation isn't an option anywhere.
I followed this guide and included their screen shots here for convienence:
First:
And then:
Hope this helps some individuals like it did for me!
-IT Technical Support Supervisor