Unpredictable BSOD, strange audio delay problem, and crawling speed

[hseidema]

I'm an engineering student, and usually can sort these problems out for myself, but this one has had me stumped for going on 5 days now, so it's time to reach out and get some help.

Problems started 5 days ago. I had been having some issues with my comp recognizing changes in connection status to an arduino device I was playing with, and not updating the connection status. After fiddling with trying to uninstall and reinstall the arduino drivers, I noticed that device manager would just spin its wheels, and hang. The rest of the computer would keep functioning, but device manager would lock up. Strange....

Then started getting BSODs. Went through my standard troubleshooting procedure, discovered I'd gotten a virus through some Autocad tutorial videos I'd downloaded. Stupid me. Scrubbed and scrubbed and scrubbed, and am pretty optimistic that my system is clean now. Ran disc check, and everything came back fine. Have run no shortage of utilities to clean up my registry and hopefully remove errors there. Still no luck.

Attached are my most recent dumps. I've had many more than this, but it looks like those older than the 18th got wiped by one of the cleaner/scrubber utilities I used. Alongside these BSOD's I get (at unpredictable times) my comp is just crawling. I also have a strange problem where when opening any video file, there's a 2-5 second delay before the audio kicks in. When it does kick in, it's in sync, and the video plays fine (whether it's a file or internet clip) and if I rewind to the start, the audio starts fine. Basically, on first load, there's a delay.

System specs:

OS: Win 7 Professional x64
CPU: Intel Core i5-2500K 3.3GHz
MB: ASUS P8Z68-V Pro GEN3 Z68
Ram: 16 GB DDR3 (I think a mismatch, G-Skill and Corsair?)
Graphics: MSI Geforce GTX 560 Ti Twin Frozr II
Network: Belkin F7D1101 version 1 USB Wireless Adapter

Any help would be greatly appreciated. Most of the problems seem to have been with the ntoskrnl.exe or the iqvw64e.sys, but this last BSOD was caused by Asushwio.sys, which suggests something's up with my MB? That has me worried...

Thanks in advance for the help. Looking forward to seeing with you all can come up with.

 

[Arc]

It is caused by ASUS driver.

*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck C4, {f6, e0, fffffa800dd74b30, fffff8800c7f3598}

*** WARNING: Unable to verify timestamp for Asushwio.sys
*** ERROR: Module load completed but symbols could not be loaded for Asushwio.sys
Probably caused by : Asushwio.sys ( Asushwio+1598 )

Followup: MachineOwner
---------

It is very old.

lmvm Asushwio
start             end                 module name
fffff880`0c7f2000 fffff880`0c7f7000   Asushwio T (no symbols)           
    Loaded symbol image file: Asushwio.sys
    Image path: \??\D:\Bin\64bit\Asushwio.sys
    Image name: Asushwio.sys
    Timestamp:        Fri Dec 28 12:54:47 2007 (4774A4BF)
    CheckSum:         00011EDD
    ImageSize:        00005000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4

Try to update it.
How old the system is? I am failing to gate the motherboard info from the data you uploaded.

 

[hseidema]

I've been trying to update all the drivers, especially from the Asus website, since I figured it might be out of date drivers. I'm not sure which package this driver is a part of though, as Asus doesn't just have a generic driver package for the board itself.

I built the system last year, with all new components, so nothing should be so old as 2007, unless it hasn't been updated in the last 6 years....

Did you take a look at the older dumps? Because the Asus fault hast been responsible for my last two BSOD, but I was having other problems before that. Blue Screen view showed a different driver at fault before these most recent blue screens, and always, it seemed like it was associated with ntoskrnl as well.

 

[hseidema]

Just noticed as well: the directory it lists for the asushwio.sys driver is D: which is my dvd/rw drive. I may have had the Asus install disk in at the time of the BSOD, so for some reason the system was trying to grab a driver from the disk? I wasn't doing an install or anything...

 

[Arc]

May be ... You may try to update the ODD driver in disc management

 

[hseidema]

I think I've sorted out the problem. I've bought myself a new SSD, and am going to do a clean windows install, and get all the drivers built up again from scratch to be safe in the long run, but I think I've resolved the problem for the short term. Thought I'd share the results in case anyone else ever comes across this.

Ran some more boot-level scans, and found that I was infected with a Bitcoin-A Trojan. It was living in the following directory:

File C:\Users\*Username*\AppData\LocalLow\Sun\Java\Deployment\cache\6.0\28\2e002d9c-3c6af29c|>com\bitcoinplus\applet\MiningApplet.class is infected by Java:Bitcoin-A [Trj]

I ran a number of successive boot-level scans until I was confident it was completely gone, but was still getting BSOD any time I tried to run an ASUS utility to try and update the MB drivers. I did some more internet searching, and found that some people having faults with ASUS drivers were having conflicts with Windows Driver Verifier. I had turned it on previously because of some recommendations from a different troubleshooting site, but hadn't been using it in any constructive way. Turning it off completely, now that I have a clean system, seems to have corrected the problem. Since disabling Driver Verifier, I've been able to run all the ASUS utility programs to get clean installs of pretty much all my drivers.

As I said, going to do a clean install on a new drive, just to be safe, but in the short term, this seems to have done it. Computer is humming along at top speed once again, and audio delay issues seem to be gone as well.

 

[Arc]

Good job, well done