MMM
Results 1 to 25 of 8487

Thread: ASUS P5W DH - Problems + Fixes Thread

Hybrid View

  1. #1
    Xtreme Member
    Join Date
    Aug 2006
    Location
    Montreal, Canada
    Posts
    132
    Quote Originally Posted by DarthVader
    On an entirely different matter (although concerning the Asus P5W DH Deluxe post v1301 BIOS) I have noticed something odd about the motherboard. I should point out this was happening before I even started my overclocking attempts. It was happening with v1301 and continues with v1305. If one saves changes in the BIOS and exits then the computer powers off for a moment but then restarts itself as normal. Secondly the same thing happens if I restart (obviously using the restart button) in Windows XP Pro x64. Is this normal?

    I am currently using v1305 of the BIOS.
    That's normal behavior when the systen is overclocked, but you're the first person I have seen experiencing that at stock. Maybe, it's something to do with XP64. Have you tried resetting BIOS to default setting and rebooting?

    -phil
    Intel Core 2 Duo E6600 (week 24 A - lapped) 2.4GHz @ 3GHz (vcore 1.35)
    ASUS P5W DH Deluxe 1901 (66MOAG/G0AAY)
    Noctua NH-U 12 w/ 2 X Coolermaster 120x120mm
    OCZ Platinum XTC PC2-6400 2X1GB - 4-5-4-15 (OCZ2P8002GK)
    OCZ ModStream 450w
    BFG nVidia GeForce 8800 GTS (320MB)
    WD Raptor 74GB
    SB X-Fi XtremeMusic

  2. #2
    Registered User
    Join Date
    Aug 2006
    Posts
    62
    Quote Originally Posted by phile
    That's normal behavior when the systen is overclocked, but you're the first person I have seen experiencing that at stock. Maybe, it's something to do with XP64. Have you tried resetting BIOS to default setting and rebooting?

    -phil
    Na I doubt it is x64 that is causing it because it does it when leaving the BIOS too. However, it did start doing this before I began overclocking when I flashed it to 1301. Although in saying that I obviously had the memory set to DDR2-800 and 4-4-4-12 at that point anyway.

    I presume this switching off won't cause any damage?

    EDIT - I did get this response in another forum though (apparently from the Asus techies):

    This behaviour is caused by system's limitation. For over-clocking, the
    internal PLL of NB would not lock on the high clock right away, so that means
    system could not hold on the clock frequency immediately after reset. That's
    why we add a auto-power down scheme to fix this issue. Of course, this
    behaviour only occurs at over-clocking scenario.
    Last edited by DarthVader; 08-30-2006 at 04:59 AM.

Tags for this Thread

Bookmarks

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
  •