BSOD after system startup: IRQL/KMODE Errors

joe5181 · 11 Nov 2012

Hey all!
First off, just to let you guys know, the computer that I'm having problems with is running Windows 7 64 bit home Premium (I'm try to fix a family member's computer). It is also a notebook , a MSI FX610.

Now, for some background information- The system has been bluescreening a little bit after startup for a couple of days now. I have ran memtest and chkdsk's and stuff, and then moved on to try and see if it was a driver issue. Because I don't have the expertiece in that area, I figured I would see if anyone else could help me!

I tried disabling different drivers (Which, if you look through the minidumps, produced different BSOD's), and I also started to use the driver verifier (which again, produced different BSOD's). I'll revert everything back to normal driverwise (Though I also have some startup programs disabled with msconfig), and disable the verifier and post more crash dumps if need be.

Thank all of you so much in advance, and I'll try to reply as quickly as I can to things, And I'll be happy to provide any more information as need. Thanks again!
-Joe5181

P.S. Sorry for the book :P

Arc · 12 Nov 2012

So many crashes, in a same day ..... can you remind it, if all started after the Atheros driver update?

Disable USB Selective Suspense:
USB Selective Suspend - Turn On or Off

Reinstall USB Ports drivers

Right click on the My Computer icon> Select manage. It will open the computer management window.
Click on the "Device manager" in the left pane.
Expand USB Serial Bus Controller.
Right click > Uninstall them all, one by one.
When Done, restart the computer.
On restart, the necessary drivers will be auto-installed.

Scan the system for possible virus infection.

Depending on the results, we will determine our next step.

joe5181 · 12 Nov 2012

Arc,

First off, thank you so much for your reply!
I honestly cant remember if I had recently updated anything or not (though I do seem to remember trying to update video drivers because the graphics card tends to fail alot for some reason).
I'll try your steps really quickly, and then I guess we'll go from there. By the way, I'm very sorry about the long reply time- Life likes to keep my Monday's filled to the brim.

-Joe5181

joe5181 · 12 Nov 2012

Arc,

I followed your suggestions and these were my procedures and results:

First, I started the laptop up and let it boot through to try and produce a baseline BSOD (this was at about 8:25 PM)

Next, I disabled the USB selective susbend options at about 8:31, and then restarted the computer and experienced another BSOD (at 8:34, which is right after the startup... yes, this computer takes forever to boot xD )

Then I uninstalled all USB drivers via the method you outlined, and restarted the computer at about 8:41 PM (BSOD was produced at about 8:46 PM)

Then I Booted into Safemode (with networking) and made sure the drivers re-installed. I then restarted the computer again (at about 8:52 PM), and a BSOD was produced at about 8:56.

It's probably worth noting that my wireless logitech mouse no longer works (it's an M305), and that the laptop had issues connecting to the network (which it has been apart of for at least 6 months), until this last boot.

I hope I clearly outlined all steps I did, and any information you might need. Feel free to ask if you need to know anything else, and suggest away!

by the way, I'm attaching the 4 BSODs that have happened so far tonight. Good luck guys, and by the way- Thank you so much for your time so far!

-Joe5181

Arc · 13 Nov 2012

Have you tried the virus scans?

Do some disc checks:

Update your SSD's Firmware (skip it, if it is not a SSD)
Re-seat the sata and power.
Run chkdsk /f/r, following the option two of the tutorial Disk Check
Seatool for dos: SeaTools | Seagate download
Burn it in a blank cd. boot from the CD, click on "Accept", wait for it to finish detecting the drives, then in the upper left corner select "Basic Tests", then select "Long Test" and let it run.

And, enable Driver verifier.
Driver Verifier - Enable and Disable
Run Driver Verifier for 24 hours or the occurrence of the next crash, whichever is earlier.

Let us know the results, with the subsequent crash dumps, if any.

joe5181 · 13 Nov 2012

Arc,

I've ran a in-depth scan using malwarebytes anti malware, but i'll try the two options that you gave (separately, of course :P)
Afterwards, I'll restart, see if no BSOD, and then methodologically continue down the line of solutions you've given me.

I'll keep a detailed list of my actions, BSOD times and everything else. Thanks!
-Joe5181

joe5181 · 13 Nov 2012

ok, So- here's what I've done so far this morning:

Did a normal startup boot at 6:22 (BSOD at 6:23)
Started in safe mode and ran TDSS Killer at 6:33 (Pictures of results and actions are attached)
The computer then BSOD'd as it tried to reboot from TDSS (at 6:38)
Started the computer normally after running TDSS, at 6:42 (BSOD at 6:44)
Then I Re-seated the hard drive (Its a SATA HDD, by the way), and started the comptuer at 6:58 (BSOD at 7:01)

After running TDSS, boot's have become even slower then normal, if that means anything.

I'll continue with the rest of your solutions when I get home from school, and in the meanwhile, I'll leave you with the dumps and screenshots from TDSS that were made this morning

Thanks for all your help so far!
-Joe5181

joe5181 · 13 Nov 2012

By the way, is it worth trying to install the microsoft update detailed here: Microsoft Security Advisory: Update for the Windows Operating System Loader
?

-Joe5181

Arc · 13 Nov 2012

I got something here which is beyond my knowledge

Code:

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

Use !analyze -v to get detailed debugging information.

BugCheck 100000B8, {fffffa8005c44b50, fffffa8005dc3b50, 0, 0}

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

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

I am asking for more help.

Arc · 13 Nov 2012

Got some inputs from Capt.Jack Sparrow.

It is probably a malware, so you have to run the virus scans for one more time.
Uninstall Avast using Avast Uninstall Utility.
Use Microsoft Security Essentials as your antivirus with windows inbuilt firewall, and free MBAM as the on demand scanner.

Download and install those, and then run full system scans with both of them, one by one.