TechSpot

Tricky BSOD

By pekkis924
Feb 24, 2007
  1. Hi all!

    Built this new system mostly of new parts:
    Asus P5B
    Core2Duo E6400
    Club3D NV 7900GS
    Logitech Cordless Internet Pro keyboard/mouse
    Buffalo 800MHz 1GB DDR2
    Antec Sonata 2 case & power 450W
    80GB Samsung IDE HDD (from old system)
    Gigabyte DVD-RW (from old system)
    XP Pro 32bit

    Ever since new the system has suffered from BSOD IRQL_NOT_LESS_OR_EQUAL stop errors. I have googled around and done many tricks to solve this but nothing helps. Memory was tested with memtest: clean, disck checked: clean, upgraded BIOS and logitech mouseware. Uninstalled zonealarm and avast antivirus, pagefile trick tried, windows reinstalled. BSOD has so far always occurred when playing 3D game like Oblivion. Temperatures should be fine. No viruses should be around.

    I'm attaching two minidumps if anyone could help it would save my day.

    Thanks!
     
  2. cfitzarl

    cfitzarl TechSpot Chancellor Posts: 1,975   +9

    That is most likely due to a faulty driver.
     
  3. pekkis924

    pekkis924 TS Rookie Topic Starter

    All drivers are the latest, motherboard, logitech and graphics card. System does not have much software installed. Only firefox and few games.

    Bios settings are on default, memory MHz on auto.
     
  4. tweaks_sav

    tweaks_sav TS Rookie Posts: 186

    I would retest your RAM using a different utility.


    021507-01:
    *******************************************************************************
    * *
    * Bugcheck Analysis *
    * *
    *******************************************************************************

    Use !analyze -v to get detailed debugging information.

    BugCheck 1000000A, {4, 2, 1, 80526c9d}

    Probably caused by : memory_corruption

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

    0: 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: 00000004, memory referenced
    Arg2: 00000002, IRQL
    Arg3: 00000001, value 0 = read operation, 1 = write operation
    Arg4: 80526c9d, address which referenced memory

    Debugging Details:
    ------------------


    WRITE_ADDRESS: 00000004

    CURRENT_IRQL: 2

    FAULTING_IP:
    nt!PopApplyAttributeState+85
    80526c9d d223 shl byte ptr [ebx],cl

    CUSTOMER_CRASH_COUNT: 1

    DEFAULT_BUCKET_ID: CODE_CORRUPTION

    BUGCHECK_STR: 0xA

    PROCESS_NAME: Idle

    LAST_CONTROL_TRANSFER: from 80526d4a to 80526c9d

    STACK_TEXT:
    8055020c 80526d4a 00000004 00000000 8055023c nt!PopApplyAttributeState+0x85
    8055021c f790d1c2 00000004 8628a0d8 8628a178 nt!PoSetSystemState+0x22
    8055023c efb64ccd 00000000 8628a178 8628a184 kbdclass!KeyboardClassServiceCallback+0x28
    80550260 ed378ace 00000001 8055027c 00000000 kbdhid!KbdHid_InsertCodesIntoQueue+0x8b
    80550274 ed378b54 0000001f 00000001 efb64c42 HIDPARSE!HidP_KbdPutKey+0x30
    80550290 ed378e3a 86300016 00000001 8630d050 HIDPARSE!HidP_TranslateUsage+0x7a
    805502c0 efb64d3c 8630d125 0000000e 00000001 HIDPARSE!HidP_TranslateUsageAndPagesToI8042ScanCodes+0x64
    805502e0 80501543 8628a1b8 8628a0d8 7699a1a4 kbdhid!KbdHid_AutoRepeat+0x22
    805503fc 8050165f 8055b0a0 ffdff9c0 ffdff000 nt!KiTimerListExpire+0x14b
    80550428 80544e5f 8055b4a0 00000000 00032287 nt!KiTimerExpiration+0xb1
    80550440 8055ae40 ffdffc50 00000000 8055ae40 nt!KiRetireDpcList+0x61
    80550450 80544d44 00000000 0000000e 00000000 nt!KiIdleThread0
    80550454 00000000 0000000e 00000000 00000000 nt!KiIdleLoop+0x28


    STACK_COMMAND: kb

    CHKIMG_EXTENSION: !chkimg -lo 50 -d !nt
    80526c9a - nt!PopApplyAttributeState+82
    [ 8b:9b ]
    1 error : !nt (80526c9a)

    MODULE_NAME: memory_corruption

    IMAGE_NAME: memory_corruption

    FOLLOWUP_NAME: memory_corruption

    DEBUG_FLR_IMAGE_TIMESTAMP: 0

    MEMORY_CORRUPTOR: ONE_BIT

    FAILURE_BUCKET_ID: MEMORY_CORRUPTION_ONE_BIT

    BUCKET_ID: MEMORY_CORRUPTION_ONE_BIT

    Followup: memory_corruption

    -----

    022407:
    *******************************************************************************
    * *
    * Bugcheck Analysis *
    * *
    *******************************************************************************

    Use !analyze -v to get detailed debugging information.

    BugCheck 1000000A, {d5, 1c, 0, 8053fa70}

    Probably caused by : ntkrpamp.exe ( nt!KeAcquireQueuedSpinLockAtDpcLevel+0 )

    Followup: MachineOwner
    ---------

    0: 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: 000000d5, memory referenced
    Arg2: 0000001c, IRQL
    Arg3: 00000000, value 0 = read operation, 1 = write operation
    Arg4: 8053fa70, address which referenced memory

    Debugging Details:
    ------------------


    READ_ADDRESS: 000000d5

    CURRENT_IRQL: 1c

    FAULTING_IP:
    nt!KeAcquireQueuedSpinLockAtDpcLevel+0
    8053fa70 8b5104 mov edx,dword ptr [ecx+4]

    CUSTOMER_CRASH_COUNT: 1

    DEFAULT_BUCKET_ID: DRIVER_FAULT

    BUGCHECK_STR: 0xA

    PROCESS_NAME: Idle

    LAST_CONTROL_TRANSFER: from 80544d64 to 8053fa70

    STACK_TEXT:
    80550450 80544d64 00000000 0000000e 00000000 nt!KeAcquireQueuedSpinLockAtDpcLevel
    80550454 00000000 0000000e 00000000 00000000 nt!KiIdleLoop+0x48


    STACK_COMMAND: kb

    FOLLOWUP_IP:
    nt!KeAcquireQueuedSpinLockAtDpcLevel+0
    8053fa70 8b5104 mov edx,dword ptr [ecx+4]

    SYMBOL_STACK_INDEX: 0

    SYMBOL_NAME: nt!KeAcquireQueuedSpinLockAtDpcLevel+0

    FOLLOWUP_NAME: MachineOwner

    MODULE_NAME: nt

    IMAGE_NAME: ntkrpamp.exe

    DEBUG_FLR_IMAGE_TIMESTAMP: 42250a1e

    FAILURE_BUCKET_ID: 0xA_nt!KeAcquireQueuedSpinLockAtDpcLevel+0

    BUCKET_ID: 0xA_nt!KeAcquireQueuedSpinLockAtDpcLevel+0

    Followup: MachineOwner
    ---------
     
  5. Jesse_hz

    Jesse_hz TS Maniac Posts: 545

    How long did you let MemTest run?
    Some errors don't show up until after a couple of hours.

    Did you use the Windows or DOS version of MemTest?

    Could you try the memory/RAM in another computer?
     
  6. pekkis924

    pekkis924 TS Rookie Topic Starter

    Now I rerun memtest for 37 passes (9 hours). Still no errors. Version was the one that is used by booting from cd to it. At least look and feel is DOS. Are there other free memory testing tools available that could be tried?

    Memory MHz was now locked to 800.

    It gives about one BSOD per week with normal daily home usage.

    There are no other DDR2 systems available for me.

    Now I will keep the MHz at 800 and after next BSOD will try underclocking to lowest value. Testing is a bit tricky with Auto setting. Is it possible that it picks too high MHz automatically?

    Are there other memory related BIOS values that should be checked or tried to be changed?
     
  7. pekkis924

    pekkis924 TS Rookie Topic Starter

    Now I got this again. This time from usb mouse - right? Should I kick that logitech usb mouse and keyboard for ps2 models? Every dump seems to show crash for different cause. Maybe motherboard is bad?

    ---------------------------------------------------------------------------
    Symbol search path is: SRV*c:\symbols*http://msdl.microsoft.com/download/symbols
    Executable search path is:
    Windows XP Kernel Version 2600 (Service Pack 2) MP (2 procs) Free x86 compatible
    Product: WinNt, suite: TerminalServer SingleUserTS
    Built by: 2600.xpsp_sp2_gdr.050301-1519
    Kernel base = 0x804d7000 PsLoadedModuleList = 0x8055c700
    Debug session time: Sun Mar 11 23:10:22.744 2007 (GMT+2)
    System Uptime: 0 days 10:34:05.721
    Loading Kernel Symbols
    ........................................................................................................................
    Loading User Symbols
    Loading unloaded module list
    ...............................
    *******************************************************************************
    * *
    * Bugcheck Analysis *
    * *
    *******************************************************************************

    Use !analyze -v to get detailed debugging information.

    BugCheck 1000000A, {4, 2, 1, 80526c9d}

    Unable to load image LMouFlt2.Sys, Win32 error 2
    *** WARNING: Unable to verify timestamp for LMouFlt2.Sys
    *** ERROR: Module load completed but symbols could not be loaded for LMouFlt2.Sys
    Probably caused by : memory_corruption

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

    0: 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: 00000004, memory referenced
    Arg2: 00000002, IRQL
    Arg3: 00000001, value 0 = read operation, 1 = write operation
    Arg4: 80526c9d, address which referenced memory

    Debugging Details:
    ------------------


    WRITE_ADDRESS: 00000004

    CURRENT_IRQL: 2

    FAULTING_IP:
    nt!PopApplyAttributeState+85
    80526c9d d223 shl byte ptr [ebx],cl

    CUSTOMER_CRASH_COUNT: 1

    DEFAULT_BUCKET_ID: CODE_CORRUPTION

    BUGCHECK_STR: 0xA

    PROCESS_NAME: Idle

    LAST_CONTROL_TRANSFER: from 80526d4a to 80526c9d

    STACK_TEXT:
    80550144 80526d4a 00000004 00000000 80550174 nt!PopApplyAttributeState+0x85
    80550154 f1a0cf72 00000004 862ccb04 85acda78 nt!PoSetSystemState+0x22
    80550174 f3934522 00000018 862ccaec 862ccb04 mouclass!MouseClassServiceCallback+0x38
    WARNING: Stack unwind information not available. Following frames may be wrong.
    805501d0 f71ffc26 862ccb04 862ccaec 00000001 LMouFlt2+0x1522
    80550204 804f13e2 00000000 011fce28 022cca48 mouhid!MouHid_ReadComplete+0x3f0
    80550234 f0effe70 8055023c 8055023c 86492b30 nt!IopfCompleteRequest+0xa2
    80550250 f0f00044 02492b18 86476aa0 00000007 HIDCLASS!HidpDistributeInterruptReport+0xae
    80550290 804f13e2 00000000 864f4560 86487c2c HIDCLASS!HidpInterruptReadComplete+0x17a
    805502c0 f6787ee5 864f4560 8558a008 864eb028 nt!IopfCompleteRequest+0xa2
    80550328 f6788b57 8642d870 00000000 864eb7d8 USBPORT!USBPORT_CompleteTransfer+0x373
    80550358 f6789754 026e6f44 864eb0e0 864eb0e0 USBPORT!USBPORT_DoneTransfer+0x137
    80550390 f678af6a 864eb028 80545aac 864eb230 USBPORT!USBPORT_FlushDoneTransferList+0x16c
    805503bc f6798fb0 864eb028 80545aac 864eb028 USBPORT!USBPORT_DpcWorker+0x224
    805503f8 f6799128 864eb028 00000001 8055b0a0 USBPORT!USBPORT_IsrDpcWorker+0x37e
    80550414 8653d70b 864eb64c 6b755044 00000000 USBPORT!USBPORT_IsrDpc+0x166
    80550428 80544e5f 864eb64c 864eb028 00000000 0x8653d70b
    80550450 80544d44 00000000 0000000e 00000000 nt!KiRetireDpcList+0x61
    80550454 00000000 0000000e 00000000 00000000 nt!KiIdleLoop+0x28


    STACK_COMMAND: kb

    CHKIMG_EXTENSION: !chkimg -lo 50 -d !nt
    80526c9a - nt!PopApplyAttributeState+82
    [ 8b:9b ]
    1 error : !nt (80526c9a)

    MODULE_NAME: memory_corruption

    IMAGE_NAME: memory_corruption

    FOLLOWUP_NAME: memory_corruption

    DEBUG_FLR_IMAGE_TIMESTAMP: 0

    MEMORY_CORRUPTOR: ONE_BIT

    FAILURE_BUCKET_ID: MEMORY_CORRUPTION_ONE_BIT

    BUCKET_ID: MEMORY_CORRUPTION_ONE_BIT

    Followup: memory_corruption
    ---------
     
  8. peterdiva

    peterdiva TechSpot Ambassador Posts: 1,088

    The cause is memory corruption. Have you tried the memory in another slot?

    CHKIMG_EXTENSION: !chkimg -lo 50 -d !nt
    80526c9a - nt!PopApplyAttributeState+82
    [ 8b:9b ]
    1 error : !nt (80526c9a)

    MODULE_NAME: memory_corruption
    IMAGE_NAME: memory_corruption
    FOLLOWUP_NAME: memory_corruption
    MEMORY_CORRUPTOR: ONE_BIT
    FAILURE_BUCKET_ID: MEMORY_CORRUPTION_ONE_BIT
     
  9. pekkis924

    pekkis924 TS Rookie Topic Starter

    Yes I have tried in another slot. Still BSOD.

    But now it has been up long without BSOD after I lowered memory frequency to 500MHz.
     
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...