locked
Windows 7 Blue Screen RRS feed

  • Question

  • Hi ,

    I have just built a system with the following components :-

    Asus M4A78LT-M LE
    Amd Athlon II X2 245
    Samsung Spinpoint F1 320gb NCQ
    Sony optiarc DVD RW AD-5240S
    PNY PC3-10660 2GB 1333Mhz

    After a few days I started to get a Blue screen. The dump has the following in it :-

    Problem signature:
    Problem Event Name: BlueScreen
    OS Version: 6.1.7600.2.0.0.768.3
    Locale ID: 2057
    Additional information about the problem:
    BCCode: 3b
    BCP1: 00000000C0000005
    BCP2: FFFFF80002A05000
    BCP3: FFFFF88004F38E10
    BCP4: 0000000000000000
    OS Version: 6_1_7600
    Service Pack: 0_0
    Product: 768_1

    How can I find out exactly what is causing this ?

    Kind Regards
    Paul

    Tuesday, January 26, 2010 3:23 PM

Answers

  • I would recommend updating the motherboard's BIOS to the lastet version and then make sure the RAM voltage and CAS timings are correct for the particular RAM you installed.
    Carey Frisch
    Tuesday, January 26, 2010 4:13 PM
  • Hi Paul,

    you have the following crash:

    Bug Check 0x3B: SYSTEM_SERVICE_EXCEPTION

    The SYSTEM_SERVICE_EXCEPTION bug check has a value of 0x0000003B. This indicates that an exception happened while executing a routine that transitions from non-privileged code to privileged code.

    Cause

    This error has been linked to excessive paged pool usage and may occur due to user-mode graphics drivers crossing over and passing bad data to the kernel code.

    Are you using the latest graphics drivers? If not update them please!

    André

    "A programmer is just a tool which converts caffeine into code" CLIP- Stellvertreter http://www.winvistaside.de/
    Tuesday, January 26, 2010 9:37 PM
  • Hi Yogabba,

     

    Would you please send me more information for analyzing. For your convenience, I have created a workspace for you.  You can upload the information files to the following link.  (Please choose "Send Files to Microsoft")

     

    Workspace URL: https://sftasia.one.microsoft.com/choosetransfer.aspx?key=a9c79dcb-3f1b-4c81-a519-51a744475455

    Password: jiN8rv5GgKOy

     

    Note: Due to differences in text formatting with various email clients, the workspace link above may appear to be broken.  Please be sure to include all text between '(' and ')' when typing or copying the workspace link into your browser. Meanwhile, please note that files uploaded for more than 72 hours will be deleted automatically. Please ensure to notify me timely after you have uploaded the files. Thank you for your understanding.

     

    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.

     

    If it is inconvenient for you to upload the dump files. I would like to suggest you analyze them with Debugging Tools by yourself. You may 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.

     

    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,

     


    Arthur Li - MSFT
    Thursday, January 28, 2010 2:58 AM

All replies

  • I would recommend updating the motherboard's BIOS to the lastet version and then make sure the RAM voltage and CAS timings are correct for the particular RAM you installed.
    Carey Frisch
    Tuesday, January 26, 2010 4:13 PM
  • Hi Paul,

    you have the following crash:

    Bug Check 0x3B: SYSTEM_SERVICE_EXCEPTION

    The SYSTEM_SERVICE_EXCEPTION bug check has a value of 0x0000003B. This indicates that an exception happened while executing a routine that transitions from non-privileged code to privileged code.

    Cause

    This error has been linked to excessive paged pool usage and may occur due to user-mode graphics drivers crossing over and passing bad data to the kernel code.

    Are you using the latest graphics drivers? If not update them please!

    André

    "A programmer is just a tool which converts caffeine into code" CLIP- Stellvertreter http://www.winvistaside.de/
    Tuesday, January 26, 2010 9:37 PM
  • Hi Yogabba,

     

    Would you please send me more information for analyzing. For your convenience, I have created a workspace for you.  You can upload the information files to the following link.  (Please choose "Send Files to Microsoft")

     

    Workspace URL: https://sftasia.one.microsoft.com/choosetransfer.aspx?key=a9c79dcb-3f1b-4c81-a519-51a744475455

    Password: jiN8rv5GgKOy

     

    Note: Due to differences in text formatting with various email clients, the workspace link above may appear to be broken.  Please be sure to include all text between '(' and ')' when typing or copying the workspace link into your browser. Meanwhile, please note that files uploaded for more than 72 hours will be deleted automatically. Please ensure to notify me timely after you have uploaded the files. Thank you for your understanding.

     

    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.

     

    If it is inconvenient for you to upload the dump files. I would like to suggest you analyze them with Debugging Tools by yourself. You may 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.

     

    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,

     


    Arthur Li - MSFT
    Thursday, January 28, 2010 2:58 AM