none
Windows 2008 R2 BSOD 0x0000003b (0x00000000c0000005, 0xfffff80001863adc, 0xfffff88008395f00, 0x0000000000000000) RRS feed

  • Question

  • Hi,

    We have got blue dump error with windows 2008 R2 Ent. OS.

    Error code as follows :- BSOD 0x0000003b (0x00000000c0000005, 0xfffff80001863adc, 0xfffff88008395f00, 0x0000000000000000). ".

    To resolve this issue we have got one KB artical with patch.

    http://support.microsoft.com/kb/980932

    But we want to know is there any other dependencies other than this patch.


    Kalpesh Pawar

    Wednesday, September 26, 2012 5:04 AM

Answers

  • That KB 980932 applied to this situation:

    Quote:

    A computer that is running Windows 7 or Windows Server 2008 R2 may crash when you use some IEEE 1394 devices. Additionally, you may receive a Stop error message that resembles the following:
    STOP 0x0000003B (Parameter1, Parameter2, Parameter3, Parameter4)
    SYSTEM_SERVICE_EXCEPTION

    Meanwhile, the BSOD could caused by many reasons, I suggest go to test this issue in Safe Mode, Clean Boot and Device Clean Boot to determine the possible cause.

    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,

    Miya


    Miya Yao

    TechNet Community Support

    Wednesday, September 26, 2012 7:09 AM
    Moderator

All replies

  • Hi,

    There is no issue with Microsoft patches.

    But sometimes its not reliable, Although many users may not notice them, Microsoft often releases more than just security updates in its regular bug patching cycle. However, they are frequently not released at the same time as security patches. Even after installing you remove the patches.

    but as far as i concerned, there is no issue with this patch.



    akshay vithalkar

    Wednesday, September 26, 2012 5:13 AM
  • That KB 980932 applied to this situation:

    Quote:

    A computer that is running Windows 7 or Windows Server 2008 R2 may crash when you use some IEEE 1394 devices. Additionally, you may receive a Stop error message that resembles the following:
    STOP 0x0000003B (Parameter1, Parameter2, Parameter3, Parameter4)
    SYSTEM_SERVICE_EXCEPTION

    Meanwhile, the BSOD could caused by many reasons, I suggest go to test this issue in Safe Mode, Clean Boot and Device Clean Boot to determine the possible cause.

    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,

    Miya


    Miya Yao

    TechNet Community Support

    Wednesday, September 26, 2012 7:09 AM
    Moderator