Archief - Bsod...

hallo beste mensen,

zeg ik krijg telkens keer dezelfde BSOD als ik winamp en bearshare lite heb opstaan de BSOD kan na 20 secs komen maar die kan dus ook na 5 uur komen heb ik ondervonden nu had ik het eens zonder winamp getest en kreeg hetzelfde ook BSOD alleen met winamp aan gebeurd het zeker dubbel zo snel nu dit is de fout die ik krijg: bezig met fyske geheugen dump naar schijf 1 enzo teld die dus op

dit is trouwens de foutcode:0x0000005c

heb al op google gezocht maar vind niks voor dit probleem op te lossen en tis redenlijk lastig telkens die BSOD krijgen

[ Bron ]

HAL_INITIALIZATION_FAILED
voir CACHE_INITIALIZATION_FAILED

CACHE_INITIALIZATION_FAILED
Erreur de chargement de la base de registre. Cette erreur ne doit jamais arriver, car elle signifie qu’il n’y a pas assez de place dans le "pool" pour charger la BDR.

[edit]
Test je hardware

STOP Messages That Occur Only at Executive Initialization

One group of STOP messages comes up only during the relatively short Windows NT startup period, which is Phase 4 of the Windows NT boot sequence. Executive initialization is one step during Phase 4. That step can be further broken down into two phases: Phase 0 and Phase 1. During Phase 0 initialization, interrupts are disabled and only a few Executive components, such as the hardware abstraction layer (HAL), are initialized. During Phase 1 initialization, the system is fully operational, and the Windows NT subcomponents do a full initialization.

If you get one of the following Phase 0 initialization STOP messages, run the hardware diagnostics. If no hardware problems are found, reinstall Windows NT and try to initialize it again. If you get the same message again, contact a trained technician.

[ Bron ]

Raanº³ zei:

[ Bron ]

HAL_INITIALIZATION_FAILED
voir CACHE_INITIALIZATION_FAILED

CACHE_INITIALIZATION_FAILED
Erreur de chargement de la base de registre. Cette erreur ne doit jamais arriver, car elle signifie qu’il n’y a pas assez de place dans le "pool" pour charger la BDR.

[edit]
Test je hardware

STOP Messages That Occur Only at Executive Initialization

One group of STOP messages comes up only during the relatively short Windows NT startup period, which is Phase 4 of the Windows NT boot sequence. Executive initialization is one step during Phase 4. That step can be further broken down into two phases: Phase 0 and Phase 1. During Phase 0 initialization, interrupts are disabled and only a few Executive components, such as the hardware abstraction layer (HAL), are initialized. During Phase 1 initialization, the system is fully operational, and the Windows NT subcomponents do a full initialization.

If you get one of the following Phase 0 initialization STOP messages, run the hardware diagnostics. If no hardware problems are found, reinstall Windows NT and try to initialize it again. If you get the same message again, contact a trained technician.

[ Bron ]

Klik om te vergroten...

bedankt voor de hulp dan is het probleem dus toch bijmijn HDD zoals ik had gedacht