TechSpot

:: BSOD Problems - Attached is my Error Content and Minidump Files ::

By bertzza
Jul 7, 2005
  1. Hi
    I am currently expriencing problems with the BSOD. This has been bugging me for a few months now so I am pretty keen to solve the problem once and for all. The problems occurs about once a week but is very frustrating. I have noticed errors such as IRQ NOT EQUAL.... or BAD POOL CALLER.

    I have tested my RAM, I have a brand new CPU/MOBO and have installed a fresh copy of Windows SP2 so I am pretty convinced that it is due to an imcompatible software or faulty driver.

    If anyone could take a look at my minidump files and the content of my error message which are attached I would greatly appreciate it as I am starting to go grey over this problem.


    -------------------------
    AMD Athlon XP 3000+
    Asus A7n8x-e deluxe
    2 X 512 Kingston PC 3200
    160 Western Digital HDD
    ATI Radeon 9600 Pro
    -------------------------
    running Windows XP Pro SP/2


    cheers bertzza.
     

    Attached Files:

  2. cpc2004

    cpc2004 TS Evangelist Posts: 1,994

    One minidump has memory corruption. Usually it is symptom of faulty hardware such as RAM.


    BugCheck 1000000A, {6d107b1c, ff, 0, 804e3b58}
    Probably caused by : memory_corruption

    Followup: memory_corruption
    ---------

    kd> !analyze -v
    *******************************************************************************
    * *
    * Bugcheck Analysis *
    * *
    *******************************************************************************

    IRQL_NOT_LESS_OR_EQUAL (a)
    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 a kernel debugger is available get the stack backtrace.
    Arguments:
    Arg1: 6d107b1c, memory referenced
    Arg2: 000000ff, IRQL
    Arg3: 00000000, value 0 = read operation, 1 = write operation
    Arg4: 804e3b58, address which referenced memory

    Debugging Details:
    ------------------
    READ_ADDRESS: 6d107b1c
    CURRENT_IRQL: ff

    FAULTING_IP:
    nt!ExAcquireResourceExclusiveLite+36
    804e3b58 66837e0c00 cmp word ptr [esi+0xc],0x0

    CUSTOMER_CRASH_COUNT: 1
    DEFAULT_BUCKET_ID: CODE_CORRUPTION
    BUGCHECK_STR: 0xA
    LAST_CONTROL_TRANSFER: from f76f2df2 to 804e3b58

    STACK_TEXT:
    a78d2758 f76f2df2 6d107b10 00000001 00000001 nt!ExAcquireResourceExclusiveLite+0x36
    a78d27d4 f76f2dc9 84d013c0 86f1f100 00000001 Ntfs!NtfsFlushVolume+0xfa
    a78d2874 f76e6385 84d013c0 852b7c80 a78d0000 Ntfs!NtfsCommonVolumeOpen+0x341
    a78d294c 804e3d77 86f1f020 852b7c80 86a41db0 Ntfs!NtfsFsdCreate+0x154
    a78d295c f7756876 804e91a1 86ef5a58 852b7c80 nt!IopfCallDriver+0x31
    a78d29a8 804e3d77 86b4faa0 00000001 852b7e34 sr!SrCreate+0x150
    a78d29b8 f7c83325 f7c83a1f 86b4e9b0 852b7c80 nt!IopfCallDriver+0x31
    WARNING: Stack unwind information not available. Following frames may be wrong.
    a78d29ec 804e3d77 86b4e9b0 86b4f9e8 a78d2a44 SiWinAcc+0x325
    a78d2a60 804e3d77 86949020 852b7c80 852b7c80 nt!IopfCallDriver+0x31
    a78d2a70 80570f9c 86ef78e8 869844a4 a78d2c18 nt!IopfCallDriver+0x31
    a78d2b50 8056386c 86ef7900 00000000 86984400 nt!IopParseDevice+0xa58
    a78d2bd8 80567c63 00000000 a78d2c18 00000040 nt!ObpLookupObjectName+0x56a
    a78d2c2c 80571477 00000000 00000000 00010301 nt!ObOpenObjectByName+0xeb
    a78d2ca8 80571546 0091e338 00100001 0091e308 nt!IopCreateFile+0x407
    a78d2d04 8057160e 0091e338 00100001 0091e308 nt!IoCreateFile+0x8e
    a78d2d44 804df06b 0091e338 00100001 0091e308 nt!NtOpenFile+0x27
    a78d2d44 7c90eb94 0091e338 00100001 0091e308 nt!KiFastCallEntry+0xf8
    0091e2d8 00000000 00000000 00000000 00000000 0x7c90eb94

    CHKIMG_EXTENSION: !chkimg -lo 50 -db !nt
    12 errors : !nt (804e3104-804e3177)
    804e3100 df 67 61 80 *90 *b9 *37 *f7 06 09 50 80 14 84 64 80 .ga...7...P...d....
    804e3120 63 ed 62 80 *d0 *b8 *37 *f7 7c e9 57 80 bc f3 57 80 c.b...7.|.W...W....
    804e3170 ae 23 58 80 *60 *bd *37 *f7 79 c6 4f 80 0c df 5c 80 .#X.`.7.y.O...\.

    MODULE_NAME: memory_corruption
    IMAGE_NAME: memory_corruption
    FOLLOWUP_NAME: memory_corruption
    DEBUG_FLR_IMAGE_TIMESTAMP: 0
    MEMORY_CORRUPTOR: STRIDE
    STACK_COMMAND: kb
    FAILURE_BUCKET_ID: MEMORY_CORRUPTION_STRIDE
    BUCKET_ID: MEMORY_CORRUPTION_STRIDE

    Followup: memory_corruption
     
  3. bertzza

    bertzza TS Rookie Topic Starter

    BSOD Continues

    Hi cpc2004

    I have done a thorough test on my RAM using a Windows Memory Diagnostic.
    I tested both sticks of RAM for about 4 hours and there were no reported errors. i have attached the details of the last 3 crashes I have experienced so I was wondering if you could debug them and post a possible culprit.

    I have a brand new CPU, MOBO and new RAM so im pretty sure these would not be the problem. Do you think it could possibly be the power supply? I am currently using the one that came with the Antec Case which is 350W.

    cheers . bertzza.
     
  4. cpc2004

    cpc2004 TS Evangelist Posts: 1,994

    Your latest dump also have memory corruption. New CPU, M/B or RAM does not mean that hardware is good and it is a wrong concept. New hardware always has hardware failure at the first month. The PSU may be culprit. As PSU is not expansive, it is worhwhile to replace PSU.

    BugCheck 1000000A, {80d6b2e4, ff, 0, 804e3b58}
    Probably caused by : memory_corruption

    Followup: memory_corruption

    STACK_TEXT:
    a7b33784 f83f9df2 80d6b2d8 00000001 00000001 nt!ExAcquireResourceExclusiveLite+0x36
    a7b33800 f83f9dc9 ff81c470 82b90850 00000001 Ntfs!NtfsFlushVolume+0xfa
    a7b338a0 f83ed385 ff81c470 81b3c008 a7b30000 Ntfs!NtfsCommonVolumeOpen+0x341
    a7b33978 804e3d77 82b90770 81b3c008 ff8031d0 Ntfs!NtfsFsdCreate+0x154
    a7b33988 f845d876 81b3c008 82b83a58 81b3c008 nt!IopfCallDriver+0x31
    a7b339d4 804e3d77 82b6da58 00000001 81b3c204 sr!SrCreate+0x150
    a7b339e4 f898a325 f898aa1f 82b35dc0 81b3c008 nt!IopfCallDriver+0x31
    WARNING: Stack unwind information not available. Following frames may be wrong.
    a7b33a18 804e3d77 82b35dc0 82b6d9a0 81b3c204 SiWinAcc+0x325
    a7b33a4c 804e3d77 82b433d0 81b3c008 825b2f38 nt!IopfCallDriver+0x31
    a7b33a60 804e3d77 8278dd30 81b3c008 81b3c008 nt!IopfCallDriver+0x31
    a7b33a70 80570f9c 82b858e8 ff9d37ac a7b33c18 nt!IopfCallDriver+0x31
    a7b33b50 8056386c 82b85900 00000000 ff9d3708 nt!IopParseDevice+0xa58
    a7b33bd8 80567c63 00000000 a7b33c18 00000040 nt!ObpLookupObjectName+0x56a
    a7b33c2c 80571477 00000000 00000000 02b55b01 nt!ObOpenObjectByName+0xeb
    a7b33ca8 80571546 0205fde4 00100081 0205fdb4 nt!IopCreateFile+0x407
    a7b33d04 8057160e 0205fde4 00100081 0205fdb4 nt!IoCreateFile+0x8e
    a7b33d44 804df06b 0205fde4 00100081 0205fdb4 nt!NtOpenFile+0x27
    a7b33d44 7c90eb94 0205fde4 00100081 0205fdb4 nt!KiFastCallEntry+0xf8
    0205fd84 00000000 00000000 00000000 00000000 0x7c90eb94

    CHKIMG_EXTENSION: !chkimg -lo 50 -db !nt
    12 errors : !nt (804e3104-804e3177)
    804e3100 df 67 61 80 *90 *89 *73 *f8 06 09 50 80 14 84 64 80 .ga...s...P...d.
    ...
    804e3120 63 ed 62 80 *d0 *88 *73 *f8 7c e9 57 80 bc f3 57 80 c.b...s.|.W...W.
    ...
    804e3170 ae 23 58 80 *60 *8d *73 *f8 79 c6 4f 80 0c df 5c 80 .#X.`.s.y.O...\.

    MODULE_NAME: memory_corruption
    IMAGE_NAME: memory_corruption
    FOLLOWUP_NAME: memory_corruption
    DEBUG_FLR_IMAGE_TIMESTAMP: 0
    MEMORY_CORRUPTOR: STRIDE
    STACK_COMMAND: kb
    FAILURE_BUCKET_ID: MEMORY_CORRUPTION_STRIDE
    BUCKET_ID: MEMORY_CORRUPTION_STRIDE
    Followup: memory_corruption
     
  5. GSL

    GSL TS Rookie Posts: 33

    I would like to add my 2 cents. I have seen this problem before...on my own machine. I had just bought a brand new mobo, cpu, and memory and was getting this. The "work around" that I found was to drop the memory speed by one until the system is stable. It urks me that I have ddr 400 memory running at ddr 333, but that's how I got the problem fixed. Hope this helps.
     
  6. Soap

    Soap TS Rookie Posts: 72

    hi,

    ive been having trouble with the bsod. it has been happening for a while and is appearing more frequently in recent times. the most common error being the irq not less or equal.

    i have tested the ram using memtest86+ and no errors were found and have recently done a fresh installation windows xp sp2.

    it would be great if someone could point me in the direction of the problem.

    thanks.
     
  7. GSL

    GSL TS Rookie Posts: 33

    While memtest is a good tool to test with this, I would still say this could be a memory problem because memtest won't catch problems 100% of the time. Try only one stick of memory(if you have more than one) and see if this fixes the issue. If not, then it could be your board or both sticks of memory...unless you've added any hardware just before this started happening.
     
  8. cpc2004

    cpc2004 TS Evangelist Posts: 1,994

    Three of minidumps crashes at IRQL x'1f' which is either machine checks or bus errors. Faulty M/B or PSU may be the culprit.

    IRQL_NOT_LESS_OR_EQUAL (a)
    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 a kernel debugger is available get the stack backtrace.
    Arguments:
    Arg1: fddff980, memory referenced
    Arg2: 0000001f, IRQL
    Arg3: 00000001, value 0 = read operation, 1 = write operation
    Arg4: 804e3919, address which referenced memory

    Debugging Details:
    ------------------
    WRITE_ADDRESS: fddff980
    CURRENT_IRQL: 1f
    FAULTING_IP:
    nt!KeInsertQueueDpc+85
    804e3919 8902 mov [edx],eax

    CUSTOMER_CRASH_COUNT: 1
    DEFAULT_BUCKET_ID: DRIVER_FAULT
    BUGCHECK_STR: 0xA
    LAST_CONTROL_TRANSFER: from f76653d1 to 804e3919

    STACK_TEXT:
    80550108 f76653d1 00000000 00000000 00000000 nt!KeInsertQueueDpc+0x85
    80550130 804da779 82ba67e8 82baf690 00000001 ACPI!ACPIInterruptServiceRoutine+0xb3
    80550148 804da721 00000000 80550164 804da72e nt!KiChainedDispatch2ndLvl+0x39
    80550148 ffdff000 00000000 80550164 804da72e nt!KiChainedDispatch+0x1b
    WARNING: Frame IP not in any known module. Following frames may be wrong.
    805501c8 804dbb39 00000008 00000202 00000000 0xffdff000

    FOLLOWUP_IP:
    ACPI!ACPIInterruptServiceRoutine+b3
    f76653d1 8b75fc mov esi,[ebp-0x4]

    SYMBOL_STACK_INDEX: 1
    FOLLOWUP_NAME: MachineOwner
    SYMBOL_NAME: ACPI!ACPIInterruptServiceRoutine+b3
    MODULE_NAME: ACPI
    IMAGE_NAME: ACPI.sys
    DEBUG_FLR_IMAGE_TIMESTAMP: 41107d27
    STACK_COMMAND: kb
    FAILURE_BUCKET_ID: 0xA_W_ACPI!ACPIInterruptServiceRoutine+b3
    BUCKET_ID: 0xA_W_ACPI!ACPIInterruptServiceRoutine+b3
     
  9. bertzza

    bertzza TS Rookie Topic Starter

    Latest Minidump File

    Hi cpc2004

    Can you please have a look at my latest minidump file. I removed my TV Card and didnt get a BSOD for about a week. Then today I got one :-(

    It didnt come up as an error in event viewer though. Just information.

    The computer has rebooted from a bugcheck. The bugcheck was: 0x100000be (0xc00137fc, 0x2cc48025, 0xa8933b68, 0x0000000a). A dump was saved in: C:\WINDOWS\Minidump\Mini083105-01.dmp.

    For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.

    cheers. bertzza.
     
  10. cpc2004

    cpc2004 TS Evangelist Posts: 1,994

    Hi Bertzza,

    You assume new hardware does not have hardware problem which I don't agree. You must understand most of my finding are based upon the problem owner's feedback. You did not reply to my post at last month and I can only assume you replace the PSU. Most probably it is faulty ram as you had two memory corruption. 95% Memory corruption is hardware problem and I only find memory corruption at one of my PC is caused faulty TV capture driver.

    I suggest you replace the PSU cos it is cheap and you did not agree it is faulty ram. You must aware some faulty ram can pass memtest as memtest is not a reliable tool.

    You may re-install windows as one of previous crash is IRQL x'ff' which is usually the device driver pass a invalid parameter to windows. Why does the device driver has invalid parameters to windows? The root cause of failure at IRQL x'ff' maybe hardware or software problem. Re-install windows can isolate whether it is hardware or software problem.

    Without your feedback. I can only guess your problem and I can't provide a reasonable answer to you. Maybe some experts can do.


    cpc2004
     
  11. cpc2004

    cpc2004 TS Evangelist Posts: 1,994

    Hi Soap,

    Do you have any update of your problem? Your feedback will help us to resolve similar problem.

    Thanks in advance
    cpc2004
     
  12. bertzza

    bertzza TS Rookie Topic Starter

    Bsod

    Hi,

    Sorry for the late reply. Im in thailand at the moment on holiday.

    Yea I formatted my computer prior to posting my last message. Fresh installation of win xp pro. I did not experience any BSOD for 2 days. Then I installed the TV Card drivers and while watching TV my computer crashed :-(

    I have two Kingston 512 meg RAM, I have tried both separately and still experienced problems. One of the stricks I purchased only a few months ago.

    I will purchase another PSU and see how it goes.

    cheers.
     
  13. cpc2004

    cpc2004 TS Evangelist Posts: 1,994

    Hi Bertzza,

    If you check my previous post, my initial finding is faulty ram. What is the TV device driver that you install?
     
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...