UNSOLVED

Lester67

updated

17 years ago

L

Lester67

97 Posts

0

6976

January 29th, 2010 05:00

Weird hardware issue with WS490 / O760

The issue I'm working now is currently on a WS490 (Bios A08, Quadro 3500).  However, the same problem appeared on an Optiplex 760 (Bios A05, Desktop Chassis, Integrated video).

(Keep in mind I just said "a" and "an", out of numerous systems these two are specific problem children)

Both systems load Windows XP just fine.

Both systems load Vista64 with no issues.

Attempting an upgrade or a clean install of Win7 64-bit nets the following error: "The computer restarted unexpectedly or encountered an unexpected error. Windows installation cannot proceed. To install Windows, click "OK" to restart the computer, and then restart the installation."

This is system 1 of 7 for the WS490, the other 6 upgraded fine (Identical).  System 1 of about 100 for the 760, all the same specs.  It's just these two specific systems that are having the problem.

Dell Diags return zero errors.  Dell and MS memory tests are clean.  RAM and HDD were swapped out.  Since WPD won't give me a motherboard and CPU replacement, I'm looking for some guidance on what I might do to track down the specific problem.

Normal 0 false false false EN-US X-NONE X-NONE MicrosoftInternetExplorer4

  • Lester67

    97 Posts

    240

    0

    Posted January 29th, 2010 07:00

    Dear Moderators,

    My post has now been moved twice.  Even though it is obviously a hardware issue, I will accept that you think it should be under Operating Systems.

    It has now been moved to "Video".  If the person that has decided that it is video could go ahead and post *WHY* they think it's video, I'd appreciate it.

    (For the record, it is not video.  I'm building on a different WS490 using the video card from the old system, and it works just fine.)

    In short, if you can leave this in one place for people to find it, that would be very helpful.

    Thanks.

  • Lester67

    97 Posts

    240

    0

    Posted February 3rd, 2010 05:00

    Since I couldn't find a solution, I targeted the motherboard first and that corrected the issue.