Jump to content
Posted 11 October 2005 - 06:50 PM
Posted 11 October 2005 - 07:01 PM
tried to download spybot but when it says update, all of the items ticked comeback with !bad checksum!!
Posted 11 October 2005 - 08:48 PM
Hello, I am a complete novice & have been having many problems lately with my pc crashing & re-booting.
When it re-boots sometimes I get a message reading that the system has successfully re-booted from a log then sometimes I get a message saying the system has recovered from a serious error. Also sometimes I get a blue screen with chkdsk stuff on there.
I would suggest you reinstall XP since you got the Fatal Blue Screen.
Back up your important stuff on a CD first.
I have a question for you. Today is my first time on this site however I can not find the New Topic Button.
You must know where it is as you were able to post this message.
I received the following message from this site, however I can not find the
"Once you enter a forum, and are logged in as a member (not as a guest) , you
will see a button at the top of the forum that is called New Topic. Press
that button to post a new topic."
I have made a note of the codes but they sometimes change slightly, this was the most recent.
BCCode:24 BCP1:001902FE BCP2:F9CA5AA4 BCP3: f9CA57AO BCP4:F96E8742 OS Ver:5_1_2600 SP:2_0 PRUDNC7256_1
The error report contents were TEMP\WERa.9fd.dir00\Mini101205-01.dmp
I have run adaware & have Norton running, tried to download spybot but when it says update, all of the items ticked comeback with !bad checksum!!
adaware did find a few nasties e.g. conscorr, tribalfusion. clicknet etc but cleaned them (I think).
I'm going to be honest & admit that I was doing some downloading from limewire, I know its my own fault but lesson learned.
Any help would be appreciated. Sorry for the long windedness but I'm worried about security & stuff.
Would it be easier just to get my pc wiped & start again.
Forgot to say XP pro
Posted 11 October 2005 - 09:56 PM
Posted 12 October 2005 - 09:08 AM
Posted 12 October 2005 - 09:51 AM
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. 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.
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 SFM volume.
0 members, 0 guests, 0 anonymous users