The Notebook Review forums were hosted by TechTarget, who shut down them down on January 31, 2022. This static read-only archive was pulled by NBR forum users between January 20 and January 31, 2022, in an effort to make sure that the valuable technical information that had been posted on the forums is preserved. For current discussions, many NBR forum users moved over to NotebookTalk.net after the shutdown.
Problems? See this thread at archive.org.

    Windows 7 x64 BSOD from multiple causes

    Discussion in 'Windows OS and Software' started by Bog, Jan 23, 2011.

  1. Bog

    Bog Losing it...

    Reputations:
    4,018
    Messages:
    6,046
    Likes Received:
    7
    Trophy Points:
    206
    Hi everybody,

    I've been having some problems with my desktop PC, but given that this is a Windows problem and I've been struggling to resolve the issue, I really am at the end of my rope.

    HARDWARE:
    please see my signature for specs (see attached pic for details).

    HISTORY:
    The machine started to BSOD frequently when I upgraded the RAM from 2x1GB DDR2 667MHz by OCZ to a 2x2GB kit by the same maker. This upgrade was RMAed for new 2x2GB modules that have passed numerous Windows memory diagnostics. Still, the BSODs have persisted, often when left on overnight and when gaming.

    TESTS:
    I've approached this problem as systemically as possible, but I've run out of ideas and haven't really narrowed the results. Here's what I've done:

    a - updated video drivers, BIOS, motherboard drivers to the latest

    b - run CHKDSK on filesystem (passed)

    c - run Western Digital LifeGuard Diagnostic for HDD (passed)

    d - run memory diagnostics provided with Windows (passed)

    e - tried running System Repair w/ Windows 7 install DVD (nothing to repair)

    f - uninstalled Symantec EndPoint Protection 10.2 and replaced with less invasive, simpler AV (Microsoft Security Essentials).

    g - I've used BlueScreenView to look at the dump files (see attached JPEG)

    RESULTS:
    Interestingly, uninstalling SEP (f) seems to have decreased the number of BSODs, but this is highly subjective. I really can't be sure, since the drivers responsible for the bluescreens are all over the map. At this point, the general nature of the BSODs has led me to believe that there is a problem with the motherboard or the PSU.

    Please take a look and let me know what you think. Thanks,

    Bog

    UPDATE 1: I just went into the BIOS and bumped the RAM speed down from 800MHz to 667MHz. The motherboard is very cheap and can't deal with the slightest overclock, so I'm hoping that this may improve stability. Such a problem would still allow the RAM to pass diagnostic tests, I think.
     

    Attached Files:

  2. newsposter

    newsposter Notebook Virtuoso

    Reputations:
    801
    Messages:
    3,881
    Likes Received:
    0
    Trophy Points:
    105
    what other overclocking are you doing?
     
  3. Astrogiblet

    Astrogiblet Notebook Evangelist

    Reputations:
    255
    Messages:
    422
    Likes Received:
    1
    Trophy Points:
    31
    The memory diagnostic within Windows is just terrible. Run Memtest to get a real idea of whether or not your RAM is bad. Let it complete one full pass and if it comes back with no errors than your RAM is fine. That will at least rule out that being part of your problem.

    Since each time your BSOD is completely different, I'd say the most likely causes would be either RAM or Motherboard.
     
  4. Bog

    Bog Losing it...

    Reputations:
    4,018
    Messages:
    6,046
    Likes Received:
    7
    Trophy Points:
    206
    I used to overclock the CPU from 2.66 to 3.0 on air, but the motherboard is just not robust enough to handle a higher FSB. I bought this desktop from a friend, and it was never built for intensive purposes so the MB was chosen for cost-saving.

    Thanks, I will run memtest and update this thread either tonight or tomorrow morning.
     
  5. sama98b

    sama98b Notebook Evangelist

    Reputations:
    40
    Messages:
    435
    Likes Received:
    0
    Trophy Points:
    30
    Not just the clock speed .. change the timing to lower too .. check what is the lowest it can run.

    Had same problem in my desktop.
     
  6. Bog

    Bog Losing it...

    Reputations:
    4,018
    Messages:
    6,046
    Likes Received:
    7
    Trophy Points:
    206
    Just an update:
    The RAM passed the extended tests recommended by Astrogiblet, but I haven't seen any blue screens since setting the BIOS to keep the RAM at 667MHz. I don't want to speak too soon, but maybe this is what crashed the system; the explanation is consistent with everything else so far.

    Also, the BIOS doesn't allow me to mess with the timings.
     
  7. maximinimaus

    maximinimaus Notebook Evangelist

    Reputations:
    468
    Messages:
    635
    Likes Received:
    0
    Trophy Points:
    30
    The screenshot of your system shows 4 x 2GB RAM installed!? I assume you added 2 x 2GB to a existing pair. If so, are your sure that the memory timings of the different pairs match?
    I experienced similar BSODs after installing so called "high density" RAM in a desktop. After replacing it with "low density" RAM the BSODs didn't appear anymore. I believe Intel chipset work best with "low density" RAM.
     
  8. usapatriot

    usapatriot Notebook Nobel Laureate

    Reputations:
    3,266
    Messages:
    7,360
    Likes Received:
    14
    Trophy Points:
    206
    First step is to reset all your hardware overclock settings back to stock and see if you run into any problems. Then begin isolating whether it is the CPU, RAM or something else.

    Previously stable overclocks can become unstable over time and may need adjustments to remain stable.
     
  9. Astrogiblet

    Astrogiblet Notebook Evangelist

    Reputations:
    255
    Messages:
    422
    Likes Received:
    1
    Trophy Points:
    31
    I agree with Patriot. Do a full reset on your BIOS to defaults. Then go back through and set everything to normal/non-OC settings (BIOS doesn't always auto detect hardware properly). See if that fixes your problems.
     
  10. Bog

    Bog Losing it...

    Reputations:
    4,018
    Messages:
    6,046
    Likes Received:
    7
    Trophy Points:
    206
    Thanks for the suggestions guys, I've got the BIOS back to default values. I've also forced the RAM clocks to 667 rather than 800 in order improve stability. However, I don't have access to RAM timings in the BIOS settings, but I'm almost sure this problem was caused by the RAM frequency.

    I'll update this thread if the system continues crashing.
     
  11. Bog

    Bog Losing it...

    Reputations:
    4,018
    Messages:
    6,046
    Likes Received:
    7
    Trophy Points:
    206
    Just a final post to confirm that the problem was resolved: the BSODs were indeed caused by the inexpensive motherboard, which could not handle RAM speeds of 800MHz. The RAM had to be manually set to 667MHz in order to maintain system stability. There haven't been any BSODs since making this change in the BIOS.