[SOLVED] BSOD on booting Win7 x64

D

doveman

Well-known member
Joined
Sep 22, 2012
Posts
58
So I shipped the PC I'd built for him to my brother and he connected it up and it booted fine and I was showing him how to use it via Teamviewer.

Then in the process of unplugging the printer's USB cable (it wasn't installing the drivers, so I told him to unplug and replug it to see if that would help), he managed to knock the power cable and it went off. Since then, we've been unable to get it to boot and he's just getting a BSOD everytime.

I thought it might be the Nebula tuner PCI card as that had given me some problems before, so I got him to remove that but it didn't help. So I got him to boot the Win7 x32 VHD I'd setup and used Teamviewer from there to load the Win7 x64 Hive in regedit and set the two Nebula drivers to 4 (CurrentControlSet002 which Select indicates is the one being used) to stop them loading but it stil BSOD on boot.

Please can anyone help as he's been waiting for this PC for so long and it's depressing that it's now not working.
 
Some further information.

On the "Windows failed to shutdown properly" screen it only shows Boot Normally and Repair Windows, no Safe mode or Last Known Good Config.

Booting to the VHD, I used BootICE to add another entry to the Windows boot menu, Win7(Safe), set in BootICE to use Safe mode, but selecting this just gave him a BSOD as well. However, it did at least produce the Safe Mode, Last Known Good Config, etc options but Safe Mode with Networking and Last Known Good both still just result in the BSOD.

He managed to boot it with Safe Mode (without networking) but obviously that doesn't allow me to connect via TeamViewer to sort anything out. When he booted into this mode, it said it was reverting some updates. It had installed about 7 Windows Updates some time before the power got cut but we hadn't had a chance to reboot, so they may have not been installed fully and maybe that's why it reverted them, I'm not sure.

I've got a EaseUS ToDo Backup System Image that he could revert to (I added the Boot disk to the grub4dos menu) but that's the nuclear option as I think I made a few changes since making that and it will be tricky to talk him through using that as I won't be able to connect to his machine to do it for him, so I'd rather try and fix the problem if at all possible.

I looked in the Win7 x64 Windows\Minidump folder whilst booted to the VHD and there wasn't any files dated today, only one from August and another from some other non-recent date, so there's no help there.
 
Tried some more things:

1. Selected Startup Repair instead of Boot Normally (by accident, my brother was too slow to change it, before then it had defaulted to Boot Normally every time anyway, so it took him by surprise). Anyway, I didn't want to interrupt it if it was doing something, so we let it run but although it said it had identified some problems and was fixing them, after about 10mins it said it had failed and showed

Startup Repair offline
Problem Signature 01 6.1.7600.16385
Problem Signature 02 6.1.7600.16385
03 Unknown
04 118
05 Auto failover
06 1
07 0x7e

2. Booted into Safe Mode (without networking) again and uninstalled KB2859537 as this article suggests it can cause BSOD on boot http://news.softpedia.com/news/Microsoft-KB2859537-Update-Causes-BSOD-on-Windows-7-375659.shtml I'm not sure this was one of the updates that was applied today before it started BSOD, as that article's dated 13 August so I think I'd probably already installed that and it hadn't caused any problems but it seemed worth a shot. It didn't help though.

3. Did a clean boot as per http://support.microsoft.com/kb/929135 but that still resulted in the BSOD.

4. Booted into Safe Mode (without networking) again, went into Device Manager and disabled the onboard Qualcomm Atheros NIC (as it boots in Safe Mode but not in Safe Mode with Networking it seemed worth trying) but that still BSOD as well.

Every time it boots into Safe Mode (without networking), it says "Failed to configure Windows Updates. Reverting" and the first time after uninstalling that update, it said it had to reboot and did so automatically. After that, it still shows that each time but then continues to the desktop. It said that the first time we booted in this mode earlier today as well, before I tried uninstalling that update, but without forcing a reboot.
 
Wrench97 said:
See if you can follow the instructions here> https://www.sysnative.com/forums/bs...g-instructions-windows-8-7-windows-vista.html Safe mode has mixed results sometimes.
Click to expand...

Thanks. I can probably do all that in Safe Mode (without networking) which seems to boot consistently. However, it isn't creating any minidumps at the moment. Would that be because I have the pagefile on D: and not C:? At least I think I do, I might have left a 1024MB pagefile on C: for this very reason but I'll have to talk my brother through how to check. Will we be able to change this in Safe Mode?
 
You should be able to change it in safe mode.

Is there a cause and a driver named on the blue screen?

If it's too fast to read you can turn off auto restart.
To turn off Auto Reboot Vista/Win7
Start> type/paste Advanced System Settings, from the list Select Advanced System Settings> On the Advanced Tab click on Startup and Recovery> in the Startup and Recovery window un check Automatically Restart, hit Ok to exit the dialogs, reboot the PC for the settings to take effect.
 
Wrench97 said:
You should be able to change it in safe mode.

Is there a cause and a driver named on the blue screen?

If it's too fast to read you can turn off auto restart.
To turn off Auto Reboot Vista/Win7
Start> type/paste Advanced System Settings, from the list Select Advanced System Settings> On the Advanced Tab click on Startup and Recovery> in the Startup and Recovery window un check Automatically Restart, hit Ok to exit the dialogs, reboot the PC for the settings to take effect.
Click to expand...

OK thanks, I'll get him to change it in safe mode then.

I asked him to look over the BSOD for a driver/file but he couldn't see anything (he's not familiar with what to look for but he probably would have seen a filename if there was one) and the only thing he could tell me was "STOP 0x0000007e". I couldn't say if that's the same code that's appeared everytime but I guess it probably is.
 
The parameters after 0x07e will tell us more (numbers like 0xC0000005, 0xFC5CCAF3, 0xFC90F8C0, 0xFC90F5C0), 0xC0000005 for example would mean a memory access violation. And it very well may not be the same code every time.
0x07e image.jpg
 
Wrench97 said:
The parameters after 0x07e will tell us more (numbers like 0xC0000005, 0xFC5CCAF3, 0xFC90F8C0, 0xFC90F5C0), 0xC0000005 for example would mean a memory access violation. And it very well may not be the same code every time.
Click to expand...

OK, thanks. I didn't get him to read me everything on that screen as I wasn't sure how much was useful but now I know I'll get him to tell me those parameters next time.
 
OK, this is what he tells me it said

"(0xffffffffc0000005, 0xfffff8800906a265, 0xfffff880031a1668, 0xfffff880031a0ec0)"

I thought I'd try uninstalling the updates it did the first time he booted it but although it did 7 then, it now only lists 2 from that date (26/09), KB2859537 which is the one we already installed the other day so I don't know why that's back and KB2836943. Maybe the "Failed to config Windows updates, reverting" routine reinstalled that update again. I also had him uninstall Avast as that updated when the Windows updates installed, so I figured that could have got corrupted as well. Didn't help though.

On the next boot (into Safe Mode without networking) it said "Reverting changes" again and then shutdown but after that we could boot into that mode again.

I tried to get him to do chkdsk C: /F but it said the drive was locked as a process was using it. It offered to schedule it for the next boot but that doesn't appear to happen when booting into safe mode as it didn't happen. He said it identified some problems in stage 3 when we ran it in read-only mode with chkdsk C: first but I've just done it (chkdsk E: /F) whilst booted into the VHD and that hasn't identified any problems.

I wanted to do a sfc /scannow but it said "There is a system repair pending which requires a reboot.". We get the same when trying it from the command prompt after booting the Win7 CD and using Shift+F10.

I also got him to try booting into Safe Mode with Command Prompt, which I assumed would just boot to the command prompt and allow us to run sfc /scannow but it just got stuck on "Windows is installing modules."

It seems it was creating minidumps (attached) despite the pagefile only being enabled on D: not C: and they all seem to reference RTKVHD64.sys, which I presume is the Realtek sound driver, so should I just try uninstalling that in Safe Mode (minimal)?
 

Attachments

Hi,

All of the attached DMP files are of the SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M (1000007e) bugcheck.

This indicates that a system thread generated an exception which the error handler did not catch.

BugCheck 1000007E, {ffffffffc0000005, fffff880090c4265, fffff88001fc3668, fffff88001fc2ec0}

As Bruce said above, the first parameter in these bugchecks is what is important. In all of your dumps, it's 0xc0000005 which implies an access violation. If we run an .exr:

Code: 
2: kd> .exr 0xfffff88001fc3668
ExceptionAddress: fffff880090c4265 ([COLOR=#ff0000][I][B]RTKVHD64[/B][/I][/COLOR]+0x0000000000239265)
   ExceptionCode: c0000005 (Access violation)

We can see the access violation was caused by RTKVHD64.sys which is the Realtek High Definition Audio Function Driver.

If we take a look at the call stack:

Code: 
2: kd> kv
Child-SP          RetAddr           : Args to Child                                                           : Call Site
fffff880`01fc38a0 fffffa80`0832f450 : 00000000`00000003 00000000`00000004 00000000`00000010 fffffa80`00000004 : [COLOR=#ff0000][U][I][B]RTKVHD64[/B][/I][/U][/COLOR]+0x239265
fffff880`01fc38a8 00000000`00000003 : 00000000`00000004 00000000`00000010 fffffa80`00000004 fffffa80`00000003 : 0xfffffa80`0832f450
fffff880`01fc38b0 00000000`00000004 : 00000000`00000010 fffffa80`00000004 fffffa80`00000003 00000000`00000000 : 0x3
fffff880`01fc38b8 00000000`00000010 : fffffa80`00000004 fffffa80`00000003 00000000`00000000 fffffa80`080a8790 : 0x4
fffff880`01fc38c0 fffffa80`00000004 : fffffa80`00000003 00000000`00000000 fffffa80`080a8790 00000004`00000008 : 0x10
fffff880`01fc38c8 fffffa80`00000003 : 00000000`00000000 fffffa80`080a8790 00000004`00000008 fffffa80`0833e510 : 0xfffffa80`00000004
fffff880`01fc38d0 00000000`00000000 : fffffa80`080a8790 00000004`00000008 fffffa80`0833e510 fffffa80`08348508 : 0xfffffa80`00000003

We can see RTKVHD64.sys is there as well, before the bugcheck eventually happened.

Uninstall your audio drivers and then visit your motherboard product page for drivers and update your audio drivers to their latest version that's listed - ASRock > 880GMH/U3S3

For reference - Realtek high definition audio driver ver:R2.45

------------------------------------------------------------------------------------

In your loaded drivers list, dtsoftbus01.sys is listed which is the Daemon Tools driver. Daemon Tools is a very popular cause of BSOD's in 7/8 based systems. Please uninstall Daemon Tools. Alternative imaging programs are: MagicISO, Power ISO, etc.

Regards,

Patrick
 
I seem to have fixed his PC now thankfully :) I set the RTKVHD64.sys to Start 4 in the registry (from the Win7 x32 VHD, as we couldn't even boot into Safe Mode Minimal anymore, with it stuck on "Installing modules" or something, which we'd previously only seen when trying Safe Mode with Command Prompt) and it booted OK after that. I uninstalled the Realtek software (it was 6.0.1.6923 and dated from May, strangely the latest driver on the Realtek site is dated April, whilst the one on the Asrock website is very outdated from March 2011 so I don't know where the May one came from) and then Windows installed the default driver from 2010. Then I re-installed Avast and rebooted and then applied the 5 Windows Updates and rebooted and it seems to be stable now.

As it was working perfectly stably before he knocked the power lead, I can only guess that this corrupted RTKVHD64.sys. I'll probably uninstall DT as you suggest as I don't think he needs it, although I don't have the SPTD driver installed which I understand is the main cause of problems.
 
Re: BSOD - DRIVER POWER STATE FAILURE (ACPI.sys)

dtsoftbus01.sys Thu Jun 20 03:22:51 2013

The Daemon tools driver is from 2013, it's the earlier drivers like from 07 through 10 that seem to be the problems.
 
Re: BSOD - DRIVER POWER STATE FAILURE (ACPI.sys)

Wrench97 said:
dtsoftbus01.sys Thu Jun 20 03:22:51 2013

The Daemon tools driver is from 2013, it's the earlier drivers like from 07 through 10 that seem to be the problems.
Click to expand...

Ah OK, thanks. I'll probably leave that installed then.
 
Patrick said:
Hi,

How is the system? Any crashes?

Regards,

Patrick
Click to expand...

I think it's been OK since fixing the Realtek driver thanks.

My brother did report that LibreOffice was crashing when trying to open his Word documents but when I tested it worked fine and then he tried again and it was fine as well, so I think it must have just been a temporary glitch.
 

Has Sysnative Forums helped you? Please consider donating to help us support the site!

Back
Top