Troubleshooting Windows Servers
 
Home­Calendar­FAQ­Search­Memberlist­Usergroups­Register­Log in
Useful Links
Search
 
 

Display results as :
 
Rechercher Advanced Search
Latest topics
» Order of Group Policy Processing
Tue Dec 30, 2008 4:05 pm by nbhatt

» Authentication Methods in IIS
Tue Dec 30, 2008 1:06 pm by Admin

» Event id 4004 DNS errors and external name resolution problems
Mon Dec 29, 2008 4:19 pm by Admin

» Stop 0x7F or UNEXPECTED_KERNEL_MODE_TRAP
Mon Dec 29, 2008 1:43 pm by Admin

» Stop 0x7B or INACCESSIBLE_BOOT_DEVICE
Sat Dec 27, 2008 10:37 pm by Anonymous

» Stop 0x7A or KERNEL_DATA_INPAGE_ERROR
Fri Dec 26, 2008 9:42 pm by Admin

» Stop 0x79 or MISMATCHED_HAL
Fri Dec 26, 2008 9:36 pm by Admin

» Stop 0x77 or KERNEL_STACK_INPAGE_ERROR
Thu Dec 25, 2008 4:19 pm by Admin

» Stop 0x6B or PROCESS1_INITIALIZATION_FAILED
Thu Dec 25, 2008 4:09 pm by Admin

Navigation
 Portal
 Index
 Memberlist
 Profile
 FAQ
 Search
Forum
Affiliates
free forum
brothersoft.com
Facebook
Follow us on Twitter
Post new topic   Reply to topicShare | 
 

 Stop 0x32 or PHASE1_INITIALIZATION_FAILED

View previous topic View next topic Go down 
AuthorMessage
Admin
Admin


Posts: 35
Join date: 2008-12-17

PostSubject: Stop 0x32 or PHASE1_INITIALIZATION_FAILED   Wed Dec 24, 2008 1:36 pm

The Stop 0x32 message indicates that system startup failed during Phase 1 of the Executive initialization. During Phase 1, interrupts are enabled, device drivers are initialized, and those Executive components that were not initialized during Phase 0 are initialized. Executive components initialized in Phase 1 include the power manager and the I/O manager. The progress bar on the startup screen advances during this phase to provide a visual representation of this part of the boot process. This error indicates a failure of one of those components.

Interpreting the Stop 0x32 Message
This Stop message has four parameters, as listed below

Parameter Description
Parameter 1 The NT status code that describes why the system initialization failed.
Parameter 2 This parameter is reserved (set aside for future use).
Parameter 3 This parameter is reserved (set aside for future use).
Parameter 4 This parameter is reserved (set aside for future use).

Troubleshooting the 0x32 Stop Error
A Stop error during Phase 1 initialization might indicate a problem with outdated firmware, corrupted system files, corrupted or outdated device drivers, an incompatible HAL type, or a hardware failure. Verify that your motherboard and peripheral firmware versions are current. As a last resort, you might be able to resolve the problem by reinstalling Windows Server 2003, which will replace faulty system files and drivers. If you get the same message, record the information in the Stop message and contact a Microsoft support technician.
Back to top Go down
View user profile http://serverunleashed.forumotion.com
 

Stop 0x32 or PHASE1_INITIALIZATION_FAILED

View previous topic View next topic Back to top 
Page 1 of 1

Permissions of this forum:You can reply to topics in this forum
Server Unleashed :: STOP Errors :: Common Stop Messages :: Stop 0x32 or PHASE1_INITIALIZATION_FAILED-
Post new topic   Reply to topic