Windows Stop Error on 1st boot of each day

By jamison
Nov 11, 2007
Topic Status:
Not open for further replies.
  1. Hello,

    I built my system 3 days ago and I've been beating my head against the wall trying to get rid of this Stop Error:

    The odd thing is I only get it on the first boot of each day. After that my system is completely stable the rest of the day. It happens about 10 minutes after the first boot and doesn't seem to be related to what I'm doing at the time.

    Here's whats listed in the event viewer:

    Day 3:
    The computer has rebooted from a bugcheck. The bugcheck was: 0x1000008e (0xc0000005, 0x8054a10d, 0xb5592a64, 0x00000000). A dump was saved in: C:\WINDOWS\Minidump\Mini111107-01.dmp.

    Day 2:
    The computer has rebooted from a bugcheck. The bugcheck was: 0x100000d1 (0x132f8d60, 0x00000002, 0x00000001, 0xba609818). A dump was saved in: C:\WINDOWS\Minidump\Mini111007-01.dmp.

    Day 1:
    The computer has rebooted from a bugcheck. The bugcheck was: 0x10000050 (0xfa3085eb, 0x00000000, 0x805ef4c2, 0x00000000). A dump was saved in: C:\WINDOWS\Minidump\Mini110907-01.dmp.



    My system setup:
    Core 2 Duo E6750
    ASUS P5N-E SLI
    Corsair XMS2 Twin 2x2048-6400C4 (In black slots)
    (Timings: 4-4-4-12 cmd:2 tRC:22 tWTR:15 Memory Voltage: 2.085)
    FSB - Memory Clock mode set to unlinked.

    ASUS EN8500GT Video Card

    Could this still be a hardware issue even though my system is stable after the first reboot?
    Any help is greatly appreciated!

    I have also ran MemTest86+ with no errors. I also attached the 3 minidump files.

    Thanks!!!

    Attached Files:

  2. technicalfury42

    technicalfury42 Banned Posts: 109

    Review the Event Viewer and report back w/ any errors that seem pertinent or lead-up to the time of the crash.
  3. howard_hopkinso

    howard_hopkinso Newcomer, in training Posts: 25,948   +17

    Hello and welcome to Techspot.

    Your minidumps crash with avrious culprits and bugchecks, including memory corruption.

    MODULE_NAME: memory_corruption

    IMAGE_NAME: memory_corruption

    FOLLOWUP_NAME: memory_corruption

    DEBUG_FLR_IMAGE_TIMESTAMP: 0

    MEMORY_CORRUPTOR: LARGE_64

    STACK_COMMAND: kb

    FAILURE_BUCKET_ID: MEMORY_CORRUPTION_LARGE_64

    BUCKET_ID: MEMORY_CORRUPTION_LARGE_64

    Followup: memory_corruption

    This is normally associated with faulty ram.

    Test your ram as per these instructions.

    You might also want to take a look at this thread HERE.

    Regards Howard :wave: :wave:
Topic Status:
Not open for further replies.


Add New Comment

TechSpot Members
Login or sign up for free,
it takes about 30 seconds.
You may also...


Get complete access to the TechSpot community. Join thousands of technology enthusiasts that contribute and share knowledge in our forum. Get a private inbox, upload your own photo gallery and more.