Bienvenido! - Willkommen! - Welcome!

Bitácora Técnica de Tux&Cía., Santa Cruz de la Sierra, BO
Bitácora Central: Tux&Cía.
Bitácora de Información Avanzada: Tux&Cía.-Información
May the source be with you!

Friday, August 5, 2011

BSoD 0x0000007F on RAID

Source
STOP: 0x0000007F (0x0000000000000008, 0x0000000080050031, 0x00000000000006F8, 0xFFFFF80003888F72)
ran a check Disk on all 3 partitions
C: (my SSD) 0 problems, 0 bad sectors.
S: (1.62TB Partition on my RAID 1 drives for storage) 0 problems, 0 bad sectors
P: (200gb partition on my RAID 1 drives for programs) and got this error:
Code :
  1. CHKDSK P:
  2. The type of the file system is NTFS.
  3. Volume label is Programs.

  4. WARNING!  F parameter not specified.
  5. Running CHKDSK in read-only mode.

  6. CHKDSK is verifying files (stage 1 of 3)...
  7.   7680 file records processed.
  8. File verification completed.
  9.   0 large file records processed.
  10.   0 bad file records processed.
  11.   0 EA records processed.
  12.   0 reparse records processed.
  13. CHKDSK is verifying indexes (stage 2 of 3)...
  14.   9000 index entries processed.
  15. Index verification completed.
  16.   0 unindexed files scanned.
  17.   0 unindexed files recovered.
  18. CHKDSK is verifying security descriptors (stage 3 of 3)...
  19.   7680 file SDs/SIDs processed.
  20. Security descriptor verification completed.
  21.   661 data files processed.
  22. CHKDSK is verifying Usn Journal...
  23.   9177824 USN bytes processed.
  24. Usn Journal verification completed.
  25. The master file table's (MFT) BITMAP attribute is incorrect.
  26. The Volume Bitmap is incorrect.
  27. Windows found problems with the file system.
  28. Run CHKDSK with the /F (fix) option to correct these.

  29. 204799999 KB total disk space.
  30.   26162916 KB in 6907 files.
  31.       3300 KB in 662 indexes.
  32.         0 KB in bad sectors.
  33.     89295 KB in use by the system.
  34.     65536 KB occupied by the log file.
  35. 178544488 KB available on disk.

  36.       4096 bytes in each allocation unit.
  37.   51199999 total allocation units on disk.
  38.   44636122 allocation units available on disk.
I ran it with /F and it fixed the problem.

No comments: