some issues lm trying to fix.

[timelesspa]

after some bsod errors, removing of ram things seem to be running better thankfully... well that is to say l havent had a bsod again since removing the older set of ram.

now l was told l had some issues with my drivers, however l want to know if lve fixed at least where usb 3.0 drivers are concerned:

where can l find the logs that would show errors like the below:

fffff880`035fe128 00000000`00000000
fffff880`035fe130 fffff880`05834c00Unable to load image \SystemRoot\system32\DRIVERS\iusb3hub.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for iusb3hub.sys
*** ERROR: Module load completed but symbols could not be loaded for iusb3hub.sys
iusb3hub+0x34c00
fffff880`035fe138 fffff880`05802147 iusb3hub+0x2147
fffff880`035fe140 fffffa80`144a4700
.
.
.
fffff880`035ff528 00000000`00000000
fffff880`035ff530 fffff880`04f6ade0Unable to load image \SystemRoot\system32\DRIVERS\iusb3xhc.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for iusb3xhc.sys
*** ERROR: Module load completed but symbols could not be loaded for iusb3xhc.sys
iusb3xhc+0x6bde0
fffff880`035ff538 00000000`000003e7
fffff880`035ff540 fffff880`04f79f60 iusb3xhc+0x7af60
fffff880`035ff548 00000000`00000000
fffff880`035ff550 fffffa80`1644c0b8

reason l ask is lve updated my Bios to the latest posted on my motherboards website and l received the following error:

Faulting application name: teracopy.exe, version: 2.3.0.0, time stamp: 0x52a2ba02
Faulting module name: ntdll.dll, version: 6.1.7601.22436, time stamp: 0x521eaa80
Exception code: 0xc0000005
Fault offset: 0x00032532
Faulting process id: 0x710
Faulting application start time: 0x01cfd4875bf40e52
Faulting application path: C:\Program Files\TeraCopy\teracopy.exe
Faulting module path: C:\Windows\SysWOW64\ntdll.dll
Report Id: a3d32145-407a-11e4-9b85-c3289d97281b

and so far lve only received the error while copying content onto a usb connected drive (thumb drives and externals) which leads me to believe that my issues with teracopy may likely be linked to the fact that lm still experiencing usb 3.0 driver issues.

 

[undefinedgamer]

Try another usb drive or other usb ports. Also enable usb 3.0 support in bios settings and also enable usb legacy support.

 

[timelesspa]

happens with more than one tho lve only noticed any issues with teracopy so far unless you consider my wireless has been screwy..

that said lve just updated my bios to F7 (latest for my board).

 

[timelesspa]

just looked into the bios, and found the option for usb support..

however the option couldnt be changed, but it its selected state was "partial initial".. to be quite honest lve only ever used the old version bios's so using UEFI based bios is pretty new to me as lm unfamiliar with it l dont want to change things other than shut down temps and such lol, at least not until lm more conferable with using it.

 

[undefinedgamer]

Have you tried formatting your usb drive again, and make sure the format is successful. The most common formats are fat32 and ntfs. Try ntfs format and see if it works now. Also make sure you've the latest motherboard chipset drivers. If still doesn't work, the chipset drivers or generic usb 3.0 drivers may not be compatible with latest version of your bios, so try re-installing the previous version of the bios which worked perfectly earlier.

 

[timelesspa]

actually it wouldnt make a difference, that said l downgraded to another version of teracopy (same version l had on the laptop) and at this second l havent had any crashes "yet" tho l had the error on multiple usb flash/external drives.

 

[trents]

What version of Windows are you using? It's well-documented that the Windows 8/8.1 USB 3 stack has bugs that cause problems with some USB 3 devices. I haven't heard of crashes being caused by this but have had it just cause the device not to work. When this happens you can see a yellow caution sign symbol in Device Manager. Microsoft has admitted the stack is broken and intends to fix it in Windows 9.

 

[timelesspa]

Win7 64bit, all goes well tho hopefully l'll be receiving a new wireless adapter tomorrow so l can rule out my hardware as being a problem, as l havent received any more bsods its hard to tell if l fixed my usb issues which appeared within a bsod dump.