[x64] BSOD on startup (before login)

[KnowledgeWorker]

Hi there,

I get BSODs when booting up, often even before trying to login, but at this point at the latest!
It happens always after some restarts (with or without USB stick inserted).
Why could that hurt the PC? I do not overclock, nor do I use an extra soundcard, just OnBoard.
Graphics: See profile (NVIDIA GeForce 8800GS (by ASUS)) See the error message attached:

Interpretation via Bug Checker:

0x7E: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED

0xC0000005: STATUS_ACCESS_VIOLATION indicates a memory access violation occurred.
(I use the same 2x2 GB DDR-2 RAM...)

I'll attach the Minidump files as soon as I get home to my 7 machine!

Anything else?

Thanks for helping in advance!

 

[TGSoldier]

Hi.

Is this a clean install or an upgrade?

 

[KnowledgeWorker]

@TGSoldier: A clean install.

Troubleshooting by this structure:

- Check to ensure all fans are working (PSU, CPU, and Video especially) Check.

- Check to ensure that there's nothing clogging the heatsinks/coolers Check.

- Check to ensure that all cables are firmly seated Check.

3. Use Speedfan to check your temps, let us know the temps that are reported.
See screenshot (also attached).

4. Check for BIOS upgrades
No BIOS upgrades available currently (BIOS 2102, ASUS P5Q).
(Did the update before installing Windows 7 (wiped the HDD afterwards from Win Vista).)

5. Check your Power Supply for specifications, post both the specifications of your system and the specifications for the PSU.
For System specs, see my profile (last tab).
For PSU: See spec chart (also attached) as well as the website page.
I know my system could be a little underpowered!

6. HD diag - Samsung SpinPoint F1 - doesn't work (see attached screenshot)

7. Mem diag - everything ok, see attached screenshot

8. Independent Virus scan - No (real) problems, see screenshots attached.

9. SiSoftSandra Lite - will follow

10. Zip up the memory dumps - see attachment

 

[KnowledgeWorker]

Every information I could get. *push*

 

[screwhead]

bsod 0x7e

The problem is caused by the Windows Update KB973879, which seems to specifically affect HP Pavillion dv Series laptops running Windows Vista 64-bit.

To fix the problem:

1. Start up your computer and continuously tap the F8 key. You will eventually see the 'Advanced Boot Options' screen, where you must select the Safe Mode option.

2. Once in safe mode, click the Start Menu and type "Programs and Features" (no quotes) in the search box. Press enter once the Programs and Features option is selected.

3. Select 'View installed updates' in the top left of the window.

4. Locate 'Update for Microsoft Windows (KB973879) in the list of updates. You can sort by name for easier searching by clicking the Name column. Click Uninstall at the top of the list when you have selected the correct update.

5. Click Restart Now. Your computer should now function properly.

Please see http://www.techerator.com/2009/08/fix-hp-pavillion-dv-series-gets-blue-screen-after-windows-updates/ for pictures and more detailed information.

 

[midnightwolf76]

The problem is caused by the Windows Update KB973879, which seems to specifically affect HP Pavillion dv Series laptops running Windows Vista 64-bit.

Had the same problem on a Dell XPS desktop, so it is not specific to HP, it is more than likely specific to hardware contained within HP, Dell and similar chipset computers.

 

[usasma]

The update in question applies to Vista and Windows Server 2008. No mention is made of Windows 7 or Server 2008 R2 in the KB article.

64 bit HP's seem to have been the first to present with this issue - but it seems to involve other manufacturer's also. I fixed 4 of these issues at work yesterday (a Dell and 3 HP's) - we still have a Dell that isn't working because we ran Driver Verifier and can't get back in to uninstall the update/disable Driver Verifier.

FWIW - my 64 bit Win7 installation doesn't have this update on it.

Please try the Hitachi Drive Fitness Test on your hard drive (free from here: Support - Downloads and Utilities ) There are references to the file system driver (NTFS.sys) in the dump files - so it's important to run this test to completion.

Please run the memory test for a minimum of 3 passes (overnight is better).

2 of the last 9 minidumps don't have any information in them - this may tend to support the idea that issues with the NTFS file system or with your hard drive may be causing this.

Although the dump files are incomplete, there's enough evidence to suggest that a program called Secure It Easy is causing this issue. The dump files refer to sieflt.sys as the cause - a component of this program. Uninstall the program completely and test to ensure that the BSOD's have gone away. I would suggest that you not reinstall the program - but if you must, then ensure that you have the latest, Win7 compatible version. If a Win7 version isn't available, then don't use it - there's known issues with lower level utility drivers for Vista when used on Win7.

BTW - your version of TeamViewerVPN is very old, I'd suggest updating it before it starts causing you issues.

Here's a summary of the dump files that I ran:

Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Debug session time: Wed Aug 26 19:32:21.522 2009 (GMT-4)
System Uptime: 0 days 0:00:34.052
*** WARNING: Unable to verify timestamp for sieflt.sys
*** ERROR: Module load completed but symbols could not be loaded for sieflt.sys
BugCheck 1000007E, {ffffffffc0000005, fffff80002f3e0fe, fffff88002ffbde8, fffff88002ffb640}
Probably caused by : sieflt.sys ( sieflt+345c )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  System
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Debug session time: Wed Aug 26 20:14:52.402 2009 (GMT-4)
System Uptime: 0 days 0:00:33.931
*** WARNING: Unable to verify timestamp for sieflt.sys
*** ERROR: Module load completed but symbols could not be loaded for sieflt.sys
BugCheck 1000007E, {ffffffffc0000005, fffff80002f7f0fe, fffff880031edde8, fffff880031ed640}
Probably caused by : sieflt.sys ( sieflt+345c )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  System
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Debug session time: Wed Aug 26 19:19:38.780 2009 (GMT-4)
System Uptime: 0 days 0:00:40.185
*** WARNING: Unable to verify timestamp for sieflt.sys
*** ERROR: Module load completed but symbols could not be loaded for sieflt.sys
BugCheck 1000007E, {ffffffffc0000005, fffff80002f420fe, fffff88002fe6de8, fffff88002fe6640}
Probably caused by : sieflt.sys ( sieflt+345c )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  System
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Debug session time: Fri Aug 28 10:49:03.128 2009 (GMT-4)
System Uptime: 0 days 0:00:35.657
*** WARNING: Unable to verify timestamp for sieflt.sys
*** ERROR: Module load completed but symbols could not be loaded for sieflt.sys
BugCheck 1000007E, {ffffffffc0000005, fffff80002f980fe, fffff88002fd8de8, fffff88002fd8640}
Probably caused by : sieflt.sys ( sieflt+345c )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  System

 

[KnowledgeWorker]

Thanks dudes for your answers!

Still I have to say, please note that I don't either use a Dell or HP PC/laptop, this is a self-built desktop PC! Also I don't use a Hitachi HDD, but a Samsung HDD (and a WD HDD out of my old external harddrive)! Or should this work with it as well?

Concerning SIE, thanks for the hint!! I'll definitely try this and e-mail the developers! But:
On their website they say they support the Win 7 RC, so final should work as well?!

Concerning TeamViewer, my version is only missing one update! Is this old? Didn't think so...

 

[usasma]

The HP/Dell KB thing is still very new and is being discussed all over the web. AFAIK it doesn't apply to Win7 - so don't worry about it.

We use the Hitachi DFT at work for all hard drives - and it seems to work well for us. The idea behind hard drive testing is that the manufacturer builds in the standard tests - and then adds some of their own. So we recommend using the manufacturer's test because of the extra tests that are present.

But if the manufacturer's test doesn't work, then we're left with trying something to do at least test the standard tests - which the Hitachi DFT does quite well.

I only look at the dates on the driver files - I have no idea what's current and what's not. My script for running the debugger sorts out the driver files from 2007 and earlier. I just mention them because we've seen (in the past) that older drivers have more compatibility issues than newer drivers.

 

[chev65]

Do you have another PSU that you can try?

 

[KnowledgeWorker]

No, at least not a stronger one. Only some no-name 400W.

*edit* I'm asked for a S/N by the Hitachi drive tester. Is there a way to get this one without taking out the HDD? I just don't want to open it up and then have to rewire it all.

 

[KnowledgeWorker]

Just a quick update, I now installed a new version of "Secure it Easy" (2.0.3.9), as the support e-mailed me "the problem mentioned may be a bug caused by the "Driver verifier" which simulates hard working conditions for the driver, conditions it can not handle without a blue screen of death. This is why, we kindly ask you if you could install a new version of "Secure it Easy" (2.0.3.9) ... which includes at its turn a debug version of the "sieflt.sys" driver."

 

[usasma]

If the Hitachi test asks for a S/N, that means it's not detecting the hard drive. Don't take things apart for that.

Now that you've got the new program installed - does the system work OK? The purpose of Driver Verifier is to stress the drivers. If they don't behave properly under the Driver Verifier stress - then there's a problem with them (either a corruption or a design flaw IMO).

 

[KnowledgeWorker]

Hi usasma, yes, it currently works fine and I will not change anything else now, never change a running system. Have to now get my work done.

I mentioned SiE now here, please add it to the list of to-avoid software. Thanks.