Windows 7 Boots to BSOD

[Gizmo73O]

I've read your BSOD instruction the only problem is I'm getting a bluescreen on startup. I'm dual booting x64/x86 Windows 7 Ultimate. x64 being the one with the problem x86 being the one I'm on now. When I run the Dump & System File Collection app it just pulls information from my 32 bit install.

I'll include the zip anyway but note the above information.

Each time I try to boot my x64 install it starts to load windows/plays the logo animation then when it's about done I get a BSOD stating.

PROCESS1_INITIALIZATION_FAILED
...
...
...
STOP:0x0000006B

The rest of the stop information is just 0x000... over and over. After it blue screens if I select the install again after restart it lets me use the recovery console. It doesn't find any problems and when I try system restore it errors out "0x800700005".

I've tried deleting the bootcat.cache file, it didn't help.

Both installs were fresh. If you need anymore information just let me know.

 

[zigzag3143]

I've read your BSOD instruction the only problem is I'm getting a bluescreen on startup. I'm dual booting x64/x86 Windows 7 Ultimate. x64 being the one with the problem x86 being the one I'm on now. When I run the Dump & System File Collection app it just pulls information from my 32 bit install.

I'll include the zip anyway but note the above information.

Each time I try to boot my x64 install it starts to load windows/plays the logo animation then when it's about done I get a BSOD stating.

PROCESS1_INITIALIZATION_FAILED
...
...
...
STOP:0x00000006B

(May not be the correct #of 0's) The rest of the stop information is just 0x000... over and over. After it blue screens if I select the install again after restart it lets me use the recovery console. It doesn't find any problems and when I try system restore it errors out "0x800700005".

I've tried deleting the bootcat.cache file, it didn't help.

Both installs were fresh. If you need anymore information just let me know.

Try this and upload dmp

If you wish to have others assist you with your computer's BSOD symptoms, upload the contents of your "\Windows\Minidump" folder. The procedure:

* Copy the contents of \Windows\Minidump to another (temporary) location somewhere on your machine.
* Zip up the copy.
* Start your own thread in the appropriate section of the forum and attach the ZIP archive to your post using the "paperclip" (file attachments) button.
* Briefly describe the problem history and circumstances in the same post. Somebody will attend to your query as soon as possible.

 

[CarlTR6]

Gizmo, see if you can update your NVida network drivers. Drivers - Download NVIDIA Drivers

I also recommend that you download and install Microsoft Security Essentials. You currently are using Windows Defender. MSE works much better with Win 7 and does not cause the conflicts that Windows Defender sometimes does. MSE will disable Windows Defender.

I see that mysqld.exe was involved in several of the crashes: Information

 

[Gizmo73O]

The folder is there but there's nothing in it. And my apologies I'm not actually dual booting atleast not on the same drives, the OS's are on 2 different drives I had just forgotten :x.

Edit: I can update my drivers but it'll be for the 32-bit install that's not having problems. =/ Installing Ethernet drivers now.

TY for the quick replys

Still blue screening. Any other directories on my x64 drive that might help? Any way for me to look at that OS's event viewer in this ones?

 

[CarlTR6]

You are welcome. Check the bottom of the first post in this tutorial and make sure your system is set up for mini dumps.

http://www.sevenforums.com/tutorials/83172-dump-files-upload-seven-forums.html

 

[Gizmo73O]

Mine is setup for a Kernel Memory Dump in the directory: %SystemRoot%\MEMORY.DMP

I can't find any such file in my windows directory so should I'm going to change it to minidump > bluescreen and see if any files show up in the minidump folder.

 

[CarlTR6]

Very good. That should work. Make it look like the screen shot in the tutorial post.

 

[Gizmo73O]

Sadly I'm getting nothing. I even tried changing the directory and it still isn't making a file.

This is what I used the first time and now to double check. Still not making a dump file. I'll just have my friend look at it since I can't convey anymore information. Thanks for trying to help.

 

[CarlTR6]

It looks like it is setup properly to me.

 

[Gizmo73O]

So... I went with a reinstall since I was at a loss. I finally get booted into the desktop and I get a notice saying windows experienced and error and it lists my bluescreen stop code etc. and lists files that may help find out what caused the error -_-. Lo and behold it finally creates the dumpfile. So here's to helping someone else that may experience this problem.

Can't help but laugh at this point.

 

[CarlTR6]

A crash that quickly is likely a hardware error, a conflict, or possibly a driver problem. Your up time before the crash was 9.874 seconds. Considering this is a reinstall, it seems very likely you have a hardware problem. I am not sure whether your computer is a desktop or a laptop. Is it still under warranty? If you have a desktop, do you have access to another power supply unit you can try? Check all of your cable connections; make sure they are firm.

You have an almost guaranteed BSOD maker on your system.[FONT=&quot] Please remove any CD virtualization programs such as Daemon Tools and Alcohol 120%. They use a driver, found in your dump, sptd.sys, that is notorious for causing BSODs. Use this SPTD uninstaller when you're done: [/FONT]DuplexSecure - Downloads. Select delete; do not select reinstall. Here is an alternative virtualization program that does not user the sptd.sys driver:
Freeware MagicISO Virtual CD/DVD-ROM(MagicDisc) Overview

Error code 6B, PROCESS1_INITIALIZATION_FAILED. Usual causes: Hard drive, Cables, Missing boot files, Disabled driver.

Kernel base = 0xfffff800`02c08000 PsLoadedModuleList = 0xfffff800`02e45e50
Debug session time: Fri Oct  8 18:25:33.877 2010 (GMT-4)
System Uptime: 0 days 0:00:09.874
Loading Kernel Symbols
...............................................................
.....
Loading User Symbols
Loading unloaded module list
...
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 6B, {0, 0, 0, 0}

Probably caused by : ntkrnlmp.exe ( nt!Phase1InitializationDiscard+1331 )

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

0: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

PROCESS1_INITIALIZATION_FAILED (6b)
Arguments:
Arg1: 0000000000000000, Indicates the NT status code that caused the failure.
Arg2: 0000000000000000, (reserved)
Arg3: 0000000000000000
Arg4: 0000000000000000

Debugging Details:
------------------


CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

BUGCHECK_STR:  0x6B

PROCESS_NAME:  System

CURRENT_IRQL:  0

LAST_CONTROL_TRANSFER:  from fffff800031a9bc1 to fffff80002c785d0

STACK_TEXT:  
fffff880`009a9b38 fffff800`031a9bc1 : 00000000`00000000 00000000`00000000 fffff800`008127f0 fffff800`008127f0 : nt!KeBugCheck
fffff880`009a9b40 fffff800`030faf89 : 01ca0417`27496778 fffffa80`03d0f5b0 00000000`00000080 fffffa80`03d0fb30 : nt!Phase1InitializationDiscard+0x1331
fffff880`009a9d10 fffff800`02f1da86 : 00000000`00000020 00000000`00000080 002e0069`00750064 fffff800`02c56af9 : nt!Phase1Initialization+0x9
fffff880`009a9d40 fffff800`02c56b06 : fffff800`02df2e80 fffffa80`03d0f5b0 fffff800`02e00c40 00000000`00016000 : nt!PspSystemThreadStartup+0x5a
fffff880`009a9d80 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxStartSystemThread+0x16


STACK_COMMAND:  kb

FOLLOWUP_IP: 
nt!Phase1InitializationDiscard+1331
fffff800`031a9bc1 cc              int     3

SYMBOL_STACK_INDEX:  1

SYMBOL_NAME:  nt!Phase1InitializationDiscard+1331

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nt

IMAGE_NAME:  ntkrnlmp.exe

DEBUG_FLR_IMAGE_TIMESTAMP:  4b88cfeb

FAILURE_BUCKET_ID:  X64_0x6B_nt!Phase1InitializationDiscard+1331

BUCKET_ID:  X64_0x6B_nt!Phase1InitializationDiscard+1331

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

0: kd> lmtsmn
start             end                 module name
fffff880`01000000 fffff880`01057000   ACPI     ACPI.sys     Mon Jul 13 19:19:34 2009 (4A5BC106)
fffff880`00ff3000 fffff880`00ffe000   amdxata  amdxata.sys  Tue May 19 13:56:59 2009 (4A12F2EB)
fffff880`00fea000 fffff880`00ff3000   atapi    atapi.sys    Mon Jul 13 19:19:47 2009 (4A5BC113)
fffff880`00e00000 fffff880`00e2a000   ataport  ataport.SYS  Mon Jul 13 19:19:52 2009 (4A5BC118)
fffff880`00f43000 fffff880`00f4f000   BATTC    BATTC.SYS    Mon Jul 13 19:31:01 2009 (4A5BC3B5)
fffff880`00cc8000 fffff880`00d88000   CI       CI.dll       Mon Jul 13 21:32:13 2009 (4A5BE01D)
fffff880`01ace000 fffff880`01afe000   CLASSPNP CLASSPNP.SYS Mon Jul 13 19:19:58 2009 (4A5BC11E)
fffff880`00c6a000 fffff880`00cc8000   CLFS     CLFS.SYS     Mon Jul 13 19:19:57 2009 (4A5BC11D)
fffff880`012fe000 fffff880`01371000   cng      cng.sys      Mon Jul 13 19:49:40 2009 (4A5BC814)
fffff880`01057000 fffff880`01060000   compbatt compbatt.sys Mon Jul 13 19:31:02 2009 (4A5BC3B6)
fffff880`01afe000 fffff880`01b0c000   crashdmp crashdmp.sys Mon Jul 13 20:01:01 2009 (4A5BCABD)
fffff880`01ab8000 fffff880`01ace000   disk     disk.sys     Mon Jul 13 19:19:57 2009 (4A5BC11D)
fffff880`01b0c000 fffff880`01b16000   dump_diskdump dump_diskdump.sys Mon Jul 13 20:01:00 2009 (4A5BCABC)
fffff880`01b55000 fffff880`01b68000   dump_dumpfve dump_dumpfve.sys Mon Jul 13 19:21:51 2009 (4A5BC18F)
fffff880`01b16000 fffff880`01b55000   dump_nvstor64 dump_nvstor64.sys Tue Aug 04 20:31:07 2009 (4A78D2CB)
fffff880`04a74000 fffff880`04a7f000   ElbyCDIO ElbyCDIO.sys Thu Dec 17 17:25:16 2009 (4B2AAFCC)
fffff880`01280000 fffff880`01294000   fileinfo fileinfo.sys Mon Jul 13 19:34:25 2009 (4A5BC481)
fffff880`01234000 fffff880`01280000   fltmgr   fltmgr.sys   Mon Jul 13 19:19:59 2009 (4A5BC11F)
fffff880`01400000 fffff880`0140a000   Fs_Rec   Fs_Rec.sys   Mon Jul 13 19:19:45 2009 (4A5BC111)
fffff880`01a7e000 fffff880`01ab8000   fvevol   fvevol.sys   Fri Sep 25 22:34:26 2009 (4ABD7DB2)
fffff880`0162b000 fffff880`01675000   fwpkclnt fwpkclnt.sys Mon Jul 13 19:21:08 2009 (4A5BC164)
fffff800`031e4000 fffff800`0322d000   hal      hal.dll      Mon Jul 13 21:27:36 2009 (4A5BDF08)
fffff880`0141e000 fffff880`01427000   hwpolicy hwpolicy.sys Mon Jul 13 19:19:22 2009 (4A5BC0FA)
fffff880`04a54000 fffff880`04a63000   kbdclass kbdclass.sys Mon Jul 13 19:19:50 2009 (4A5BC116)
fffff800`00bba000 fffff800`00bc4000   kdcom    kdcom.dll    Mon Jul 13 21:31:07 2009 (4A5BDFDB)
fffff880`015cf000 fffff880`015e9000   ksecdd   ksecdd.sys   Mon Jul 13 19:20:54 2009 (4A5BC156)
fffff880`01600000 fffff880`0162b000   ksecpkg  ksecpkg.sys  Fri Dec 11 01:03:32 2009 (4B21E0B4)
fffff880`00c49000 fffff880`00c56000   mcupdate_AuthenticAMD mcupdate_AuthenticAMD.dll Mon Jul 13 21:29:09 2009 (4A5BDF65)
fffff880`04a63000 fffff880`04a72000   mouclass mouclass.sys Mon Jul 13 19:19:50 2009 (4A5BC116)
fffff880`00fd0000 fffff880`00fea000   mountmgr mountmgr.sys Mon Jul 13 19:19:54 2009 (4A5BC11A)
fffff880`011cc000 fffff880`011d6000   msisadrv msisadrv.sys Mon Jul 13 19:19:26 2009 (4A5BC0FE)
fffff880`012a0000 fffff880`012fe000   msrpc    msrpc.sys    Mon Jul 13 19:21:32 2009 (4A5BC17C)
fffff880`01ba0000 fffff880`01bab000   mssmbios mssmbios.sys Mon Jul 13 19:31:10 2009 (4A5BC3BE)
fffff880`01200000 fffff880`01212000   mup      mup.sys      Mon Jul 13 19:23:45 2009 (4A5BC201)
fffff880`016ab000 fffff880`0179d000   ndis     ndis.sys     Mon Jul 13 19:21:40 2009 (4A5BC184)
fffff880`0179d000 fffff880`017fd000   NETIO    NETIO.SYS    Mon Jul 13 19:21:46 2009 (4A5BC18A)
fffff800`02c08000 fffff800`031e4000   nt       ntkrnlmp.exe Sat Feb 27 02:55:23 2010 (4B88CFEB)
fffff880`0142c000 fffff880`015cf000   Ntfs     Ntfs.sys     Mon Jul 13 19:20:47 2009 (4A5BC14F)
fffff880`055f9000 fffff880`055fa180   nvBridge nvBridge.kmd Sat Sep 11 00:21:30 2010 (4C8B03CA)
fffff880`04a00000 fffff880`04a53600   nvmf6264 nvmf6264.sys Wed Nov 11 18:16:48 2009 (4AFB45E0)
fffff880`00e2a000 fffff880`00e55000   nvstor   nvstor.sys   Wed May 20 02:45:37 2009 (4A13A711)
fffff880`00c00000 fffff880`00c3f000   nvstor64 nvstor64.sys Tue Aug 04 20:31:07 2009 (4A78D2CB)
fffff880`011e3000 fffff880`011f8000   partmgr  partmgr.sys  Mon Jul 13 19:19:58 2009 (4A5BC11E)
fffff880`00f10000 fffff880`00f43000   pci      pci.sys      Mon Jul 13 19:19:51 2009 (4A5BC117)
fffff880`011f8000 fffff880`011ff000   pciide   pciide.sys   Mon Jul 13 19:19:49 2009 (4A5BC115)
fffff880`00fc0000 fffff880`00fd0000   PCIIDEX  PCIIDEX.SYS  Mon Jul 13 19:19:48 2009 (4A5BC114)
fffff880`015e9000 fffff880`015fa000   pcw      pcw.sys      Mon Jul 13 19:19:27 2009 (4A5BC0FF)
fffff880`00c56000 fffff880`00c6a000   PSHED    PSHED.dll    Mon Jul 13 21:32:23 2009 (4A5BE027)
fffff880`01294000 fffff880`0129fe00   PxHlpa64 PxHlpa64.sys Tue Jun 23 19:16:35 2009 (4A416253)
fffff880`013bd000 fffff880`013f7000   rdyboost rdyboost.sys Mon Jul 13 19:34:34 2009 (4A5BC48A)
fffff880`01413000 fffff880`0141e000   Sahdad64 Sahdad64.sys Mon Oct 27 23:56:11 2008 (49068D5B)
fffff880`0140a000 fffff880`01413000   Saibad64 Saibad64.sys Mon Oct 27 23:56:15 2008 (49068D5F)
fffff880`01b96000 fffff880`01ba0000   SaibVdAd64 SaibVdAd64.sys Mon Oct 27 23:56:20 2008 (49068D64)
fffff880`0168d000 fffff880`016aa000   sbp2port sbp2port.sys Mon Jul 13 19:19:53 2009 (4A5BC119)
fffff880`01b7c000 fffff880`01b96000   SCDEmu   SCDEmu.SYS   Mon Apr 12 04:52:25 2010 (4BC2DF49)
fffff880`0119d000 fffff880`011cc000   SCSIPORT SCSIPORT.SYS Mon Jul 13 20:01:04 2009 (4A5BCAC0)
fffff880`01685000 fffff880`0168d000   spldr    spldr.sys    Mon May 11 12:56:27 2009 (4A0858BB)
fffff880`01060000 fffff880`01194000   sptd     sptd.sys     Sun Mar 22 08:35:35 2009 (49C63097)
fffff880`00d88000 fffff880`00dea000   storport storport.sys Mon Jul 13 20:01:18 2009 (4A5BCACE)
fffff880`01801000 fffff880`019fe000   tcpip    tcpip.sys    Mon Jul 13 19:25:34 2009 (4A5BC26E)
fffff880`01b68000 fffff880`01b7c000   termdd   termdd.sys   Mon Jul 13 20:16:36 2009 (4A5BCE64)
fffff880`011d6000 fffff880`011e3000   vdrvroot vdrvroot.sys Mon Jul 13 20:01:31 2009 (4A5BCADB)
fffff880`01675000 fffff880`01685000   vmstorfl vmstorfl.sys Mon Jul 13 19:42:54 2009 (4A5BC67E)
fffff880`00f4f000 fffff880`00f64000   volmgr   volmgr.sys   Mon Jul 13 19:19:57 2009 (4A5BC11D)
fffff880`00f64000 fffff880`00fc0000   volmgrx  volmgrx.sys  Mon Jul 13 19:20:33 2009 (4A5BC141)
fffff880`01371000 fffff880`013bd000   volsnap  volsnap.sys  Mon Jul 13 19:20:08 2009 (4A5BC128)
fffff880`00e5d000 fffff880`00f01000   Wdf01000 Wdf01000.sys Mon Jul 13 19:22:07 2009 (4A5BC19F)
fffff880`00f01000 fffff880`00f10000   WDFLDR   WDFLDR.SYS   Mon Jul 13 19:19:54 2009 (4A5BC11A)
fffff880`01194000 fffff880`0119d000   WMILIB   WMILIB.SYS   Mon Jul 13 19:19:51 2009 (4A5BC117)

Unloaded modules:
fffff880`04a72000 fffff880`04a74000   swenum.sys
    Timestamp: unavailable (00000000)
    Checksum:  00000000
fffff880`04a28000 fffff880`055f9000   nvlddmkm.sys
    Timestamp: unavailable (00000000)
    Checksum:  00000000
fffff880`03eb0000 fffff880`03fa4000   dxgkrnl.sys
    Timestamp: unavailable (00000000)
    Checksum:  00000000

In addition to the notorious sptd driver, you have some out of date drivers on your system. Obsolete drivers can and do cause crashes. Update these drivers, especially those in red font.

PxHlpa64.sys Tue Jun 23 19:16:35 2009 - Sonic CD/DVD driver (used by many different CD/DVD programs) pxHelp20.sys programs
Go to C:\Windows\System32\drivers and rename PxHlpa64.sys to PxHlpa64.BAK
This will break your CD/DVD program, but can easily be renamed after we've finished.

Sahdad64.sys Mon Oct 27 23:56:11 2008 - Unknown driver - suspect it's part of Saitek device (Saitek HDD Filter Driver) Download drivers and software for Saitek products

Saibad64.sys Mon Oct 27 23:56:15 2008 - Saitek Volume Filter Driver, Download drivers and software for Saitek products.

SaibVdAd64.sys Mon Oct 27 23:56:20 2008 - Saitek Virtual Disk Driver, Download drivers and software for Saitek products

You may have to do the following in the safe mode.

1. Uninstall Daemon Tools/Alcohol and the sptd driver.
2. Update the above drivers or uninstall the software they are related to. The Saitek version you have is not compatible with Win 7.
3. Reboot and run your system. Let's see how your system does.

I also found this in your Perfmon report:

Error
Symptom:

Device is not present, not working properly, or does not have all of its drivers installed.Cause:A device has a configuration problem that prevents it from working properly.Details:The device, Null, is reporting "tv_ConfigMgrErr24". This device will not be available until the issue is resolved. The Plug and Play ID for this device is ROOT\LEGACY_NULL\0000.Resolution:1. Verify the correct driver is installed.
2. Try updating the drivers using Windows Update.
3. Check with the manufacturer for an updated driver.
4. Attempt to uninstall and then reinstall the device using Device Manager.Related:Explanation of Error Codes Generated by Device Manager
Manage Devices in Windows