(Another) ntoskrnl power fail BSOD

Gorgrak · 16 Oct 2010

It has happened the last few times I have shutdown/restarted my computer. I am almost 100% sure it is due to a driver Microsoft pointed me too that updated (and supposedly) fixed my usb 3.0 stuff on my motherboard...

I am almost certain due to the fact that I hadn't had these errors up until installing this driver.

I am uploading the driver and dump file I received from using Nirsoft's BlueScreenView program. The driver comes from Gigabyte. I noticed that my addresses and stuff were different than other posts so I figured better to be safe than sorry and am now writing this post.

Thanks for all your help!!!
~Derek

Jonathan_King · 16 Oct 2010

Welcome!

Start by following these directions: https://www.sevenforums.com/crashes-d...tructions.html

I suggest a system restore to get to a point before the problem began.

Gorgrak · 16 Oct 2010

Oops, sorry about that. Here we go.

Win 7 x64
System is less than a year old

Jonathan_King · 16 Oct 2010

Looks like your Tascom sound device is the issue. The drivers are quite old:

Code:

tascusb2.sys Fri Jul 25 13:17:30 2008

Try updating the drivers, and see what happens.

...Summary of the Dumps:

Code:


Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Debug session time: Sat Oct 16 02:45:23.610 2010 (UTC - 4:00)
System Uptime: 0 days 0:22:24.233
BugCheck 9F, {3, fffffa800693b060, fffff80000b9c518, fffffa8007f70220}
Probably caused by : usbhub.sys
BUGCHECK_STR:  0x9F
PROCESS_NAME:  System
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Debug session time: Sat Oct 16 02:22:18.706 2010 (UTC - 4:00)
System Uptime: 0 days 5:47:26.330
BugCheck 9F, {3, fffffa8005e34060, fffff80000b9c518, fffffa8006abb850}
Probably caused by : usbhub.sys
BUGCHECK_STR:  0x9F
PROCESS_NAME:  System
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨

Code:

FAILURE_BUCKET_ID:  X64_0x9F_3_tascusb2_IMAGE_usbhub.sys

Gorgrak · 17 Oct 2010

Wow, yeah that was the culprit! I didn't believe it at first and begrudgingly uninstalled the drivers... lo and behold the BSOD is gone, my audio is working perfectly (apparently some robotic sounding artifacts were rooted in this faulty driver!!!), and I have yet to install some updated ones. Thanks you SO MUCH for the help!!!!!!!

Just in case anyone is reading this, DO NOT BUY A TASCAM US122/122L/144 INTERFACE. THEY ARE A WASTE OF MONEY DUE TO THE AMOUNT OF PROBLEMS THEY CAUSE. Tascam equipment is wonderful from my experience, all except for this line of interfaces. There is your warning. </rant

>

Jonathan_King · 17 Oct 2010

You're very welcome, I'm glad it worked for you. Let us know if you need anything else!