[XP] Explorer.exe toepassingsfout en I/O-foutstatus melding*

[Verwijderd]

Het probleem is dat de explorer wordt afgesloten (waarbij wordt gevraagd of het probleem verstuurd moet worden of niet)

Later kreeg ik hetzelfde probleem, alleen met drwtsn32.exe

gedaan:

Drwatson uitgeschakeld
Register aanpassingen via internet gevonden

Nu komt:

Connections Tray: explorer.exe - Toepassingsfout
De instructie op 0x77d2370b verwijst naar geheugen op 0x764c3da0. De benodigde gegevens zijn niet in het geheugen geplaast vanwege een I/O-foutstatus van 0xc000009c.

Ik zal kijken als ik nog wat screenshots erbij kan posten, maar het is een laptop van een gebruiker, dus ik kan er niet zomaar op.

Ik heb al rondgezocht op internet, maar ik kan er niet echt iets van vinden. Kan iemand me hiermee helpen?

[ Voor 9% gewijzigd door Verwijderd op 20-09-2007 10:13 ]

[Bitage]

http://www.updatexp.com/stop-messages.html

Zoeken naar '0xC000009C'

An I/O status code of 0xC000009C or 0xC000016A indicates that the requested data could not be found. You can try to correct this by restarting the computer. If a problem with disk integrity exists, Autochk, a program that attempts to mark bad disk sectors as defective so that they are not used in the future, starts automatically. If Autochk fails to run, you can manually perform the integrity check yourself by following the instructions to run Chkdsk provided in "Stop 0x00000024 or NTFS_FILE_SYSTEM" earlier in this list.

Stop 0x00000024 or NTFS_FILE_SYSTEM
(Troubleshooting Stop 0x24 or NTFS_FILE_SYSTEM Error Messages)

Stop 0x00000024 or NTFS_FILE_SYSTEM

The Stop 0x24 message indicates that a problem occurred within Ntfs.sys, the driver file that allows the system to read and write to NTFS file system drives. A similar Stop message, 0x23, exists for the file allocation table (FAT16 or FAT32) file systems.

Possible Resolutions:

* Malfunctioning SCSI and Advanced Technology Attachment (ATA) hardware or drivers can also adversely affect the system's ability to read and write to disk, causing errors. If using SCSI hard disks, check for cabling and termination problems between the SCSI controller and the disks. Periodically check Event Viewer for error messages related to SCSI or FASTFAT in the System log or Autochk in the Application log.
* Verify that the tools you use to continually monitor your system, such as virus scanners, backup programs, or disk defragmenters are compatible with Windows XP. Some disks and adapters come packaged with diagnostic software that you can use to run hardware tests.

To test hard disk or volume integrity

Method 1:
1. In the Run dialog box, in the Open box type:

cmd
2. Start the Chkdsk tool, which detects and attempts to resolve file system structural corruption. At the command prompt type:

chkdsk drive: /f

Method 2:
1. Double-click My Computer, and then select the hard disk you want to check.
2. On the File menu, click Properties.
3. Click the Tools tab.
4. In the Error-checking box, click Check Now.
5. In Check disk options, select the Scan for and attempt recovery of bad sectors check box. You can also select the Automatically fix file system errors check box.

If the volume you are checking is in use, a message asks whether you want to delay disk error checking until the next time you restart your computer. After you restart, disk error checking runs and the volume chosen is not available to run other tasks during this process. If you cannot restart the computer due to the error, use safe mode or Recovery Console.

If you are not using the NTFS file system, and the system partition is formatted with the file allocation table (FAT16 or FAT32) file system, long file name (LFN) information can be lost if hard disk tools are started from an MS-DOS command prompt. A command prompt appears when using a startup floppy disk or when using the command prompt startup option on multiple boot systems that use FAT16 or FAT32 partitions with Microsoft® Windows® 95 OEM Service Release 2 (OSR2), Microsoft® Windows® 98, or Microsoft® Windows® Millennium Edition (Me) installed. Do not use tools meant for other operating systems on Windows XP partitions!
* Nonpaged pool memory might be depleted, which can cause the system to stop. You can resolve this situation by adding more RAM, which increases the quantity of nonpaged pool memory available to the kernel.

[Verwijderd]

Heel erg bedankt, het probleem is opgelost

[alt-92]

Kies in het vervolg een wat meer omschrijvende titel dan alleen "probleem"

Ik heb er ook even het OS in gezet zoals de Windows Clients - Policy aangeeft..