TechSpot

Frequent BSOD Problem

By Spoon
Mar 10, 2008
  1. Hi, i am having some pretty frequent BSODs, I built my computer about 6 months ago and shortly after it was put together I started to get very random BSODs. This would happen when i was watching videos, playing games, and such.

    A couple days ago I decided that I was going to reinstall windows XP to see if that fixed anything.

    I have since received some BSODs and hopefully somebody can help me figure out what the problem is.
    I have run memtest86 for 7 passes on each individual stick of RAM and both of them combined without any errors(2, 1 gig sticks).
     
  2. Route44

    Route44 TechSpot Ambassador Posts: 11,966   +70

    The one definitive driver that was cited is yk51x86.sys which is a driver for the process NDIS5.1 Miniport Driver for Marvell Yukon Gigabit Ethernet Controller or NDIS5.1 Miniport Driver for Marvell Yukon Gigabit Ethernet Adapter or NDIS5.1 Miniport Driver for Marvell Yukon Ethernet Controller belonging to the software Marvell Yukon Gigabit Ethernet Controller or Marvell Yukon Gigabit Ethernet Adapter or Marvell Yukon Ethernet Controller by Marvell.

    Did you get all that? :)

    Try this: Update your drivers for your Gigabyte Ethernet. If that doesn't work, post more minidumps.
     
  3. cpc2004

    cpc2004 TS Evangelist Posts: 1,994

    Summary of your debug report
    1. One minidump is crashed at IRQL x'1c' and it is the symptom of faulty ram
    2. 4 minidumps are crashed at win32k.sys and it is also the symptom of faulty ram
    3. The stack trace of 1 minidump has memory access fault and it is also the symptom of faulty ram.

    Finding
    It is hardware error. Probably the ram is bad. Reseat the memory module to another memory slot.

    Mini030908-02.dmp BugCheck 100000D1, {1fe5959, 2, 0, ba605868}
    Probably caused by : yk51x86.sys ( yk51x86+f4f4 )

    Mini030908-03.dmp BugCheck 1000008E, {c0000005, bf82015d, b756eb98, 0}
    Probably caused by : win32k.sys ( win32k!DestroyThreadsTimers+13 )

    Mini031008-01.dmp BugCheck 1000000A, {6e496d4d, 1c, 0, 805021af}
    Crash at Timer IRQL 28
    Probably caused by : win32k.sys ( win32k!InternalSetTimer+162 )

    Mini031008-02.dmp BugCheck 1000000A, {0, 2, 1, 805219c4}
    Probably caused by : win32k.sys ( win32k!vDIBSolidBlt+19b )

    Mini031008-03.dmp BugCheck 1000000A, {0, 2, 1, 805219c4} ?<- Memory access Fault ??
    Probably caused by : win32k.sys ( win32k!vSolidFillRect1+108 )
     
  4. cpc2004

    cpc2004 TS Evangelist Posts: 1,994

    From the stack trace of the minidumps, most of crashes are at timer routine and it is also the symptom of faulty ram.
     
  5. Spoon

    Spoon TS Rookie Topic Starter

    Ok, i moved the RAM to different slots and that did not fix the problem. i am currently testing each stick individually to see if either one specifically gives me problems. Thanks!
     
  6. cpc2004

    cpc2004 TS Evangelist Posts: 1,994

    1. If you overclock the ram, change it back to original setting. Check to default setting if you video card is overclocked.
    2. Make sure that the ram is compatible to the motherboard
    For example : If the ram and the motherboard has dual mode compatibility problem, you must stop using dual mode and switch to single channel mode
    http://www.techspot.com/vb/showthread.php?p=251045#post251045
    3. Check the bios setting about memory timing and make sure that it is on
    For example : DIMM1 and DIMM2 do not have the same timing.
    DIMM1: Corsair CMX512-3200C2 512 MB PC3200 DDR SDRAM (2.5-3-3-8 @ 200 MHz) (2.0-3-3-7 @ 166 MHz)
    DIMM2: Corsair CMX512-3200C2 512 MB PC3200 DDR SDRAM (3.0-3-3-8 @ 200 MHz)
    DIMM3: Corsair CMX512-3200C2 512 MB PC3200 DDR SDRAM (3.0-3-3-8 @ 200 MHz)
     
Topic Status:
Not open for further replies.

Similar Topics

Add New Comment

You need to be a member to leave a comment. Join thousands of tech enthusiasts and participate.
TechSpot Account You may also...