W2k reboots whenever disk io increases
Results 1 to 5 of 5

Thread: W2k reboots whenever disk io increases

  1. #1
    Registered User storm's Avatar
    Join Date
    Apr 1999
    Location
    fredericksburg, va, usa
    Posts
    322

    Post W2k reboots whenever disk io increases

    the facts:

    W2K sp1
    tyan s1590 MB with via chipset and udma33 support
    amd k6-2 500mhtz w/3d now
    maxtor 20 gig udma66 hd

    the system randomly reboots and does a sysdump with the following error messages in the event log: event id 11; the driver detected a controller error on \device\harddisk0\DRO and event id 5; A parity error was detected on \device\ide\ideport0

    the knowledge base said this had to do with the MB only supporting udma33 and the hd was udma66. the fix was to change the settings in device manager for the ide controller from DMA to pio which i did. that didn't work

    in the bios i changed the dma settings to 3 and 4 and also disabled udma and that didn't work. (each was done one at a time)

    i changed the HD data cable to a standard HD data cable and that didn't work.

    i could use a few more options if anyone is willing to kick a few cents in...thanks..

    storm.........

    [This message has been edited by storm (edited August 17, 2000).]

    [This message has been edited by storm (edited August 17, 2000).]
    "no eternal reward will forgive us now for wasting the dawn"

  2. #2
    Registered User
    Join Date
    Nov 1998
    Location
    La Baie Quebec Canada
    Posts
    545

    Smile

    hi try a new power supply,

  3. #3
    Registered User
    Join Date
    Jan 2000
    Location
    Edmonton
    Posts
    152

    Post

    Run Scandisk, hada system taht would just up and reboot, problem was taht it had got a spike and created 2 FATS but could only update 1 ata time, so one was always wrong, so it rebooted when the data could not be found in that location due to conflict.

  4. #4
    PaulD
    Guest

    Post

    Rejection man...that was a "too cool" answer.
    I have to remember that on...I think I may have seen this one before but with Win98. The area gets alot of lightning strikes so that could've been the answer.Although scandisk did not find it.

  5. #5
    Registered User storm's Avatar
    Join Date
    Apr 1999
    Location
    fredericksburg, va, usa
    Posts
    322

    Post

    got the problem fixed and wanted to update the thread for future use:

    bottom line, it was the motherboard.

    i dissected all the bug check hex dumps ( you can actually run the hex number through the knowledge base and an article associated with that particular dump will explain possible causes)

    and they all pointed towards the MoBo.

    i change out the tyan s1590 with an epox (sorry don't have the model hndy at this time) and all is right with world.

    thanks for all the responses...

    storm..

Bookmarks

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •