UPDATE:

I'm not sure how or why this is happening; these BSODs just happen arbitrarily, even when I'm not doing anything. I tried plugging off the USB mouse for a while, since the error called it bugcode_usb_driver, but the BSOD popped up. Maybe I was using a specific program at the time to improve the visual game quality, so I closed that program and the BSOD still occured. I tried closing the bittorrent program since I heard the torrents can lead to these errors, but the same thing happens. Afterwards, another BSOD occured when I took off the power supply to pack my laptop to school; for some reason, the screen lights didn't dim after the plug was removed, so I open/closed the lid and POOF, another BSOD. Then on the same day when that latter BSOD happened while I was idling on a message board I frequently go to, another one just came out of the blue.

Let me stress on the latest BSOD: no usb ports were used, the bittorrent and video program were not open, I didn't close the lid, the only things that are connected to the computer are the power supplies and the headphone/mic jack used for the external speakers. I still got a BSOD!

What else am I suppose to remove just to avoid this frequent blues? :4-dontkno

 

Hi and welcome to TSF please follow the instructions here http://www.techsupportforum.com/for...orum.com/forums/f217/blue-screen-of-death-bsod-posting-instructions-452654.html this will give a analyst a chance to debug the files and try to narrow down the cause

 

I already uploaded the zip file on the very first page. If it's because I didn't name the zip properly, or that I didn't post the zip on the second post, I apologize.

Unfortunately, I'm unable to edit my first post and I can't upload a differently-named zip file on another post because it already existed. If this hinders anyone's attempt at providing solutions for me, could you please remove this thread (or remove the attached file) so I can try again but make it proper?

 

Hi sorry that was my error I missed seeing DoH
Edit you may need to visit here to have your sytem checked out torrents can be very dangerous in regard to malware NEW INSTRUCTIONS - Read This Before Posting For Malware Removal Help - Tech Support Forum

 

I already had my system checked for malware, and it's been cleaned. Again, I haven't touch the torrent program or upload any torrents since I got my laptop back from a trusted computer specialist who cleaned my computer, which was last Thursday.

 

Just to update, my computer just crashed with the same BSOD seven minutes ago. All I did was go online and watched a flash-based video, while I have internet tabs for that and a message board site. Since I can't upload for an updated zip, here's the info:


Problem signature:
Problem Event Name: BlueScreen
OS Version: 6.1.7600.2.0.0.768.3
Locale ID: 1033

Additional information about the problem:
BCCode: fe
BCP1: 0000000000000008
BCP2: 0000000000000006
BCP3: 0000000000000005
BCP4: FFFFFA80076FB7A0
OS Version: 6_1_7600
Service Pack: 0_0
Product: 768_1

Files that help describe the problem:
C:\Windows\Minidump\021011-21075-01.dmp
C:\Users\*****\AppData\Local\Temp\WER-51589-0.sysdata.xml


:4-dontkno

 

Hi that is still pointing to a usb issue,please list all usb devices you may have connected

 

- Ipod Touch 32 GB
- Microsoft Wireless Mobile Mouse 3000
- WD 320 gb external harddrive

Those are the only USB devices I used for this laptop, and I haven't connected to any of them when the BSODs occurred. I haven't even used the mouse since mid-january, out of fear that that might be defected. I even deleted all of the usb drivers, which were restored after a computer restart, and that didn't help much either.

 

Hi I have put out a call for a analyst to look over the dump files please be patient they are very busy but will get to you as soon as is possible

 

Hello,

Uninstall Daemon Tools, as it is using the notorious SPTD. Remove SPTD when you're done, using this utility: http://www.duplexsecure.com/download/SPTDinst-v174-x64.exe

Could you run driver verifier? See this guide: Driver Verifier - Windows 7 & Vista (BSOD-related) - Tech Support Forum

Also, run some hardware diagnostic. Run Memtest86 overnight: RAM - Test with Memtest86+ - Windows 7 Forums

Also, run the Blend and Small FFTs Prime95 tests: CPU - Stress Test with Prime95 - Windows 7 Forums

...Summary of the dumps:

[font=lucida console]
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Debug session time: Tue Feb  8 23:12:14.698 2011 (UTC - 5:00)
System Uptime: 0 days 1:21:21.290
Probably caused by : usbhub.sys ( usbhub!UsbhHubProcessChangeWorker+ec )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0xFE
PROCESS_NAME:  System
FAILURE_BUCKET_ID:  X64_0xFE_usbhub!UsbhHubProcessChangeWorker+ec
SystemProductName = G60JX
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Debug session time: Tue Feb  8 16:56:16.113 2011 (UTC - 5:00)
System Uptime: 5 days 6:22:07.716
Probably caused by : usbhub.sys ( usbhub!UsbhHubProcessChangeWorker+ec )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0xFE
PROCESS_NAME:  System
FAILURE_BUCKET_ID:  X64_0xFE_usbhub!UsbhHubProcessChangeWorker+ec
SystemProductName = G60JX
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Debug session time: Thu Jan 20 13:24:03.448 2011 (UTC - 5:00)
System Uptime: 6 days 0:00:05.130
Probably caused by : usbhub.sys ( usbhub!UsbhHubProcessChangeWorker+ec )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0xFE
PROCESS_NAME:  System
FAILURE_BUCKET_ID:  X64_0xFE_usbhub!UsbhHubProcessChangeWorker+ec
SystemProductName = G60JX
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Debug session time: Thu Jan 13 15:59:13.490 2011 (UTC - 5:00)
System Uptime: 0 days 18:02:49.082
Probably caused by : usbhub.sys ( usbhub!UsbhHubProcessChangeWorker+ec )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0xFE
PROCESS_NAME:  System
FAILURE_BUCKET_ID:  X64_0xFE_usbhub!UsbhHubProcessChangeWorker+ec
SystemProductName = G60JX
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
  
[/font]

 

Delete Daemon Tools? :sigh:

I kinda depended on that program; not occasionally, but there are times when I use it. Plus, this program had never been a problem for me before the BSODs started to occur on this computer. But for sake of the resolving this problem, I uninstalled this program as well as removed the SPTD. I'll give it a month if removing Daemon Tools is the solution for this problem. If the BSOD occurs during the timesink, then Daemon Tools was not the issue and I'll reinstall it.

I ran both stress tests on Prime95, each lasting 4 hours. Both showed no errors or glitches on the results, so neither the CPUs nor the RAMs were the issue and thus there's no need to run the hardware diagnostic.

I did run Driver Verifier, and it's currently running (with all but accidentally one non-Microsoft drivers in check). The point of this program is whenever a BSOD happens, it records whatever device might cause in a separate mini-file, right? Can I use my computer normally while the Verifier is still running? At this point, all I can do is wait. I don't know how or when another BSOD will pop up, so this is an arbitrary process.


Judgin' by the dump summary, the usbhub.sys seems to be the main culprit. What am I suppose to do with this information? Can this be easily solved?

 

Yes, go ahead and use your computer normally.

Verifier works in the background, testing the drivers for problems. If it finds an error, it will cause the computer to BSOD, the resulting dump file should then be helpful.

 

Got a BSOD while the Verifier is up. And yet, it doesn't seem to record anything, because I checked the mini-dump folder and it doesn't have the latest dump file for today. When the BSOD occured and it was checking for data, I was suppose to turn off the computer manually, right? Usually, the computer restarts after a few seconds, but this one took a while; figuring this was due to the verifier, I thought I was suppose to turn it off myself.

If I screwed up, I'll wait for another BSOD while the Verifier is still enabled and let the computer restart by itself, but let me stress that it isn't Daemon Tools that's causing this dilemma.

I did check the Verifier query on the cmd prompt, and I found two drivers that are unloaded while the others aren't: dump_iastor.sys and dump_dumpfve.sys. Does that information help solve anything?

Also, you didn't explain what I should do with the usbhub.sys file.

 

Don't worry about the _dump drivers; they are normal.

Be sure to remove SPTD completely, using this tool: http://www.duplexsecure.com/download/SPTDinst-v174-x64.exe

You can use MagicDisc or Virtual CloneDrive as a free alternative.

As for the Verifier and the missing dump, leave Verifier running and see if you get another BSOD. If you do, leave it for maybe 5 or 10 minutes and see if it writes a dump. If not, go ahead and force reboot.

 

Thanks for the virtual clone drive reccomendation.

Just bumping this thread for progress's sake. Guessing by the lack of proper response, it seems like my mini-dump files didn't help pin-point the source of my problem. My verifier is still enabled and no BSOD has occured for the past four days; not to say it arbitrarily resolved itself, I'm still being cautious of any more BSOD surprises.

I re-installed a new Windows Live Essentials after windows update didn't able to upgrade my previous one. That may sound insignificant, but this is just giving a heads up for what I did so far.

 

Go ahead and turn off Driver Verifier now. Open a command prompt and enter verifier /reset.

Cross your fingers and pray the BSODs don't return!

 

Why should I? It hasn't been resolved until I find the source for the BSODs, and how could I if the Verifier has been turned off?

 

If Verifier has been running so long without causing a BSOD, it is pretty unlikely that your problem is software related.

If you removed SPTD, that might have been the cause.

 

How long does one normally leave the Driver Verifier for? And how is it software related when it's driver related, specially one for the usb?

And let's not forget, the computer had a BSOD not long after the SPTD was removed. That was the one where I couldn't save the data because I force shutdown the computer.

 

Typically, we recommend that OPs leave Verifier running for maybe 24-36 hours. Verifier tests software (drivers), not hardware, though consistent flagging of a known good driver may indicate a hardware problem behind it.

Did you use the SPTD utility to remove SPTD, or did you just uninstall Daemon Tools?

 

As I said, I removed the SPTD right after I uninstalled Daemon Tools, using the utility that you posted.

 

It's baaaaacck!

12 days after crash and 5 days after disabling the verifier, it just popped up. I wish I could be angry about this, but I've gotten used to it appearance, like accepting a tumor. I'm now enabling the verifier to see if it pops up again.

My latest dump is in the zip file.

 

All I can do with that dump file is recommend a couple of driver updates.

nvlddmkm.sys    Fri Jul 09 17:15:58 2010 (4C37918E)
[url=http://sysnative.com/0x1/DriverReference.html#nvlddmkm.sys]http[i]:[/i]//sysnative.com/0x1/DriverReference.html#nvlddmkm.sys[/url] 

L1C62x64.sys    Fri Nov 13 04:47:36 2009 (4AFD2B38)
[url=http://sysnative.com/0x1/DriverReference.html#L1C62x64.sys]http[i]:[/i]//sysnative.com/0x1/DriverReference.html#L1C62x64.sys[/url] 

iaStor.sys      Fri Oct 02 15:58:50 2009 (4AC65B7A)
[url=http://sysnative.com/0x1/DriverReference.html#iaStor.sys]http[i]:[/i]//sysnative.com/0x1/DriverReference.html#iaStor.sys[/url]

Looking back on some errors in your event logs, I suggest you uninstall GameTap.

Event[1161]:
  Log Name: System
  Source: Application Popup
  Date: 2011-02-03T10:34:49.493
  Event ID: 1060
  Task: N/A
  Level: Error
  Opcode: N/A
  Keyword: Classic
  User: N/A
  User Name: N/A
  Computer: Hardbound
  Description: 
\??\C:\Program Files (x86)\GameTap Web Player\bin\Release\X4HSX has been blocked from loading due to incompatibility with this system. Please contact your software vendor for a compatible version of the driver.

Please upload a new jcgriff2 report: http://www.techsupportforum.com/for.../blue-screen-of-death-bsod-posting-instructions-windows-7-and-vista-452654.html

 

I decided to do a full system recovery on my ASUS laptop, using the Preload Wizard and setting for first partition.

This was one of the two advices I got from the ASUS customer service. My plan is that I'm going to leave this computer untouched (except for deleting a few bloatwares) for about two weeks. Afterwards, slowly but surely, I will download some of my old software like iTunes and document those that I did. If a BSOD occurs, then it's a software problem. If a BSOD occurs within two weeks, then I'm pretty much screwed and decided to send the laptop in to ASUS for repairs. I pray that doing a system recovery is the solution to my problem.

Thank goodness I backed-up my old files.

 

Two days after giving my computer the full system recovery, I got a BSOD again. But it's different. Instead of a USB_bugcode, I got...

DRIVER_IRQL_NOT_LESS_OR_EQUAL

And judging by the blue screen image that's currently on my laptop (I'm typing this on a different computer), the probable cause is "athrx.sys" because of something about a timestamp. According to the sites I google, I guess it's an obsolete driver for my wireless network, so I'll just have to remove it and install the latest one. Hopefully, that would help somehow.

I have to stop using the Verifier at this point. It had been a hour since the blue screen image appeared in my laptop, and it didn't restart itself; this is the second time this happened while the verifier was enabled. From what I read, what the verifier suppose to do is once the settings are made and the verifier tells you to restart, when you do, it then results in a BSOD to record the problem. Since my BSODs occurred while the OS is active, the verifier doesn't quite work the same way. If that's the case, then the verifier only served to be a nuisance instead of helping me.

Sorry that I couldn't upload the data, because my laptop froze with BSOD and I don't think the computer collected any data despite the "initializing data for crash dump" message appearing for a while. I had to force quit the computer.