BSOD.

I'm having problems with my pc. I keep getting a blue screen with the error message. I NEED HELP!

Please describe any events that may have preceded the problem and may be related to it:

• Updates, new software or hardware, error messages, other problems?

Is there any sign of malware on the system or have you had to recently deal with a malware infection.

Let's collect some more information: I'll have a look at it and help you try to resolve the problem.

Download the following 2 files and save both to the My Documents folder:

• BSOD_XP_v1.3_jcgriff2_PROD_.exe - a system file collection application provided by jcgriff2
• autoruns.exe - an application provided by Microsoft SysInternals.

Go to the My Documents folder and run #1 (BSOD_XP_v1.3_jcgriff2_PROD_.exe). (That will also run #2.)

It will take a little time to complete: Please be patient and wait for it to finish.
A new folder named TSF_XP_Support will be created in My Documents.

Zip up the newly created TSF_XP_Support folder.

• Right-click on the TSF_XP_Support folder > Send to ... > Compressed (zipped) Folder.
  The newly created zip file will be located in the My Documents folder.

Please upload the zip file to a file sharing website of your choice and and post a link to it in this thread so that we can access your uploaded zip file.

Note: The BC forums will allow a total attachment size of only 512 kb (and what you need to attach will exceed this limit).
See the suggestions in the following links for recommendations on file sharing websites:

• http://lifehacker.com/388284/best-online-file-sharing-services
• http://www.hongkiat.com/blog/15-great-free-online-file-sharing-alternatives/
• http://www.smashingapps.com/2008/08/28/5-best-free-file-hosting-services-to-store-your-files.html

Please Publish a Snapshot using Speccy, and post a link to it in this thread.

• It is a convenient and accurate way of providing us with details of your computer specifications.

Please download MiniToolBox, save it to your desktop and run it.

• Checkmark the following checkboxes:
  
  • List Installed Programs
• Click Go.
  When the scan is finished, a text file will open in a Notepad window.
• Copy the entire contents of the Notepad window, and paste in your reply.
  (Result.txt will be saved in the same directory the tool is run.)

I'm not really sure the events that led to the problem I'm having. But, when I play mp3's from iTunes, WMP, etc... and videos on any website such as Youtube, I get a random distorted static noise. Not to mention, it even makes that noise when I reply on AIM, when my computer plays the music at startup.. Any solution?

Here's the TSF_XP:
http://limelinx.com/files/394a454c3cdb212060bc401b834382fd

Snapshot:
http://speccy.piriform.com/results/M0LHyw7pETxhv4scjexRLFe

All Installed Programs:
http://limelinx.com/files/1dfb80c2d33d523df0d38c80ab4555ae

Forgot to add Autoruns: "There are many missing files"
http://limelinx.com/files/81002aa0acda55a263a838af3cab8ebc

There is a problem with the hard drive. Backup any personal files of importance and test the hard drive.

Try the WD utility (but it is temperamental, so if you have a problem use Seagate's SeaTools utility).

Check your system HDD with the HDD manufacturer's diagnostic utility. (The exact same tool is used for all Western Digital hard drives, so do not concern yourself about the reference to a different model in the following instructions.)

Go to the WD Caviar Black (SATA & SAS) Downloads page and download Data Lifeguard Diagnostic for DOS (CD)

• From the two files available, choose the .ISO version Diag504fCD.iso

If you do not already have a suitable burning program for writing .ISO images to disc ...

• Download and install ImgBurn.
  Ensure that you UN-check the box agreeing to install the Ask toolbar during the installation.
• Place a new (blank) CD disc in the drive tray.
• Choose Write image file to disc.
  
  • Under Source, click on the Browse button: Navigate to and select the .ISO file that you wish to burn.
  • Place a check-mark in the box beside Verify.
• Click
  
  When the CD has been burned and verified as successful, it will be bootable.

Boot from the CD.

• (You may need to change the boot order to enable booting from CD before hard drive.)
• Run the Short/Quick test and then the Long/Extended test.
• There is a chance that during the Long test, you may be offered the opportunity to attempt repairs on the hard drive:
  If so, go ahead and attempt to do so, but ONLY after backing up all important personal files.
• Please let us know the results of the tests.

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

SEATOOLS ... if necessary.

Test the hard drive. It is best to use the hard drive manufacturer's own diagnostic utility, but Seagate's tool will work OK on most brands. The diagnostic tool is run from a bootable CD (Windows does not need to be working. The first two steps are done on a working computer, while the third step is to boot the ailing computer with the CD that you create in the first two steps.)

Please download SeaTools for DOS (CD) from Seagate's SeaTools for DOS web page

or use the following direct download link to download the latest version of SeaTools for DOS:
Download SeaTools for DOS ISO Image

The downloaded file name is SeaToolsDOS223ALL.ISO
[/list]
Burn the downloaded .ISO image to a CD using the appropriate burning software.

• If you do not already have a suitable burning program for writing .ISO images to disc ...
  
  • Download and install ImgBurn.
    Ensure that you UN-check the box agreeing to install the Ask toolbar during the installation.
  • Place a new (blank) CD disc in the drive tray.
  • Choose Write image file to disc.
    
  • Under Source, click on the Browse button: Navigate to and select the .ISO file that you wish to burn.
  • Place a check-mark in the box beside Verify.
• Click
  
  When the CD has been burned and verified as successful, it will be bootable.

Boot from the CD.

• (You may need to access the BIOS Setup Menu or the Boot Menu and change the boot order to enable booting from CD before hard drive.)
  
• From Basic tests on the Main Menu, run the Short test and then the Long test.
  
  (The long test will take some considerable time to complete.)
  The results will be shown as either a PASS or FAIL.
  There is a chance that during the Long test, you may be offered the opportunity to attempt repairs on the hard drive:
  
• If so, go ahead and attempt to do so, but ONLY after backing up all important personal files.

[/list]Note: You may wish to view the following ...

• Learn more about SeaTools for DOS. (view a 24 page pdf document)
• See the tutorial on the usage of SeaTools for DOS.

Please let us know the results of the tests.

It says, "Bad or missing command interpreter. Please enter a valid file name (e. g. C:\COMMAND.COM"

I booted from CD and both test PASSED.

Any suggestions?

The two Event logs previously collected by the jcgriff2 application are corrupt.

Please try saving the logs as text files:

• Start > Run and type eventvwr and press <ENTER>
• In the left pane, click on Application to highlight it.
• Go to Action > Save Log File As ...
• At the top beside Save in, choose a convenient location (the Desktop) to save the file.
• Beside File name, type in application for the name of the file.
• Beside Save as type, use the drop-down menu to select Text (Tab delimited)(*.txt)
• Click Save

Do the same for the System Event Log, naming the saved text file system.

At the Desktop, select both the text files that you have just created, zip them up and attach the .zip file to your reply:

• Click on one of the event log text files to select it.
• Hold down the <Ctrl> key, and click on the other file to select both files.
• Release the <Ctrl> key.
• Now, right-click on any one of the selected files > Send to ... > Compressed (zipped) Folder.
  The zip file will be located in the same place as the two event log text files.
• Attach the zip file to your next reply.
  When you click on Add Reply, you will see the facility to attach a file just below the box where you type your message.

Alright, before I do so.. I have one alternate question. When I get the blue screen error it says something like, "kernel_inpage" Could that deal with the hard drive also?

From the Speccy report:

MS Windows XP Home 32-bit SP3
Installation Date: 05 April 2012, 18:37

The Windows XP system has been installed very recently:

• What reason did you have for doing that?
• How was the re-installation performed?
• From the DELL factory restore partition or DELL installation disks?
• If you installed from a retail Microsoft XP installation CD, did you download and install all drivers for the motherboard from the DELL website?

From the Speccy report:

Hard Drives
WDC WD800JD-75JNA0
----------------
S.M.A.R.T
01 Read Error Rate: 200 (200 worst) Data 00000036D3
03 Spin-Up Time: 165 (164) Data 0000000A9C <<< 2716 milliseconds
04 Start/Stop Count: 100 (100) Data 000000032B
05 Reallocated Sectors Count: 199 (199) Data 0000000002
07 Seek Error Rate: 200 (200) Data 0000000000
09 Power-On Hours (POH): 040 (040) Data 000000ADF0
0A Spin Retry Count: 100 (100) Data 0000000000
0B Recalibration Retries: 100 (100) Data 0000000000
0C Device Power Cycle Count: 100 (100) Data 00000002F6
C2 Temperature: 095 (077) Data 0000000030
C4 Reallocation Event Count: 198 (198) Data 0000000002
C5 Current Pending Sector Count: 192 (150) Data 0000000070
C6 Uncorrectable Sector Count: 200 (171) Data 0000000000
C7 UltraDMA CRC Error Count: 200 (200) Data 000000001C
C8 Write Error Rate / Multi-Zone Error Rate: 200 (147) Data 0000000000
Temperature: 48 °C
Temperature Range: ok (less than 50 °C)
Status: Good

The S.M.A.R.T results don't look good to me, and suggest a likely problem with the hard drive.

WinDbg results on the minidumps confirm my above suspicion and indicate very strongly that there is a problem with the hard drive. If you take a look at the BSOD BUGCHECK SUMMARY below, I think that will answer your question "When I get the blue screen error it says something like, "kernel_inpage" Could that deal with the hard drive also?"

I am inclined to dismiss the result that you reported from running the WD diagnostic utility, and require confirmation of the hard drive's health using other diagnostic tools. Please test the hard drive with SeaTools, and let us know the result.

If you are able to provide the event logs in text file format that may help with diagnosis, but I fear that you will find the event logs to be corrupt when you attempt it.

Edit to add ...
We are dealing with an old DELL desktop PC (Dimension 4700 ?), with an 80 GB SATA HDD. It is possible that the "hard drive problem" is being caused by loose/poor contacts being made by the connectors on both/either end of the SATA data cable(s). Check the SATA data cable connections to devices (particularly the HDD) and to the motherboard. Un-plug them, and then re-connect them firmly and securely.
***Warning: Ensure all power is OFF, and that you ground yourself to the bare metal of the box before touching any electronic component in the box!***

=======================
BSOD BUGCHECK SUMMARY: 6 recent minidumps available
................................................................
Loading Dump File [C:\CactusIsland\athboyy_BC\TSF_XP_Support\Mini040712-01.dmp]
Built by: 2600.xpsp_sp3_gdr.100216-1514
Debug session time: Sun Apr 8 07:50:02.062 2012 (UTC + 10:00)
System Uptime: 0 days 1:45:09.613
Probably caused by : Unknown_Image ( ANALYSIS_INCONCLUSIVE )
KERNEL_DATA_INPAGE_ERROR (7a)
The requested page of kernel data could not be read in. Typically caused by
a bad block in the paging file or disk controller error. Also see
KERNEL_STACK_INPAGE_ERROR.
If the error status is 0xC000000E, 0xC000009C, 0xC000009D or 0xC0000185,
it means the disk subsystem has experienced a failure.
If the error status is 0xC000009A, then it means the request failed because
a filesystem failed to make forward progress.
ERROR_CODE: (NTSTATUS) 0xc000009c - STATUS_DEVICE_DATA_ERROR
DISK_HARDWARE_ERROR: There was error with disk hardware
BUGCHECK_STR: 0x7a_c000009c
DEFAULT_BUCKET_ID: DRIVER_FAULT
BUCKET_ID: BAD_STACK
Bugcheck code 0000007A
Arguments c03e2838 c000009c f8a0ed8a 1ed69860
................................................................
Loading Dump File [C:\CactusIsland\athboyy_BC\TSF_XP_Support\Mini040512-01.dmp]
Built by: 2600.xpsp_sp2_gdr.100216-1441
Debug session time: Fri Apr 6 12:06:31.463 2012 (UTC + 10:00)
System Uptime: 0 days 1:09:05.435
Probably caused by : memory_corruption ( nt!MiWaitForInPageComplete+1c5 )
KERNEL_DATA_INPAGE_ERROR (7a)
The requested page of kernel data could not be read in. Typically caused by
a bad block in the paging file or disk controller error. Also see
KERNEL_STACK_INPAGE_ERROR.
If the error status is 0xC000000E, 0xC000009C, 0xC000009D or 0xC0000185,
it means the disk subsystem has experienced a failure.
If the error status is 0xC000009A, then it means the request failed because
a filesystem failed to make forward progress.
ERROR_CODE: (NTSTATUS) 0xc000009c - STATUS_DEVICE_DATA_ERROR
DISK_HARDWARE_ERROR: There was error with disk hardware
BUGCHECK_STR: 0x7a_c000009c
DEFAULT_BUCKET_ID: DRIVER_FAULT
FAILURE_BUCKET_ID: 0x7a_c000009c_nt!MiWaitForInPageComplete+1c5
Bugcheck code 0000007A
Arguments c038a45c c000009c e2917000 097eb880
................................................................
Loading Dump File [C:\CactusIsland\athboyy_BC\TSF_XP_Support\Mini040312-01.dmp]
Built by: 2600.xpsp_sp3_gdr.100216-1514
Debug session time: Tue Apr 3 17:05:29.328 2012 (UTC + 10:00)
System Uptime: 0 days 3:07:43.884
Probably caused by : memory_corruption ( nt!MiMakeOutswappedPageResident+362 )
KERNEL_STACK_INPAGE_ERROR (77)
The requested page of kernel data could not be read in. Caused by
bad block in paging file or disk controller error.
In the case when the first arguments is 0 or 1, the stack signature
in the kernel stack was not found. Again, bad hardware.
An I/O status of c000009c (STATUS_DEVICE_DATA_ERROR) or
C000016AL (STATUS_DISK_OPERATION_FAILED) normally indicates
the data could not be read from the disk due to a bad
block. Upon reboot autocheck will run and attempt to map out the bad
sector.
ERROR_CODE: (NTSTATUS) 0xc000009c - STATUS_DEVICE_DATA_ERROR
DISK_HARDWARE_ERROR: There was error with disk hardware
BUGCHECK_STR: 0x77_c000009c
DEFAULT_BUCKET_ID: DRIVER_FAULT
PROCESS_NAME: System
FAILURE_BUCKET_ID: 0x77_c000009c_nt!MiMakeOutswappedPageResident+362
Bugcheck code 00000077
Arguments c000009c c000009c 00000000 00d8b000
BiosVersion = A10
BiosReleaseDate = 01/04/2006
SystemManufacturer = Dell Inc.
SystemProductName = Dimension 4700
CPUID: " Intel® Pentium® 4 CPU 2.80GHz"
MaxSpeed: 2800
CurrentSpeed: 2793
................................................................
Loading Dump File [C:\CactusIsland\athboyy_BC\TSF_XP_Support\Mini040212-02.dmp]
Built by: 2600.xpsp_sp3_gdr.100216-1514
Debug session time: Tue Apr 3 07:23:12.609 2012 (UTC + 10:00)
System Uptime: 0 days 2:31:03.168
Probably caused by : CLASSPNP.SYS ( CLASSPNP!ClassPnpQueryFdoRelations+36 )
KERNEL_DATA_INPAGE_ERROR (7a)
The requested page of kernel data could not be read in. Typically caused by
a bad block in the paging file or disk controller error. Also see
KERNEL_STACK_INPAGE_ERROR.
If the error status is 0xC000000E, 0xC000009C, 0xC000009D or 0xC0000185,
it means the disk subsystem has experienced a failure.
ERROR_CODE: (NTSTATUS) 0xc000009c - STATUS_DEVICE_DATA_ERROR
DISK_HARDWARE_ERROR: There was error with disk hardware
BUGCHECK_STR: 0x7a_c000009c
DEFAULT_BUCKET_ID: DRIVER_FAULT
PROCESS_NAME: System
WARNING: SystemResourcesList->Flink chain invalid. Resource may be corrupted, or already deleted.
WARNING: SystemResourcesList->Blink chain invalid. Resource may be corrupted, or already deleted.
FAILURE_BUCKET_ID: 0x7a_c000009c_CLASSPNP!ClassPnpQueryFdoRelations+36
Bugcheck code 0000007A
Arguments c03e1de4 c000009c f87796f2 1c4dc860
................................................................
Loading Dump File [C:\CactusIsland\athboyy_BC\TSF_XP_Support\Mini040212-01.dmp]
Built by: 2600.xpsp_sp2_gdr.100216-1441
Debug session time: Sun Apr 1 19:10:32.781 2012 (UTC + 10:00)
System Uptime: 0 days 4:38:10.339
Probably caused by : memory_corruption ( nt!MiMakeOutswappedPageResident+362 )
KERNEL_STACK_INPAGE_ERROR (77)
The requested page of kernel data could not be read in. Caused by
bad block in paging file or disk controller error.
In the case when the first arguments is 0 or 1, the stack signature
in the kernel stack was not found. Again, bad hardware.
An I/O status of c000009c (STATUS_DEVICE_DATA_ERROR) or
C000016AL (STATUS_DISK_OPERATION_FAILED) normally indicates
the data could not be read from the disk due to a bad
block. Upon reboot autocheck will run and attempt to map out the bad
sector.
ERROR_CODE: (NTSTATUS) 0xc000009c - STATUS_DEVICE_DATA_ERROR
DISK_HARDWARE_ERROR: There was error with disk hardware
BUGCHECK_STR: 0x77_c000009c
DEFAULT_BUCKET_ID: DRIVER_FAULT
PROCESS_NAME: System
FAILURE_BUCKET_ID: 0x77_c000009c_nt!MiMakeOutswappedPageResident+362
Bugcheck code 00000077
Arguments c000009c c000009c 00000000 006f8000
................................................................
Loading Dump File [C:\CactusIsland\athboyy_BC\TSF_XP_Support\Mini033112-01.dmp]
Built by: 2600.xpsp1.020828-1920
Debug session time: Sun Apr 1 12:05:09.218 2012 (UTC + 10:00)
System Uptime: 0 days 4:32:44.685
Probably caused by : memory_corruption ( nt!MiMakeOutswappedPageResident+363 )
KERNEL_STACK_INPAGE_ERROR (77)
The requested page of kernel data could not be read in. Caused by
bad block in paging file or disk controller error.
In the case when the first arguments is 0 or 1, the stack signature
in the kernel stack was not found. Again, bad hardware.
An I/O status of c000009c (STATUS_DEVICE_DATA_ERROR) or
C000016AL (STATUS_DISK_OPERATION_FAILED) normally indicates
the data could not be read from the disk due to a bad
block. Upon reboot autocheck will run and attempt to map out the bad
sector.
ERROR_CODE: (NTSTATUS) 0xc000009c - STATUS_DEVICE_DATA_ERROR
DISK_HARDWARE_ERROR: There was error with disk hardware
BUGCHECK_STR: 0x77_c000009c
DEFAULT_BUCKET_ID: DRIVER_FAULT
PROCESS_NAME: System
FAILURE_BUCKET_ID: 0x77_c000009c_nt!MiMakeOutswappedPageResident+363
Bugcheck code 00000077
Arguments c000009c c000009c 00000000 05611000
................................................................

1. I kept getting the blue screen error. PC running slow!

2. I reformatted.

3. Dell installation disks.

4. I installed all the drivers I could find. Some wasn't compatible.

From the SYSTEM event log:

4/8/2012 1:19:32 PM Disk Error None 7 N/A SHANE The device, \Device\Harddisk0\D, has a bad block.

4/8/2012 12:15:53 AM Disk Error None 7 N/A SHANE The device, \Device\Harddisk0\D, has a bad block.

Again, the finger is being pointed at a problem with the hard drive.

So how can I resolve this problem?

I ran both test with both tools.

Here's the log file (I think)
http://limelinx.com/files/a3c40942dc2fe8253ac93aa805acf34c

Pic shows the SeaTools utility window, with the Short test having been run ... and PASSED.

Did you also run the Long test? Did that PASS or FAIL ?

Yes, I ran the long test with both tools. All PASSED.