What else? BSOD -- upon login.

Sony Vaio VGN-FW590FEB purchased 2009 December 23.
OEM installation of Windows 7 Home Edition x64.
No OS re-installs. Only Microsoft pushed updates for the OS.

Other updates from Sony or HP (for an installed HP Officejet 7310 All-in-one) may be present.

Requested 7 Forums debug information:

Windows_NT6_BSOD_jcgriff2.zip attached.

"perfmon /report" simply display "An error occured while attempting to generate the report." The system cannot find the path specified.

Recent activity included the Microsoft updates that included SP1 and working with a nuvi GPS through a USB connection. Not pointing fingers -- just sayin'. Although the very first DMP file is from December 8th. None before that.

Normal boot gets to the login screen and then BSOD shortly after with System Service Exception.

Safe Modes are iffy at best. If I get past certain points I can work in the safe mode without further issue. Safe Mode with Command Prompt is most stable as a standard user. Further details follow:

Safe Mode gets to the login screen and I can log in as User1 -- a standard user.
Safe Mode gets to the login screen and I CANNOT log in as User2 -- an administrator -- System Service Exception BSOD. Did this twice.
Tried safe mode and logging in as User1 again, all is fine. Switched to User2 and BSOD.
[Later Safe Mode attempts with or without command prompt have been questionable.]

Safe Mode with Networking Support always gets BSOD in iaStor before getting very far.

I can boot to Safe Mode Command Prompt -- usually.

Also see the IRQL_NOT_LESS_OR_EQUAL BSOD occassionally

Other Safe Modes boot to the user login screen (2 users defined), but upon login give me the BSOD.

My debug efforts:

chkdsk /f /r changed nothing.
Windows 7 Repair Disk could not repair with the following information:

Windows 7 Repair Disk says there are no restore points. I thought there should be, but I could be wrong.

Windows 7 Repair Disk mounts the usual C: partition as D:

Attempting to run MBRCheck (error 5 on all drives and no prompt to run upon reboot) and TDSSKiller (can't load driver) without much luck from the User1 (standard user) Safe Mode Command Prompt.


Thanks, guys... I'm two days into it and no closer to a solution...

Steve

Hi smrosenberry and Welcome to the Forum.

I Suggest you Download TDSSKiller and run it in Safe Mode.

There's a rootkit that's been doing the rounds since December that shows itself through blue screens with a IRQ not less or equal stop code. It usually blames the iastor.sys driver as the cause.

Yeah, tryin' my darndest to run that sucker...

I've tried from Safe Mode with Command Prompt using a standard user login running normally or running as administrator. Get the message "Can't load driver". Don't know what driver though.

Also have tried running from the Windows 7 Repair Disc Command Prompt, but then I get a message that it can't be run at all -- incorrect image, wrong image, something along those lines. Can't check now, full scan in progress.

Any other suggestions or hints gladly welcome. I don't know if my current activity covers the TDSSKiller functionality or not...

Currently, I'm running a full scan with the Kaspersky Rescue Disk 10. So far the score is four (4) viruses and five (5) Trojans -- all located in the temp and cache directories. The detailed report shows the following seven (7) events:

four (4) instances listed as "Trojan program Trojan-Spy.win32.Zbot.bcyl"
two (2) instances of "virus HEUR:Trojan-Downloader.Script.Generic"
one (1) instance of "Trojan program Exploit.Java.CVE-2010-0840.c"

Interesting factoid about the last item -- the last screen activity I saw before everything went south, was the Java Environment starting up. Guess I'll explore a little more on that one...

Thanks,
Steve

Your interesting factoid may go a long way to explaining things.

BTW No Kaspersky rescue doesn't cover TDSSKiller as that hunts a Rootkit. Also I haven't (yet) looked at your dump files. Just thought you needed to kill the rootkit (?) before it killed your PC!!

I tried a couple more tricks with TDSSKiller last night: changing the extension from .exe to .com and just simply renaming completely. Alas, I cannot seem to get it to run from a standard user account. Actually, I shouldn't imply that it would run from the admin user account as I haven't been able to have that account up long enough to attempt running it.

Any good alternatives?

Going to try finding a Windows 7 install CD to see if I can get further with the TDSSKiller with it than I do with the Windows 7 Repair CD...

Thanks your continued attention,
Steve