TechSpot

BSOD problem

By general
Feb 11, 2006
  1. cpc2004

    cpc2004 TS Evangelist Posts: 1,994

    Hi,

    Your windows are crashed various bugcheck codes and failing modules. I believe that it is fauty memory (ie RAM, video memory or cache memory of CPU)

    You can run memtest to stress the ram. If memtest reports the ram is faulty, ram is bad. However Memtest is not a perfect tool to test the memory as some faulty ram can pass memtest.

    Suggestion
    1. Check the temperature of the CPU and make sure that it is not overheat (ie temperature < 60C)
    Make sure that the CPU fan works properly
    2. Reseat the memory stick to another memory slot. Reseat video card as well.
    3. Downclock the ram. Check to default setting if you video card is overclocked.
    4. Clean the dust inside the computer case
    5. Make sure that the ram is compatible to the motherboard
    6. 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)
    7. Make sure that your PSU has adequate power to drive all the hardware including USB devices
    8. Run chkdsk /r at command prompt
    9. Run 3DMark 2005 to test your video card
    10. Upgrade BIOS and make sure that the motherboard has no leaking capacitor

    If it still crashes, diagnostic which memory stick is faulty
    Take out one memory stick. If windows does not crash, the removed memory stick is faulty.


    Mini010106-01.dmp BugCheck 1000000A, {80f82e58, ff, 0, 804e35e9}
    Probably caused by : ntoskrnl.exe ( nt!ExAcquireResourceExclusiveLite+36 )

    Mini011406-01.dmp BugCheck 4E, {99, 33e5b, 5, 0}
    Probably caused by : memory_corruption ( nt!MiDeletePte+3e8 )

    Mini020906-01.dmp BugCheck 1000000A, {1c, 2, 1, 8053b885}
    Probably caused by : memory_corruption ( nt!MiDecrementCloneBlockReference+a )

    Mini121605-01.dmp BugCheck 1000008E, {c0000005, bf9c58a2, b8907c94, 0}
    Probably caused by : dxg.sys ( dxg!EDD_DEVLOCK::EDD_DEVLOCK+8 )

    Mini122405-01.dmp BugCheck 1000008E, {c0000005, bfa8b682, b7a37c08, 0}
    Probably caused by : ati3duag.dll ( ati3duag+17682 )
     
  2. general

    general TS Rookie Topic Starter

    thanx for ur reply

    but i took out one ram (256) and left (512) , i tried to clean it , after i cleaned it , i put it back and turn on my PC , but it didn't work there was a sound like " Beep , Beep, Beep " , i took it out (256) and decided to run my pc at 512 only. so i think 256 is faulty.

    thanx again
     
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...