also @ TechSpot: iTunes 11.0.3 delivers revamped MiniPlayer, security fixes

Blue screen, doing physical memory dump

Discussion in 'Windows BSOD, Freezing, Restarting Help' started by Kemikal, Oct 3, 2011.

Post New Reply
  1. Kemikal Newcomer, in training

    Allright, so my computer is either randomly restarting, blue screening or just simply freezes.

    Every time when the blue screen occurs it does a physical memory dump.

    Memtest didn't find anything from my old memory sticks which were Corsair 1333 Mhz
    2048mb ddr3

    Either way, I decided to replace them just in case to try out with equivalents from OCZ.
    This didn't help.
    It still does the same thing as frequently as before.

    I've reinstalled windows, that didn't help.
    I've reinstalled all of the drivers twice, that didn't help.

    Currently testing to run the computer without my gfx card. (Gigabyte nvidia Geforce gtx 460, overclocked version)
    Updating the thread as getting results.

    I would post 3 minidump files as well if those help in solving the problem, but the file size exceeds the limit for uploading.
    I'm all ears for suggestions.

    Thank you in advance for your help.


    Here's the specs of my computer:

    Motherboard: M4A89GTD PRO/USB3, AM3, AMD890GX, SATA 6Gbps, DDR3, VGA, DVI/VGA/HDMI, ATX, Core Uncloker
    Processor: AMD Phenom II X6 1055T Processor 2.8 GHz
    Gfx card (as above): Gigabyte nvidia geforce gtx 460 overclock
    Hard drive: Western digital caviar blue 500gb SATA II
  2. Tmagic650 TS Ambassador Posts: 18,724   +62

    So you are running the computer on it's on-board graphics, with no BSOD's so far?
  3. Kemikal Newcomer, in training

    I just had a BSOD without having the gfx card plugged.

    Completely out of ideas what it could be.

    I could send the minidump files to someone's e-mail if that specific person wants to have a closer look.
  4. Tmagic650 TS Ambassador Posts: 18,724   +62

    I think you can still attach some minidumps without having many posts. No need to email them
  5. Kemikal Newcomer, in training

    Here are the minidump files, 2 from monday and 2 from yesterday.
    I had to zip them up to attach them.

    Attached Files:

  6. Route44 TechSpot Ambassador Posts: 12,022   +18

    Guys F.Y.I. - the error codes are 0x1E, 0xC2, and 0x7E with the fourth dump unreadable.

    Y - nothing specific was cited, just Windows OS drivers.

    * Possible wrong memory voltage settings in the BIOS?
     
  7. Kemikal Newcomer, in training

    How can i check the memory voltage settings?
    What should they look like?

    Thank you for your time.
  8. Route44 TechSpot Ambassador Posts: 12,022   +18

    Your memory manufacture will will tell you what your memory's voltage specs.

    Your BIOS will tell you what the motherboard has it set at. You need to look for VDIMM Voltage.
  9. Kemikal Newcomer, in training

    I'm not too familiar yet with the bios page.
    Any idea which category it should be at?
  10. Tmagic650 TS Ambassador Posts: 18,724   +62

    Maybe CPU settings
  11. Kemikal Newcomer, in training

    I checked bios and apparently the dram frequency was set wrong, instead of 1333 MHz it was 986 MHz or something rather which was completely wrong.

    It's running fine at the moment, the voltage of the memories were fine (1.5 as it should be)

    I will update if anything goes wrong.
  12. Tmagic650 TS Ambassador Posts: 18,724   +62

    Yes 1.5 volts is nominal for 1333MHz DDR3 memory... Happy computing!
  13. Kemikal Newcomer, in training

    The problem persisted.

    Here's some details from the BSOD.


    Problem signature:
    Problem Event Name: BlueScreen
    OS Version: 6.1.7600.2.0.0.256.48
    Locale ID: 1035

    Additional information about the problem:
    BCCode: c2
    BCP1: 0000000000000007
    BCP2: 0000000000001097
    BCP3: 0000000000000000
    BCP4: FFFFF900C078CE40
    OS Version: 6_1_7600
    Service Pack: 0_0
    Product: 256_1

    Also attached the minidump files.

    Memory frequencies and voltages are fine, could this be a motherboard issue?

    Attached Files: