Solved BSOD on boot, crashes at AVGIDSxx.sys, CLASSPNP.sys

[wongnog]

I just upgraded my system from an old Q6600 to i7-2600K, replacing motherboard, CPU, CPU cooler, and RAM, and now my Windows 7 system won't boot. I get a BSOD after the Windows logo, general error message that says STOP: 0x0000007B. I then tried to boot into safe mode but it crashes loading AVGIDSxx.sys. Did some googling and found this seems to be a problem with AVG anti-virus, so I loaded my Windows 7 CD and tried to repair my Windows. That didn't work, so in recovery console I went to command prompt and renamed all files AVG*.sys files to AVG*.sys.old in C:\Windows\System32\Drivers as recommended on another forum. Upon rebooting, I still got a BSOD so tried again to go to safe mode and found now it is crashing at CLASSPNP.SYS. I tried to google that error but there seems to be many possible causes for that.

I've tried a bunch of different things, repair windows install from Win 7 CD several times, I also tried to repair/fix the MBR but I forget which command I used for that. I'm now running chkdsk /x on all partitions from the recovery console command prompt.

A bit more googling suggests both these system files causing crashing may be due to a virus or trojan. Any ideas?

 

[Jonathan_King]

Hello,

It sounds like you may have a virus that is affecting many systems lately. Run the Kaspersky TDSSKILLER program: How to remove malware belonging to the family Rootkit.Win32.TDSS (aka Tidserv, TDSServ, Alureon)?

Download that to a CD or USB drive, and boot to a command prompt. Locate the file, and run it from there. If you have it on F:\Tools, enter f:\tools\tdsskiller.exe into the command prompt.

You can also try the manual bootrec commands. Enter these from a command prompt:

bootrec /fixboot
bootrec /fixmbr
bootrec /rebuildbcd

See if that works.

For info, your system is probably not crashing on CLASSPNP.SYS; that is the last driver that was loaded, and it is stuck on the next one.

 

[wongnog]

Thanks I will give that a try. I knew I kept my netbook after getting an iPad for a reason!

 

[wongnog]

Download that to a CD or USB drive, and boot to a command prompt. Locate the file, and run it from there. If you have it on F:\Tools, enter f:\tools\tdsskiller.exe into the command prompt.

You can also try the manual bootrec commands. Enter these from a command prompt:

bootrec /fixboot
bootrec /fixmbr
bootrec /rebuildbcd

See if that works.

For info, your system is probably not crashing on CLASSPNP.SYS; that is the last driver that was loaded, and it is stuck on the next one.

I cannot run the TDSSKILLER tool from my USB key as it does not work in a DOS environment. I tried formatting my USB key using a Windows ME boot disk tool, then booting with this key to run the tool. I also tried booting from my Windows 7 CD, attempt a repair install and then went to command prompt.

I also ran those three bootrec commands and they all said they ran successfully but I still get BSOD on boot. The /rebuildbcd command showed the following however:

Successfully scanned Windows installations
Total identified Windows installation: 0

I notice that the Windows 7 CD detects my windows directory on my hard drive's D:\ partition where before my hardware upgrade it was the C:\ partition. Now the C:\ partition appears to be the Windows 7 recovery partition, which was previously hidden. Maybe I need to run a partition manager? How else can I run that TDSSKILLER program?

 

[Jonathan_King]

Mark your Windows partition as Active, and then run Startup repair.

http://www.sevenforums.com/tutorials/71432-partition-mark-active.html

 

[wongnog]

Thanks, I followed that link to re-set my Windows 7 partition as active, it now shows up as C:\ in startup repair. I'm still getting the BSOD on boot and I've run the startup repair a few times... I reran the bootrec commands and the last one still says 0 windows installations. Any more ideas?

 

[Jonathan_King]

Download Ubuntu, boot it up, and select "Try Ubuntu". Backup your data, and then do a clean install.

Download | Ubuntu

Before you reinstall Windows, wipe the hard drive using Clean All. See here: http://www.sevenforums.com/tutorials/52129-disk-clean-clean-all-diskpart-command.html

 

[wongnog]

I SOLVED MY PROBLEM!!!! Turns out it was my new motherboard's SATA mode. It was set to default in AHCI mode, but my hard drives were formatted in IDE mode. Once I switched it to IDE mode I was able to boot into my new system!

 

[Jonathan_King]

Good, good. Now you can use this guide and enable AHCI again: http://www.sevenforums.com/tutorials/61869-ahci-enable-windows-7-vista.html

If you need anything else, don't hesitate to post a new thread.

 

[wongnog]

Thanks worked like a charm!

 

[ZaqhydN]

Turns out it was my new motherboard's SATA mode. It was set to default in AHCI mode, but my hard drives were formatted in IDE mode. Once I switched it to IDE mode I was able to boot into my new system!

I had encountered the same problem.

I use Imagex to backup my system image regularly.
Upgrading to newer hardware, I applied my image to the new machine.
At first it would refuse to boot and BCDBOOT would fail; I overcame that eventually and ran into this problem.
Windows would start to load, then dump and reboot the machine.
I tried to boot w/ Command prompt to watch what was loading and hopefully find a clue; it was choking on the avgidsha.sys load and dumping to a BSOD.
I've researched this problem extensively and stumbled across the above quote.
I recalled the setting in my BIOS where AHCI was set; I presumed that was the mode of my HDD.
I set it to IDE and presto! Now all I need to do is follow the steps to enable AHCI.
Just wanted to fortify the above claim and solution.

Thanks all!