I've posted before how I keep getting the blue screen and it crashed on
me several times freezing and the only way to get rid of the freeze was
to manually restart. I reformatted my computer. Everything has run
smoothly until the second week, no freezing but the blue screen just
comes up! Ever since that time it come up it does it now at least 2-3
times a day. I don't know what to do with this computer anymore.
-Sony Vaio VGN-CS115J

I've installed two different registry repairs and it seems to make
everything worse than it already is. I run chkdsk and it gives me just
the information "chkdsk /f" doesn't work. How can I repair what the
chkdsk has encountered?

Any ideas? Clues?
I don't have the time and money to take it to a "professional" so any
advice would be for me to do myself to the computer.

Thank You.


--
theanna

The actual Stop msg might give some clues
When you formatted / reinstalled Win you used the Sony recovery disk and
drivers disk?
And when you ran MS Update to install critical updates did you also make the
mistake of installing driver updates?

"theanna" wrote in message
...

I've posted before how I keep getting the blue screen and it crashed on
me several times freezing and the only way to get rid of the freeze was
to manually restart. I reformatted my computer. Everything has run
smoothly until the second week, no freezing but the blue screen just
comes up! Ever since that time it come up it does it now at least 2-3
times a day. I don't know what to do with this computer anymore.
-Sony Vaio VGN-CS115J

I've installed two different registry repairs and it seems to make
everything worse than it already is. I run chkdsk and it gives me just
the information "chkdsk /f" doesn't work. How can I repair what the
chkdsk has encountered?

Any ideas? Clues?
I don't have the time and money to take it to a "professional" so any
advice would be for me to do myself to the computer.

Thank You.


--
theanna

Hi, theanna.

There are thousands of versions of "the blue screen", often called the Blue
Screen of Death, or BSOD. Each BSOD includes some "boilerplate" language,
which we don't care about, plus some VERY IMPORTANT information: The STOP
CODE and usually some additional information.

The Stop Code is in the form of:
STOP: 0x80000007B INACCESSIBLE_BOOT_DEVICE

There is often - but not always - some other information, such as 4 strings
of 16 hexadecimal digits each; sometimes there is the name of a driver or
other file.

These may look like gibberish to you, but they tell a very important story
to those who know how to read them - and many of those experts read these
newsgroups daily. So if you post that information - VERBATIM - someone here
should be able to point you in the right direction.

If the BSOD simply blinks on, and then the computer restarts, you can change
the default setting for "what to do on system failure" so that you will have
time to read what the computer is trying to tell you. Actually changing the
setting is very easy, but you have to furnish Administrator credentials and
follow a long click path to get to the easy setting:
Start | Control Panel | System | Advanced system settings (furnish
credentials), then on the Advanced tab, under Startup and Recovery, click
Settings - and you're finally to the page. Now, under System failure,
remove the check from the box in front of Automatically restart. Then OK
your way out to the Desktop.

The next time the BSOD happens, you'll still have to Restart by pushing the
hardware Reset button. But the BSOD will stay on the screen until you do,
giving you all the time you need to copy down that Stop Code information.
Post that here and someone should be able to tell you the next step.

I've installed two different registry repairs and it seems to make
everything worse than it already is. I run chkdsk and it gives me just

For some problems, the best cure is "a bigger hammer"; for others, that's a
disaster. Registry repairs usually fall into the "bigger hammer" category;
chkdsk is probably not the right tool for your problem. :( The Stop Codes
can help us help you figure out what kind of a problem you have so that you
can decide between a hammer and a screwdriver. :^}

RC
--
R. C. White, CPA
San Marcos, TX

Microsoft Windows MVP
Windows Live Mail 2009 (14.0.8064.0206) in Win7 Ultimate x64 RC 7100

"theanna" wrote in message
...

I've posted before how I keep getting the blue screen and it crashed on
me several times freezing and the only way to get rid of the freeze was
to manually restart. I reformatted my computer. Everything has run
smoothly until the second week, no freezing but the blue screen just
comes up! Ever since that time it come up it does it now at least 2-3
times a day. I don't know what to do with this computer anymore.
-Sony Vaio VGN-CS115J

I've installed two different registry repairs and it seems to make
everything worse than it already is. I run chkdsk and it gives me just
the information "chkdsk /f" doesn't work. How can I repair what the
chkdsk has encountered?

Any ideas? Clues?
I don't have the time and money to take it to a "professional" so any
advice would be for me to do myself to the computer.

Thank You.


--
theanna

I had similar symtoms once and the fix was to pull the cpu, clean it and the
fan, put on new thermal paste: the end.
This was after weeks of research and part swaps to no avail, including 2
power supplies.
Al

"R. C. White" wrote in message
...
Hi, theanna.

There are thousands of versions of "the blue screen", often called the
Blue Screen of Death, or BSOD. Each BSOD includes some "boilerplate"
language, which we don't care about, plus some VERY IMPORTANT information:
The STOP CODE and usually some additional information.

The Stop Code is in the form of:
STOP: 0x80000007B INACCESSIBLE_BOOT_DEVICE

There is often - but not always - some other information, such as 4
strings of 16 hexadecimal digits each; sometimes there is the name of a
driver or other file.

These may look like gibberish to you, but they tell a very important story
to those who know how to read them - and many of those experts read these
newsgroups daily. So if you post that information - VERBATIM - someone
here should be able to point you in the right direction.

If the BSOD simply blinks on, and then the computer restarts, you can
change the default setting for "what to do on system failure" so that you
will have time to read what the computer is trying to tell you. Actually
changing the setting is very easy, but you have to furnish Administrator
credentials and follow a long click path to get to the easy setting:
Start | Control Panel | System | Advanced system settings (furnish
credentials), then on the Advanced tab, under Startup and Recovery, click
Settings - and you're finally to the page. Now, under System failure,
remove the check from the box in front of Automatically restart. Then OK
your way out to the Desktop.

The next time the BSOD happens, you'll still have to Restart by pushing
the hardware Reset button. But the BSOD will stay on the screen until you
do, giving you all the time you need to copy down that Stop Code
information. Post that here and someone should be able to tell you the
next step.

I've installed two different registry repairs and it seems to make
everything worse than it already is. I run chkdsk and it gives me just

For some problems, the best cure is "a bigger hammer"; for others, that's
a disaster. Registry repairs usually fall into the "bigger hammer"
category; chkdsk is probably not the right tool for your problem. :(
The Stop Codes can help us help you figure out what kind of a problem you
have so that you can decide between a hammer and a screwdriver. :^}

RC
--
R. C. White, CPA
San Marcos, TX

Microsoft Windows MVP
Windows Live Mail 2009 (14.0.8064.0206) in Win7 Ultimate x64 RC 7100

"theanna" wrote in message
...

I've posted before how I keep getting the blue screen and it crashed on
me several times freezing and the only way to get rid of the freeze was
to manually restart. I reformatted my computer. Everything has run
smoothly until the second week, no freezing but the blue screen just
comes up! Ever since that time it come up it does it now at least 2-3
times a day. I don't know what to do with this computer anymore.
-Sony Vaio VGN-CS115J

I've installed two different registry repairs and it seems to make
everything worse than it already is. I run chkdsk and it gives me just
the information "chkdsk /f" doesn't work. How can I repair what the
chkdsk has encountered?

Any ideas? Clues?
I don't have the time and money to take it to a "professional" so any
advice would be for me to do myself to the computer.

Thank You.


--
theanna

theanna wrote:
I've posted before how I keep getting the blue screen and it crashed on
me several times freezing and the only way to get rid of the freeze was
to manually restart. I reformatted my computer. Everything has run
smoothly until the second week, no freezing but the blue screen just
comes up! Ever since that time it come up it does it now at least 2-3
times a day. I don't know what to do with this computer anymore.
-Sony Vaio VGN-CS115J

I've installed two different registry repairs and it seems to make
everything worse than it already is. I run chkdsk and it gives me just
the information "chkdsk /f" doesn't work. How can I repair what the
chkdsk has encountered?

Any ideas? Clues?
I don't have the time and money to take it to a "professional" so any
advice would be for me to do myself to the computer.

Thank You.


You need to make an ELEVATED Command Prompt to use CHKDSK. Right click
on the COMMAND PROMPT (under accessories) and select RUN AS ADMINISTRATOR.

The type

CHKDSK /R/F

Note there is a single space after the K. It will tell you it needs to
run this at the next reboot. Say Y for yes and then do a restart.

When that has finished (and it may take hours), again at an elevated
Command Prompt type

sfc /scannow

It will do a simple repair. Report back what it finds

Most important when you did the reformat, did you use the Sony
Motherboard drivers and make sure you have the latest

Kotuku

I got an error as well. It keeps showing up.

Technical Information:
*** Stop:0x00000024 (0x00000000001904AA, 0xFFFFFA600DEB788,
0xFFFFFA600D6EB160, 0xFFFFFA60010D2631)

*** Ntfs.sys - address FFFFFA60010D2631 base at FFFFFA6001008000,
Datestamp49e022ca

Any ideas and help would be appreciated.
Thank you

"Kotuku" wrote:

theanna wrote:
I've posted before how I keep getting the blue screen and it crashed on
me several times freezing and the only way to get rid of the freeze was
to manually restart. I reformatted my computer. Everything has run
smoothly until the second week, no freezing but the blue screen just
comes up! Ever since that time it come up it does it now at least 2-3
times a day. I don't know what to do with this computer anymore.
-Sony Vaio VGN-CS115J

I've installed two different registry repairs and it seems to make
everything worse than it already is. I run chkdsk and it gives me just
the information "chkdsk /f" doesn't work. How can I repair what the
chkdsk has encountered?

Any ideas? Clues?
I don't have the time and money to take it to a "professional" so any
advice would be for me to do myself to the computer.

Thank You.


You need to make an ELEVATED Command Prompt to use CHKDSK. Right click
on the COMMAND PROMPT (under accessories) and select RUN AS ADMINISTRATOR.

The type

CHKDSK /R/F

Note there is a single space after the K. It will tell you it needs to
run this at the next reboot. Say Y for yes and then do a restart.

When that has finished (and it may take hours), again at an elevated
Command Prompt type

sfc /scannow

It will do a simple repair. Report back what it finds

Most important when you did the reformat, did you use the Sony
Motherboard drivers and make sure you have the latest

Kotuku

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

Parameters
The error message includes the following four parameters in order of
appearance:

Parameter Description
1 Source file and line number
2 Address of the exception record (optional)
3 Address of the context record (optional)
4 Address where the original exception occurred (optional)


All bug checks due to problems with the file system have encoded in their
first parameter the source file and the line number within the source file
that generated the bug check. The high 16 bits (the first four hexadecimal
digits after the 0x) identify the source file number, while the lower 16
bits (the last four hexadecimal digits of the parameter) identify the source
line in the file where the bug check occurred.

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
Resolving 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. Run Chkdsk /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.

Resolving a nonpaged pool memory depletion problem: Either increase the
amount of installed random access memory (RAM), which increases the quantity
of nonpaged pool memory available to the kernel, or reduce the number of
files on the SFM volume.



--
..
--
"Valyria M." Valyria wrote in message
...
I got an error as well. It keeps showing up.

Technical Information:
*** Stop:0x00000024 (0x00000000001904AA, 0xFFFFFA600DEB788,
0xFFFFFA600D6EB160, 0xFFFFFA60010D2631)

*** Ntfs.sys - address FFFFFA60010D2631 base at FFFFFA6001008000,
Datestamp49e022ca

Any ideas and help would be appreciated.
Thank you

"Kotuku" wrote:

theanna wrote:
I've posted before how I keep getting the blue screen and it crashed on
me several times freezing and the only way to get rid of the freeze was
to manually restart. I reformatted my computer. Everything has run
smoothly until the second week, no freezing but the blue screen just
comes up! Ever since that time it come up it does it now at least 2-3
times a day. I don't know what to do with this computer anymore.
-Sony Vaio VGN-CS115J

I've installed two different registry repairs and it seems to make
everything worse than it already is. I run chkdsk and it gives me just
the information "chkdsk /f" doesn't work. How can I repair what the
chkdsk has encountered?

Any ideas? Clues?
I don't have the time and money to take it to a "professional" so any
advice would be for me to do myself to the computer.

Thank You.


You need to make an ELEVATED Command Prompt to use CHKDSK. Right click
on the COMMAND PROMPT (under accessories) and select RUN AS
ADMINISTRATOR.

The type

CHKDSK /R/F

Note there is a single space after the K. It will tell you it needs to
run this at the next reboot. Say Y for yes and then do a restart.

When that has finished (and it may take hours), again at an elevated
Command Prompt type

sfc /scannow

It will do a simple repair. Report back what it finds

Most important when you did the reformat, did you use the Sony
Motherboard drivers and make sure you have the latest

Kotuku

Delete and recreate the installation volume (partition) during setup.

--
Best of Luck,

Rick Rogers, aka "Nutcase" - Microsoft MVP
http://mvp.support.microsoft.com/
Windows help - www.rickrogers.org
Vote for my shoe: http://rick-mvp.blogspot.com

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

Parameters
The error message includes the following four parameters in order of
appearance:

Parameter Description
1 Source file and line number
2 Address of the exception record (optional)
3 Address of the context record (optional)
4 Address where the original exception occurred (optional)


All bug checks due to problems with the file system have encoded in their
first parameter the source file and the line number within the source file
that generated the bug check. The high 16 bits (the first four hexadecimal
digits after the 0x) identify the source file number, while the lower 16
bits (the last four hexadecimal digits of the parameter) identify the
source line in the file where the bug check occurred.

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
Resolving 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. Run Chkdsk /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.

Resolving a nonpaged pool memory depletion problem: Either increase the
amount of installed random access memory (RAM), which increases the
quantity of nonpaged pool memory available to the kernel, or reduce the
number of files on the SFM volume.



--
.
--
"Valyria M." Valyria wrote in message
...
I got an error as well. It keeps showing up.

Technical Information:
*** Stop:0x00000024 (0x00000000001904AA, 0xFFFFFA600DEB788,
0xFFFFFA600D6EB160, 0xFFFFFA60010D2631)

*** Ntfs.sys - address FFFFFA60010D2631 base at FFFFFA6001008000,
Datestamp49e022ca

Any ideas and help would be appreciated.
Thank you

"Kotuku" wrote:

theanna wrote:
I've posted before how I keep getting the blue screen and it crashed
on
me several times freezing and the only way to get rid of the freeze
was
to manually restart. I reformatted my computer. Everything has run
smoothly until the second week, no freezing but the blue screen just
comes up! Ever since that time it come up it does it now at least 2-3
times a day. I don't know what to do with this computer anymore.
-Sony Vaio VGN-CS115J

I've installed two different registry repairs and it seems to make
everything worse than it already is. I run chkdsk and it gives me just
the information "chkdsk /f" doesn't work. How can I repair what the
chkdsk has encountered?

Any ideas? Clues?
I don't have the time and money to take it to a "professional" so any
advice would be for me to do myself to the computer.

Thank You.


You need to make an ELEVATED Command Prompt to use CHKDSK. Right click
on the COMMAND PROMPT (under accessories) and select RUN AS
ADMINISTRATOR.

The type

CHKDSK /R/F

Note there is a single space after the K. It will tell you it needs to
run this at the next reboot. Say Y for yes and then do a restart.

When that has finished (and it may take hours), again at an elevated
Command Prompt type

sfc /scannow

It will do a simple repair. Report back what it finds

Most important when you did the reformat, did you use the Sony
Motherboard drivers and make sure you have the latest

Kotuku