Long term BSOD's


  1. Posts : 13
    Windows 7, 64-Bit
       #1

    Long term BSOD's


    Hi,

    I've been having a long term problem (going on for a few months) with various BSOD's, including the IRQ less or not equal, system service exceptions, and various others, and can never seem to understand what is going on.

    Usually, in windows 7 (64bit) it is MOST likely to crash when the graphics card and sound card are running at the same time - but not always - when it happens. In fact, it's got so bad the computer for using games etc etc it's practically unusable. It even crashes in facebook game areas, with the system exception fault.

    I've attached all the crashes from the last 3 months (there's a lot of them) and thats really just the tip of the iceberg. Can anybody find the problem, and from there, a solution?

    Thanks
    Rich
      My Computer


  2. Posts : 28,845
    Win 8 Release candidate 8400
       #2

    Devilish said:
    Hi,

    I've been having a long term problem (going on for a few months) with various BSOD's, including the IRQ less or not equal, system service exceptions, and various others, and can never seem to understand what is going on.

    Usually, in windows 7 (64bit) it is MOST likely to crash when the graphics card and sound card are running at the same time - but not always - when it happens. In fact, it's got so bad the computer for using games etc etc it's practically unusable. It even crashes in facebook game areas, with the system exception fault.

    I've attached all the crashes from the last 3 months (there's a lot of them) and thats really just the tip of the iceberg. Can anybody find the problem, and from there, a solution?

    Thanks
    Rich
    Rich

    With that many different causes you have to think hardware. We have to examine one thing at a time. I would start by testing your memory. To do that download memtestx86 and run for at least 5 passes. If that passes (and I doubt it will) you can Run a system file check. To verify and repair your system files
    Type cmd in search>right click and run as admin>sfc /scannow (note the space between sfc and "/")

    If you are overclocking you need to stop
    If you have adjusted ram voltages reset them to default

    You have drivers that need to be updated.
    Code:
    ASACPI.sys        fffff880`04124000    fffff880`0412c000    0x00008000    0x42476c4c    3/27/2005 10:30:36 PM                        
    secdrv.SYS        fffff880`0974c000    fffff880`09757000    0x0000b000    0x4508052e    9/13/2006 9:18:38 AM
    If all else fails (and this might be easiest) I would do a clean re-install of win 7

    Ken
      My Computer


  3. Posts : 13
    Windows 7, 64-Bit
    Thread Starter
       #3

    Thanks for the reply.

    I have done some severe (quite dramatic) changes during this timeframe, including a memory test - which yielded no faults previously on many occassions. (and the memory test passed with no faults.

    I know it's not a memory fault as i've tried 3 different sets of memory. In fact - i've changed every system part - PSU, Mobo, CPU, Memory, HDD, sound card - to no avail.

    Even doing a complete re-install of windows never fixed it, as I had tried endlessly.

    I never know what it is.
      My Computer


  4. Posts : 13
    Windows 7, 64-Bit
    Thread Starter
       #4

    Latest BSOD...
      My Computer


  5. Posts : 28,845
    Win 8 Release candidate 8400
       #5

    Devilish said:
    Latest BSOD...

    Yet again this one points to hardware. we have to start minimizing what is connected. What external devices do you have (IE USB, firewire, bluetooth,etc)

    Do the BSOD's happen in safe mode(F8)?

    how about you give us the specifics on your system, maybe we can spot something that is incompatible.


    Code:
    Microsoft (R) Windows Debugger Version 6.11.0001.404 X86
    Copyright (c) Microsoft Corporation. All rights reserved.
    
    
    Loading Dump File [C:\Users\K\Desktop\032710-93506-01.dmp]
    Mini Kernel Dump File: Only registers and stack trace are available
    
    Symbol search path is: SRV*F:\symbols*http://msdl.microsoft.com/download/symbols
    Executable search path is: 
    Windows 7 Kernel Version 7600 MP (4 procs) Free x64
    Product: WinNt, suite: TerminalServer SingleUserTS Personal
    Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
    Machine Name:
    Kernel base = 0xfffff800`03257000 PsLoadedModuleList = 0xfffff800`03494e50
    Debug session time: Sat Mar 27 12:20:18.008 2010 (GMT-4)
    System Uptime: 0 days 0:35:53.460
    Loading Kernel Symbols
    ...............................................................
    ................................................................
    .......................
    Loading User Symbols
    Loading unloaded module list
    ................
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    
    Use !analyze -v to get detailed debugging information.
    
    BugCheck D1, {fffff5000dba51e0, 2, 1, fffff88005c32e63}
    
    Probably caused by : hardware ( mouhid!MouHid_StartRead+11b )
    
    Followup: MachineOwner
    ---------
    
    2: kd> !analyze -v
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    
    DRIVER_IRQL_NOT_LESS_OR_EQUAL (d1)
    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.
    Arguments:
    Arg1: fffff5000dba51e0, memory referenced
    Arg2: 0000000000000002, IRQL
    Arg3: 0000000000000001, value 0 = read operation, 1 = write operation
    Arg4: fffff88005c32e63, address which referenced memory
    
    Debugging Details:
    ------------------
    
    
    WRITE_ADDRESS: GetPointerFromAddress: unable to read from fffff800034ff0e0
     fffff5000dba51e0 
    
    CURRENT_IRQL:  2
    
    FAULTING_IP: 
    mouhid!MouHid_StartRead+11b
    fffff880`05c32e63 0da8320000      or      eax,32A8h
    
    CUSTOMER_CRASH_COUNT:  1
    
    DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
    
    BUGCHECK_STR:  0xD1
    
    PROCESS_NAME:  firefox.exe
    
    TRAP_FRAME:  fffff88002f92810 -- (.trap 0xfffff88002f92810)
    NOTE: The trap frame does not contain all registers.
    Some register values may be zeroed or incorrect.
    rax=0000000000009300 rbx=0000000000000000 rcx=fffffa8006dd2940
    rdx=0000000000000001 rsi=0000000000000000 rdi=0000000000000000
    rip=fffff88005c32e63 rsp=fffff88002f929a0 rbp=fffffa8004989930
     r8=0000000000000000  r9=fffff88005c1b3a8 r10=000000000000001c
    r11=0000000000000001 r12=0000000000000000 r13=0000000000000000
    r14=0000000000000000 r15=0000000000000000
    iopl=0         nv up ei ng nz ac pe cy
    mouhid!MouHid_StartRead+0x11b:
    fffff880`05c32e63 0da8320000      or      eax,32A8h
    Resetting default scope
    
    MISALIGNED_IP: 
    mouhid!MouHid_StartRead+11b
    fffff880`05c32e63 0da8320000      or      eax,32A8h
    
    LAST_CONTROL_TRANSFER:  from fffff800032c8469 to fffff800032c8f00
    
    STACK_TEXT:  
    fffff880`02f926c8 fffff800`032c8469 : 00000000`0000000a fffff500`0dba51e0 00000000`00000002 00000000`00000001 : nt!KeBugCheckEx
    fffff880`02f926d0 fffff800`032c70e0 : 00000000`00000000 00000000`00000103 fffffa80`0780000b fffff880`02f92878 : nt!KiBugCheckDispatch+0x69
    fffff880`02f92810 fffff880`05c32e63 : 00000000`00000000 00000000`00000000 fffffa80`04989900 fffffa80`06dd28a0 : nt!KiPageFault+0x260
    fffff880`02f929a0 fffff880`05c32cd1 : 00000000`00000000 00000000`ffffffff fffffa80`06d6c660 fffffa80`06dd28a0 : mouhid!MouHid_StartRead+0x11b
    fffff880`02f929f0 fffff800`032cb516 : fffffa80`04989c8b fffff880`00000000 fffffa80`00000001 00000000`00000000 : mouhid!MouHid_ReadComplete+0x6f5
    fffff880`02f92a70 fffff880`05c12acc : fffffa80`06dd1310 fffffa80`06dd1306 fffffa80`06dcf700 00000000`00000000 : nt!IopfCompleteRequest+0x3a6
    fffff880`02f92b50 fffff880`05c12d35 : fffffa80`06dd1a02 fffffa80`06dd1a00 fffffa80`06dcf7f0 00000000`00000008 : HIDCLASS!HidpDistributeInterruptReport+0x130
    fffff880`02f92be0 fffff800`032cb516 : fffffa80`048e7b2b 00000000`00000000 fffffa80`06dcf601 fffffa80`048e7860 : HIDCLASS!HidpInterruptReadComplete+0x235
    fffff880`02f92c70 fffff880`03e665d9 : fffffa80`04fc1050 fffffa80`03a53e00 00000000`00000000 00000000`00000000 : nt!IopfCompleteRequest+0x3a6
    fffff880`02f92d50 fffff880`03e66ab7 : fffffa80`03f08002 fffffa80`048e7860 00000000`ffffffff fffffa80`04fc1ea8 : USBPORT!USBPORT_Core_iCompleteDoneTransfer+0xa15
    fffff880`02f92e30 fffff880`03e6464f : fffffa80`04fc1ea8 fffffa80`04fc11a0 fffffa80`04fc2040 00000000`00000000 : USBPORT!USBPORT_Core_iIrpCsqCompleteDoneTransfer+0x3a7
    fffff880`02f92e90 fffff880`03e55f89 : fffffa80`04fc1050 00000000`00000000 fffffa80`04fc1e02 fffffa80`04fc1ea8 : USBPORT!USBPORT_Core_UsbIocDpc_Worker+0xf3
    fffff880`02f92ed0 fffff800`032d45dc : fffff880`02f63180 fffffa80`04fc1ea8 fffffa80`04fc1ec0 00000000`0000fffd : USBPORT!USBPORT_Xdpc_Worker+0x1d9
    fffff880`02f92f00 fffff800`032cf065 : 00000000`00000000 fffffa80`042ed060 00000000`00000000 fffff880`03e55db0 : nt!KiRetireDpcList+0x1bc
    fffff880`02f92fb0 fffff800`032cee7c : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxRetireDpcList+0x5
    fffff880`0c08efe0 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiDispatchInterruptContinue
    
    
    STACK_COMMAND:  kb
    
    FOLLOWUP_IP: 
    mouhid!MouHid_StartRead+11b
    fffff880`05c32e63 0da8320000      or      eax,32A8h
    
    SYMBOL_STACK_INDEX:  3
    
    SYMBOL_NAME:  mouhid!MouHid_StartRead+11b
    
    FOLLOWUP_NAME:  MachineOwner
    
    IMAGE_NAME:  hardware
    
    DEBUG_FLR_IMAGE_TIMESTAMP:  0
    
    MODULE_NAME: hardware
    
    FAILURE_BUCKET_ID:  X64_IP_MISALIGNED_mouhid.sys
    
    BUCKET_ID:  X64_IP_MISALIGNED_mouhid.sys
    
    Followup: MachineOwner
    ---------
      My Computer


  6. Posts : 13
    Windows 7, 64-Bit
    Thread Starter
       #6

    As far as i'm aware (ive rarely been into safe mode) that it has never ever happened there.

    Externally, i'm using a Logitech Wave Multimedia keyboard (USB 2.0) and a Microsoft Habu (USB) Mouse, plugged in. There are no firewire or bluetooth devices plugged in.

    Internal Hardware :
    Asus P5Q Pro Turbo Motherboard with Intel Q9550 CPU installed (not overclocked.)
    4GB (2x 2GB) OCZ Reaper 1066 Memory
    Nvidia 9800 GTX (512mb) GFX
    Creative Soundblaster X-Fi Titanium (PCI-E).
    1TB HDD (Western Digital Green) + 500GB Seagate Barracude (slave.)
      My Computer


  7. Posts : 13
    Windows 7, 64-Bit
    Thread Starter
       #7

    Latest crashdump, this is after i removed the graphics card - and put a new one in. (nvidia gts 250.)

    Memtest passed ok, and now every single piece of hardware has been changed. This is absolutely rediculous.

    This time it crashed when the computer was under more stress (3 games running, winamp and firefox.)
      My Computer


  8. Posts : 28,845
    Win 8 Release candidate 8400
       #8

    Devilish said:
    Latest crashdump, this is after i removed the graphics card - and put a new one in. (nvidia gts 250.)

    Memtest passed ok, and now every single piece of hardware has been changed. This is absolutely rediculous.

    This time it crashed when the computer was under more stress (3 games running, winamp and firefox.)


    It is still being caused by hardware.

    Have you run a chkdsk /r ?
    Code:
    Microsoft (R) Windows Debugger Version 6.11.0001.404 X86
    Copyright (c) Microsoft Corporation. All rights reserved.
    
    
    Loading Dump File [C:\Users\K\Desktop\040210-21855-01.dmp]
    Mini Kernel Dump File: Only registers and stack trace are available
    
    Symbol search path is: SRV*F:\symbols*http://msdl.microsoft.com/download/symbols
    Executable search path is: 
    Windows 7 Kernel Version 7600 MP (4 procs) Free x64
    Product: WinNt, suite: TerminalServer SingleUserTS Personal
    Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
    Machine Name:
    Kernel base = 0xfffff800`03217000 PsLoadedModuleList = 0xfffff800`03454e50
    Debug session time: Fri Apr  2 08:04:35.769 2010 (GMT-4)
    System Uptime: 0 days 0:23:15.220
    Loading Kernel Symbols
    ...............................................................
    ................................................................
    ......................
    Loading User Symbols
    Loading unloaded module list
    .....
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    
    Use !analyze -v to get detailed debugging information.
    
    BugCheck A, {39800000000, e, 1, fffff80003297382}
    
    Probably caused by : hardware ( nt!KiIpiProcessRequests+82 )
    
    Followup: MachineOwner
    ---------
    
    1: 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: 0000039800000000, memory referenced
    Arg2: 000000000000000e, IRQL
    Arg3: 0000000000000001, bitfield :
        bit 0 : value 0 = read operation, 1 = write operation
        bit 3 : value 0 = not an execute operation, 1 = execute operation (only on chips which support this level of status)
    Arg4: fffff80003297382, address which referenced memory
    
    Debugging Details:
    ------------------
    
    
    WRITE_ADDRESS: GetPointerFromAddress: unable to read from fffff800034bf0e0
     0000039800000000 
    
    CURRENT_IRQL:  e
    
    FAULTING_IP: 
    nt!KiIpiProcessRequests+82
    fffff800`03297382 892a            mov     dword ptr [rdx],ebp
    
    CUSTOMER_CRASH_COUNT:  1
    
    DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
    
    BUGCHECK_STR:  0xA
    
    PROCESS_NAME:  winamp.exe
    
    TRAP_FRAME:  fffff880055ac6a0 -- (.trap 0xfffff880055ac6a0)
    NOTE: The trap frame does not contain all registers.
    Some register values may be zeroed or incorrect.
    rax=00000000a2f6def7 rbx=0000000000000000 rcx=fffffa8007366000
    rdx=0000039800000000 rsi=0000000000000000 rdi=0000000000000000
    rip=fffff80003297382 rsp=fffff880055ac838 rbp=00000000055ac908
     r8=fffffa8007dd4a10  r9=0000000000000000 r10=fffff80003580a00
    r11=fffff880055acbd8 r12=0000000000000000 r13=0000000000000000
    r14=0000000000000000 r15=0000000000000000
    iopl=0         nv up ei ng nz ac pe cy
    nt!KiIpiProcessRequests+0x82:
    fffff800`03297382 892a            mov     dword ptr [rdx],ebp ds:6c40:00000398`00000000=????????
    Resetting default scope
    
    MISALIGNED_IP: 
    nt!KiIpiProcessRequests+82
    fffff800`03297382 892a            mov     dword ptr [rdx],ebp
    
    LAST_CONTROL_TRANSFER:  from fffff80003288469 to fffff80003288f00
    
    STACK_TEXT:  
    fffff880`055ac558 fffff800`03288469 : 00000000`0000000a 00000398`00000000 00000000`0000000e 00000000`00000001 : nt!KeBugCheckEx
    fffff880`055ac560 fffff800`032870e0 : 00000000`00000000 fffff8a0`02f1bc30 00000000`000c2462 00000000`000c2462 : nt!KiBugCheckDispatch+0x69
    fffff880`055ac6a0 fffff800`03297382 : fffff880`0ff74e1c fffff880`04013000 fffffa80`07366ca0 00000000`00000000 : nt!KiPageFault+0x260
    fffff880`055ac838 fffff880`02f63180 : fffffa80`041ffb20 fffffa80`07dd4a10 fffff800`0328f1a2 00000000`00000001 : nt!KiIpiProcessRequests+0x82
    fffff880`055ac918 fffffa80`041ffb20 : fffffa80`07dd4a10 fffff800`0328f1a2 00000000`00000001 00001f80`00000000 : 0xfffff880`02f63180
    fffff880`055ac920 fffffa80`07dd4a10 : fffff800`0328f1a2 00000000`00000001 00001f80`00000000 fffffa80`07b97381 : 0xfffffa80`041ffb20
    fffff880`055ac928 fffff800`0328f1a2 : 00000000`00000001 00001f80`00000000 fffffa80`07b97381 00000000`0000030c : 0xfffffa80`07dd4a10
    fffff880`055ac930 fffff800`035809ff : fffff880`055acbd8 00000000`00000000 00000000`00000000 00000000`00000000 : nt!SwapContext_PatchXSave+0x9f
    fffff880`055ac970 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!PspProcessDelete+0x6
    
    
    STACK_COMMAND:  kb
    
    FOLLOWUP_IP: 
    nt!KiIpiProcessRequests+82
    fffff800`03297382 892a            mov     dword ptr [rdx],ebp
    
    SYMBOL_STACK_INDEX:  3
    
    SYMBOL_NAME:  nt!KiIpiProcessRequests+82
    
    FOLLOWUP_NAME:  MachineOwner
    
    IMAGE_NAME:  hardware
    
    DEBUG_FLR_IMAGE_TIMESTAMP:  0
    
    MODULE_NAME: hardware
    
    FAILURE_BUCKET_ID:  X64_IP_MISALIGNED
    
    BUCKET_ID:  X64_IP_MISALIGNED
    
    Followup: MachineOwner
    ---------
      My Computer


  9. Posts : 13
    Windows 7, 64-Bit
    Thread Starter
       #9

    Hi again.

    I've done the chkdsk on it, and it;s come up fine again.

    I did have a secondary HDD attached which had old copies/installations of windows on. Ive disabled/disconnected it permanently now, and it seems more stable.....but not quite.

    latest BSOD (just now) i won't post, but its still and is still an IRQ not or less equal....but the component error was in hidclass.sys.

    is this a relation to the mouse (i have a USB microsoft habu.)?
      My Computer


 

  Related Discussions
Our Sites
Site Links
About Us
Windows 7 Forums is an independent web site and has not been authorized, sponsored, or otherwise approved by Microsoft Corporation. "Windows 7" and related materials are trademarks of Microsoft Corp.

© Designer Media Ltd
All times are GMT -5. The time now is 07:37.
Find Us