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

Misterfied · 31 Jan 2015

Golden said:

Do you recall the code? 0x7E?

Yes. There's a screenshot on the first page of the thread. Did you not see it?

Golden · 31 Jan 2015

So, you get the same BSOD 0x7E regardless of whether the sound drivers are installed or not?

Misterfied · 31 Jan 2015

Golden said:

So, you get the same BSOD 0x7E regardless of whether the sound drivers are installed or not?

It's definitely a 0x7E error when I restart after enabling verifier.exe, but not sure if the other details are exactly the same.

After restarting, the stop came quite along way into the boot process this time, with the Windows logo stuttering as it tried to join together, but never made it to the desktop, then eventually BSOD'd again!

With the sound drivers the STOP is very early in the boot just as the logo dots start to converge.

Again, no Minidumps anywhere though.

What else can I do?

Golden · 31 Jan 2015

So, since we get 0x7E both with and without the sound drivers installed, we can conclude that the problem is not neccessarily the sound drivers only.

Code:

Event[30]:
  Log Name: System
  Source: volmgr
  Date: 2015-01-31T17:39:18.169
  Event ID: 46
  Task: N/A
  Level: Error
  Opcode: N/A
  Keyword: Classic
  User: N/A
  User Name: N/A
  Computer: 37L4247F27-25
  Description: 
Crash dump initialization failed!

I suspect hard disk errors.

Run the LONG test of the DOS version of SeaTools on both the Kingston and 3 x WesternDigital disks:
SeaTools for DOS and Windows - How to Use

Misterfied · 31 Jan 2015

Aha, wait.

I manage to boot into safe mode on Win 7 and got a report of an error and a mini dump!

Here it is:

Misterfied · 31 Jan 2015

Re: Not only sound drivers.

Yes, as I said earlier in the thread. I tried updataing the SATA drivers and also got a BSOD too. I REALLY don't see how the hard drives can ALL be faulty.

I've installed it on 3 different drives now, both of the WD 500GB drives on various partitions and also on the Kingston SSD. No difference.

Golden · 31 Jan 2015

Code:

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

Use !analyze -v to get detailed debugging information.

BugCheck A, {10, 2, 1, fffff800028a9440}

Probably caused by : rdyboost.sys ( rdyboost!ST_STORE<SMD_TRAITS>::StDmCurrentRegionSet+9b )

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

Turn ReadyBoost OFF on every device that has it turned ON.

Complete the hard disk checks.

Misterfied · 31 Jan 2015

Remember this a fresh vanilla install! ReadyBoost I have NEVER consciously used. It's not on by default is it? Surely it's only for removable drives like USB sticks anyway? Not hard disks?

OK, I'll check the hard disks tomorrow, but I am certain it will be a waste of time.

It's 3 am here! Will report back later.

Misterfied · 01 Feb 2015

As expected, all the hard disks check out OK, and the SSD too.

Misterfied · 02 Feb 2015

I also changed the graphics card. No difference at all.