Win 7 x64 PROCESS1_INITIALIZATION_FAILURE after trying to get Halo 2 for Vista to run. PLEASE help!!

#1
I recieve a PROCESS1_INITIALIZATION_FAILURE. I am experienced in computer truobleshooting with the exception of Blue Screens. Thus, this is my first post in ANY windows troubleshooting forum. I am looking for ANY help so please read all of this since I don't really know what information is critical so I am getting detailed.

I was trying to get Halo 2 for Vista to work on Windows 7 x64 Ult custom build (By trying the following: Halo 2 Windows 7 (workaround) - "System Cannot Find the Path Specified" or "LIVE gaming on Windows failed to initialize" - Games for Windows Live ).
I also unistalled an unrecognized USB driver from device manager.
After that failed to fix my Halo 2 problem I updated my GPU card driver and rebooted my PC.

*ENTER BSOD*:shocked:

After "Starting Windows" screen appears for roughly ten seconds a "PROCESS1_INITIALIZATION_FAILURE" BS appears. The computer reboots (after about 1.5 seconds) after the Memory Dump reaches 100. I do not get any option to boot into safemode or with "Last known working configuration" but I DO get the options to either start the start-up repair or reboot windows normally.

If I reboot normally the problem repeats, trapping me in a boot loop. So I launch start-up repair.

I tried "Startup Repair" as well as System Restore (I tried ALL of my restore points) but get an error telling me "Windows cannot repair this computer automattically" or "System restore was not successful", respectivaly. I can then choose to send information about this problem or not but I get no further troubleshooting options.

FORTUNATLY, I was able to boot to desktop AFTER using the command prompt to xcopy a "bootcat.cache" file from my HP Laptop (Also running 7 x64 Ult.) into my build's \system32\CodeIntegrity folder in:
- C:\ (The DISKPART > "list volume" command says this is a 100MB system reserve partition of my main HDD)
- D:\ (actual 931GB partition of my main HDD that is my Local Disk [I do not know why it is D:\ and not C:\ but before this it was E:\ and my CD-ROM drive was D:\ so it gets reassigned each time I reboot. [I have even tried the DISKPART > "assign letter=C" command to reassign letter C to this drive but it doesn't seem to help or hurt anything since my Local disk was not C in startup repair but is back to C: now that i have booted]). And
- X:\ (I do not know what this is but it was the default drive when I entered the command prompt [I believe the default was X:\sources or something like that]). I exit command prompt and reboot.

*I AM NOW ABLE TO BOOT TEMPERARILY*

Then and ONLY then will the computer boot to my desktop. A few drivers, such as my GPU driver must be reistalled (I assume this because these drivers were not on my HP's bootcat.cache?).

So besides some missing/inactive drivers I have full function of my PC. BUT WHEN I REBOOT THE PROBLEM COMES BACK AND I B.S. AGAIN. So I performed my fix again and booted to my desktop once more. I have now started backing up my files in preparation an imminent clean install (I am willing to try ANYTHING to avoid this!). While files are backing up I am saving Application and System event logs. (PM me for the logs). Running and screen-shotting CPU-Z and posting this thread.

I do not know what I should try now that I am back at my desktop. ANY help at all will make my day.

Thank you all!


CPU-Z CPU.JPG CPU-Z SBD1.JPG CPU-Z SBD2.JPG CPU-Z SBD3.JPG CPU-Z SBD4.JPG CPU-Z MEMORY.JPG PROCESS1_INITIALIZATION_FAILED.jpg

View attachment 012511-37440-01.dmp
View attachment 021511-40061-01.dmp
View attachment 021611-21949-01.dmp
View attachment 012911-38766-01.dmp
 


Last edited:
#2
Hi there. :)

The PROCESS1_INITIALIZATION_FAILED bug check has a value of 0x0000006B. This bug check indicates that the initialization of the Microsoft Windows operating system failed.

1. Your RAM is set wrong - 1367Mhz 9-9-9-21 while you actually need 1333Mhz 9-9-9-20.

2. Attach the .dmp's from C:\Windows\Minidump.

Good luck.
 


#3
Hi there. :)

The PROCESS1_INITIALIZATION_FAILED bug check has a value of 0x0000006B. This bug check indicates that the initialization of the Microsoft Windows operating system failed.

1. Your RAM is set wrong - 1367Mhz 9-9-9-21 while you actually need 1333Mhz 9-9-9-20.

2. Attach the .dmp's from C:\Windows\Minidump.

Good luck.
I checked for a bios update then restarted. In my BIOS it says my ram is set 1333Mhz 9-9-9-20 already.

Tried to boot. BSOD again.
 


#4
1. Attach CPU-Z memory tab so I can see your new settings
2. Attach the .dmp's from C:\Windows\Minidump.
 


#5
Ran start-up repair again just now.

Root cause found
---------------------
A recent driver installation or upgrade may be preventing the system from starting.

Repair action: System Restore
Result: Completed successfully. Error code = 0x0
Time taken = 391547 ms

Repair action: System restore
Result: Cancelled

Repair action: System files integrety check and repair
Result: Failed. error code = 0xa
Time taken = 8237 ms
------------------------


Working on getting up a new CPU-Z memory tab...

Hm....It still says it's wrong but my BIOS says it's right...
CPU-Z MEMORYb.JPG
Could it be something I am doing in start-up repair or the computer is doing anywhere else while booting changes it?

dmp's:
View attachment 021611-45630-01.dmp
View attachment 021611-21949-01.dmp
View attachment 021511-40061-01.dmp
View attachment 012911-38766-01.dmp
View attachment 012511-37440-01.dmp
 


Last edited:
#6
You got it almost right - 1333Mhz 9-9-9-21.
Try again to achieve this - 1333Mhz 9-9-9-20.

Reattach the memory tab with the new settings.

~~~~~

Again, the goal is to set your RAM 1333Mhz 9-9-9-20.
 


#7
You got it almost right - 1333Mhz 9-9-9-21.
Try again to achieve this - 1333Mhz 9-9-9-20.

Reattach the memory tab with the new settings.

~~~~~

Again, the goal is to set your RAM 1333Mhz 9-9-9-20.
But my Bios says my RAM is at 1333Mhz 9-9-9-20... I do not know why CPU_Z tells me it is wrong each time...
 


#8
Ok, let's then blame CPU-Z for not showing it right.


~~~~~~~

Good that you attached the crash dumps, let's move on:


PROCESS1_INITIALIZATION_FAILED (6b)
BugCheck 6B, {0, 0, 0, 0}
PROCESS_NAME: System
Probably caused by : ntkrnlmp.exe ( nt!Phase1InitializationDiscard+133d ) <--- MS Kernel File

1. Remove Avast:

avast! Uninstall Utility


2. Uninstall LAVASOFT ADAWARE


3. Install MSE:

https://www.microsoft.com/security_essentials/



4. Update old drivers:


FNet Turbo HDD USB Driver
FNETURPX.SYS Fri Oct 03 22:27:02 2008
Welcome to PQI Website


Intel Matrix Storage
iaStor.sys Thu Jun 04 21:53:40 2009
Intel® Driver Update Utility



JMicron RAID
jraid.sys Thu Aug 13 04:10:27 2009
Driver


Marvell 91xx Confige Device Driver for 6G SATA Controller
mv91cons.sys Tue Sep 22 17:36:37 2009
Marvell: SATA controllers - PC/Consumer

Sonic CD/DVD driver (used by many different CD/DVD programs)
PxHlpa64.sys Mon Dec 10 18:49:01 2007
Update it or go to C:\Windows\System32\drivers and rename PxHelp20.sys to PXHelp20.BAK
This will break your CD/DVD program, but can easily be renamed back if needed






Crash Dumps:

Code:
Microsoft (R) Windows Debugger Version 6.12.0002.633 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [F:\a\Minidump\D M P\DMP\021611-21949-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*c:\websymbols*http://msdl.microsoft.com/download/symbols
Executable search path is: 
Windows 7 Kernel Version 7600 MP (8 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7600.16695.amd64fre.win7_gdr.101026-1503
Machine Name:
Kernel base = 0xfffff800`0304a000 PsLoadedModuleList = 0xfffff800`03287e50
Debug session time: Wed Feb 16 02:12:25.747 2011 (UTC - 5:00)
System Uptime: 0 days 0:00:12.636
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+133d )

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 fffff800035ecd8d to fffff800030ba710

STACK_TEXT:  
fffff880`009a9b38 fffff800`035ecd8d : 00000000`00000000 00000000`00000000 fffff800`00812b90 fffff800`00812b90 : nt!KeBugCheck
fffff880`009a9b40 fffff800`0353d219 : 8948db33`e18b4cf2 fffffa80`06707b60 00000000`00000080 fffffa80`06707040 : nt!Phase1InitializationDiscard+0x133d
fffff880`009a9d10 fffff800`0335d7c6 : 06842024`44c72824 00000000`00000080 75358d48`cf8b4c00 fffff800`03098c19 : nt!Phase1Initialization+0x9
fffff880`009a9d40 fffff800`03098c26 : fffff800`03234e80 fffffa80`06707b60 fffff800`03242c40 0d282444`c7000000 : 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+133d
fffff800`035ecd8d cc              int     3

SYMBOL_STACK_INDEX:  1

SYMBOL_NAME:  nt!Phase1InitializationDiscard+133d

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nt

IMAGE_NAME:  ntkrnlmp.exe

DEBUG_FLR_IMAGE_TIMESTAMP:  4cc791bd

FAILURE_BUCKET_ID:  X64_0x6B_nt!Phase1InitializationDiscard+133d

BUCKET_ID:  X64_0x6B_nt!Phase1InitializationDiscard+133d

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




















Microsoft (R) Windows Debugger Version 6.12.0002.633 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [F:\a\Minidump\D M P\DMP\021511-40061-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*c:\websymbols*http://msdl.microsoft.com/download/symbols
Executable search path is: 
Windows 7 Kernel Version 7600 MP (8 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7600.16695.amd64fre.win7_gdr.101026-1503
Machine Name:
Kernel base = 0xfffff800`03001000 PsLoadedModuleList = 0xfffff800`0323ee50
Debug session time: Tue Feb 15 01:56:53.168 2011 (UTC - 5:00)
System Uptime: 0 days 0:00:13.168
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+133d )

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 fffff800035a3d8d to fffff80003071710

STACK_TEXT:  
fffff880`009a9b38 fffff800`035a3d8d : 00000000`00000000 00000000`00000000 fffff800`00812c50 fffff800`00812c50 : nt!KeBugCheck
fffff880`009a9b40 fffff800`034f4219 : 00000000`00000000 fffffa80`067082c0 00000000`00000080 fffffa80`06708840 : nt!Phase1InitializationDiscard+0x133d
fffff880`009a9d10 fffff800`033147c6 : 00000000`00000000 00000000`00000080 00000000`00000000 fffff800`0304fc19 : nt!Phase1Initialization+0x9
fffff880`009a9d40 fffff800`0304fc26 : fffff800`031ebe80 fffffa80`067082c0 fffff800`031f9c40 00000000`00000000 : 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+133d
fffff800`035a3d8d cc              int     3

SYMBOL_STACK_INDEX:  1

SYMBOL_NAME:  nt!Phase1InitializationDiscard+133d

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nt

IMAGE_NAME:  ntkrnlmp.exe

DEBUG_FLR_IMAGE_TIMESTAMP:  4cc791bd

FAILURE_BUCKET_ID:  X64_0x6B_nt!Phase1InitializationDiscard+133d

BUCKET_ID:  X64_0x6B_nt!Phase1InitializationDiscard+133d

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




















Microsoft (R) Windows Debugger Version 6.12.0002.633 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [F:\a\Minidump\D M P\DMP\021611-45630-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*c:\websymbols*http://msdl.microsoft.com/download/symbols
Executable search path is: 
Windows 7 Kernel Version 7600 MP (8 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7600.16695.amd64fre.win7_gdr.101026-1503
Machine Name:
Kernel base = 0xfffff800`03001000 PsLoadedModuleList = 0xfffff800`0323ee50
Debug session time: Wed Feb 16 14:54:42.563 2011 (UTC - 5:00)
System Uptime: 0 days 0:00:10.436
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+133d )

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 fffff800035a3d8d to fffff80003071710

STACK_TEXT:  
fffff880`009a9b38 fffff800`035a3d8d : 00000000`00000000 00000000`00000000 fffff800`00812b90 fffff800`00812b90 : nt!KeBugCheck
fffff880`009a9b40 fffff800`034f4219 : 00000000`00000000 fffffa80`06708b60 00000000`00000080 fffffa80`06708040 : nt!Phase1InitializationDiscard+0x133d
fffff880`009a9d10 fffff800`033147c6 : 00000000`00000000 00000000`00000080 00000000`00000000 fffff800`0304fc19 : nt!Phase1Initialization+0x9
fffff880`009a9d40 fffff800`0304fc26 : fffff800`031ebe80 fffffa80`06708b60 fffff800`031f9c40 00000000`00000000 : 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+133d
fffff800`035a3d8d cc              int     3

SYMBOL_STACK_INDEX:  1

SYMBOL_NAME:  nt!Phase1InitializationDiscard+133d

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nt

IMAGE_NAME:  ntkrnlmp.exe

DEBUG_FLR_IMAGE_TIMESTAMP:  4cc791bd

FAILURE_BUCKET_ID:  X64_0x6B_nt!Phase1InitializationDiscard+133d

BUCKET_ID:  X64_0x6B_nt!Phase1InitializationDiscard+133d

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



Drivers:

Code:
start             end                 module name
fffff880`00d46000 fffff880`00d9d000   ACPI     ACPI.sys     Mon Jul 13 19:19:34 2009 (4A5BC106)
fffff880`01200000 fffff880`0120b000   amdxata  amdxata.sys  Tue May 19 13:56:59 2009 (4A12F2EB)
fffff880`02f86000 fffff880`02fcf000   aswSP    aswSP.SYS    Fri Dec 31 15:00:41 2010 (4D1E3669)
fffff880`01376000 fffff880`0137f000   atapi    atapi.sys    Mon Jul 13 19:19:47 2009 (4A5BC113)
fffff880`0137f000 fffff880`013a9000   ataport  ataport.SYS  Mon Jul 13 19:19:52 2009 (4A5BC118)
fffff880`00e53000 fffff880`00f13000   CI       CI.dll       Mon Jul 13 21:32:13 2009 (4A5BE01D)
fffff880`017c9000 fffff880`017f9000   CLASSPNP CLASSPNP.SYS Mon Jul 13 19:19:58 2009 (4A5BC11E)
fffff880`00ce8000 fffff880`00d46000   CLFS     CLFS.SYS     Mon Jul 13 19:19:57 2009 (4A5BC11D)
fffff880`01649000 fffff880`016bc000   cng      cng.sys      Mon Jul 13 19:49:40 2009 (4A5BC814)
fffff880`019ef000 fffff880`019fd000   crashdmp crashdmp.sys Mon Jul 13 20:01:01 2009 (4A5BCABD)
fffff880`019d9000 fffff880`019ef000   disk     disk.sys     Mon Jul 13 19:19:57 2009 (4A5BC11D)
fffff880`01600000 fffff880`01609000   dump_atapi dump_atapi.sys Mon Jul 13 19:19:47 2009 (4A5BC113)
fffff880`0183a000 fffff880`01846000   dump_dumpata dump_dumpata.sys Mon Jul 13 19:19:47 2009 (4A5BC113)
fffff880`01609000 fffff880`0161c000   dump_dumpfve dump_dumpfve.sys Mon Jul 13 19:21:51 2009 (4A5BC18F)
fffff880`01167000 fffff880`0117b000   fileinfo fileinfo.sys Mon Jul 13 19:34:25 2009 (4A5BC481)
fffff880`0120b000 fffff880`01257000   fltmgr   fltmgr.sys   Mon Jul 13 19:19:59 2009 (4A5BC11F)
fffff880`0161c000 fffff880`01625000   FNETURPX FNETURPX.SYS Fri Oct 03 22:27:02 2008 (48E6D476)
fffff880`016cd000 fffff880`016d7000   Fs_Rec   Fs_Rec.sys   Mon Jul 13 19:19:45 2009 (4A5BC111)
fffff880`01800000 fffff880`0183a000   fvevol   fvevol.sys   Fri Sep 25 22:34:26 2009 (4ABD7DB2)
fffff880`018d6000 fffff880`01920000   fwpkclnt fwpkclnt.sys Mon Jul 13 19:21:08 2009 (4A5BC164)
fffff800`035de000 fffff800`03627000   hal      hal.dll      Mon Jul 13 21:27:36 2009 (4A5BDF08)
fffff880`019d0000 fffff880`019d9000   hwpolicy hwpolicy.sys Mon Jul 13 19:19:22 2009 (4A5BC0FA)
fffff880`0104b000 fffff880`01167000   iaStor   iaStor.sys   Thu Jun 04 21:53:40 2009 (4A287AA4)
fffff880`01258000 fffff880`01376000   iaStorV  iaStorV.sys  Wed Apr 08 12:57:17 2009 (49DCD76D)
fffff880`013a9000 fffff880`013c7000   jraid    jraid.sys    Thu Aug 13 04:10:27 2009 (4A83CA73)
fffff880`02f66000 fffff880`02f75000   kbdclass kbdclass.sys Mon Jul 13 19:19:50 2009 (4A5BC116)
fffff800`00b98000 fffff800`00ba2000   kdcom    kdcom.dll    Mon Jul 13 21:31:07 2009 (4A5BDFDB)
fffff880`01400000 fffff880`0141a000   ksecdd   ksecdd.sys   Mon Jul 13 19:20:54 2009 (4A5BC156)
fffff880`018ab000 fffff880`018d6000   ksecpkg  ksecpkg.sys  Fri Dec 11 01:03:32 2009 (4B21E0B4)
fffff880`0117b000 fffff880`01190000   Lbd      Lbd.sys      Tue May 25 03:45:36 2010 (4BFB8020)
fffff880`00c90000 fffff880`00cd4000   mcupdate_GenuineIntel mcupdate_GenuineIntel.dll Mon Jul 13 21:29:10 2009 (4A5BDF66)
fffff880`02f75000 fffff880`02f84000   mouclass mouclass.sys Mon Jul 13 19:19:50 2009 (4A5BC116)
fffff880`00c5c000 fffff880`00c76000   mountmgr mountmgr.sys Mon Jul 13 19:19:54 2009 (4A5BC11A)
fffff880`00fcf000 fffff880`00fd9000   msisadrv msisadrv.sys Mon Jul 13 19:19:26 2009 (4A5BC0FE)
fffff880`0119c000 fffff880`011fa000   msrpc    msrpc.sys    Mon Jul 13 19:21:32 2009 (4A5BC17C)
fffff880`02f5b000 fffff880`02f66000   mssmbios mssmbios.sys Mon Jul 13 19:31:10 2009 (4A5BC3BE)
fffff880`019be000 fffff880`019d0000   mup      mup.sys      Mon Jul 13 19:23:45 2009 (4A5BC201)
fffff880`00ff5000 fffff880`00fff000   mv91cons mv91cons.sys Tue Sep 22 17:36:37 2009 (4AB94365)
fffff880`016d7000 fffff880`017c9000   ndis     ndis.sys     Mon Jul 13 19:21:40 2009 (4A5BC184)
fffff880`0184b000 fffff880`018ab000   NETIO    NETIO.SYS    Mon Jul 13 19:21:46 2009 (4A5BC18A)
fffff800`03001000 fffff800`035de000   nt       ntkrnlmp.exe Tue Oct 26 22:43:09 2010 (4CC791BD)
fffff880`01456000 fffff880`015f9000   Ntfs     Ntfs.sys     Mon Jul 13 19:20:47 2009 (4A5BC14F)
fffff880`00fd9000 fffff880`00fee000   partmgr  partmgr.sys  Mon Jul 13 19:19:58 2009 (4A5BC11E)
fffff880`00e00000 fffff880`00e33000   pci      pci.sys      Mon Jul 13 19:19:51 2009 (4A5BC117)
fffff880`00fee000 fffff880`00ff5000   pciide   pciide.sys   Mon Jul 13 19:19:49 2009 (4A5BC115)
fffff880`00e40000 fffff880`00e50000   PCIIDEX  PCIIDEX.SYS  Mon Jul 13 19:19:48 2009 (4A5BC114)
fffff880`016bc000 fffff880`016cd000   pcw      pcw.sys      Mon Jul 13 19:19:27 2009 (4A5BC0FF)
fffff880`00cd4000 fffff880`00ce8000   PSHED    PSHED.dll    Mon Jul 13 21:32:23 2009 (4A5BE027)
fffff880`01190000 fffff880`0119bae0   PxHlpa64 PxHlpa64.sys Mon Dec 10 18:49:01 2007 (475DD06D)
fffff880`01984000 fffff880`019be000   rdyboost rdyboost.sys Mon Jul 13 19:34:34 2009 (4A5BC48A)
fffff880`02f41000 fffff880`02f5b000   SCDEmu   SCDEmu.SYS   Mon Apr 12 04:52:25 2010 (4BC2DF49)
fffff880`013c7000 fffff880`013f6000   SCSIPORT SCSIPORT.SYS Mon Jul 13 20:01:04 2009 (4A5BCAC0)
fffff880`0197c000 fffff880`01984000   spldr    spldr.sys    Mon May 11 12:56:27 2009 (4A0858BB)
fffff880`01a01000 fffff880`01bfe000   tcpip    tcpip.sys    Sun Jun 13 23:39:04 2010 (4C15A458)
fffff880`02f2d000 fffff880`02f41000   termdd   termdd.sys   Mon Jul 13 20:16:36 2009 (4A5BCE64)
fffff880`00e33000 fffff880`00e40000   vdrvroot vdrvroot.sys Mon Jul 13 20:01:31 2009 (4A5BCADB)
fffff880`01920000 fffff880`01930000   vmstorfl vmstorfl.sys Mon Jul 13 19:42:54 2009 (4A5BC67E)
fffff880`00d9d000 fffff880`00db2000   volmgr   volmgr.sys   Mon Jul 13 19:19:57 2009 (4A5BC11D)
fffff880`00c00000 fffff880`00c5c000   volmgrx  volmgrx.sys  Mon Jul 13 19:20:33 2009 (4A5BC141)
fffff880`01930000 fffff880`0197c000   volsnap  volsnap.sys  Mon Jul 13 19:20:08 2009 (4A5BC128)
fffff880`01625000 fffff880`01639000   vpcnfltr vpcnfltr.sys Tue Sep 22 21:32:30 2009 (4AB97AAE)
fffff880`02ed6000 fffff880`02f2c180   vpcvmm   vpcvmm.sys   Tue Sep 22 21:32:38 2009 (4AB97AB6)
fffff880`00f13000 fffff880`00fb7000   Wdf01000 Wdf01000.sys Mon Jul 13 19:22:07 2009 (4A5BC19F)
fffff880`00fb7000 fffff880`00fc6000   WDFLDR   WDFLDR.SYS   Mon Jul 13 19:19:54 2009 (4A5BC11A)
fffff880`00fc6000 fffff880`00fcf000   WMILIB   WMILIB.SYS   Mon Jul 13 19:19:51 2009 (4A5BC117)

Unloaded modules:
fffff880`02f84000 fffff880`02f86000   swenum.sys
    Timestamp: unavailable (00000000)
    Checksum:  00000000
    ImageSize:  00002000
fffff880`01635000 fffff880`0163f000   aswRdr.SYS
    Timestamp: unavailable (00000000)
    Checksum:  00000000
    ImageSize:  0000A000
fffff880`01625000 fffff880`01635000   aswTdi.SYS
    Timestamp: unavailable (00000000)
    Checksum:  00000000
    ImageSize:  00010000
 


#9
Thank you, I will start working on those steps. However It is worth mentioning that I now cannot boot at all even with my temporary fix described in the OP. BUT...I do not blue screen anymore. Im not complaining but I still boot loop at the "Starting Windows" screen. Is there a way I can do all of those steps from the Command Prompt in Start-Up Repair?


Btw, all my files are now backed up so even though I was against it before I am now ready and willing to wipe/clean install just to fix this and the other few quirks my machine has been having. (Idk if these other problems are related but one example was the computer would fail to come out of Hibernation if left for a few hours.)
 


Last edited:
#10
Thank you, I will start working on those steps.
Im not complaining but I still boot loop at the "Starting Windows" screen. Is there a way I can do all of those steps from the Command Prompt in Start-Up Repair?
Uninstall Avast and update the drivers.
Then if you get any problems during boot, use start up repair from 7 DVD.

Troubleshoot Startup Problems with Startup Repair Tool in Windows 7

Command Prompt -> chkdsk /f
Command Prompt -> sfc /scannow
 


#12
HELP! I have the same error and also was doing stuff with Halo! I need your bootcat.cache file and ntdll.dll for my x64 Ult Win 7 machine! PLEASE! :D
 


kemical

Windows Forum Admin
Staff member
Premium Supporter
#13
Hi Decimation,
not sure if you've noticed but the last time this thread was active is 2011. Have you tried the fixes outlined by Cybercore in post #10?
 


#14
Who cares if it was 2011? I don't have Avast, and how the hell am I going to update drivers if I can't even access the OS?
 


This website is not affiliated, owned, or endorsed by Microsoft Corporation. It is a member of the Microsoft Partner Program.
Top