locked
Win7 Home Premium 64bit Blue Screen Errors RRS feed

  • Question

  • I built a new rig a little over a month ago, my tech level is fairly low but I'd have to say it's better than the average Joe.
    Admittedly, I made a noob mistake when setting up my SSD and forgot to set it to AHCI mode before installing windows and everything else, but thanks to some very helpful people on another forum I followed some steps and made the switch from IDE to AHCI on my SSD. I'm not sure if this is part of the problem, but it has happened a few times before the switch to the SATA Controller was made (although I didn't make note of the error codes then so it could have happened for a different reason).
    These blue screen errors have occurred shortly after start up; most recently after being shut down, though the other times it could have happened after hibernation, can't be sure, all my drivers are up to date.

    The error code I am getting on the blue screen is as follows:
    Most recently,
    STOP: 0x000000F4 (0x0000000000000003), 0xFFFFFA80069D0B30, 0xFFFFFA80069D0E10, 0xFFFFF80002FDE5D0)

    Previously (but still after switching to AHCI)
    STOP: 0x000000F4 (0x0000000000000003), 0xFFFFFA80069B130, 0xFFFFFA80069B1E10, 0xFFFFF80002FCA5D0)

    Any help with this would be greatly appreciated!
    Saturday, October 9, 2010 3:36 PM

Answers

  •  F4 - CRITICAL_OBJECT_TERMINATION -
     
    Can you upload the minidump files from C:\Windows\Minidump to Skydrive
    for further analysis,
     
     

    -- Mike Burr
    • Marked as answer by Sabrina Shen Monday, October 18, 2010 6:13 AM
    Saturday, October 9, 2010 9:57 PM
  • Hi,

     

    Please go to test this issue in Clean Boot, Device Clean Boot and Safe Mode to determine the possible cause.

     

    If it works fine in Clean Boot, the root cause can be the third party software. If the issue reoccurs in Clean Boot, but works fine in Safe Mode, the cause can be the incompatible hardware drivers. You may narrow down the causes in Device Clean Boot.

     

    Device Clean Boot

    =================

    1. Click Start, type "devmgmt.msc" (without quotation marks) in the Search bar and press Enter.

     

    2. Expand "Sound, video and game controllers".

     

    3. Right click on your sound card and then click "Properties.

     

    4. In the dropdown menu of Device Usage, please choose "Do not use this device (disable)" and click OK.

     

    5. Please use the same method to disable other dubious hardware such as: internal modem, network card and CD-R drive. Please note some devices such as video adapter are not available to be disabled.

     

    ·         If the issue persists, would you please upload more minidump files for further research?

     

    Collect Minidump Files

    =================

    1. Click "Start", input "SYSDM.CPL" (without quotation marks) in the “Search” bar and press “Enter”.

    2. Switch to the "Advanced" tab and click the "Settings" button under "Startup and Recovery".

    3. Under "Write debugging information" section, make sure the "Small memory dump (128KB)" option is selected.

    4. Make sure "%SystemRoot%\Minidump" is in the "Small dump directory" open box and click “OK”.

     

    If the Blue Screen appears again, please refer to the following steps to collect memory dump files:

     

    1. Click “Start”, type “%SystemRoot%\Minidump" (without quotation marks) in “Search” bar and press “Enter”.

    2. Go to your Desktop, right-click on it and create a new folder named "Dump".

    3. Copy all the memory dump files (looks like [Mini092008-01.dmp]) in Minidump to this folder.

    4. Right-click on the Dump folder, click "Send To", and click "Compressed (zipped) Folder".

    5. Please send the ZIP file to us.

     

    You can refer to the following link to upload the information:

     

    http://social.technet.microsoft.com/Forums/en-US/w7itproui/thread/4fc10639-02db-4665-993a-08d865088d65

     

    You may also analyze them with Debugging Tools by yourself. You can install it and it’s Symbol Packages from the following link:

     

    http://www.microsoft.com/whdc/Devtools/Debugging/default.mspx

     

    WinDbg will tell you the possible cause. For more information, please read Microsoft KB Article:

     

    How to read the small memory dump files that Windows creates for debugging.

     

    If no clue can be found, you may contact Microsoft Customer Service and Support (CSS) via telephone so that a dedicated Support Professional can assist with your request. To troubleshoot this kind of kernel crash issue, we need to debug the crashed system dump. Unfortunately, debugging is beyond what we can do in the forum. Please be advised that contacting phone support will be a charged call.

     

    To obtain the phone numbers for specific technology request please take a look at the web site listed below:

     

    http://support.microsoft.com/default.aspx?scid=fh;EN-US;OfferProPhone#faq607

     

    Regards,

     

    Sabrina


    This posting is provided "AS IS" with no warranties or guarantees, and confers no rights. |Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.
    • Marked as answer by Sabrina Shen Monday, October 18, 2010 6:13 AM
    Tuesday, October 12, 2010 3:13 AM

All replies

  •  F4 - CRITICAL_OBJECT_TERMINATION -
     
    Can you upload the minidump files from C:\Windows\Minidump to Skydrive
    for further analysis,
     
     

    -- Mike Burr
    • Marked as answer by Sabrina Shen Monday, October 18, 2010 6:13 AM
    Saturday, October 9, 2010 9:57 PM
  • Hi,

     

    Please go to test this issue in Clean Boot, Device Clean Boot and Safe Mode to determine the possible cause.

     

    If it works fine in Clean Boot, the root cause can be the third party software. If the issue reoccurs in Clean Boot, but works fine in Safe Mode, the cause can be the incompatible hardware drivers. You may narrow down the causes in Device Clean Boot.

     

    Device Clean Boot

    =================

    1. Click Start, type "devmgmt.msc" (without quotation marks) in the Search bar and press Enter.

     

    2. Expand "Sound, video and game controllers".

     

    3. Right click on your sound card and then click "Properties.

     

    4. In the dropdown menu of Device Usage, please choose "Do not use this device (disable)" and click OK.

     

    5. Please use the same method to disable other dubious hardware such as: internal modem, network card and CD-R drive. Please note some devices such as video adapter are not available to be disabled.

     

    ·         If the issue persists, would you please upload more minidump files for further research?

     

    Collect Minidump Files

    =================

    1. Click "Start", input "SYSDM.CPL" (without quotation marks) in the “Search” bar and press “Enter”.

    2. Switch to the "Advanced" tab and click the "Settings" button under "Startup and Recovery".

    3. Under "Write debugging information" section, make sure the "Small memory dump (128KB)" option is selected.

    4. Make sure "%SystemRoot%\Minidump" is in the "Small dump directory" open box and click “OK”.

     

    If the Blue Screen appears again, please refer to the following steps to collect memory dump files:

     

    1. Click “Start”, type “%SystemRoot%\Minidump" (without quotation marks) in “Search” bar and press “Enter”.

    2. Go to your Desktop, right-click on it and create a new folder named "Dump".

    3. Copy all the memory dump files (looks like [Mini092008-01.dmp]) in Minidump to this folder.

    4. Right-click on the Dump folder, click "Send To", and click "Compressed (zipped) Folder".

    5. Please send the ZIP file to us.

     

    You can refer to the following link to upload the information:

     

    http://social.technet.microsoft.com/Forums/en-US/w7itproui/thread/4fc10639-02db-4665-993a-08d865088d65

     

    You may also analyze them with Debugging Tools by yourself. You can install it and it’s Symbol Packages from the following link:

     

    http://www.microsoft.com/whdc/Devtools/Debugging/default.mspx

     

    WinDbg will tell you the possible cause. For more information, please read Microsoft KB Article:

     

    How to read the small memory dump files that Windows creates for debugging.

     

    If no clue can be found, you may contact Microsoft Customer Service and Support (CSS) via telephone so that a dedicated Support Professional can assist with your request. To troubleshoot this kind of kernel crash issue, we need to debug the crashed system dump. Unfortunately, debugging is beyond what we can do in the forum. Please be advised that contacting phone support will be a charged call.

     

    To obtain the phone numbers for specific technology request please take a look at the web site listed below:

     

    http://support.microsoft.com/default.aspx?scid=fh;EN-US;OfferProPhone#faq607

     

    Regards,

     

    Sabrina


    This posting is provided "AS IS" with no warranties or guarantees, and confers no rights. |Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.
    • Marked as answer by Sabrina Shen Monday, October 18, 2010 6:13 AM
    Tuesday, October 12, 2010 3:13 AM