BSOD driver_irql_not_less...

By x1x1x1 ยท 4 replies
Apr 18, 2006
  1. Hi there,

    i just install my windows 4 days ago

    i using winXP service pack 2.

    i face the "driver_irql_not_less..." so often, i even already try change my memory 3 times but the problem still exist.

    can somebody help me? I'm very stress with this issue

    i attached the mini dump log

    P.s: sorry for my bad english

    Attached Files:

  2. sledz41

    sledz41 TS Rookie

    Ok, I'm not good at this but I just looked at the dumps
    and It writes about C21ndis.sys and Symtdi.sys.

    I couldn't find anything on C21ndis.sys but Symtdi.sys is a file from Symantec Norton Internet Security Program. Try checking for viruses and trojans and reinstalling Symantec software.
    Thats my best bet. Hope that was of some help.
  3. x1x1x1

    x1x1x1 TS Rookie Topic Starter

    problem solved

    hi sledz41, thanks for your answer but now i already fixed my problem

    c21indis.sys is com21 (Cable Modem) and i already update the driver.

    actually i just realize that the BSOD only appear when i'm using BitTorrent. So i'm uninstall bittorrent after i update the com21 driver and then install again and now my computer is fine.

  4. Tedster

    Tedster Techspot old timer..... Posts: 6,002   +15

    using bit torrent? congrats. You have a virus.

    only fools and newbies use P2P programs. They're conduits for viri.
  5. cpc2004

    cpc2004 TS Evangelist Posts: 1,994

    Hi x1x1x1,

    Your windows is crashed with multiple culprits. I believe bittorrent is one of the culprit and the other culprit is faulty. From the debug report, I find code corruption and illegal instruction. They are the signs of faulty ram.

    Mini041706-01.dmp BugCheck 100000D1, {48195b4, 2, 0, f7e92053}
    Owning Process 81690360 Image: btdownloadgui.e
    Probably caused by : memory_corruption (12 memory errors)

    Mini041706-02.dmp BugCheck 1000008E, {c000001d, 814d180a, f4dc8940, 0}
    Owning Process 814d1020 Image: btdownloadgui.e
    Probably caused by : SYMIDS.SYS ( SYMIDS+3c4b ) <-- crashed by hardware error

    Mini041706-03.dmp BugCheck C2, {7, cd4, 2040005, 81a851a8}
    Owning Process 814ed950 Image: nvsvc32.exe
    Probably caused by : ntoskrnl.exe ( nt!ExFreePoolWithTag+2be )

    Mini041806-01.dmp BugCheck 100000D1, {15, 2, 0, f8014ec0}
    Probably caused by : SYMTDI.SYS ( SYMTDI+1fec0 )

    Mini041806-02.dmp BugCheck 1000008E, {c0000005, 804e83e1, f7e4c86c, 0}
    Probably caused by : ntoskrnl.exe ( nt!FsRtlAcquireFileExclusiveCommon+2f )

    Mini041806-03.dmp BugCheck 10000050, {f2e9dbfe, 0, 804f3868, 0}
    Probably caused by : sisidex.sys ( sisidex+403 )

    Mini041806-04.dmp BugCheck 1000000A, {4c, ff, 0, 804e35e9}
    Probably caused by : ntoskrnl.exe ( nt!ExAcquireResourceExclusiveLite+36 ) <-- faulty ram or device driver is corrupted

    You had better run memtest to stress test the ram.
Topic Status:
Not open for further replies.

Similar Topics

Add your comment to this article

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