Usb code 10

To reconfirm, your audio device has class upper filter ksthunk and no lower filter listed, correct?


that is correct

[IMG][/IMG]

OK. In your DevMgr snapshot, Expand USB just to check new yellow icons there either.

Ughh. You're problem is tougher to figure out what's going on then i first guessed. Device Manager writes a trace file. Let's have a look at that too
1. Create a .zip file of C:\WINDOWS\inf\setupapi.dev.log. Attach to next post.

2. Delete the original file

3. Let things run. Try to notice machine clock time when problem clears up and again approx machine clock time when problem reappears. The create a new .zip of the new setupapi.dev.log and tell me the approx clock times when things were good and again when it broke.

Hoping to find more helpful info in there

OK. In your DevMgr snapshot, Expand USB just to check new yellow icons there either.

all clear

here we go

2. Delete the original file

will i delete that log file

If i disable my OC and return BIOS to default everything is fine :) i can reset my PC loads of times without issue. But when i enable my OC i get that error

upload the new setup.api.log file windows built.

This is a tricky one. From what i have found
> ksthunk.sys is a filter only used on 64 bit machine
> I think it's used to interface to apps/modules that are 32 bit
> Googling ksthunk code 10 reveals a lot of forum posts from people with a variety of issues (BSODs as well) but not much in solutions

But we'll still take a look. Suggest you go back to Driver Details for the audio device
> Click on each module in the display to see its Provider and Version number
> Are they all from Microsoft? If not, who else Provdes?
> Also not the version and date of ksthunk. Just in case the process of reinstalling changes the version.

torchwood said:

See that youve overclocked, according to your specs, thats more than likely the problem.

Roy

Accolades to torchwood for suggesting OC early on. I've never tried OC nor know much about it. I'm much more a "software kind-a-guy". So I'm curious how OC fits into the equation and could be causing these s/w issues if anyone(s) want to jump in with more info?


@Driver170
I don't want to hijack your thread.. but thought it might help all around to get a better idea of how OC could be part of your code 10 problem.

Its the OC for sure no code 10 as yet with asus default :)

@Driver170
I don't want to hijack your thread.. but thought it might help all around to get a better idea of how OC could be part of your code 10 problem.

Well if i disable my OC and use default the error 10 code is gone!