1. You are viewing our forum as a guest. For full access please Register. WindowsBBS.com is completely free, paid for by advertisers and donations.

I've been having random blue screens...

Discussion in 'Windows XP' started by ryanrenegade, 2008/10/16.

  1. 2008/10/16
    ryanrenegade

    ryanrenegade Inactive Thread Starter

    Joined:
    2008/10/16
    Messages:
    4
    Likes Received:
    0
    there is also no pattern to them, It was just idling then all of a sudden blue screen.

    *******************************************************************************
    * *
    * Bugcheck Analysis *
    * *
    *******************************************************************************

    KERNEL_MODE_EXCEPTION_NOT_HANDLED_M (1000008e)
    This is a very common bugcheck. Usually the exception address pinpoints
    the driver/function that caused the problem. Always note this address
    as well as the link date of the driver/image that contains this address.
    Some common problems are exception code 0x80000003. This means a hard
    coded breakpoint or assertion was hit, but this system was booted
    /NODEBUG. This is not supposed to happen as developers should never have
    hardcoded breakpoints in retail code, but ...
    If this happens, make sure a debugger gets connected, and the
    system is booted /DEBUG. This will let us see why this breakpoint is
    happening.
    Arguments:
    Arg1: c0000005, The exception code that was not handled
    Arg2: 805a1eab, The address that the exception occurred at
    Arg3: b52cd3f0, Trap Frame
    Arg4: 00000000

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


    EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at "0x%08lx" referenced memory at "0x%08lx ". The memory could not be "%s ".

    FAULTING_IP:
    nt!NtRequestWaitReplyPort+711
    805a1eab 0100 add dword ptr [eax],eax

    TRAP_FRAME: b52cd3f0 -- (.trap 0xffffffffb52cd3f0)
    ErrCode = 00000002
    eax=082069a0 ebx=89429460 ecx=8aedeb38 edx=00000000 esi=88b06990 edi=8895b3c0
    eip=805a1eab esp=b52cd464 ebp=b52cd548 iopl=0 nv up ei pl nz na pe nc
    cs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000 efl=00010206
    nt!NtRequestWaitReplyPort+0x711:
    805a1eab 0100 add dword ptr [eax],eax ds:0023:082069a0=????????
    Resetting default scope

    CUSTOMER_CRASH_COUNT: 1

    DEFAULT_BUCKET_ID: DRIVER_FAULT

    BUGCHECK_STR: 0x8E

    PROCESS_NAME: svchost.exe

    MISALIGNED_IP:
    nt!NtRequestWaitReplyPort+711
    805a1eab 0100 add dword ptr [eax],eax

    LAST_CONTROL_TRANSFER: from 805bdd10 to 805a1eab

    STACK_TEXT:
    b52cd548 805bdd10 8aeff900 00000000 88b06990 nt!NtRequestWaitReplyPort+0x711
    b52cd5c0 805ba398 00000000 b52cd600 00000240 nt!ObpLookupObjectName+0x53c
    b52cd614 80574e4d 00000000 00000000 00000000 nt!ObOpenObjectByName+0xea
    b52cd690 8057583a b52cd748 00100001 b52cd728 nt!IopCreateFile+0x407
    b52cd6d8 ba7010bd b52cd748 00100001 b52cd728 nt!IoCreateFileSpecifyDeviceObjectHint+0x52
    b52cd74c ba70132b 8930ac58 b52cd784 ba701864 fltMgr!FltpNormalizeNameComponent+0x75
    b52cd758 ba701864 8930ac58 00000000 8930ac58 fltMgr!FltpCallNormalizeNameComponentHandler+0x41
    b52cd784 ba702590 0000002a 00000000 8930ac58 fltMgr!FltpExpandShortNames+0x110
    b52cd7a0 ba702ba1 0000ac58 00000000 000000fe fltMgr!FltpGetNormalizedFileNameWorker+0x90
    b52cd7b8 ba70075e 8930ac58 00000000 8930ac58 fltMgr!FltpGetNormalizedFileName+0x19
    b52cd7d0 ba7007a9 80553000 8930ac58 b52cd80c fltMgr!FltpCreateFileNameInformation+0x84
    b52cd7e0 ba6f1bfb 8930ac58 00000000 88a3a7b8 fltMgr!CreateTemporaryFileNameInformation+0xf
    b52cd80c ba6f2142 8930ac58 88ca5694 88ca5694 fltMgr!FltpGetFileNameInformation+0xdf
    b52cd830 b535dcc3 88ca5694 00000101 b52cd864 fltMgr!FltGetFileNameInformation+0x106
    WARNING: Stack unwind information not available. Following frames may be wrong.
    b52cd844 b5368e63 88ca5694 00000101 b52cd864 bdfsfltr+0x5cc3
    b52cd868 b5359037 88ca5694 00000003 b52cd948 bdfsfltr+0x10e63
    b52cd978 ba6ed944 88ca5694 b52cd998 b52cd9c8 bdfsfltr+0x1037
    b52cd9d8 ba6ef352 002cda1c 88ca5638 00000000 fltMgr!FltpPerformPreCallbacks+0x2d4
    b52cd9ec ba6fbccb b52cda1c ba6fa094 00000000 fltMgr!FltpPassThroughInternal+0x32
    b52cda04 ba6fc142 b52cda1c 88a3dba0 8ae5b368 fltMgr!FltpCreateInternal+0x63
    b52cda38 804eeeb1 894dbb68 88a3dd68 8ad65ac0 fltMgr!FltpCreate+0x1d2
    b52cda48 b5a34330 00000000 88a3dd68 893fc6d0 nt!IopfCallDriver+0x31
    b52cda5c b5a33bce 893fc618 88a3db90 893fc6d0 trufos+0x1330
    b52cda70 804eeeb1 893fc618 88a3db90 88a3db90 trufos+0xbce
    b52cda80 80581ec2 8aeff8e8 889dca14 b52cdc18 nt!IopfCallDriver+0x31
    b52cdb60 805bdd10 8aeff900 00000000 889dc970 nt!IopParseDevice+0xa58
    b52cdbd8 805ba398 00000000 b52cdc18 00000040 nt!ObpLookupObjectName+0x53c
    b52cdc2c 80574e4d 00000000 00000000 00000001 nt!ObOpenObjectByName+0xea
    b52cdca8 805757c4 049dee30 00100001 049dedd4 nt!IopCreateFile+0x407
    b52cdd04 80578f83 049dee30 00100001 049dedd4 nt!IoCreateFile+0x8e
    b52cdd44 8054060c 049dee30 00100001 049dedd4 nt!NtOpenFile+0x27
    b52cdd44 7c90eb94 049dee30 00100001 049dedd4 nt!KiFastCallEntry+0xfc
    049df0a0 00000000 00000000 00000000 00000000 0x7c90eb94


    STACK_COMMAND: kb

    FOLLOWUP_IP:
    bdfsfltr+5cc3
    b535dcc3 ?? ???

    SYMBOL_STACK_INDEX: e

    SYMBOL_NAME: bdfsfltr+5cc3

    FOLLOWUP_NAME: MachineOwner

    MODULE_NAME: hardware

    IMAGE_NAME: hardware

    DEBUG_FLR_IMAGE_TIMESTAMP: 0

    FAILURE_BUCKET_ID: IP_MISALIGNED

    BUCKET_ID: IP_MISALIGNED

    Followup: MachineOwner
    ---------
     
    ryanrenegade,
    #1
  2. 2008/10/16
    retiredlearner

    retiredlearner SuperGeek WindowsBBS Team Member

    Joined:
    2004/06/25
    Messages:
    7,214
    Likes Received:
    514
    Hi, can you give some more info on whether you have added new Hardware/Software recently. PC specs and what's running. Thanks Neil.
     
    retiredlearner,
    #2


  3. to hide this advert.

  4. 2008/10/16
    TJGarner

    TJGarner Well-Known Member

    Joined:
    2008/10/12
    Messages:
    72
    Likes Received:
    0
    Just a shot in the dark, does the BSOD disappear when you hit a key or move the mouse? I recently worked on a PC that had a virus that had a Screen Saver of the BSOD and a XP reload screen - to make it look like a real BSOD.
     
    TJGarner,
    #3
  5. 2008/10/16
    ryanrenegade

    ryanrenegade Inactive Thread Starter

    Joined:
    2008/10/16
    Messages:
    4
    Likes Received:
    0
    I believe i've fixed it it was a problem with BitDefender, and the ram voltage was set at 2.20 instead of 2.10.

    Also the people who overclocked this machine for me overclocked the video card to the point to where it destorts game graphics.

    However, thanks for the replies.
     
    ryanrenegade,
    #4
  6. 2008/10/17
    ryanrenegade

    ryanrenegade Inactive Thread Starter

    Joined:
    2008/10/16
    Messages:
    4
    Likes Received:
    0
    Processor: IntelCore2DuoE8600 3.33ghz OC'd to 4.0
    Ram: 4GB, OCZ Reaper HPC OCZ2RPR10664GK
    GPU: EVGA geForce GTX 280
    HDD: 1x 70gig Raptor(10,000), 1x 150 gig seagate(7200), 1x 300 gig Western Digital(7200)
    Audio: Sound Blaster Audigy 2 ZS
    Motherboard: Asus Rampage Formula
    OS: Windows XP Professional SP2

    apparently its not fixed... so here's another copy and paste. This computer was barely built this tuesday. So its basically brand new.

    I was playing Unreal Tournament when all of a sudden WHAM, BSOD.

    *******************************************************************************
    * *
    * Bugcheck Analysis *
    * *
    *******************************************************************************

    KERNEL_MODE_EXCEPTION_NOT_HANDLED_M (1000008e)
    This is a very common bugcheck. Usually the exception address pinpoints
    the driver/function that caused the problem. Always note this address
    as well as the link date of the driver/image that contains this address.
    Some common problems are exception code 0x80000003. This means a hard
    coded breakpoint or assertion was hit, but this system was booted
    /NODEBUG. This is not supposed to happen as developers should never have
    hardcoded breakpoints in retail code, but ...
    If this happens, make sure a debugger gets connected, and the
    system is booted /DEBUG. This will let us see why this breakpoint is
    happening.
    Arguments:
    Arg1: c0000005, The exception code that was not handled
    Arg2: 805a4fd0, The address that the exception occurred at
    Arg3: b57e49d0, Trap Frame
    Arg4: 00000000

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


    EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at "0x%08lx" referenced memory at "0x%08lx ". The memory could not be "%s ".

    FAULTING_IP:
    nt!LpcpFreeToPortZone+42
    805a4fd0 8908 mov dword ptr [eax],ecx

    TRAP_FRAME: b57e49d0 -- (.trap 0xffffffffb57e49d0)
    ErrCode = 00000002
    eax=00000000 ebx=8055c0a0 ecx=00600008 edx=00000000 esi=8949c3f8 edi=00000000
    eip=805a4fd0 esp=b57e4a44 ebp=b57e4a60 iopl=0 nv up ei pl nz na po cy
    cs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000 efl=00010203
    nt!LpcpFreeToPortZone+0x42:
    805a4fd0 8908 mov dword ptr [eax],ecx ds:0023:00000000=????????
    Resetting default scope

    CUSTOMER_CRASH_COUNT: 1

    DEFAULT_BUCKET_ID: DRIVER_FAULT

    BUGCHECK_STR: 0x8E

    PROCESS_NAME: UT3.exe

    LAST_CONTROL_TRANSFER: from 805a1ed7 to 805a4fd0

    STACK_TEXT:
    b57e4a60 805a1ed7 8058151b 895e3678 8af1eb38 nt!LpcpFreeToPortZone+0x42
    b57e4b4c 805bdd10 8aebc900 00000000 895e3668 nt!NtRequestWaitReplyPort+0x73d
    b57e4bc4 805ba398 00000000 b57e4c04 00000040 nt!ObpLookupObjectName+0x53c
    b57e4c18 80574e4d 00000000 00000000 db0d0001 nt!ObOpenObjectByName+0xea
    b57e4c94 805757c4 0032f744 80100080 0032f6e4 nt!IopCreateFile+0x407
    b57e4cf0 80577e8e 0032f744 80100080 0032f6e4 nt!IoCreateFile+0x8e
    b57e4d30 8054060c 0032f744 80100080 0032f6e4 nt!NtCreateFile+0x30
    b57e4d30 7c90eb94 0032f744 80100080 0032f6e4 nt!KiFastCallEntry+0xfc
    WARNING: Frame IP not in any known module. Following frames may be wrong.
    0032f73c 00000000 00000000 00000000 00000000 0x7c90eb94


    STACK_COMMAND: kb

    FOLLOWUP_IP:
    nt!LpcpFreeToPortZone+42
    805a4fd0 8908 mov dword ptr [eax],ecx

    SYMBOL_STACK_INDEX: 0

    SYMBOL_NAME: nt!LpcpFreeToPortZone+42

    FOLLOWUP_NAME: MachineOwner

    MODULE_NAME: nt

    IMAGE_NAME: ntkrpamp.exe

    DEBUG_FLR_IMAGE_TIMESTAMP: 41107b0d

    FAILURE_BUCKET_ID: 0x8E_nt!LpcpFreeToPortZone+42

    BUCKET_ID: 0x8E_nt!LpcpFreeToPortZone+42

    Followup: MachineOwner
    ---------
     
    ryanrenegade,
    #5
  7. 2008/10/17
    PeteC

    PeteC SuperGeek Staff

    Joined:
    2002/05/10
    Messages:
    28,896
    Likes Received:
    389
    I wouls suspect a hardware problem - rather than troubleshoot it yourself return it to whoever built it for them to sort out.
     
    PeteC,
    #6
  8. 2008/10/17
    ryanrenegade

    ryanrenegade Inactive Thread Starter

    Joined:
    2008/10/16
    Messages:
    4
    Likes Received:
    0
    ahh well see thats where the problem lies, i built it myself.
     
    ryanrenegade,
    #7
  9. 2008/10/17
    PeteC

    PeteC SuperGeek Staff

    Joined:
    2002/05/10
    Messages:
    28,896
    Likes Received:
    389
    Before you proceed with any troubleshooting you should remove the overclock settings and revert back to standard and see if the problem remains.

    Would you please confirm that you loaded the chipset drivers for the motherboard.

    I would start by checking the RAM ....

    The only satisfactory way of testing RAM is to test the installed RAM in various configurations. If you have a single module swap it around the slots. If you have a pair of modules run each one singly, swapping between slots; then run them in pairs swapping between pairs of slots. If you have 2 sets of matched modules do not get them mixed up.
     
    PeteC,
    #8

Share This Page

  1. This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
    By continuing to use this site, you are consenting to our use of cookies.
    Accept Learn More...