Error "1e" and "fe" are the main ones that keep appearing. I've never posted something like this online before, so I might have done some thing wrong. Just ask for more information. I've included some files which might help anyway... I also think the two .rar files are quite similar lol. Any help is appreciated, I'm just out of ideas.
Hi Leprechaun and welcome to Seven Forums
Most of your crashes were Related to usbohci.sys related to OHCI USB Miniport Driver from Microsoft..
I would run a system file check to verify and repair the Operating system files and read about the problem here. USB Driver - General Fix for Problems
Code:Microsoft (R) Windows Debugger Version 6.11.0001.404 X86 Copyright (c) Microsoft Corporation. All rights reserved. Loading Dump File [C:\Users\JMH\Desktop\Windows_NT6_BSOD_jcgriff2\053011-22074-01.dmp] Mini Kernel Dump File: Only registers and stack trace are available Symbol search path is: SRV*C:\Symbols*http://msdl.microsoft.com/download/symbols;srv*e:\symbols *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.17592.amd64fre.win7sp1_gdr.110408-1631 Machine Name: Kernel base = 0xfffff800`03013000 PsLoadedModuleList = 0xfffff800`03258650 Debug session time: Mon May 30 14:37:12.510 2011 (GMT-4) System Uptime: 0 days 0:01:35.024 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 : usbohci.sys ( usbohci!OHCI_ProcessDoneIsoTd+25 ) 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: +53bc952f0318dd50 00000000`00000000 ?? ??? EXCEPTION_PARAMETER1: 0000000000000000 EXCEPTION_PARAMETER2: 0000000000000000 CUSTOMER_CRASH_COUNT: 1 DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT BUGCHECK_STR: 0x1E PROCESS_NAME: System CURRENT_IRQL: 2 EXCEPTION_RECORD: fffff88002ffd888 -- (.exr 0xfffff88002ffd888) ExceptionAddress: fffff88004477ce1 (usbohci!OHCI_ProcessDoneIsoTd+0x0000000000000025) ExceptionCode: c0000005 (Access violation) ExceptionFlags: 00000000 NumberParameters: 2 Parameter[0]: ffffffffffffffff Parameter[1]: 0000000000000000 Attempt to execute non-executable address 0000000000000000 TRAP_FRAME: fffff88002ffd930 -- (.trap 0xfffff88002ffd930) NOTE: The trap frame does not contain all registers. Some register values may be zeroed or incorrect. rax=00000000ffffffff rbx=0000000000000000 rcx=fffffa80086c96a0 rdx=fffff880009f3a00 rsi=0000000000000000 rdi=0000000000000000 rip=fffff88004477ce1 rsp=fffff88002ffdac0 rbp=ff00fa800c3e7fc0 r8=000000004f444601 r9=fffff880009f3a00 r10=00000000ffffffff r11=fffff88002ffdb28 r12=0000000000000000 r13=0000000000000000 r14=0000000000000000 r15=0000000000000000 iopl=0 nv up ei ng nz na po nc usbohci!OHCI_ProcessDoneIsoTd+0x25: fffff880`04477ce1 488b7530 mov rsi,qword ptr [rbp+30h] ss:0018:ff00fa80`0c3e7ff0=???????????????? Resetting default scope LAST_CONTROL_TRANSFER: from fffff8000308a6be to fffff80003092cd0 STACK_TEXT: fffff880`02ffc968 fffff800`0308a6be : fffffa80`09f49c90 00000000`00000040 fffff880`02ffd0e0 fffff800`030be890 : nt!KeBugCheck fffff880`02ffc970 fffff800`030be55d : fffff800`03299968 fffff800`031d6cbc fffff800`03013000 fffff880`02ffd888 : nt!KiKernelCalloutExceptionHandler+0xe fffff880`02ffc9a0 fffff800`030bd335 : fffff800`031da0fc fffff880`02ffca18 fffff880`02ffd888 fffff800`03013000 : nt!RtlpExecuteHandlerForException+0xd fffff880`02ffc9d0 fffff800`030ce3b1 : fffff880`02ffd888 fffff880`02ffd0e0 fffff880`00000000 fffffa80`0beadf68 : nt!RtlDispatchException+0x415 fffff880`02ffd0b0 fffff800`03092382 : fffff880`02ffd888 00000000`00000013 fffff880`02ffd930 00000000`00000980 : nt!KiDispatchException+0x135 fffff880`02ffd750 fffff800`03090b52 : fffffa80`0bea1110 fffffa80`0bea71e8 fffffa80`0bea1400 fffff880`0455188b : nt!KiExceptionDispatch+0xc2 fffff880`02ffd930 fffff880`04477ce1 : fffffa80`06adc840 fffff880`02e23110 fffff880`70627301 fffff880`044aeea0 : nt!KiStackFault+0x112 fffff880`02ffdac0 fffff880`04477f7d : 00000000`00000013 fffff880`009f3180 fffffa80`086c8101 fffffa80`0beadf68 : usbohci!OHCI_ProcessDoneIsoTd+0x25 fffff880`02ffdb30 fffff880`0447a744 : fffffa80`0beadf68 fffffa80`0beadd20 fffffa80`086c81a0 00000000`ffffff02 : usbohci!OHCI_PollIsoEndpoint+0x101 fffff880`02ffdb80 fffff880`04482e8b : 00000000`00000002 fffffa80`0beadd20 fffffa80`086c81a0 00000000`00000000 : usbohci!OHCI_PollEndpoint+0x4c fffff880`02ffdbb0 fffff880`044879d1 : 00000000`00000010 00000000`00000004 fffffa80`0beadd20 fffffa80`086c8050 : USBPORT!MPf_PollEndpoint+0x9b fffff880`02ffdbe0 fffff880`04493077 : fffffa80`086c81a0 00000000`00000010 fffffa80`0000000e 00000000`00000000 : USBPORT!USBPORT_iSetGlobalEndpointStateTx+0x7c1 fffff880`02ffdc40 fffff880`04483f89 : fffffa80`086c8050 00000000`00000000 fffffa80`086c8a02 fffffa80`086c8a18 : USBPORT!USBPORT_Core_UsbHcIntDpc_Worker+0x1c3 fffff880`02ffdca0 fffff800`0309e10c : fffff880`02fd5180 fffffa80`086c8a18 fffffa80`086c8a30 00000000`00000000 : USBPORT!USBPORT_Xdpc_Worker+0x1d9 fffff880`02ffdcd0 fffff800`0308aa2a : fffff880`02fd5180 fffff880`02fdffc0 00000000`00000000 fffff880`04483db0 : nt!KiRetireDpcList+0x1bc fffff880`02ffdd80 00000000`00000000 : fffff880`02ffe000 fffff880`02ff8000 fffff880`02ffdd40 00000000`00000000 : nt!KiIdleLoop+0x5a STACK_COMMAND: kb FOLLOWUP_IP: usbohci!OHCI_ProcessDoneIsoTd+25 fffff880`04477ce1 488b7530 mov rsi,qword ptr [rbp+30h] SYMBOL_STACK_INDEX: 7 SYMBOL_NAME: usbohci!OHCI_ProcessDoneIsoTd+25 FOLLOWUP_NAME: MachineOwner MODULE_NAME: usbohci IMAGE_NAME: usbohci.sys DEBUG_FLR_IMAGE_TIMESTAMP: 4d8c0bff FAILURE_BUCKET_ID: X64_0x1E_usbohci!OHCI_ProcessDoneIsoTd+25 BUCKET_ID: X64_0x1E_usbohci!OHCI_ProcessDoneIsoTd+25 Followup: MachineOwner ---------
Thankyou! I will try that now. =)
I keep getting a few different reasons for the error, mainly due to apparent problems with my USB driver but there are other things too. I've tried a lot of things already but nothing seems to be helping. I've uploaded some files which might help to find my problem. Any help at all is appreciated, even if it is to tell me this can't be fixed.
The most recent was Related to usbehci.sys Microsoft USB 2.0 Enhanced Host Controller Miniport Driver.
I would run a system file check to verify and repair and read here USB Driver - General Fix for Problems
Run a system file check to verify and repair your system files.
To do this type cmd in search, then right click to run as administrator, then
SFC /SCANNOW
Read here for more information SFC /SCANNOW Command - System File Checker
Let us know the results from the report at the end.
Code:Microsoft (R) Windows Debugger Version 6.11.0001.404 X86 Copyright (c) Microsoft Corporation. All rights reserved. Loading Dump File [C:\Users\K\Desktop\Seven Forums\060211-27034-01.dmp] Mini Kernel Dump File: Only registers and stack trace are available Symbol search path is: SRV*C:\Symbols*http://msdl.microsoft.com/download/symbols;srv*e:\symbols *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.17592.amd64fre.win7sp1_gdr.110408-1631 Machine Name: Kernel base = 0xfffff800`03057000 PsLoadedModuleList = 0xfffff800`0329c650 Debug session time: Thu Jun 2 09:02:52.552 2011 (GMT-4) System Uptime: 0 days 0:00:46.066 Loading Kernel Symbols ............................................................... ................................................................ ................ Loading User Symbols Loading unloaded module list .... ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* Use !analyze -v to get detailed debugging information. BugCheck FE, {5, fffffa80084a71a0, 10024396, fffffa800819ec48} Probably caused by : usbehci.sys ( usbehci!EHCI_PollActiveControlEndpoint+57 ) Followup: MachineOwner --------- 3: kd> !analyze -v ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* BUGCODE_USB_DRIVER (fe) USB Driver bugcheck, first parameter is USB bugcheck code. Arguments: Arg1: 0000000000000005, USBBUGCODE_INVALID_PHYSICAL_ADDRESS The host controller is using a physical memory address that was not allocated by the USBport driver. Arg2: fffffa80084a71a0, Device extension pointer of the host controller Arg3: 0000000010024396, PCI Vendor,Product id for the controller Arg4: fffffa800819ec48, Pointer to Endpoint data structure Debugging Details: ------------------ CUSTOMER_CRASH_COUNT: 1 DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT BUGCHECK_STR: 0xFE PROCESS_NAME: System CURRENT_IRQL: 2 LAST_CONTROL_TRANSFER: from fffff88003f46f7e to fffff800030d6d00 STACK_TEXT: fffff880`009b0c88 fffff880`03f46f7e : 00000000`000000fe 00000000`00000005 fffffa80`084a71a0 00000000`10024396 : nt!KeBugCheckEx fffff880`009b0c90 fffff880`041b57fb : 00000000`cfcb8180 fffffa80`0819ea00 fffffa80`084a86a0 fffffa80`0819ec48 : USBPORT!USBPORTSVC_MapHwPhysicalToVirtual+0x18a fffff880`009b0cd0 fffff880`041b5c57 : fffff880`043c9080 fffffa80`0819ea00 fffffa80`084a86a0 fffffa80`0b99f4a0 : usbehci!EHCI_PollActiveControlEndpoint+0x57 fffff880`009b0d20 fffff880`041bad98 : fffffa80`0819ec48 fffffa80`084a71a0 fffff880`02fd5180 fffff800`030e08b9 : usbehci!EHCI_PollControlEndpoint+0xc3 fffff880`009b0da0 fffff880`03f1ae8b : 00000000`00000002 fffffa80`084a71a0 00000000`00000000 00000000`00000010 : usbehci!EHCI_PollEndpoint+0x48 fffff880`009b0de0 fffff880`03f1f9d1 : 00000000`00000010 00000000`00000004 fffffa80`0819ea00 fffffa80`084a7050 : USBPORT!MPf_PollEndpoint+0x9b fffff880`009b0e10 fffff880`03f2b077 : fffffa80`084a71a0 00000000`00000010 fffffa80`0000000e 00000000`00000000 : USBPORT!USBPORT_iSetGlobalEndpointStateTx+0x7c1 fffff880`009b0e70 fffff880`03f1bf89 : fffffa80`084a7050 00000000`00000000 fffffa80`084a7a02 fffffa80`084a7a18 : USBPORT!USBPORT_Core_UsbHcIntDpc_Worker+0x1c3 fffff880`009b0ed0 fffff800`030e210c : fffff880`02fd5180 fffffa80`084a7a18 fffffa80`084a7a30 00000000`00000000 : USBPORT!USBPORT_Xdpc_Worker+0x1d9 fffff880`009b0f00 fffff800`030d9765 : 00000000`00000000 fffffa80`0b80ab60 00000000`00000000 fffff880`03f1bdb0 : nt!KiRetireDpcList+0x1bc fffff880`009b0fb0 fffff800`030d957c : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KyRetireDpcList+0x5 fffff880`06aa7640 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiDispatchInterruptContinue STACK_COMMAND: kb FOLLOWUP_IP: usbehci!EHCI_PollActiveControlEndpoint+57 fffff880`041b57fb 488baf38010000 mov rbp,qword ptr [rdi+138h] SYMBOL_STACK_INDEX: 2 SYMBOL_NAME: usbehci!EHCI_PollActiveControlEndpoint+57 FOLLOWUP_NAME: MachineOwner MODULE_NAME: usbehci IMAGE_NAME: usbehci.sys DEBUG_FLR_IMAGE_TIMESTAMP: 4d8c0c00 FAILURE_BUCKET_ID: X64_0xFE_usbehci!EHCI_PollActiveControlEndpoint+57 BUCKET_ID: X64_0xFE_usbehci!EHCI_PollActiveControlEndpoint+57 Followup: MachineOwner ---------
http://gyazo.com/96f511914c328af9936815dd267e4df2.png
Results from the scan
They are the very results we hope to see.
Did you check the link below as requested in post 5?
USB Driver - General Fix for Problems
I did look at that link, however I'm not sure what USB device is the one I'm having issues with. I did delete the drivers however I'm not sure it helped (maybe I did something wrong, I'll try again now anyway)
I also want to add that I was trying to turn on my computer today and I got many BSODs and my computer basically refusing to turn on (this has happened before too, but never this bad and I've not seen this error before).
Problem signature:
Problem Event Name: BlueScreen
OS Version: 6.1.7601.2.1.0.768.3
Locale ID: 2057
Additional information about the problem:
BCCode: 7e
BCP1: FFFFFFFFC0000005
BCP2: FFFFF80003093C25
BCP3: FFFFF8800375C628
BCP4: FFFFF8800375BE80
OS Version: 6_1_7601
Service Pack: 1_0
Product: 768_1
Is this related to that? How can I fix this? Thankyou for all your help by the way. =(
Without the DMP we can only tell you it is a memory exception and
If you are not equipped to debug this problem, you should use some basic troubleshooting techniques.
- Make sure you have enough disk space.
- If a driver is identified in the bug check message, disable the driver or check with the manufacturer for driver updates.
- Try changing video adapters.
- Check with your hardware vendor for any BIOS updates.
- Disable BIOS memory options such as caching or shadowing.
Here's some more files, sorry I completely forgot to add them yesterday. And thanks for the advice I will check all of the basic troubleshooting ideas now. =)
Quote