blue screen of death

Discussion in 'Software' started by manzoor, Jul 6, 2008.

  1. manzoor

    manzoor Private E-2

    Yet, another BSOD. I'm getting blue screen of death mostly when browsing the net with Firefox and viewing websites which have some sort of flash in em, like youtube.com, manutd.com etc

    What could cause the problem?

    Firefox or Adobe Flash Player ?

    Is there any alternative to Adobe Flash Player.
     
  2. manzoor

    manzoor Private E-2

    I updated Firefox to version 3, and reinstalled the new version of Adobe Flash Player,

    started viewing youtube.com, insidesoccer.com and guess what got another BSOD Damn

    I couldn't get to load the Windows because after having a bsod, my pc restarts at boot times, or windows login screen

    Here's the BSOD error I got

    DRIVER_IRQL_NOT_LESS_OR_EQUAL

    Technical Information:
    *** STOP: 0x000000D1 (0x00000004, 0x00000002, 0x00000001, 0xF7227823)
    USBPORT.SYS - Address F7227823 base at F7214000, DateStamp 4110d62

    It's the one when I was viewing flash content

    After restarting I couldn't load windows and was getting BSODs

    The error then was

    BAD_POOL_HEADER

    0x00000019 (0x00000020, 0x86156000, 0x861561ED, 0x1A3c0000)

    Is it a problem of hardware or software?


    Recently, I haven't added anything new to my pc accept the new HD 160GB

    But I think thats not likely to cause the problem.
     
  3. wildwolf220

    wildwolf220 Oracle of Doom

  4. manzoor

    manzoor Private E-2

    Another BSOD Yet darn lol

    Error

    PFN_LIST_CORRUPT

    0x0000004E (0x00000007, 0x00007EC4, 0x00000000)
     
  5. studiot

    studiot MajorGeek

    Does it happen with a nomal, non usb keyboard or mouse?

    Do you have any other usb devices attached?

    If so what happens if you disconnect them?
     
  6. manzoor

    manzoor Private E-2

    After debugging with WinDB

    I get this, but I don't know how to solve it so please guide me

    Is this a USB Prob ??

    ?

    Code:
    Microsoft (R) Windows Debugger Version 6.9.0003.113 X86
    Copyright (c) Microsoft Corporation. All rights reserved.
    
    
    Loading Dump File [C:\WINDOWS\Minidump\Mini070608-04.dmp]
    Mini Kernel Dump File: Only registers and stack trace are available
    
    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.070227-2254
    Kernel base = 0x804d7000 PsLoadedModuleList = 0x8055c700
    Debug session time: Sun Jul  6 16:40:46.312 2008 (GMT-7)
    System Uptime: 0 days 1:21:06.005
    Loading Kernel Symbols
    ......................................................................................................................
    Loading User Symbols
    Loading unloaded module list
    ..............
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    
    Use !analyze -v to get detailed debugging information.
    
    BugCheck 100000D1, {4, 2, 1, f7227823}
    
    Probably caused by : USBPORT.SYS ( USBPORT!USBPORT_RootHub_EndpointWorker+3f5 )
    
    Followup: MachineOwner
    ---------
    
    1: 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: 00000004, memory referenced
    Arg2: 00000002, IRQL
    Arg3: 00000001, value 0 = read operation, 1 = write operation
    Arg4: f7227823, address which referenced memory
    
    Debugging Details:
    ------------------
    
    
    WRITE_ADDRESS:  00000004 
    
    CURRENT_IRQL:  2
    
    FAULTING_IP: 
    USBPORT!USBPORT_RootHub_EndpointWorker+3f5
    f7227823 895104          mov     dword ptr [ecx+4],edx
    
    CUSTOMER_CRASH_COUNT:  4
    
    DEFAULT_BUCKET_ID:  COMMON_SYSTEM_FAULT
    
    BUGCHECK_STR:  0xD1
    
    PROCESS_NAME:  System
    
    LAST_CONTROL_TRANSFER:  from f721d98c to f7227823
    
    STACK_TEXT:  
    f7b0fd10 f721d98c 85f90c68 80545d0c 8608d008 USBPORT!USBPORT_RootHub_EndpointWorker+0x3f5
    f7b0fd38 f722141a 86202028 00000003 86202028 USBPORT!USBPORT_CoreEndpointWorker+0x6d2
    f7b0fd7c f7219fc0 86202028 00000000 8603db18 USBPORT!USBPORT_Worker+0x212
    f7b0fdac 805ce84c 86202028 00000000 00000000 USBPORT!USBPORT_WorkerThread+0x12a
    f7b0fddc 8054532e f7219e96 86202028 00000000 nt!PspSystemThreadStartup+0x34
    00000000 00000000 00000000 00000000 00000000 nt!KiThreadStartup+0x16
    
    
    STACK_COMMAND:  kb
    
    FOLLOWUP_IP: 
    USBPORT!USBPORT_RootHub_EndpointWorker+3f5
    f7227823 895104          mov     dword ptr [ecx+4],edx
    
    SYMBOL_STACK_INDEX:  0
    
    SYMBOL_NAME:  USBPORT!USBPORT_RootHub_EndpointWorker+3f5
    
    FOLLOWUP_NAME:  MachineOwner
    
    MODULE_NAME: USBPORT
    
    IMAGE_NAME:  USBPORT.SYS
    
    DEBUG_FLR_IMAGE_TIMESTAMP:  41107d62
    
    FAILURE_BUCKET_ID:  0xD1_W_USBPORT!USBPORT_RootHub_EndpointWorker+3f5
    
    BUCKET_ID:  0xD1_W_USBPORT!USBPORT_RootHub_EndpointWorker+3f5
    
    Followup: MachineOwner
    ---------
    
    
     
  7. manzoor

    manzoor Private E-2

    I have a USB Mouse,

    But it mainly happens when viewing website with flash content

    I today got five BSOD

    I'm gonna post them all

    Code:
    Microsoft (R) Windows Debugger Version 6.9.0003.113 X86
    Copyright (c) Microsoft Corporation. All rights reserved.
    
    
    Loading Dump File [C:\WINDOWS\Minidump\Mini070608-03.dmp]
    Mini Kernel Dump File: Only registers and stack trace are available
    
    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.070227-2254
    Kernel base = 0x804d7000 PsLoadedModuleList = 0x8055c700
    Debug session time: Sun Jul  6 13:12:22.390 2008 (GMT-7)
    System Uptime: 0 days 0:02:13.078
    Loading Kernel Symbols
    ...........................................................................................................................
    Loading User Symbols
    Loading unloaded module list
    .....
    Unable to load image inspect.sys, Win32 error 0n2
    *** WARNING: Unable to verify timestamp for inspect.sys
    *** ERROR: Module load completed but symbols could not be loaded for inspect.sys
    *** ERROR: Symbol file could not be found.  Defaulted to export symbols for NDIS.SYS - 
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    
    Use !analyze -v to get detailed debugging information.
    
    BugCheck 100000D1, {0, 2, 1, f741e350}
    
    *** ERROR: Symbol file could not be found.  Defaulted to export symbols for psched.sys - 
    *** WARNING: Unable to verify timestamp for Rtnicxp.sys
    *** ERROR: Module load completed but symbols could not be loaded for Rtnicxp.sys
    Probably caused by : inspect.sys ( inspect+5350 )
    
    Followup: MachineOwner
    ---------
    
    0: 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: 00000000, memory referenced
    Arg2: 00000002, IRQL
    Arg3: 00000001, value 0 = read operation, 1 = write operation
    Arg4: f741e350, address which referenced memory
    
    Debugging Details:
    ------------------
    
    
    WRITE_ADDRESS:  00000000 
    
    CURRENT_IRQL:  2
    
    FAULTING_IP: 
    inspect+5350
    f741e350 8908            mov     dword ptr [eax],ecx
    
    CUSTOMER_CRASH_COUNT:  3
    
    DEFAULT_BUCKET_ID:  DRIVER_FAULT
    
    BUGCHECK_STR:  0xD1
    
    PROCESS_NAME:  ekrn.exe
    
    LAST_CONTROL_TRANSFER:  from f740fd02 to f741e350
    
    STACK_TEXT:  
    WARNING: Stack unwind information not available. Following frames may be wrong.
    f7a53e98 f740fd02 85daa278 85dd4000 85dcbf5c inspect+0x5350
    f7a53ecc f6ae75d7 00000008 85dd4000 85dcbf5c NDIS!EthFilterDprIndicateReceive+0x20c
    f7a53f0c f740fbd6 8607c008 85dd4000 85dcbf5c psched!RegisterPsComponent+0x72a9
    f7a53f40 f700beb2 8618ad58 85dd4000 85dcbf5c NDIS!EthFilterDprIndicateReceive+0xe0
    f7a53f74 f700c276 00000060 8052a550 85dd4000 Rtnicxp+0xbeb2
    f7a53f88 f700c314 85dd4000 8052a550 85dd4000 Rtnicxp+0xc276
    f7a53fa0 f700627a 00dd4000 861b06c0 f7a53fcc Rtnicxp+0xc314
    f7a53fb0 f7408712 85dd4000 85e08bb0 ffdff9c0 Rtnicxp+0x627a
    f7a53fcc 805450bf 85dd416c 85dd4158 00000000 NDIS!NdisMIndicateStatusComplete+0x1a75
    f7a53ff4 80544c2b edd50d44 00000000 00000000 nt!KiRetireDpcList+0x61
    f7a53ff8 edd50d44 00000000 00000000 00000000 nt!KiDispatchInterrupt+0x2b
    80544c2b 00000000 00000009 0081850f bb830000 0xedd50d44
    
    
    STACK_COMMAND:  kb
    
    FOLLOWUP_IP: 
    inspect+5350
    f741e350 8908            mov     dword ptr [eax],ecx
    
    SYMBOL_STACK_INDEX:  0
    
    SYMBOL_NAME:  inspect+5350
    
    FOLLOWUP_NAME:  MachineOwner
    
    MODULE_NAME: inspect
    
    IMAGE_NAME:  inspect.sys
    
    DEBUG_FLR_IMAGE_TIMESTAMP:  48344138
    
    FAILURE_BUCKET_ID:  0xD1_W_inspect+5350
    
    BUCKET_ID:  0xD1_W_inspect+5350
    
    Followup: MachineOwner
    ---------
    
    
    Code:
    Microsoft (R) Windows Debugger Version 6.9.0003.113 X86
    Copyright (c) Microsoft Corporation. All rights reserved.
    
    
    Loading Dump File [C:\WINDOWS\Minidump\Mini070608-05.dmp]
    Mini Kernel Dump File: Only registers and stack trace are available
    
    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.070227-2254
    Kernel base = 0x804d7000 PsLoadedModuleList = 0x8055c700
    Debug session time: Sun Jul  6 17:23:30.203 2008 (GMT-7)
    System Uptime: 0 days 0:35:21.905
    Loading Kernel Symbols
    ......................................................................................................................
    Loading User Symbols
    Loading unloaded module list
    ............
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    
    Use !analyze -v to get detailed debugging information.
    
    BugCheck 4E, {7, aec4, 10, 0}
    
    Probably caused by : memory_corruption ( nt!MiDispatchFault+3b0 )
    
    Followup: MachineOwner
    ---------
    
    1: kd> !analyze -v
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    
    PFN_LIST_CORRUPT (4e)
    Typically caused by drivers passing bad memory descriptor lists (ie: calling
    MmUnlockPages twice with the same list, etc).  If a kernel debugger is
    available get the stack trace.
    Arguments:
    Arg1: 00000007, A driver has unlocked a page more times than it locked it
    Arg2: 0000aec4, page frame number
    Arg3: 00000010, current share count
    Arg4: 00000000, 0
    
    Debugging Details:
    ------------------
    
    
    BUGCHECK_STR:  0x4E_7
    
    CUSTOMER_CRASH_COUNT:  5
    
    DEFAULT_BUCKET_ID:  COMMON_SYSTEM_FAULT
    
    PROCESS_NAME:  MRT.exe
    
    TRAP_FRAME:  eddeab38 -- (.trap 0xffffffffeddeab38)
    ErrCode = 00000000
    eax=5a249000 ebx=00000001 ecx=c0601688 edx=00000000 esi=00000000 edi=85b4ed20
    eip=80517037 esp=eddeabac ebp=eddeac04 iopl=0         nv up ei ng nz na pe cy
    cs=0008  ss=0010  ds=0023  es=0023  fs=0030  gs=0000             efl=00010287
    nt!MiSetPageModified+0xdf:
    80517037 8a00            mov     al,byte ptr [eax]          ds:0023:5a249000=??
    Resetting default scope
    
    LAST_CONTROL_TRANSFER:  from 80521fdf to 804f9deb
    
    STACK_TEXT:  
    eddeaa2c 80521fdf 0000004e 00000007 0000aec4 nt!KeBugCheckEx+0x1b
    eddeaa4c 80515b14 81c14930 c02d1248 e13dea88 nt!MiDecrementReferenceCount+0x33
    eddeaab4 8051fdca e13dea88 5a249000 c02d1248 nt!MiDispatchFault+0x3b0
    eddeab20 805437c8 00000000 5a249000 00000000 nt!MmAccessFault+0x111c
    eddeab20 80517037 00000000 5a249000 00000000 nt!KiTrap0E+0xd0
    eddeac04 805afd5a 85f67b58 5a249000 85b4ed20 nt!MiSetPageModified+0xdf
    eddeac48 805b0976 85c77650 5a100000 eddead18 nt!MiMapViewOfImageSection+0x382
    eddeaca4 805b0d3b 00000004 85b4ee10 eddead18 nt!MmMapViewOfSection+0x13c
    eddead34 8054086c 00000088 ffffffff 0006f418 nt!NtMapViewOfSection+0x2bd
    eddead34 7c90eb94 00000088 ffffffff 0006f418 nt!KiFastCallEntry+0xfc
    WARNING: Frame IP not in any known module. Following frames may be wrong.
    0006f434 00000000 00000000 00000000 00000000 0x7c90eb94
    
    
    STACK_COMMAND:  kb
    
    FOLLOWUP_IP: 
    nt!MiDispatchFault+3b0
    80515b14 8b55ec          mov     edx,dword ptr [ebp-14h]
    
    SYMBOL_STACK_INDEX:  2
    
    SYMBOL_NAME:  nt!MiDispatchFault+3b0
    
    FOLLOWUP_NAME:  MachineOwner
    
    MODULE_NAME: nt
    
    DEBUG_FLR_IMAGE_TIMESTAMP:  45e53f9d
    
    IMAGE_NAME:  memory_corruption
    
    FAILURE_BUCKET_ID:  0x4E_7_nt!MiDispatchFault+3b0
    
    BUCKET_ID:  0x4E_7_nt!MiDispatchFault+3b0
    
    Followup: MachineOwner
    ---------
    
    
    Code:
    Microsoft (R) Windows Debugger Version 6.9.0003.113 X86
    Copyright (c) Microsoft Corporation. All rights reserved.
    
    
    Loading Dump File [C:\WINDOWS\Minidump\Mini070608-01.dmp]
    Mini Kernel Dump File: Only registers and stack trace are available
    
    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.070227-2254
    Kernel base = 0x804d7000 PsLoadedModuleList = 0x8055c700
    Debug session time: Sun Jul  6 03:35:04.328 2008 (GMT-7)
    System Uptime: 0 days 2:19:42.037
    Loading Kernel Symbols
    .....................................................................................................................
    Loading User Symbols
    Loading unloaded module list
    .................
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    
    Use !analyze -v to get detailed debugging information.
    
    BugCheck 1000000A, {10039, 1c, 1, 805021b4}
    
    Probably caused by : ntkrpamp.exe ( nt!KiUnlinkThread+c )
    
    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: 00010039, memory referenced
    Arg2: 0000001c, IRQL
    Arg3: 00000001, 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: 805021b4, address which referenced memory
    
    Debugging Details:
    ------------------
    
    
    WRITE_ADDRESS:  00010039 
    
    CURRENT_IRQL:  1c
    
    FAULTING_IP: 
    nt!KiUnlinkThread+c
    805021b4 8916            mov     dword ptr [esi],edx
    
    CUSTOMER_CRASH_COUNT:  1
    
    DEFAULT_BUCKET_ID:  DRIVER_FAULT
    
    BUGCHECK_STR:  0xA
    
    PROCESS_NAME:  Idle
    
    LAST_CONTROL_TRANSFER:  from 80502216 to 805021b4
    
    STACK_TEXT:  
    805502b0 80502216 85a9d3c0 85a9d3c8 00000102 nt!KiUnlinkThread+0xc
    805502c4 8050240d 00000000 805502e0 00000000 nt!KiUnwaitThread+0x12
    805502f0 80501626 8415612a 00000082 80550418 nt!KiWaitTest+0xab
    805503fc 80501813 8055b0a0 ffdff9c0 ffdff000 nt!KiTimerListExpire+0x7a
    80550428 805450bf 8055b4a0 00000000 00082f82 nt!KiTimerExpiration+0xb1
    80550440 8055ae40 ffdffc50 00000000 8055ae40 nt!KiRetireDpcList+0x61
    80550450 80544fa4 00000000 0000000e 00000000 nt!KiIdleThread0
    80550454 00000000 0000000e 00000000 00000000 nt!KiIdleLoop+0x28
    
    
    STACK_COMMAND:  kb
    
    FOLLOWUP_IP: 
    nt!KiUnlinkThread+c
    805021b4 8916            mov     dword ptr [esi],edx
    
    SYMBOL_STACK_INDEX:  0
    
    SYMBOL_NAME:  nt!KiUnlinkThread+c
    
    FOLLOWUP_NAME:  MachineOwner
    
    MODULE_NAME: nt
    
    IMAGE_NAME:  ntkrpamp.exe
    
    DEBUG_FLR_IMAGE_TIMESTAMP:  45e53f9d
    
    FAILURE_BUCKET_ID:  0xA_W_nt!KiUnlinkThread+c
    
    BUCKET_ID:  0xA_W_nt!KiUnlinkThread+c
    
    Followup: MachineOwner
    ---------
    
    
     
  8. manzoor

    manzoor Private E-2

    Removed the USB Mouse and then started viewing some flash websites but still i'm getting the BSODs Whats causing the problem ?

    I think there isn't any thing wrong with the USB PORT
     
  9. studiot

    studiot MajorGeek

  10. jenritz2k3

    jenritz2k3 Private E-2

    sir try to use minipi or hiren's bootable cd run the harddisk repair software. hope it helps.
     
  11. studiot

    studiot MajorGeek


MajorGeeks.Com Menu

Downloads All In One Tweaks \ Android \ Anti-Malware \ Anti-Virus \ Appearance \ Backup \ Browsers \ CD\DVD\Blu-Ray \ Covert Ops \ Drive Utilities \ Drivers \ Graphics \ Internet Tools \ Multimedia \ Networking \ Office Tools \ PC Games \ System Tools \ Mac/Apple/Ipad Downloads

Other News: Top Downloads \ News (Tech) \ Off Base (Other Websites News) \ Way Off Base (Offbeat Stories and Pics)

Social: Facebook \ YouTube \ Twitter \ Tumblr \ Pintrest \ RSS Feeds