locked
BSOD BugCheck 1001 Three Times In Three Days RRS feed

  • Question

  • I apologize for making yet another topic on this same issue but I'm not that big on reading .dmp files, and you folks know what's what better than I do.

    I did a fresh installation of Windows 7 about a week ago but now - for the first time since forever - I've been getting bluescreens.

    //////////////////////////////////////////////////////////////////////////

    Here's the dump file:

    https://onedrive.live.com/redir?resid=9FCFB68E12F1D23F!172&authkey=!AFIgTUizGz9k_iY&ithint=file%2c.dmp

    //////////////////////////////////////////////////////////////////////////

    And here's the mess from event viewer:

    Log Name:      System
    Source:        Microsoft-Windows-WER-SystemErrorReporting
    Date:          2.6.2014 11:11:46
    Event ID:      1001
    Task Category: None
    Level:         Error
    Keywords:      Classic
    User:          N/A
    Computer:      Monocube
    Description:
    The computer has rebooted from a bugcheck.  The bugcheck was: 0x000000f4 (0x0000000000000003, 0xfffffa8007e1ab30, 0xfffffa8007e1ae10, 0xfffff80002d81270). A dump was saved in: C:\Windows\MEMORY.DMP. Report Id: 060214-4508-01.
    Event Xml:
    <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
      <System>
        <Provider Name="Microsoft-Windows-WER-SystemErrorReporting" Guid="{ABCE23E7-DE45-4366-8631-84FA6C525952}" EventSourceName="BugCheck" />
        <EventID Qualifiers="16384">1001</EventID>
        <Version>0</Version>
        <Level>2</Level>
        <Task>0</Task>
        <Opcode>0</Opcode>
        <Keywords>0x80000000000000</Keywords>
        <TimeCreated SystemTime="2014-06-02T08:11:46.000000000Z" />
        <EventRecordID>4150</EventRecordID>
        <Correlation />
        <Execution ProcessID="0" ThreadID="0" />
        <Channel>System</Channel>
        <Computer>Monocube</Computer>
        <Security />
      </System>
      <EventData>
        <Data Name="param1">0x000000f4 (0x0000000000000003, 0xfffffa8007e1ab30, 0xfffffa8007e1ae10, 0xfffff80002d81270)</Data>
        <Data Name="param2">C:\Windows\MEMORY.DMP</Data>
        <Data Name="param3">060214-4508-01</Data>
      </EventData>
    </Event>



    • Edited by Aamaxu Monday, June 2, 2014 8:24 AM
    Monday, June 2, 2014 8:24 AM

Answers

  • Hi,

    The attached DMP file is of the CRITICAL_OBJECT_TERMINATION (f4) bug check.

    This indicates that a process or thread crucial to system operation has unexpectedly exited or been terminated.

    BugCheck F4, {3, fffffa8007e1ab30, fffffa8007e1ae10, fffff80002d81270}

    0: kd> !process fffffa8007e1ab30 3
    GetPointerFromAddress: unable to read from fffff80002cb3000
    PROCESS fffffa8007e1ab30
        SessionId: none  Cid: 021c    Peb: 7fffffdb000  ParentCid: 020c
        DirBase: 1cbc8c000  ObjectTable: fffff8a000edbb20  HandleCount: <Data Not Accessible>
        Image: csrss.exe
    

    The process that crashed was csrss.exe which is the Client/Server Runtime Sybsystem.

    -------------------------------

    1. Uninstall Corsair Link ASAP, very buggy software. You can control your fans with other software if you use it to control your fan speed.

    2. If the above doesn't help, please run Chkdsk and Seatools:

    Chkdsk:
    There are various ways to run Chkdsk~


    Method 1:

    Start > Search bar > Type cmd (right click run as admin to execute Elevated CMD)

    Elevated CMD should now be opened, type the following:

    chkdsk x: /r

    x implies your drive letter, so if your hard drive in question is letter c, it would be:

    chkdsk c: /r

    Restart system and let chkdsk run.

    Method 2:


        Open the "Computer" window
        Right-click on the drive in question
        Select the "Tools" tab
        In the Error-checking area, click <Check Now>.

    If you'd like to get a log file that contains the chkdsk results, do the following:

    Press Windows Key + R and type powershell.exe in the run box

    Paste the following command and press enter afterwards:

    get-winevent -FilterHashTable @{logname="Application"; id="1001"}| ?{$_.providername –match "wininit"} | fl timecreated, message | out-file Desktop\CHKDSKResults.txt

    This will output a .txt file on your Desktop containing the results of the chkdsk.

    If chkdsk turns out okay, run Seatools -

    http://www.seagate.com/support/downloads/seatools/

    You can run it via Windows or DOS. Do note that the only difference is simply the environment you're running it in. In Windows, if you are having what you believe to be driver related issues that may cause conflicts or a false positive, it may be a wise decision to choose the most minimal testing environment (DOS). I always recommend running Seatools in DOS if absolutely possible.

    -- Run all tests EXCEPT: Fix All and anything Advanced.

    Regards,

    Patrick

    “Be kind whenever possible. It is always possible.” - Dalai Lama

    • Proposed as answer by Yolanda Zhu Tuesday, June 3, 2014 2:52 AM
    • Marked as answer by Aamaxu Saturday, June 7, 2014 1:26 PM
    Monday, June 2, 2014 9:17 AM

All replies

  • Hi,

    The attached DMP file is of the CRITICAL_OBJECT_TERMINATION (f4) bug check.

    This indicates that a process or thread crucial to system operation has unexpectedly exited or been terminated.

    BugCheck F4, {3, fffffa8007e1ab30, fffffa8007e1ae10, fffff80002d81270}

    0: kd> !process fffffa8007e1ab30 3
    GetPointerFromAddress: unable to read from fffff80002cb3000
    PROCESS fffffa8007e1ab30
        SessionId: none  Cid: 021c    Peb: 7fffffdb000  ParentCid: 020c
        DirBase: 1cbc8c000  ObjectTable: fffff8a000edbb20  HandleCount: <Data Not Accessible>
        Image: csrss.exe
    

    The process that crashed was csrss.exe which is the Client/Server Runtime Sybsystem.

    -------------------------------

    1. Uninstall Corsair Link ASAP, very buggy software. You can control your fans with other software if you use it to control your fan speed.

    2. If the above doesn't help, please run Chkdsk and Seatools:

    Chkdsk:
    There are various ways to run Chkdsk~


    Method 1:

    Start > Search bar > Type cmd (right click run as admin to execute Elevated CMD)

    Elevated CMD should now be opened, type the following:

    chkdsk x: /r

    x implies your drive letter, so if your hard drive in question is letter c, it would be:

    chkdsk c: /r

    Restart system and let chkdsk run.

    Method 2:


        Open the "Computer" window
        Right-click on the drive in question
        Select the "Tools" tab
        In the Error-checking area, click <Check Now>.

    If you'd like to get a log file that contains the chkdsk results, do the following:

    Press Windows Key + R and type powershell.exe in the run box

    Paste the following command and press enter afterwards:

    get-winevent -FilterHashTable @{logname="Application"; id="1001"}| ?{$_.providername –match "wininit"} | fl timecreated, message | out-file Desktop\CHKDSKResults.txt

    This will output a .txt file on your Desktop containing the results of the chkdsk.

    If chkdsk turns out okay, run Seatools -

    http://www.seagate.com/support/downloads/seatools/

    You can run it via Windows or DOS. Do note that the only difference is simply the environment you're running it in. In Windows, if you are having what you believe to be driver related issues that may cause conflicts or a false positive, it may be a wise decision to choose the most minimal testing environment (DOS). I always recommend running Seatools in DOS if absolutely possible.

    -- Run all tests EXCEPT: Fix All and anything Advanced.

    Regards,

    Patrick

    “Be kind whenever possible. It is always possible.” - Dalai Lama

    • Proposed as answer by Yolanda Zhu Tuesday, June 3, 2014 2:52 AM
    • Marked as answer by Aamaxu Saturday, June 7, 2014 1:26 PM
    Monday, June 2, 2014 9:17 AM
  • Thanks for the quick reply! And thanks for the advice.

    I uninstalled Crosair Link as you suggested. Really wasn't using it for anything else than keeping the fans quiet. I think BIOS lets me do it also anyway.

    //////////////////////////////////////////////////////////////////////////

    I also ran Chkdsk and it gave a generally positive results as far as I can tell. Thanks for telling me how to create a log file of it. I was wondering how it's done.

    TimeCreated : 2.6.2014 14:16:13
    Message     :
                  
                  Checking file system on C:
                  The type of the file system is NTFS.
                  
                  A disk check has been scheduled.
                  Windows will now check the disk.                         
                  
                  CHKDSK is verifying files (stage 1 of 5)...
                    280320 file records processed.                                 
                          
                  File verification completed.
                    1161 large file records processed.                             
                        
                    0 bad file records processed.                                  
                     
                    20098 EA records processed.                                    
                         
                    76 reparse records processed.                                  
                      
                  CHKDSK is verifying indexes (stage 2 of 5)...
                    389772 index entries processed.                                
                          
                  Index verification completed.
                    0 unindexed files scanned.                                     
                     
                    0 unindexed files recovered.                                   
                     
                  CHKDSK is verifying security descriptors (stage 3 of 5)...
                    280320 file SDs/SIDs processed.                                
                          
                  Cleaning up 1921 unused index entries from index $SII of file 0x9
                  .
                  Cleaning up 1921 unused index entries from index $SDH of file 0x9
                  .
                  Cleaning up 1921 unused security descriptors.
                  Security descriptor verification completed.
                    54727 data files processed.                                    
                         
                  CHKDSK is verifying Usn Journal...
                    35608072 USN bytes processed.                                  
                            
                  Usn Journal verification completed.
                  CHKDSK is verifying file data (stage 4 of 5)...
                    280304 files processed.                                        
                          
                  File data verification completed.
                  CHKDSK is verifying free space (stage 5 of 5)...
                    41242452 free clusters processed.                              
                            
                  Free space verification is complete.
                  CHKDSK discovered free space marked as allocated in the
                  master file table (MFT) bitmap.
                  CHKDSK discovered free space marked as allocated in the volume bi
                  tmap.
                  Windows has made corrections to the file system.
                  
                   244196351 KB total disk space.
                    78678284 KB in 223557 files.
                      158216 KB in 54728 indexes.
                           0 KB in bad sectors.
                      390039 KB in use by the system.
                       65536 KB occupied by the log file.
                   164969812 KB available on disk.
                  
                        4096 bytes in each allocation unit.
                    61049087 total allocation units on disk.
                    41242453 allocation units available on disk.
                  
                  Internal Info:
                  00 47 04 00 17 3f 04 00 59 4f 08 00 00 00 00 00  .G...?..YO......
                  c3 01 00 00 4c 00 00 00 00 00 00 00 00 00 00 00  ....L...........
                  00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00  ................
                  
                  Windows has finished checking your disk.
                  Please wait while your computer restarts.
                  
    //////////////////////////////////////////////////////////////////////////

    Seatools also returned PASS on every test except the ones you said not to do. I also ran system file checker and there were no errors.

    For now it seems like everything is a-ok. But don't lock this thread or however it works just yet, in case things go south again.

    Thank you again for your help.


    • Edited by Aamaxu Monday, June 2, 2014 11:58 AM
    Monday, June 2, 2014 11:52 AM
  • My pleasure! No worries, it will not be closed. Please keep me updated,

    Regards,

    Patrick

    “Be kind whenever possible. It is always possible.” - Dalai Lama

    Monday, June 2, 2014 12:08 PM
  • I don't fancy brining (relatively) old threads back up but I thought I'd make a proper update.

    No blue screens since removing Corsair Link. Also the pump and the fans still work like they used to. So, mystery solved. Odd thing it didn't bring BSOD in W8 or 8.1. Maybe they handle things differently enough.

    Oh well! Thanks again for the help! Super neat!


    • Edited by Aamaxu Friday, June 6, 2014 2:57 PM
    Friday, June 6, 2014 2:57 PM
  • My pleasure, glad to hear.

    If and when you are comfortable and feel your issue has been solved, I'd recommend marking any posts of mine that answered your question as answered so this thread no longer shows up as requiring an answer.

    Regards,

    Patrick


    “Be kind whenever possible. It is always possible.” - Dalai Lama

    Friday, June 6, 2014 10:22 PM
  • Hey again.

    Hate to resurrect this thing but I just received a BSOD related to BugCheck and witheroor 1001. I've not reinstalled Corsair Link. It might be worth a mention that before the machine crashed, I was trying to launch Dota 2 but got a 'no executable' error from Steam. Might be related?

    //////////////////////////////////////////////////////////////////////////

    Dump file:

    https://onedrive.live.com/redir?resid=9FCFB68E12F1D23F!173&authkey=!AAkuWl0fnfSYYE8&ithint=file%2c.dmp

    //////////////////////////////////////////////////////////////////////////

    I think I should also mention that my internet connection takes a good while after Windows boot to make a connection. Windows displays it was "Identifying..."

    Also related to network troubles, sometimes all communication ceases for roughly 10 seconds. No error messages of any kind. I mention this only because it might have something to do with the BSOD. No need to wrack your brain over it.

    I suppose it could be my motherboard dying.


    • Edited by Aamaxu Sunday, June 15, 2014 8:52 AM
    Sunday, June 15, 2014 8:51 AM