locked
Having repeated BSOD's with Windows 7 RRS feed

  • Question

  • After looking through other threads, figured I would just go with the suggestions to create my own thread about my specific problem.  I have random BSOD's, which are occurring more often than before. First off, ANY updates I was prompted to install, starting with the service packs, caused my system to not be able to restart until I recovered the system from previous dates.  I have now just been relegated to hiding any new updates the computer is prompted to install, but that was about 5 days ago.  Now, my computer blue screens every few days, and when it tries to restart itself, it will either make it to the Windows log in screen, but restart after I enter my password, or it will restart before getting to that point, and continuously loop restarting.  Safe Mode is a crap shoot, as it makes it there sometimes, and others it will restart before booting in safe mode.  I can eventually get the computer back up and running, but typically just waiting an hour or two is how that happens...

     

    I cant post the exact error code that happened, but if anyone can lemme know how to post the .dmp file I will gladly do so.

     

    Thanks in advance.

     

    Kyle

    Thursday, November 17, 2011 3:12 AM

Answers

  • OK, I looked at the rest and the driver/issue being blamed jumos around
    a lot. This usually points to a memory issue. Can you get back to me
    with the memtest86+ results?
     

    -- Mike Burr
    Technology
    • Proposed as answer by Niki Han Wednesday, November 23, 2011 8:00 AM
    • Marked as answer by Niki Han Friday, November 25, 2011 9:33 AM
    Thursday, November 17, 2011 6:05 AM

All replies

  • Sorry to hear about your troubles, it sounds like there are some fairly
    serious issues occurring. Without knowing more, it might be worth giving
    a memory check a shot with memtest86+,
     
     
    If you can get the system to boot for long enough, can you pull off any
    memory dumps and upload them to skydrive, they will be in
    c:\windows\minidump by default for Windows 7,
     
     
    If you want to have a look at them too, I wrote a post on basic
    debugging as well as a couple of posts on more common issues,
     
     
    Based on the issues that you describe, it may be worth doing a rebuild
    after we identify and resolve any hardware issues.
     

    -- Mike Burr
    Technology
    Thursday, November 17, 2011 4:09 AM
  • Thank you for the response.  This build is now a year and 2 months old, so I would REALLY like to not drop a lotta money into a new one, but I will attempt to upload them through skydrive.  It wasn't allowing me permission to link the latest, or any, .dmp files in there, so I just copy and pasted one of the latest in there and uploaded the copied version.

     

    Hope this works:

    <iframe title ="Preview" scrolling="no" marginheight="0" marginwidth="0" frameborder="0" style="width:98px;height:115px;padding:0;background-color:#fcfcfc;" src="https://skydrive.live.com/embedicon.aspx/.Documents/Public/111611-22526-01%20-%20Copy.dmp?cid=34f245e36d1190a8&sc=documents"></iframe>

    • Edited by tituskb Thursday, November 17, 2011 5:14 AM
    Thursday, November 17, 2011 5:13 AM
  • So it isn't seeming to work... I followed the directions in your link and copied that directly from the Embed tool in SkyDrive?  I will keep trying I guess.

     

    Kyle

    Thursday, November 17, 2011 5:17 AM
  • Do you have any firewire devices plugged in, the dump that I was able to
    get identified the firewire driver as a potential cause,
     
    1: kd>  !analyze -v
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
     
    SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M (1000007e)
    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: ffffffffc0000005, The exception code that was not handled
    Arg2: fffff88000db5992, The address that the exception occurred at
    Arg3: fffff880031bd118, Exception Record Address
    Arg4: fffff880031bc980, Context Record Address
     
    Debugging Details:
    ------------------
     EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.
     
    FAULTING_IP:
    +3436656231323433
    00000000`00000000 ??              ???
     
    EXCEPTION_RECORD:  fffff880031bd118 -- (.exr 0xfffff880031bd118)
    ExceptionAddress: fffff88000db5992 (Wdf01000!imp_WdfObjectGetTypedContextWorker+0x000000000000006a)
       ExceptionCode: c0000005 (Access violation)
      ExceptionFlags: 00000000
    NumberParameters: 2
       Parameter[0]: 0000000000000000
       Parameter[1]: 0000000000000020
    Attempt to read from address 0000000000000020
     
    CONTEXT:  fffff880031bc980 -- (.cxr 0xfffff880031bc980)
    rax=0000000000000000 rbx=0000000000000000 rcx=fffffa8005e88770
    rdx=0000057ffa177888 rsi=fffffa800492cdd0 rdi=fffffa8005d71a00
    rip=fffff88000db5992 rsp=fffff880031bd350 rbp=0000000000000000
     r8=0000000000000018  r9=0000000000000000 r10=fffffa8004edec80
    r11=fffffa8005e8f1b8 r12=0000000000000000 r13=0000000000000000
    r14=0000000000000000 r15=fffff88000dd80f0
    iopl=0         nv up ei pl zr na po nc
    cs=0010  ss=0018  ds=002b  es=002b  fs=0053  gs=002b             efl=00010246
    Wdf01000!imp_WdfObjectGetTypedContextWorker+0x6a:
    fffff880`00db5992 4d394808        cmp     qword ptr [r8+8],r9 ds:002b:00000000`00000020=????????????????
    Resetting default scope
     
    PROCESS_NAME:  System
     
    CURRENT_IRQL:  0
     
    ERROR_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.
     
    EXCEPTION_PARAMETER1:  00000000fffff880
     
    EXCEPTION_PARAMETER2:  0000000000000002
     
    EXCEPTION_PARAMETER3:  0000000000000000
     
    EXCEPTION_PARAMETER4: 0
     
    WRITE_ADDRESS: GetPointerFromAddress: unable to read from fffff80003cfb0e0
     0000000000000002
     
    FOLLOWUP_IP:
    1394ohci!AsyncTx::Prepare+97
    fffff880`0426f08b 48894740        mov     qword ptr [rdi+40h],rax
     
    FAILED_INSTRUCTION_ADDRESS:
    +97
    00000000`00000000 ??              ???
     
    BUGCHECK_STR:  0x7E
     
    DEFAULT_BUCKET_ID:  NULL_CLASS_PTR_DEREFERENCE
     
    LOCK_ADDRESS:  fffff80003cc7420 -- (!locks fffff80003cc7420)
     
    Resource @ nt!PiEngineLock (0xfffff80003cc7420)    Available
     
    WARNING: SystemResourcesList->Flink chain invalid. Resource may be corrupted, or already deleted.
     WARNING: SystemResourcesList->Blink chain invalid. Resource may be corrupted, or already deleted.
     
    1 total locks
     
    PNP_TRIAGE:
        Lock address  : 0xfffff80003cc7420
        Thread Count  : 0
        Thread address: 0x0000000000000000
        Thread wait   : 0x0
     
    LAST_CONTROL_TRANSFER:  from fffff8800426f08b to fffff88000db5992
     
    STACK_TEXT:
    fffff880`031bd350 fffff880`0426f08b : fffff880`00dd0000 fffffa80`00000000 fffff880`04297628 fffff880`0428cee2 : Wdf01000!imp_WdfObjectGetTypedContextWorker+0x6a
    fffff880`031bd3a0 fffff880`04286562 : 00000000`00000000 00000000`00000000 fffffa80`0492cdd0 fffffa80`05d6c960 : 1394ohci!AsyncTx::Prepare+0x97
    fffff880`031bd410 fffff880`042853a1 : 0000057f`fa293a08 0000057f`fb6d42a8 0000057f`fb6d42a8 00000000`00000000 : 1394ohci!OhciDevice::PrepareObjects+0x1ce
    fffff880`031bd450 fffff880`00dcacfe : fffffa80`05d72020 fffff880`031bd510 00000000`00000000 fffffa80`05d72020 : 1394ohci!OhciDevice::WdfEvtDevicePrepareHardware+0x6d
    fffff880`031bd490 fffff880`00dc99ce : fffffa80`05e45770 00000000`00000108 00000000`00000000 00000000`00000000 : Wdf01000!FxPkgPnp::PnpPrepareHardware+0x8e
    fffff880`031bd4d0 fffff880`00dc9841 : 00000000`00000101 00000000`00000108 00000000`00000108 fffff800`03a82300 : Wdf01000!FxPkgPnp::PnpEventHardwareAvailable+0x9a
    fffff880`031bd510 fffff880`00dc94fe : fffffa80`05d72020 fffff880`031bd640 00000000`00000004 fffff880`00dd8390 : Wdf01000!FxPkgPnp::PnpEnterNewState+0x1a5
    fffff880`031bd580 fffff880`00dc9201 : 00000000`00000000 00000000`00000002 00000000`00000000 fffffa80`05d72020 : Wdf01000!FxPkgPnp::PnpProcessEventInner+0x122
    fffff880`031bd5f0 fffff880`00dc0d9c : 00000000`00000000 fffffa80`05d72020 fffffa80`0601f6e0 00000000`00000000 : Wdf01000!FxPkgPnp::PnpProcessEvent+0x1b1
    fffff880`031bd680 fffff880`00dbfdd6 : fffffa80`04edec80 fffffa80`0601f6e0 00000000`00000000 fffffa80`05d72020 : Wdf01000!FxPkgPnp::_PnpStartDevice+0x20
    fffff880`031bd6b0 fffff880`00d8f245 : fffffa80`03972600 fffffa80`03972600 fffffa80`05e45770 fffff800`03bc2a40 : Wdf01000!FxPkgPnp::Dispatch+0x1b2
    fffff880`031bd720 fffff880`00d8f14b : 00000000`00000002 fffffa80`03972600 fffffa80`0601f6e0 fffffa80`05e45770 : Wdf01000!FxDevice::Dispatch+0xa9
    fffff880`031bd750 fffff800`03e8256e : fffffa80`03972600 fffffa80`0601f6e0 fffffa80`05e45770 fffff880`009ea180 : Wdf01000!FxDevice::DispatchWithLock+0x93
    fffff880`031bd790 fffff800`03bbcddd : fffffa80`048bba20 fffffa80`0601f6e0 fffff800`03bc2a40 00000000`00000000 : nt!PnpAsynchronousCall+0xce
    fffff880`031bd7d0 fffff800`03e8d356 : fffff800`03cc71e0 fffffa80`048b7b90 fffffa80`0601f6e0 fffffa80`048b7d38 : nt!PnpStartDevice+0x11d
    fffff880`031bd890 fffff800`03e8d5f4 : fffffa80`048b7b90 fffffa80`03a1003e fffffa80`03a1f550 00000000`00000001 : nt!PnpStartDeviceNode+0x156
    fffff880`031bd920 fffff800`03eb08e6 : fffffa80`048b7b90 fffffa80`03a1f550 00000000`00000002 00000000`00000000 : nt!PipProcessStartPhase1+0x74
    fffff880`031bd950 fffff800`03eb0d9c : fffff800`03cc4da0 00000000`00000000 00000000`00000001 fffff800`03d2ccf8 : nt!PipProcessDevNodeTree+0x296
    fffff880`031bdbc0 fffff800`03bc5092 : 00000001`00000003 fffff800`03c685f8 00000000`00000001 00000000`00000000 : nt!PiProcessStartSystemDevices+0x7c
    fffff880`031bdc10 fffff800`03ad07e1 : fffff800`03bc4d90 fffff880`01090e01 fffffa80`039fab00 00000000`00000000 : nt!PnpDeviceActionWorker+0x302
    fffff880`031bdcb0 fffff800`03d636fa : 00000554`00000000 fffffa80`039fab60 00000000`00000080 fffffa80`039e6890 : nt!ExpWorkerThread+0x111
    fffff880`031bdd40 fffff800`03aa1b46 : fffff880`02f63180 fffffa80`039fab60 fffff880`02f6dfc0 00000554`00000000 : nt!PspSystemThreadStartup+0x5a
    fffff880`031bdd80 00000000`00000000 : fffff880`031be000 fffff880`031b8000 fffff880`031bca10 00000000`00000000 : nt!KiStartSystemThread+0x16
     SYMBOL_STACK_INDEX:  1
     
    SYMBOL_NAME:  1394ohci!AsyncTx::Prepare+97
     
    FOLLOWUP_NAME:  MachineOwner
     
    MODULE_NAME: 1394ohci
     
    IMAGE_NAME:  1394ohci.sys
     
    DEBUG_FLR_IMAGE_TIMESTAMP:  4a5bcc30
     
    STACK_COMMAND:  .cxr 0xfffff880031bc980 ; kb
     
    FAILURE_BUCKET_ID:  X64_0x7E_NULL_IP_1394ohci!AsyncTx::Prepare+97
     
    BUCKET_ID:  X64_0x7E_NULL_IP_1394ohci!AsyncTx::Prepare+97
     
    Followup: MachineOwner
    ---------
     
     

    -- Mike Burr
    Technology
    Thursday, November 17, 2011 5:22 AM
  • Not really making much progress correcting this link issue... I could e-mail you the .dmp file or try any other suggestions you may have.

     

    Thanks

    Kyle

    Thursday, November 17, 2011 5:23 AM
  • I was able to pull the link out of that, was that the only dump?
     

    -- Mike Burr
    Technology
    Thursday, November 17, 2011 5:27 AM
  • I have more, I will upload the most recent ones.  And as for the firewire devices, none that I know of....?  I don't know why it would suggest that, as I can't think of anything I use that uses firewire.  

     

    These are all from 11/15/11:

    <iframe title ="Preview" scrolling="no" marginheight="0" marginwidth="0" frameborder="0" style="width:98px;height:115px;padding:0;background-color:#fcfcfc;" src="https://skydrive.live.com/embedicon.aspx/.Documents/Public/111511-24024-01%20-%20Copy.dmp?cid=34f245e36d1190a8&sc=documents"></iframe>

     

    <iframe title ="Preview" scrolling="no" marginheight="0" marginwidth="0" frameborder="0" style="width:98px;height:115px;padding:0;background-color:#fcfcfc;" src="https://skydrive.live.com/embedicon.aspx/.Documents/Public/111511-20935-01%20-%20Copy.dmp?cid=34f245e36d1190a8&sc=documents"></iframe>

     

    <iframe title ="Preview" scrolling="no" marginheight="0" marginwidth="0" frameborder="0" style="width:98px;height:115px;padding:0;background-color:#fcfcfc;" src="https://skydrive.live.com/embedicon.aspx/.Documents/Public/111511-18673-01%20-%20Copy.dmp?cid=34f245e36d1190a8&sc=documents"></iframe>

     

    This one is from 11/09/11:

    <iframe title ="Preview" scrolling="no" marginheight="0" marginwidth="0" frameborder="0" style="width:98px;height:115px;padding:0;background-color:#fcfcfc;" src="https://skydrive.live.com/embedicon.aspx/.Documents/Public/110911-39530-01%20-%20Copy.dmp?cid=34f245e36d1190a8&sc=documents"></iframe>

     

    I'm sure you could have figured those out from the time stamps... But there are four more for your viewing.  Thank you very much for taking the time to check these out.

     

    Kyle

     

    Thursday, November 17, 2011 5:44 AM
  • There are 7 more I have not linked from this year.  If those are needed as well, just let me know.  I will do the MemTest tomorrow as this computer does not have a CD burner, so I will have to use another computer to burn the program onto a disc. 
    Thursday, November 17, 2011 6:00 AM
  • OK, I looked at the rest and the driver/issue being blamed jumos around
    a lot. This usually points to a memory issue. Can you get back to me
    with the memtest86+ results?
     

    -- Mike Burr
    Technology
    • Proposed as answer by Niki Han Wednesday, November 23, 2011 8:00 AM
    • Marked as answer by Niki Han Friday, November 25, 2011 9:33 AM
    Thursday, November 17, 2011 6:05 AM
  • I have been trying all morning to get Memtest to work, and I haven't been successful...  Burned the ISO file 4 times to a disc, but not one has turned out correctly, I don't think.  Followed three different guides of how to do it and use it after the first failure, so I will keep trying, or have my IT friend show me up and get it running..  Thanks for looking, but as of now I don't think I will have Memtest working until I can have him look at my computer. 

     

    If it makes any difference, I have removed one of my RAM sticks when I was preparing to run Memtest on the boot up, and my computer started without any problems?  I haven't tried switching the sticks to check and see if the other one works the same way, but this is the first time I can remember my computer shutting down and starting up correctly.  Though I usually leave it on standby and only shut down when I would install updates, which I figured were then wreaking havoc on my computer..

    Thursday, November 17, 2011 5:47 PM
  •  
    > If it makes any difference, I have removed one of my RAM sticks when I
    > was preparing to run Memtest on the boot up, and my computer started
    > without any problems?  I haven't tried switching the sticks to check
    > and see if the other one works the same way, but this is the first
    > time I can remember my computer shutting down and starting up
    > correctly.  Though I usually leave it on standby and only shut down
    > when I would install updates, which I figured were then wreaking havoc
    > on my computer..
    >
     
    I wouldn't say you have anything conclusive with regard to the memory
    issues, but if this allows your system to boot, then it may give you the
    opportunity to back up any files you want to save before the system
    degrades further...
     

    -- Mike Burr
    Technology
    Thursday, November 17, 2011 7:04 PM
  • By the way, what procedure did you use to burn the ISO? Also, have you
    tried creating a bootable USB key?
     

    -- Mike Burr
    Technology
    Thursday, November 17, 2011 7:04 PM
  • I used a cd burning software on my other computer, and when that didn't work, I used Free ISO burner's software.  I tried burning the zipped and unzipped file, it was exactly as the instructions said.  The file was an ISO file named exactly as they said it would be, and since Free ISO Burner only burns ISO files, it seemed fairly foolproof.  Turns out I was wrong hah.  I downloaded Memtest from their website, unzipped it to desktop, the ISO file that was unzipped to desktop was then burned to 4 different discs, neither one successfully giving me a copy that turned out how the instructions described. Each disc, when opened from My Computer -> the disc itself, showed a folder called ISOLinux (which confused me since it said Linux, which I then made sure I downloaded the Windows one), and also has 2 other files both called SRC_V40A.  These are a WinRAR archive and a WinRAR zip archive.  Inside the ISOLinux folder there is a bunch of different files, including the boot file that is apparently supposed to be the one that launches Memtest on the boot up.  I don't know, I probably messed up somewhere in there, but I followed the directions as thoroughly as I could, I thought.

    Haven't tried the USB route, though. It says only bootable in Linux, so that discouraged me from attempting it.

     

    And yea, I am using my computer now with both RAM cards back in, and I've already backed up the files I need, fortunately.  I just can't get Memtest to work to potentially narrow down the problem :-/.

     

    Is it worth testing the memory with the memory tested in Windows? Or is that basically useless since it's just a cursory little peek into the RAM, and not as thorough as Memtest.

    Friday, November 18, 2011 4:12 AM
  • Hi,
     
    You can try using the extended tests for windiag, but memtest is usually
    the most thorough.
     
    Have you tried using the built in ISO burner in Windows 7?
     
     

    -- Mike Burr
    Technology
    Friday, November 18, 2011 1:58 PM