1. TechSpot is dedicated to computer enthusiasts and power users. Ask a question and give support. Join the community here.
    TechSpot is dedicated to computer enthusiasts and power users.
    Ask a question and give support.
    Join the community here, it only takes a minute.
    Dismiss Notice

Bluescreen problems

By Tolah
Nov 10, 2005
  1. Hi all,

    I have experienced a lot of bluescreens recently, playing games, watching movies or just surfing. The computer crashes with a bluescreen. I would be happy if you could help me. I've done everything to try and find out the fault myself but memtest didnt find anything and I have no idea what else to do.


  2. cpc2004

    cpc2004 TS Evangelist Posts: 1,994


    The culprit is faulty memory. 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.

    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
    3. Downclock the ram
    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
    If it still crashes, diagnostic which memory stick is faulty
    1. Take out one memory stick. If windows does not crash, the removed memory stick is faulty.
    2. If you have only one memory stick, replace the ram

    An attempt was made to access a pageable (or completely invalid) address at an
    interrupt request level (IRQL) that is too high. This is usually
    caused by drivers using improper addresses.
    If kernel debugger is available get stack backtrace.
    Arg1: 00000000, memory referenced
    Arg2: 00000002, IRQL
    Arg3: 00000001, value 0 = read operation, 1 = write operation
    Arg4: eef4282e, address which referenced memory

    Debugging Details:
    WRITE_ADDRESS: 00000000

    eef4282e 6c insb

    LAST_CONTROL_TRANSFER: from eef42c6f to eef4282e

    a83e87a0 eef42c6f 84f0f008 a83e87c4 0000000e tcpip!GetARPBufferAtDpcLevel+0x5
    a83e87cc eef428ce 84f0f008 850176b0 84ea0220 tcpip!ARPSendData+0x85
    a83e87f8 eef4270a 84f0f008 a83e8800 00000001 tcpip!ARPTransmit+0x193
    a83e8828 eef424a9 84f0f730 0101a8c0 850176b0 tcpip!SendIPPacket+0x18e
    a83e8974 eef46b83 eef806b4 8629bbb0 84e19470 tcpip!IPTransmit+0x287f
    a83e8a14 eef4694a 84b75890 8629bbb0 8636d0c0 tcpip!UDPSend+0x41b
    a83e8a38 eef469b0 003e8a5c 8636d008 84e194b0 tcpip!TdiSendDatagram+0xd5
    a83e8a70 eef45308 8636d0c0 8636d178 8636d0c0 tcpip!UDPSendDatagram+0x4f
    a83e8a8c f7db488b 85016f18 8636d0c0 8636d008 tcpip!TCPDispatchInternalDeviceControl+0xff
    WARNING: Stack unwind information not available. Following frames may be wrong.
    a83e8b08 eeef7bce 0012fc88 eeef7bce 86275e30 avgtdi+0x88b
    a83e8c50 8057c012 8635bf90 00000001 0012fb58 afd!AfdFastIoDeviceControl+0x2a7
    a83e8d00 8057bfa5 00000560 00000454 00000000 nt!IopXxxControlFile+0x261
    a83e8d34 804de7ec 00000560 00000454 00000000 nt!NtDeviceIoControlFile+0x2a
    a83e8d34 7c91eb94 00000560 00000454 00000000 nt!KiFastCallEntry+0xf8
    0012fc48 00000000 00000000 00000000 00000000 0x7c91eb94

    CHKIMG_EXTENSION: !chkimg -lo 50 -db !tcpip
    !chkimg -lo 50 -db !tcpip
    7 errors : !tcpip (eef42825-eef4283e)
    eef42820 c9 c2 0c 00 90 *01 *00 90 90 8b ff 55 8b ec *6c c0 ...........U..l.

    eef42830 80 7d 10 2a 77 *ff *77 75 0c ff 35 38 2e *5f *5e e8 .}.*w.wu..58._^.

    MODULE_NAME: memory_corruption
    IMAGE_NAME: memory_corruption
    FOLLOWUP_NAME: memory_corruption
  3. Tolah

    Tolah TS Rookie Topic Starter


    thanks for your quick answer.. is just ran Memtest+ which took roughly 8 hours. and I had 80 errors on Test #7.. which was random numbers if I remember correctly.

    Are both ram modules faulty or might it be only one.. But i guess, buying 2 new ram moduls for dual ram might be better.

    Thanks a lot anyways :)
  4. cpc2004

    cpc2004 TS Evangelist Posts: 1,994


    Try out a memory stick. If the system does not crash, the removed memory stick is faulty. Vice Versa swap the memory stick. If it still crashes, both memory sticks are faulty.
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...