BSOD Windows 7 on Startup.

[gimills]

I have a triple-boot operating system: Ubuntu Linux, and then Windows XP and Windows 7 through the Windows Boot Manager. Booting into Ubuntu Linux works fine. Trying to boot into Windows XP doesn’t work at all and just goes back to the Windows Boot Manager options. Trying to boot into Windows 7 gets me a BSOD.
I can get into Windows 7, but I have to boot from the Windows 7 installation DVD and go through a big process (Repair Your Computer\System Recovery Options\Startup Repair\Prior Restore Point). At this point, I can boot from the installed Windows 7 on the computer and use of Windows 7 is just fine ….. until I reboot, at which point I get BSOD and have to use the Windows 7 DVD again.

Windows 7 Details:

• Windows 7 Professional x64 (OEM DVD upgrade from Windows 7 Release Candidate)
• Original Installed OS on System: Vista x64
• Age of OS Installation: November, 2009.
• Age of Hardware: Late 2008. Except: Western Digital Caviar Green hard drive bought in February, 2011.
• See also my System Specs below this e-mail.

I’m no expert at this, but looking at the dump files using BlueScreenViewer, it seems my ATI display drivers are one of the problems, but that’s a secondary problem to the other one that has been causing BSOD’s. If I had to guess, I’d say the problem is related to my installation of Ubuntu Linux, because I think the regular BSOD’s started happening right after that.
Anyway, if anyone can help me out in a way that doesn’t involve reinstallation of operating systems I’d be really grateful.

 

[mgorman87]

Only your two crashes in April blamed the video card. The rest from May were a STOP 0x6B
"STOP: 0x0000006B" Stop error message during startup on a computer that is running Windows 7 or Windows Server 2008 R2

[B]STOP 0x0000006B: PROCESS1_INITIALIZATION_FAILED[URL="http://carrona.org/bsodindx.html#top"]
[/URL][/B]

 Usual causes:  Hard drive, Cables, Missing boot files, Disabled driver 

Cause
Any part of the disk subsystem can cause the PROCESS1_INITIALIZATION_FAILED bug check,
including bad disks, bad or incorrect cables, mixing different ATA-type devices on the same chain, 
or drives that are not available becuase of hardware regeneration.
This bug check can also be caused by a missing file from the boot partition
 or by a driver file that a user accidentally disabled in the Drivers tab.

This issue occurs because the Bootcat.cache file is corrupted or
because  the size of the Bootcat.cache file is changed since the last successful  start. 

Note The Bootcat.cache file is located at  %SystemRoot%\system32\codeintegrity.

Try deleting that file and then rebooting your computer and it should re-create it properly.


BSOD BUGCHECK SUMMARY

[FONT=lucida console]
Built by: 7601.17514.amd64fre.win7sp1_rtm.101119-1850
Debug session time: Fri May  6 03:04:09.735 2011 (UTC - 4:00)
System Uptime: 0 days 0:00:10.966
Probably caused by : ntkrnlmp.exe ( nt!Phase1InitializationDiscard+133b )
BUGCHECK_STR:  0x6B
PROCESS_NAME:  System
FAILURE_BUCKET_ID:  X64_0x6B_nt!Phase1InitializationDiscard+133b
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7601.17514.amd64fre.win7sp1_rtm.101119-1850
Debug session time: Thu May  5 10:23:45.449 2011 (UTC - 4:00)
System Uptime: 0 days 0:00:14.291
Probably caused by : ntkrnlmp.exe ( nt!Phase1InitializationDiscard+133b )
BUGCHECK_STR:  0x6B
PROCESS_NAME:  System
FAILURE_BUCKET_ID:  X64_0x6B_nt!Phase1InitializationDiscard+133b
BiosReleaseDate = 02/18/2008
SystemManufacturer = Gateway
SystemProductName = GT5676
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7601.17514.amd64fre.win7sp1_rtm.101119-1850
Debug session time: Wed May  4 23:20:12.964 2011 (UTC - 4:00)
System Uptime: 0 days 0:00:14.180
Probably caused by : ntkrnlmp.exe ( nt!Phase1InitializationDiscard+133b )
BUGCHECK_STR:  0x6B
PROCESS_NAME:  System
FAILURE_BUCKET_ID:  X64_0x6B_nt!Phase1InitializationDiscard+133b
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7601.17514.amd64fre.win7sp1_rtm.101119-1850
Debug session time: Wed May  4 21:22:41.548 2011 (UTC - 4:00)
System Uptime: 0 days 0:00:10.779
Probably caused by : ntkrnlmp.exe ( nt!Phase1InitializationDiscard+133b )
BUGCHECK_STR:  0x6B
PROCESS_NAME:  System
FAILURE_BUCKET_ID:  X64_0x6B_nt!Phase1InitializationDiscard+133b
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7601.17514.amd64fre.win7sp1_rtm.101119-1850
Debug session time: Tue May  3 08:53:14.541 2011 (UTC - 4:00)
System Uptime: 0 days 0:00:14.757
Probably caused by : ntkrnlmp.exe ( nt!Phase1InitializationDiscard+133b )
BUGCHECK_STR:  0x6B
PROCESS_NAME:  System
FAILURE_BUCKET_ID:  X64_0x6B_nt!Phase1InitializationDiscard+133b
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7601.17514.amd64fre.win7sp1_rtm.101119-1850
Debug session time: Sat Apr  2 21:02:53.934 2011 (UTC - 4:00)
System Uptime: 0 days 0:00:33.775
*** WARNING: Unable to verify timestamp for atikmpag.sys
*** ERROR: Module load completed but symbols could not be loaded for atikmpag.sys
Probably caused by : atikmpag.sys ( atikmpag+10aec )
PROCESS_NAME:  System
BUGCHECK_STR:  0x7E
FAILURE_BUCKET_ID:  X64_0x7E_atikmpag+10aec
BiosReleaseDate = 02/18/2008
SystemManufacturer = Gateway
SystemProductName = GT5676
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7601.17514.amd64fre.win7sp1_rtm.101119-1850
Debug session time: Sat Apr  2 17:13:45.923 2011 (UTC - 4:00)
System Uptime: 0 days 0:00:30.170
*** WARNING: Unable to verify timestamp for atikmpag.sys
*** ERROR: Module load completed but symbols could not be loaded for atikmpag.sys
Probably caused by : atikmpag.sys ( atikmpag+10aec )
PROCESS_NAME:  System
BUGCHECK_STR:  0x7E
FAILURE_BUCKET_ID:  X64_0x7E_atikmpag+10aec
BiosReleaseDate = 02/18/2008
SystemManufacturer = Gateway
SystemProductName = GT5676
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
  
[/FONT]

 

[gimills]

Bootcat.cache

Mgorman87 - appreciate the reponse. Deleting bootcat.cache was one thing I did try but forgot to mention in my original post. It didn't have any effect at all. Still got BSOD's in the same manner.

I will check the drivers because its conceivable I disabled something I shouldn't have. I suppose I could turn them all back on and see if the problem goes away.

 

[gimills]

Miya Yao

Thanks for the e-mail. I uploaded the minidump files to SkyDrive as you requested. (They were also attached to my intial post in this forum.)

..... Gareth.