Jump to content

Welcome to Geeks to Go - Register now for FREE

Geeks To Go is a helpful hub, where thousands of volunteer geeks quickly serve friendly answers and support. Check out the forums and get free advice from the experts. Register now to gain access to all of our features, it's FREE and only takes one minute. Once registered and logged in, you will be able to create topics, post replies to existing threads, give reputation to your fellow members, get your own private messenger, post status updates, manage your profile and so much more.

Create Account How it Works
Photo

Problem, that is aggravating


  • Please log in to reply

#1
cyrawhite

cyrawhite

    Member

  • Member
  • PipPip
  • 96 posts
I have a Compaq Presario, OS is XP, which has a new hard drive installed. I just got the computer back from my mom, and it's acting a fool.
Sometimes when I'm on it, it cuts off and reloads, then it says "disk read error. Pres CTRL ALT DELETE to restart, but it never does anything. I'm getting really aggravated with it, considering the new hard drive we just had installed. If anyone knows what might be wrong, please let me know Thanks.
Cyra
  • 0

Advertisements


#2
rshaffer61

rshaffer61

    Moderator

  • Moderator
  • 34,114 posts
Are you able to get into windows?
If so please do the following in order and reply back with results from each as they complete.

Download WhoCrashed from the link in my signature below
This program checks for any drivers which may have been causing your computer to crash....

Click on the file you just downloaded and run it.
Put a tick in Accept then click on Next
Put a tick in the Don't create a start menu folder then click Next
Put a tick in Create a Desktop Icon then click on Install and make sure there is a tick in Launch Whocrashed before clicking Finish
Click Analyze
It will want to download the Debugger and install it Say Yes

WhoCrashed will create report but you have to scroll down to see it
Copy and paste it into your next reply

Go to
Start and then to Run
Type in Chkdsk /r Note the space between k and /
Click Enter ...It will probably ask if you want to do this on the next reboot...click Y

If the window doesn't shutdown on its own then reboot the system manually. On reboot the system will start the chkdsk operation
This one will take longer then chkdsk /f

Note... there are 5 stages...
It may appear to hang at a certain percent for a hour or more or even back up and go over the same area...this is normal...
DO NOT SHUT YOUR COMPUTER DOWN WHILE CHKDSK IS RUNNING OR YOU CAN HAVE SEVERE PROBLEMS
This can take several hours to complete.
When completed it will boot the system back into windows.

Let me know if this fixes the problem
  • 0

#3
rev_olie

rev_olie

    Member

  • Member
  • PipPipPip
  • 532 posts

Sometimes when I'm on it, it cuts off and reloads, then it says "disk read error.


Sorry if im wrong but would it be a possible risk to run check disk if that is likely to happen during the test?
  • 0

#4
cyrawhite

cyrawhite

    Member

  • Topic Starter
  • Member
  • PipPip
  • 96 posts
Here is the report from Whocrashed. I'm doing the other steps also. I will let you know what happens. Thanks

Crash dump directory: C:\WINDOWS\Minidump

Crash dumps are enabled on your computer.


On Thu 7/23/2009 4:21:07 PM your computer crashed
This was likely caused by the following module: ntoskrnl.exe
Bugcheck code: 0x77 (0xC0000185, 0xC0000185, 0x0, 0xC1F2000)
Error: KERNEL_STACK_INPAGE_ERROR
file path: C:\WINDOWS\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
The crash took place in a standard Microsoft module. Likely the culprit is another driver on your system which cannot be identified.



On Thu 7/23/2009 1:41:44 AM your computer crashed
This was likely caused by the following module: win32k.sys
Bugcheck code: 0x7A (0xE19466B8, 0xC0000185, 0xBF8CEBFC, 0xACD9860)
Error: KERNEL_DATA_INPAGE_ERROR
file path: C:\WINDOWS\system32\win32k.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Multi-User Win32 Driver
The crash took place in a standard Microsoft module. Likely the culprit is another driver on your system which cannot be identified.



On Thu 7/16/2009 8:18:17 PM your computer crashed
This was likely caused by the following module: ntoskrnl.exe
Bugcheck code: 0x77 (0xC0000185, 0xC0000185, 0x0, 0x9318000)
Error: KERNEL_STACK_INPAGE_ERROR
file path: C:\WINDOWS\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
The crash took place in a standard Microsoft module. Likely the culprit is another driver on your system which cannot be identified.



On Sat 7/4/2009 1:06:13 AM your computer crashed
This was likely caused by the following module: win32k.sys
Bugcheck code: 0x7A (0xC070B498, 0xC0000185, 0xE1693004, 0x89628C0)
Error: KERNEL_DATA_INPAGE_ERROR
file path: C:\WINDOWS\system32\win32k.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Multi-User Win32 Driver
The crash took place in a standard Microsoft module. Likely the culprit is another driver on your system which cannot be identified.



On Thu 6/18/2009 12:41:34 AM your computer crashed
This was likely caused by the following module: ati2mtag.sys
Bugcheck code: 0x1000007F (0x8, 0x80042000, 0x0, 0x0)
Error: UNEXPECTED_KERNEL_MODE_TRAP_M
file path: C:\WINDOWS\system32\drivers\ati2mtag.sys
product: ATI Radeon WindowsNT Miniport Driver
company: ATI Technologies Inc.
description: ATI Radeon WindowsNT Miniport Driver



On Mon 6/15/2009 12:52:45 PM your computer crashed
This was likely caused by the following module: sr.sys
Bugcheck code: 0x7A (0xC07BA120, 0xC0000185, 0xF74249DC, 0x11D0A860)
Error: KERNEL_DATA_INPAGE_ERROR
file path: C:\WINDOWS\system32\drivers\sr.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: System Restore Filesystem Filter Driver
The crash took place in a standard Microsoft module. Likely the culprit is another driver on your system which cannot be identified.



On Sun 6/14/2009 6:17:55 PM your computer crashed
This was likely caused by the following module: csrss.exe
Bugcheck code: 0xF4 (0x3, 0x8432CAE8, 0x8432CC5C, 0x805C8C88)
Error: CRITICAL_OBJECT_TERMINATION
file path: C:\WINDOWS\system32\csrss.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Client Server Runtime Process
The crash took place in a standard Microsoft module. Likely the culprit is another driver on your system which cannot be identified.



On Fri 6/12/2009 4:10:22 PM your computer crashed
This was likely caused by the following module: ntoskrnl.exe
Bugcheck code: 0x7A (0xC07BA128, 0xC000000E, 0xF7425016, 0x163DF860)
Error: KERNEL_DATA_INPAGE_ERROR
file path: C:\WINDOWS\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
The crash took place in a standard Microsoft module. Likely the culprit is another driver on your system which cannot be identified.



On Sun 6/7/2009 4:41:12 AM your computer crashed
This was likely caused by the following module: ati2mtag.sys
Bugcheck code: 0x1000007F (0x8, 0x80042000, 0x0, 0x0)
Error: UNEXPECTED_KERNEL_MODE_TRAP_M
file path: C:\WINDOWS\system32\drivers\ati2mtag.sys
product: ATI Radeon WindowsNT Miniport Driver
company: ATI Technologies Inc.
description: ATI Radeon WindowsNT Miniport Driver



On Wed 6/3/2009 7:23:05 PM your computer crashed
This was likely caused by the following module: ati2mtag.sys
Bugcheck code: 0x1000007F (0x8, 0x80042000, 0x0, 0x0)
Error: UNEXPECTED_KERNEL_MODE_TRAP_M
file path: C:\WINDOWS\system32\drivers\ati2mtag.sys
product: ATI Radeon WindowsNT Miniport Driver
company: ATI Technologies Inc.
description: ATI Radeon WindowsNT Miniport Driver



On Tue 5/26/2009 11:19:24 PM your computer crashed
This was likely caused by the following module: sr.sys
Bugcheck code: 0x7A (0xC07BA120, 0xC0000185, 0xF74249DC, 0xCCCF860)
Error: KERNEL_DATA_INPAGE_ERROR
file path: C:\WINDOWS\system32\drivers\sr.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: System Restore Filesystem Filter Driver
The crash took place in a standard Microsoft module. Likely the culprit is another driver on your system which cannot be identified.



On Tue 4/28/2009 10:55:57 PM your computer crashed
This was likely caused by the following module: csrss.exe
Bugcheck code: 0xF4 (0x3, 0x843A4770, 0x843A48E4, 0x805C8C88)
Error: CRITICAL_OBJECT_TERMINATION
file path: C:\WINDOWS\system32\csrss.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Client Server Runtime Process
The crash took place in a standard Microsoft module. Likely the culprit is another driver on your system which cannot be identified.



On Tue 4/21/2009 1:22:16 PM your computer crashed
This was likely caused by the following module: ntoskrnl.exe
Bugcheck code: 0x7A (0xC0601C40, 0xC0000185, 0xC0388D10, 0xA2DA884)
Error: KERNEL_DATA_INPAGE_ERROR
file path: C:\WINDOWS\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
The crash took place in a standard Microsoft module. Likely the culprit is another driver on your system which cannot be identified.



On Mon 4/20/2009 11:54:40 PM your computer crashed
This was likely caused by the following module: csrss.exe
Bugcheck code: 0xF4 (0x3, 0x84390490, 0x84390604, 0x805C8C88)
Error: CRITICAL_OBJECT_TERMINATION
file path: C:\WINDOWS\system32\csrss.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Client Server Runtime Process
The crash took place in a standard Microsoft module. Likely the culprit is another driver on your system which cannot be identified.



On Mon 4/20/2009 12:30:23 PM your computer crashed
This was likely caused by the following module: atapi.sys
Bugcheck code: 0x7A (0xC070A538, 0xC000000E, 0xE14A7000, 0x19B278C0)
Error: KERNEL_DATA_INPAGE_ERROR
file path: C:\WINDOWS\system32\drivers\atapi.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: IDE/ATAPI Port Driver
The crash took place in a standard Microsoft module. Likely the culprit is another driver on your system which cannot be identified.



On Sat 4/18/2009 9:05:13 PM your computer crashed
This was likely caused by the following module: win32k.sys
Bugcheck code: 0x7A (0xE1912C88, 0xC0000185, 0xBF9883A3, 0x15466860)
Error: KERNEL_DATA_INPAGE_ERROR
file path: C:\WINDOWS\system32\win32k.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Multi-User Win32 Driver
The crash took place in a standard Microsoft module. Likely the culprit is another driver on your system which cannot be identified.



On Fri 4/17/2009 1:23:26 AM your computer crashed
This was likely caused by the following module: pfc027.sys
Bugcheck code: 0x100000D0 (0x2626262A, 0x2, 0x1, 0x80542DE9)
Error: Unknown
file path: C:\WINDOWS\system32\drivers\pfc027.sys




--------------------------------------------------------------------------------
Conclusion
--------------------------------------------------------------------------------

17 crash dumps have been found and analyzed. Note that it's not always possible to state with certainty whether a reported driver is really responsible for crashing your system or that the root cause is in another module. Nonetheless it's suggested you look for updates for the products that these drivers belong to and regularly visit Windows update or enable automatic updates for Windows. In case a piece of malfunctioning hardware is causing trouble, a search with Google on the bug check errors together with the model name and brand of your computer may help you investigate this further.
  • 0

#5
rshaffer61

rshaffer61

    Moderator

  • Moderator
  • 34,114 posts
OS system has a problem from the log you supplied.
Can you boot into Safe Mode and see if the problem happens there?
If not we may have a driver issue as I also saw a entry for the ATI graphics card in the crash log.

You can try this to see in safe mode also but I suggest you go into safe mode for awhile and see if the system has the same issue first before we proceed.
  • 0

#6
cyrawhite

cyrawhite

    Member

  • Topic Starter
  • Member
  • PipPip
  • 96 posts
Check disk is complete, didn't take as long as I thought it would. All seems okay for the moment. I'm going to keep my computer of for awhile and get back on in about an hour, and see if anything is wrong. Thanks for the help
  • 0

#7
cyrawhite

cyrawhite

    Member

  • Topic Starter
  • Member
  • PipPip
  • 96 posts
Ugh, thought it was fixed, worked fine for awhile, then all of sudden it just started giving me the disk read error, and kept shutting down and cutting back on. I'm really aggravated with this computer
  • 0

#8
rshaffer61

rshaffer61

    Moderator

  • Moderator
  • 34,114 posts
Well it seems to have lasted about 3 weeks before it returned.
Rerun Chkdsk steps from post #2

If it finds errors and fixes them then rerun it again till it doens't find any.
After that then do the following.

Let's check your memory and make sure there is no issue with it. Download memtest86 from the link in my signature below.


Get the file that is named Download - The one you want is "Download - Pre-compiled Bootable ISO (.zip). When it downloads, it will be labeled memtest86+2.11.iso.zip
Unzip the file once you download it. You should have a .iso file in the unzipped directory. It will look like a zip file in some cases but the file name will now be memtest86+2.11.iso

if you don't have a burning program that will burn .ISO files get burncdcc in my signature below.

NOTE...do not put a blank cd in until burncdcc opens the tray for you
1. Start BurnCDCC
2. Browse to the ISO file you want to burn on cd/dvd ....in this case its memtest86.iso
3. Select the ISO file
4. click on Start

Make sure the bios is set for the cd drive as the first boot device
Put the cd in the cd drive and then boot your computer.

Running the Diagnostic Program:

The basic diagnostic screen has five main sections of relevant information. Three at the top which are labeled, PASS %, TEST %, and TEST #. This will basically show you the total progress of the current test, the overall progress of the diagnostic test, and the test number is currently performing.

On the middle left hand side of the of the program interface there is a “Wall Time” section that will keep track of how long the diagnostic test has been running for. This just gives you an idea if you are not attending the testing process.

The main section to look for is the lower half of the screen which is usually blank. As long as the memory testing is going ok with no errors this section of the screen should remain blank. If the diagnostic program finds any serious faults in the memory you will see it display a memory dump of address’s in this section. This is similar to what is displayed on your screen when you encounter a blue screen of death.

You now have most everything you need to know about setting up and testing your memory with diagnostic programs. This guide should help you get to the source of any intermittent problems related to your memory.


Run memtest for at least 2 hours
If it starts showing any errors during that time then you will have to replace the memory
If there are no errors after 2 hours press Esc and that will end the tests
We will then try other options
  • 0

#9
cyrawhite

cyrawhite

    Member

  • Topic Starter
  • Member
  • PipPip
  • 96 posts
Did everything, passed all tests with no errors. Earlier this morning when I decided to turn the computer on again, it said it needed to send an error report, well I sent it and it said that it seems to be a driver issue, had me run check disk, It had a lot of file record segments is unreadable. I've uninstalled what I knew was okay to do, but left the other stuff. Did a virus scan and found no virus.
  • 0

#10
Broni

Broni

    Kraków my love :)

  • Member
  • PipPipPipPipPipPipPipPip
  • 12,300 posts

it says "disk read error


Run hard drive diagnostics: http://www.tacktech....ay.cfm?ttid=287
Make sure, you select tool, which is appropriate for the brand of your hard drive.
Depending on the program, it'll create bootable floppy, or bootable CD.
If downloaded file is of .iso type, use ImgBurn: http://www.imgburn.com/ to burn .iso file to a CD (select "Write image file to disc" option), and make the CD bootable.

NOTE. If your hard drive is made by Toshiba, unfortunately, you're out of luck, because Toshiba doesn't provide any diagnostic tool.
  • 0






Similar Topics

0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users

As Featured On:

Microsoft Yahoo BBC MSN PC Magazine Washington Post HP