P5Q BSOD on Boot when installing Sound Driver on Win 7 X64

[Misterfied]

Hi, I'm at my wits end here. Re-installed Win 7 X64 about 20 times now! I'm getting various BSOD's after installing a fresh Win 7 X64 after trying to install sound drivers (and SATA drivers - see below) on a P5Q motherboard.

I've tried different versions of the drivers (Realtek HD Audio) from R271-R285 with no difference at all. Also tried the default Asus ALC drivers.

If I install an Nvidia graphics card driver (with HD Audio driver) same thing too, If I disable the onboard HD Audio and re-boot, I still get the crash!

The weird thing is, that I have been happily using Win 7 X64 for about 2 years prior to this with no problems at all! I just wanted to have a nice clean fresh OS.

The only thing I can think of that could be the cause, is possiby the motherboard is faulty, as at one time the onboard NIC packed up, and disabling it / re-enabling it in the BIOS made no difference. Then suddenly it started working again.

I was also triple booting XP Pro / Win 7 X64 / Win 8.1 X64. The sound drivers on the other 2 OS's work fine, no crashes or anything! I hear no sound problems or any other anomalies when using Win 8.1.

I've subsequently got rid of XP and now just dual boot Win 7 / Win 8.1.

The drive I'm installing Windows 7 X64 on is a Kingston V+220 (SVP200S). It is completely clean, formatted, zeroed, aligned and checked with AS-SSD, which reports its health at 99% and 8 years life left.

I also tried integrating all Windows 7 updates (all 180 of them to Jan 20th 2015) into the Windows 7 ISO (installed by USB btw), it makes no difference.

I know about the ATK0110 file. Installing the 2009 version makes no difference to the blue screens on boot.

I've tried installing sound drivers before AND after using the v9 and v10 Intel chipset .inf installer, with no difference.

I've tried installing in AHCI mode and Enhanced IDE mode. No difference other than BSOD messages. With Enhanced IDE mode I was getting a IRQ less than or Equal 0x0A error. In AHCI mode I'm getting STOP 0x7E error.

To re-iterate. The install goes absolutely fine. I set a system restore point, then install a sound driver and boom - crashes on boot. Do a system restore and all's fine again.

Surely if the motherboard was THAT faulty, Windows 8.1 would crash too?

Can anyone PLEASE help me sort this out as it's driving me crazy and I just don't know what to do next.

 

[Misterfied]

Here is the BSOD screen after installing the official P5Q sound drivers from Asus (R2.55).

 

[Misterfied]

I've just found that I get a STOP 0x7E error after installing the default SATA drivers (IMSM_V8901023) too.

I also tried doing a fresh install on another hard drive (there are 4 altogether including the SSD). It made no difference at all. As soon as the sound drivers were installed - BSOD on boot.

 

[Laith]

Does the C: drive have enough space?
Try switching the video adapters.
Does the BIOS have the latest update?

 

[Misterfied]

Thanks for the reply Laith.

The C: drives I tried have loads of space - 75GB+.

The BIOS is the latest that Asus made for this motherboard which is v2209. I also flashed an earlier BIOS to see if it made a difference (which it did not). So, I re-flashed the 2209 BIOS. Loaded defaults, then went from there.

I haven't tried changing the graphics card (yet). Do you really think this could be a problem?

Incidentally, I just tried a fresh install of Windows 8.1 Pro and the audio and video drivers install and run absolutely fine!

I just don't understand it. There seems to be some sort of incompatibility with the P45 Chipset and Windows 7 X64, but I also can't understand why it used to work fine until a brand new install?!

 

[Laith]

Wait so it did fix? But if it is not switch video adapters.

 

[Misterfied]

Nothing is fixed! Windows 7 X64 crashes on reboot after installing SATA or sound drivers.

Was leaving changing the graphics card as a last resort. I have a relatively new card installed (GTX 750 Ti). Luckily I kept my old GTS-250.

 

[Laith]

Okay, run SeaTools for DOS and Windows.
http://www.sevenforums.com/tutorials/313457-seatools-dos-windows-how-use.html
After you've done that run Driver Verifier.
http://www.sevenforums.com/tutorials/101379-driver-verifier-enable-disable.html

 

[Misterfied]

Hi Laith. What is the point of checking my hard drives when I've installed Windows 7 X64 to both SATA and SSD drives with the same result?

Also, how can I verify the sound drivers from Windows when I can't boot into Windows?!

The only way I can boot into Windows is by doing a system restore to the time BEFORE the drivers were installed.

The exact same sound drivers / SATA drivers work fine on Windows 8.1, so surely they're not at fault and surely not ALL of the Realtek drivers can be faulty?

 

[Laith]

Thats why i said you should run Driver Verifier. Run Driver Verifier and skip seatools. If Driver Verifier BSODs on startup with the sound driver than it is badly coded or isnt compatible with windows 7.

 

[Misterfied]

OK, well I did a system restore and Win 7 booted fine again.

I set up Driver verifier as per the instructions in the link, then rebooted and... got a BSOD! Similar to the one above i.e. STOP 0x7E. It's a nightmare.

 

[Golden]

Everytime you get new BSOD's always re-run DM Log Collector and upload a fresh ZIP file.

1. Download the DM Log Collector application to your desktop by clicking the link below

DM Log Collector.exe

2. Run it by double-clicking the icon on your desktop, and follow the prompts.
3. Locate the .ZIP file that is created on your desktop, and upload it here in your next reply.

 

[Misterfied]

Here is the log collector file as requested. I had to do a system restore to get it to boot to the desktop, so no sound drivers have been installed of course.

 

[Golden]

There aren't any .dmp file in your attachment. These are required to analyse the BSOD.

Follow these steps:

1. Configure Windows to create minidumps:
http://www.sevenforums.com/tutorials/174459-dump-files-configure-windows-create-bsod.html

2. Set the paging file on C: to be the same size as the physically installed RAM:
Virtual Memory Paging File - Change

3. Set the Windows Error Reporting service to MANUAL:
http://www.sevenforums.com/tutorials/2495-services-start-disable.html

4. Run Driver Verifier as below:

Run Driver Verifier for 24 hours or the occurrence of the next crash, whichever is earlier.
http://www.sevenforums.com/tutorials/101379-driver-verifier-enable-disable.html

Driver Verifier will cause your computer to run very sluggishly - this is normal. What it is trying to do is force your system to BSOD and isolate the offending driver/s. When it does, reboot, disable driver verifier, reboot as normal and upload the new dmp file/s here.

I recommend creating a system restore point before turning on driver verifier:
http://www.sevenforums.com/tutorials/697-system-restore-point-create.html

If your system fails to boot to desktop once driver verifier is enabled, turn it off by booting into Safe Mode:
http://www.sevenforums.com/tutorials/69585-safe-mode.html

 

[Misterfied]

You did read this thread from the beginning Golden?

I CANNOT run driver verifier to verify the offending driver because the driver is NOT INSTALLED!

If I install the sound driver it cause a BSOD on BOOT and I can't subsequently get into Windows to enable verifier other than if I do a system restore from the boot recovery tools which then removes the driver.

If I configure Windows to create minidumps, will the BOOT BSOD still create a minidump to analyse?

 

[Golden]

Driver Verifier has nothing to do with verifying the sound drivers. It stresses all the drivers to determine where weaknesses may lie, and forces a BSOD - its a quicker way of seeing where the issue lies.

You keep getting 0x7E BSOD's.......I need to see the accompanying .dmp file (usually stored in C:\Windows\Minidump). Do whatever you did to generate that BSOD, and then upload that .dmp files if it exists.

 

[Misterfied]

OK I configured Win 7 to do minidumps, set the page file to 4096 MB, set Error Reporting service to manual, then restarted, all fine.

Set a restore point and installed the sound driver.

Restarted, got a BSOD on BOOT, then came here, but no Minidumps have been generated!

Remember the BSOD is on BOOT. Windows did not go to the desktop after installing the driver. Would that cause the minidump not to be generated?

Have I done something wrong?

 

[Golden]

Remember the BSOD is on BOOT. Windows did not go to the desktop after installing the driver. Would that cause the minidump not to be generated?

Not neccesarily. Restore back to the last restore point, reboot, run Driver Verifier. I want to confirm that the system is stable without the sound drivers, that there isn't anything else conflicting with the sound drivers, making the problem appear to be the sound drivers. Its unlikely, but in BSOD space with deal with factual observations, so lets get some.

 

[Misterfied]

Thanks for helping Golden. I REALLY appreciate it. I've been at this nearly a week now!

OK, well I'm replying from Windows 7 now.

I've set another restore point and got verifier running but it asks to restart the computer. Of course when I do that, I get another BSOD on boot! LOL

Then what?

 

[Golden]

Do you recall the code? 0x7E?