Question

Q: BSOD with BCCODE: 24

Hi all,

I had a blue screen of death when I was using VPC in XP mode.
I'm running Windows 7 Pro SP1 64bit.
I hope anyone could help me with this one.
Many thanks in advance!

The error is given below:

Problem signature:
  Problem Event Name:    BlueScreen
  OS Version:    6.1.7601.2.1.0.256.48
  Locale ID:    2057

Additional information about the problem:
  BCCode:    24
  BCP1:    00000000001904FB
  BCP2:    FFFFF88007539FD8
  BCP3:    FFFFF88007539830
  BCP4:    FFFFF8800123A51C
  OS Version:    6_1_7601
  Service Pack:    1_0
  Product:    256_1

Files that help describe the problem:
  C:\Windows\Minidump\120711-23322-01.dmp
  C:\Users\mrandmrspun\AppData\Local\Temp\WER-11874359-0.sysdata.xml

Read our privacy statement online:
  http://go.microsoft.com/fwlink/?linkid=104288&clcid=0x0409

If the online privacy statement is not available, please read our privacy statement offline:
  C:\Windows\system32\en-US\erofflps.txt

Answer

A:

 

Hi,

        

1.     When did you get this error?

2.     Have you made any changes to your computer prior to the issue?

 

The Blue screen of Death error (BSOD) description you have posted indicates Bug Check Code 24 (BCCode: 24) that is caused by a problem in Ntfs.sys

 

Usually it is caused by disk corruption, disk defragmenters, or (in rare cases) creating a partition larger than 7 GB on a Services for Macintosh volume with a large number of files.

 

I’d like to ask if you get this blue screen while working with a particular program or randomly. The general troubleshooting steps to solve this issue if it occurs randomly are suggested below.

 

Method 1: Please follow the link mentioned below:

Check a drive for errors

http://windows.microsoft.com/en-US/windows7/Check-a-drive-for-errors

 

Method 2: Run SFC scan. System File Checker (sfc) scan will make Windows replace corrupt or missing system files on your computer.

 Steps to perform sfc scan:
a. Click Start, click All Programs, click Accessories, right-click Command Prompt, and select Run as Administrator.
b. Click Continue or supply Administrator credentials if prompted.
c. In the Command Prompt window type the following, and press Enter:
sfc /scannow

Refer this KB article for more information:
http://support.microsoft.com/kb/929833

 

 

Method 3: Resolving stop (blue screen) errors in Windows 7
http://windows.microsoft.com/en-US/windows7/Resolving-stop-blue-screen-errors-in-Windows-7

 

 

 

 

 

Did this solve your problem?

Sorry this didn't help.

Answer

A:

Hi,

Since this happened within VPC you should check with the Experts in TechNet where it is
Supported.

Technet - Forums - Windows 7 virtualization
http://social.technet.microsoft.com/Forums/en/w7itprovirt/threads

==================================================================

These should help :

Use Safe Mode as needed - repeatedly tap F8 as you boot.

Check this thread for information using BlueScreenView, MyEventViewer and other methods
to troubleshoot BlueScreens - top 3 replies (+1 other).

http://answers.microsoft.com/en-us/windows/forum/windows_7-system/sometimes-i-get-a-blue-screen-when-using-ie-8/c675b7b8-795f-474d-a1c4-6b77b3fcd990

We can analyze the minidumps if you make them available from the SkyDrive or other file
sharing sites (such as MediaFire). If you have problems uploading the minidumps copy
them to the Desktop or the Documents folder and upload them from there.

Zip or upload the contents of C:\Windows\minidump

Use SkyDrive to upload collected files.
http://social.technet.microsoft.com/Forums/en-US/w7itproui/thread/4fc10639-02db-4665-993a-08d865088d65

===========================================================

BCCode: 24      0x00000024

Remove ALL power and reseat the cards, memory, and cables (on both ends when possible)
- actually remove and replace - do not just snug.

The primary cause of this Bug_Check is disk issues however it can be caused by memory problems
and even antivirus/antispyware/security programs.

-----------------------------------

BCCode: 24      0x00000024

Bug Check 0x24: NTFS_FILE_SYSTEM

The NTFS_FILE_SYSTEM bug check has a value of 0x00000024. This indicates a problem occurred in ntfs.sys, the driver file that allows the system to read and write to NTFS drives.

Important Information If You Have Received a STOP Code

If you have received a blue screen error, or stop code, the computer has shut down abruptly to protect itself from data loss. A hardware device, its driver, or related software might have caused this error. If your copy of Windows came with your computer, call the manufacturer of your computer. If you purchased Windows separately from your computer, Microsoft provides support. To find contact information for Microsoft or your computer manufacturer, Contact Support.

If you have experience with computers and want to try to recover from this error, follow the steps provided in the Microsoft article Resolving STOP (Blue Screen) Errors in Windows.

The following actions might prevent an error like this from happening again:

  1. Download and install updates and device drivers for your computer from Windows Update.
  2. Scan your computer for computer viruses.
  3. Check your hard disk for errors.
NTFS_FILE_SYSTEM Parameters

The following parameters are displayed on the blue screen.

Parameter Description

1

Specifies source file and line number information. The high 16 bits (the first four hexadecimal digits after the "0x") identify the source file by its identifier number. The low 16 bits identify the source line in the file where the bug check occurred.

2

If NtfsExceptionFilter is on the stack, this parameter specifies the address of the exception record.

3

If NtfsExceptionFilter is on the stack, this parameter specifies the address of the context record.

4


Cause

One possible cause of this bug check is disk corruption. Corruption in the NTFS file system or bad blocks (sectors) on the hard disk can induce this error. Corrupted SCSI and IDE drivers can also adversely affect the system's ability to read and write to disk, thus causing the error.

Another possible cause is depletion of nonpaged pool memory. If the nonpaged pool memory is completely depleted, this error can stop the system. However, during the indexing process, if the amount of available nonpaged pool memory is very low, another kernel-mode driver requiring nonpaged pool memory can also trigger this error.

Resolving the Problem

To debug this problem: Use the .cxr (Display Context Record) command with Parameter 3, and then use the kb (Display Stack Trace) command.

To resolve a disk corruption problem: Check Event Viewer for error messages from SCSI and FASTFAT (System Log) or Autochk (Application Log) that might help pinpoint the device or driver that is causing the error. Try disabling any virus scanners, backup programs, or disk defragmenter tools that continually monitor the system. You should also run hardware diagnostics supplied by the system manufacturer. For details on these procedures, see the owner's manual for your computer. RunChkdsk /f /r to detect and resolve any file system structural corruption. You must restart the system before the disk scan begins on a system partition.

To resolve a nonpaged pool memory depletion problem: Either add new physical memory to the computer (thus increasing the quantity of nonpaged pool memory available to the kernel), or reduce the number of files on the Services for Macintosh (SFM) volume.

BCCode: 24      0x00000024  <-- read this link
http://www.faultwire.com/solutions-fatal_error/NTFS-FILE-SYSTEM-0x00000024-*1051.html?order=votes

=============================================================

To check for Disk Issues - Use Safe Mode if needed - repeatedly tap F8 as you boot.

Run DiskCleanup - Start - All Programs - Accessories - System Tools - Disk Cleanup

Start - type in Search box -  COMMAND   find at top of list -  RIGHT CLICK  -  RUN AS ADMIN

sfc /scannow

How to Repair Windows 7 System Files with System File Checker
http://www.sevenforums.com/tutorials/1538-sfc-scannow-command-system-file-checker.html

Then run checkdisk (chkdsk).

How to Run Disk Check in Windows 7
http://www.sevenforums.com/tutorials/433-disk-check.html

==========================================

Memory tests do not catch all errors such as mismatched memory (possible even for sticks
that appear to be identical) and when faster memory is placed in system behind slower memory.
So it is best to also swap sticks in and out to check for those even if all memory tests fail to show
a problem.

To test RAM check here - let it run 4+ hours or so.  <-- best method
www.memtest.org

For the Vista/Windows 7 Memory Diagnostic Tool

Start - type in Search box ->  Memory - find Memory Diagnostics tool at top of list - Right Click -
RUN AS ADMIN follow the instructions

Windows Vista: How to Scan / Test your RAM or Memory with Windows Vista Memory Diagnostic
Tool
http://www.shivaranjan.com/2007/11/01/windows-vista-how-to-scan-test-your-ram-or-memory-with-windows-vista-memory-diagnostic-tool/

How to Run the Memory Diagnostics Tool in Windows 7
http://www.sevenforums.com/tutorials/715-memory-diagnostics-tool.html

Test Your Computer’s Memory Using Windows Vista Memory Diagnostic Tool
http://www.howtogeek.com/howto/windows-vista/test-your-computers-memory-using-windows-vista-memory-diagnostic-tool/

Hope this helps and Happy Holidays!


Rob Brown - Microsoft MVP - Windows Desktop Experience : Bicycle - Mark Twain said it right.
Rob Brown - Microsoft MVP - Windows and Devices for IT 2010 - current
Windows Insider MVP 2016 - current

Did this solve your problem?

Sorry this didn't help.



 
Question Info

Views: 6,575 Last updated: June 11, 2018 Applies to: