Windows fails to start up sometimes, error 6b

[Rorza33]

Hey guys, so i recently built a new computer and on occasion when i turn the computer on, i'll get a blue screen saying windows failed to load type thing, and then it restarts and i have to recover. now the weird thing is it doesn't happen all the time It more often than not doesn't work, but still there will be times where it works all day. I can't figure out why it works sometimes and not others. i don't do anything different, just facebook and Star Wars the Old Republic, so i don't think its a program which is causing the issue. Anyway here are my comp specs and the problem details

Intel i5 2500 3.30GHz
Gigabyte GTX560OC
C/Master Extreme 700W
WD 1TB Black
Gigabyte GA-Z68AP-D3
LG DWDRW
8GB of RAM

now the problem

Problem signature:
Problem Event Name: BlueScreen
OS Version: 6.1.7601.2.1.0.768.3
Locale ID: 3081

Additional information about the problem:
BCCode: 6b
BCP1: 0000000000000000
BCP2: 0000000000000000
BCP3: 0000000000000000
BCP4: 0000000000000000
OS Version: 6_1_7601
Service Pack: 1_0
Product: 768_1

Files that help describe the problem:
C:\Windows\Minidump\011212-27580-01.dmp
C:\Users\Rory\AppData\Local\Temp\WER-49904-0.sysdata.xml

Read our privacy statement online:
Windows 7 Privacy Statement - Microsoft Windows

If the online privacy statement is not available, please read our privacy statement offline:
C:\Windows\system32\en-US\erofflps.txt

Hope you guys can help me out, doesn't seem to be doing any damage and comp still runs fine after recovery just a bit concerned

 

[JMH]

IF you are experiencing a BSOD we do need the DMP file as it contains the only record of the sequence of events leading up to the crash, what drivers were loaded, and what was responsible.

You may be able to get the DMP files without crashing by booting into safe mode (F8) with networking.

To enable us to 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.
* Attach the ZIP archive to your post using the "paperclip" (file attachments) button.
*If the files are too large please upload them to a file sharing service like "Rapidshare" and put a link to them in your reply.

To ensure minidumps are enabled:

* Go to Start, in the Search Box type: sysdm.cpl, press Enter.
* Under the Advanced tab, click on the Startup and Recovery Settings... button.
* Ensure that Automatically restart is unchecked.
* Under the Write Debugging Information header select Small memory dump (256 kB) in the dropdown box (the 256kb varies).
* Ensure that the Small Dump Directory is listed as %systemroot%\Minidump.
* OK your way out.
* Reboot if changes have been made.

 

[Rorza33]

Here is the minidump folder compressed

 

[mgorman87]

All crashes were the same

STOP 0x0000006B: PROCESS1_INITIALIZATION_FAILED


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


You say it boots sometimes and other times it doesn't?

Check your cable connections to the HDD and motherboard. Also, if you have a spare SATA cable laying around try swapping or if you don't, try a different port on the motherboard.

Please run this hard drive test and report back the results
Hard drive scan usings SeaTools - SeaTools for Windows | Seagate - Both long and short tests


BSOD BUGCHECK SUMMARY

[font=lucida console]
Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506
Debug session time: Sat Jan 21 09:12:26.182 2012 (UTC - 5:00)
System Uptime: 0 days 0:00:14.041
Probably caused by : ntkrnlmp.exe ( nt!Phase1InitializationDiscard+133b )
BUGCHECK_STR:  0x6B
PROCESS_NAME:  System
FAILURE_BUCKET_ID:  X64_0x6B_nt!Phase1InitializationDiscard+133b
BiosReleaseDate = 07/21/2011
SystemManufacturer = Gigabyte Technology Co., Ltd.
SystemProductName = Z68AP-D3
CPUID:        "Intel(R) Core(TM) i5-2500 CPU @ 3.30GHz"
MaxSpeed:     3300
CurrentSpeed: 3309
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506
Debug session time: Thu Jan 19 18:26:43.839 2012 (UTC - 5:00)
System Uptime: 0 days 0:00:13.698
Probably caused by : ntkrnlmp.exe ( nt!Phase1InitializationDiscard+133b )
BUGCHECK_STR:  0x6B
PROCESS_NAME:  System
FAILURE_BUCKET_ID:  X64_0x6B_nt!Phase1InitializationDiscard+133b
BiosReleaseDate = 07/21/2011
SystemManufacturer = Gigabyte Technology Co., Ltd.
SystemProductName = Z68AP-D3
CPUID:        "Intel(R) Core(TM) i5-2500 CPU @ 3.30GHz"
MaxSpeed:     3300
CurrentSpeed: 3309
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506
Debug session time: Tue Jan 17 19:28:57.529 2012 (UTC - 5:00)
System Uptime: 0 days 0:00:12.388
Probably caused by : ntkrnlmp.exe ( nt!Phase1InitializationDiscard+133b )
BUGCHECK_STR:  0x6B
PROCESS_NAME:  System
FAILURE_BUCKET_ID:  X64_0x6B_nt!Phase1InitializationDiscard+133b
BiosReleaseDate = 07/21/2011
SystemManufacturer = Gigabyte Technology Co., Ltd.
SystemProductName = Z68AP-D3
CPUID:        "Intel(R) Core(TM) i5-2500 CPU @ 3.30GHz"
MaxSpeed:     3300
CurrentSpeed: 3309
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506
Debug session time: Mon Jan 16 18:41:37.217 2012 (UTC - 5:00)
System Uptime: 0 days 0:00:11.466
Probably caused by : ntkrnlmp.exe ( nt!Phase1InitializationDiscard+133b )
BUGCHECK_STR:  0x6B
PROCESS_NAME:  System
FAILURE_BUCKET_ID:  X64_0x6B_nt!Phase1InitializationDiscard+133b
BiosReleaseDate = 07/21/2011
SystemManufacturer = Gigabyte Technology Co., Ltd.
SystemProductName = Z68AP-D3
CPUID:        "Intel(R) Core(TM) i5-2500 CPU @ 3.30GHz"
MaxSpeed:     3300
CurrentSpeed: 3309
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506
Debug session time: Sat Jan 14 18:32:46.310 2012 (UTC - 5:00)
System Uptime: 0 days 0:00:12.169
Probably caused by : ntkrnlmp.exe ( nt!Phase1InitializationDiscard+133b )
BUGCHECK_STR:  0x6B
PROCESS_NAME:  System
FAILURE_BUCKET_ID:  X64_0x6B_nt!Phase1InitializationDiscard+133b
BiosReleaseDate = 07/21/2011
SystemManufacturer = Gigabyte Technology Co., Ltd.
SystemProductName = Z68AP-D3
CPUID:        "Intel(R) Core(TM) i5-2500 CPU @ 3.30GHz"
MaxSpeed:     3300
CurrentSpeed: 3309
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506
Debug session time: Thu Jan 12 19:14:16.059 2012 (UTC - 5:00)
System Uptime: 0 days 0:00:12.308
Probably caused by : ntkrnlmp.exe ( nt!Phase1InitializationDiscard+133b )
BUGCHECK_STR:  0x6B
PROCESS_NAME:  System
FAILURE_BUCKET_ID:  X64_0x6B_nt!Phase1InitializationDiscard+133b
BiosReleaseDate = 07/21/2011
SystemManufacturer = Gigabyte Technology Co., Ltd.
SystemProductName = Z68AP-D3
CPUID:        "Intel(R) Core(TM) i5-2500 CPU @ 3.30GHz"
MaxSpeed:     3300
CurrentSpeed: 3309
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506
Debug session time: Thu Jan 12 05:36:55.416 2012 (UTC - 5:00)
System Uptime: 0 days 0:00:13.665
Probably caused by : ntkrnlmp.exe ( nt!Phase1InitializationDiscard+133b )
BUGCHECK_STR:  0x6B
PROCESS_NAME:  System
FAILURE_BUCKET_ID:  X64_0x6B_nt!Phase1InitializationDiscard+133b
BiosReleaseDate = 07/21/2011
SystemManufacturer = Gigabyte Technology Co., Ltd.
SystemProductName = Z68AP-D3
CPUID:        "Intel(R) Core(TM) i5-2500 CPU @ 3.30GHz"
MaxSpeed:     3300
CurrentSpeed: 3309
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506
Debug session time: Mon Jan  9 17:41:03.154 2012 (UTC - 5:00)
System Uptime: 0 days 0:00:12.013
Probably caused by : ntkrnlmp.exe ( nt!Phase1InitializationDiscard+133b )
BUGCHECK_STR:  0x6B
PROCESS_NAME:  System
FAILURE_BUCKET_ID:  X64_0x6B_nt!Phase1InitializationDiscard+133b
BiosReleaseDate = 07/21/2011
SystemManufacturer = Gigabyte Technology Co., Ltd.
SystemProductName = Z68AP-D3
CPUID:        "Intel(R) Core(TM) i5-2500 CPU @ 3.30GHz"
MaxSpeed:     3300
CurrentSpeed: 3309
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506
Debug session time: Sun Jan  8 17:56:48.276 2012 (UTC - 5:00)
System Uptime: 0 days 0:00:14.135
Probably caused by : ntkrnlmp.exe ( nt!Phase1InitializationDiscard+133b )
BUGCHECK_STR:  0x6B
PROCESS_NAME:  System
FAILURE_BUCKET_ID:  X64_0x6B_nt!Phase1InitializationDiscard+133b
BiosReleaseDate = 07/21/2011
SystemManufacturer = Gigabyte Technology Co., Ltd.
SystemProductName = Z68AP-D3
CPUID:        "Intel(R) Core(TM) i5-2500 CPU @ 3.30GHz"
MaxSpeed:     3300
CurrentSpeed: 3309
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506
Debug session time: Thu Jan  5 19:15:23.888 2012 (UTC - 5:00)
System Uptime: 0 days 0:00:12.136
Probably caused by : ntkrnlmp.exe ( nt!Phase1InitializationDiscard+133b )
BUGCHECK_STR:  0x6B
PROCESS_NAME:  System
FAILURE_BUCKET_ID:  X64_0x6B_nt!Phase1InitializationDiscard+133b
BiosReleaseDate = 07/21/2011
SystemManufacturer = Gigabyte Technology Co., Ltd.
SystemProductName = Z68AP-D3
CPUID:        "Intel(R) Core(TM) i5-2500 CPU @ 3.30GHz"
MaxSpeed:     3300
CurrentSpeed: 3309
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506
Debug session time: Wed Jan  4 18:42:02.775 2012 (UTC - 5:00)
System Uptime: 0 days 0:00:14.634
Probably caused by : ntkrnlmp.exe ( nt!Phase1InitializationDiscard+133b )
BUGCHECK_STR:  0x6B
PROCESS_NAME:  System
FAILURE_BUCKET_ID:  X64_0x6B_nt!Phase1InitializationDiscard+133b
BiosReleaseDate = 07/21/2011
SystemManufacturer = Gigabyte Technology Co., Ltd.
SystemProductName = Z68AP-D3
CPUID:        "Intel(R) Core(TM) i5-2500 CPU @ 3.30GHz"
MaxSpeed:     3300
CurrentSpeed: 3309
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
  
[/font]

 

[Rorza33]

well what happens is i get the error and once i do i have to restore my comp and then it works for a certain amount of time. and that length of time that is works is allways different. sometimes i have to recover twice in a since day, other times my computer will be fine for 2-3 days before i get the blue screen again and need to recover. when i do get a blue screen i have to restore because otherwise if i just restart normally i just get the bluescreen again

 

[mgorman87]

Have you run the tests yet

 

[Rorza33]

Short Generic Test showed all passed, but the long generic showed my usb-1394 failed and my pata-sata ones passed

 

[mgorman87]

Do you have the windows 7 dvd? If you do there is a hotfix released by microsoft that address this issue. It requires that you boot into the repair mode and go into command prompt and delete a file bootcat.cache which is located %SystemRoot%\system32\codeintegrity

Here is the link for the KB article - "Stop error code 0x0000006B PROCESS1_INITIALIZATION_FAILED" error message during startup on a computer that is running Windows 7 or Windows Server 2008 R2

You should give that a shot

 

[Rorza33]

I ran my computer in safe mode with command prompt and deleted the bootcat but i'm still getting the same issue. Then i tried through the wondows 7 dvd, but the cmd wouldn't let me delete the file. kept saying it couldn't follow the path or somthing like that

 

[writhziden]

If you post a screenshot of your disk management, I can help you find the path. Start Menu -> Right click Computer -> Manage -> Disk management (from the list on the left) -> http://www.sevenforums.com/tutorials/9733-screenshots-files-upload-post-seven-forums.html

 

[Rorza33]

Heres the pic of my disk management

View attachment 197221

 

[writhziden]

Alright in the recovery environment, your system reserved partition is seen as the C: drive, and your C: drive is seen as the D: drive. %SystemRoot%\system32\codeintegrity becomes D:\Windows\system32\codeintegrity



Also, given the problems you are having, you should check for corrupted files.

• Run Disk Check with both boxes checked for all HDDs and with Automatically fix file system errors checked for all SSDs. Post back your logs for the checks after finding them using http://www.sevenforums.com/tutorials/96938-check-disk-chkdsk-read-event-viewer-log.html
  
  
  
• Run http://www.sevenforums.com/tutorials/1538-sfc-scannow-command-system-file-checker.html up to three times to fix all errors. Post back if it continues to show errors after a fourth run or if the first run comes back with no integrity violations.

Additionally, please follow the http://www.sevenforums.com/crashes-debugging/96879-blue-screen-death-bsod-posting-instructions.html to provide us with more information about your system and possible driver conflicts, event viewer logs, and system hardware/software to give us more information so we may provide better troubleshooting steps.