locked
New Build - Blue Screen RRS feed

  • Question

  • Hello,

    I recently built my first desktop and it began having problems right after I installed windows 7.  At first, it wasn't getting a blue screen, the display would turn into some colored lines and the computer would automatically restart (no warning or error messages).  I replaced the graphics card and it appears that that problem went away, however, I get a blue screen about 5-10 minutes after I log into windows.  The most recent ones I have gotten are 0x0000007E (which from what I found elsewhere doesn't give much useful information about the cause).

    The other one I got was 0x0000003B  SYSTEM_SERVICE_EXCEPTION.  I haven't found a whole lot of insight as to what may cause this.

    I have already run memtest for about 3 or 4 passes with no errors.  As I said earlier, I have replaced the graphics card.  I have tried running with a single memory stick in, but the problem still exists.  I did a few clean installs of windows and made sure all the drivers were up to date and installed all the chipset drivers from the motherboard’s disc.

    Here are my specs:

    • Windows 7 64-bit
    • Seagate Barracuda 1TB 7200 RPM 32MB Cache SATA 3.0Gb/s 3.5" Internal Hard Drive
    • PowerColor AX5770 512MD5-H Radeon HD 5770 512MB
    • GIGABYTE GA-770TA-UD3 AM3 AMD 770 SATA 6Gb/s USB 3.0 ATX AMD Motherboard
    • Diablotek DA Series PSDA500 500W ATX Power Supply
    • CORSAIR XMS3 4GB (2 x 2GB) 240-Pin DDR3 SDRAM DDR3 1600 (PC3 12800)
    • AMD Phenom II X4 3.2GHz 4 x 512KB L2 Cache 6MB L3 Cache Socket AM3 125W Quad-Core

    Any suggestions are greatly appreciated. Let me know of any other information you may need and I will try and get it ASAP.

    Thanks!

    Friday, February 25, 2011 9:21 PM

Answers

  • SYSTEM_SERVICE_EXCEPTION (3b)
    An exception happened while executing a system service routine.
    Arguments:
    Arg1: 00000000c0000005, Exception code that caused the bugcheck

    FOLLOWUP_NAME:  Pool_corruption

    STACK_TEXT: 
    nt!ExDeferredFreePool+0x100

    This maybe RAM issues.

    Please download memtest86+ [1], burn a new bootable CD (use a CD-RW if possible) from the ISO (download and use ImgBurn [2][3] to do this or make double click on the ISO in Windows 7), reboot your PC and scan your RAM 4-5hours for errors. If memtest86+ detects errors, test each module its own and replace the faulty RAM.

    If the memtest tells no error, please download CPU-Z [4], look in the memory and SPD tab and verify that the current RAM Speed and the Timings match to the values that you see in the SPD tab. If your RAM run at CR (Command Rate) 1T, change the value into 2T in the BIOS. This should fix the crashes.

    André

    [1] http://www.memtest.org/download/4.20/memtest86+-4.20.iso.zip
    [2] http://www.imgburn.com/index.php?act=download
    [3] http://forum.imgburn.com/index.php?showtopic=61
    [4] http://www.cpuid.com/softwares/cpu-z.html


    "A programmer is just a tool which converts caffeine into code" CLIP- Stellvertreter http://www.winvistaside.de/
    • Proposed as answer by Andre.Ziegler Saturday, February 26, 2011 11:45 PM
    • Marked as answer by Leo Huang Friday, March 4, 2011 9:39 AM
    Friday, February 25, 2011 11:47 PM
  • Just out of curiosity, what exactly is the Command Rate and the difference between 1T and 2T.  Is it just different ways of accessing memory?

    Child-SP          RetAddr           Call Site
    fffff880`031caa58 fffff800`031108a6 nt!RtlCompareUnicodeStrings+0x44
    fffff880`031caa60 fffff880`00d21445 nt!RtlCompareUnicodeString+0x26
    fffff880`031caaa0 fffff880`00d203dd CI!I_ReloadCatalogs+0x199
    fffff880`031cac40 fffff880`00d1e9cd CI!I_FindFileOrHeaderHashInCatalogs+0x101
    fffff880`031cace0 fffff880`00d1f381 CI!CipFindFileHash+0xf9
    fffff880`031cadb0 fffff880`00d1dfbb CI!CipValidateFileHash+0x311
    fffff880`031caf20 fffff800`030dbb6e CI!CiValidateImageHeader+0x213
    fffff880`031cb000 fffff800`030dba5c nt!SeValidateImageHeader+0x2e
    fffff880`031cb040 fffff800`0316aa95 nt!MiValidateImageHeader+0xa4
    fffff880`031cb100 fffff800`0315fd13 nt!MmCreateSection+0x8c9
    fffff880`031cb310 fffff800`02e70993 nt!NtCreateSection+0x162
    fffff880`031cb390 fffff800`02e6cf30 nt!KiSystemServiceCopyEnd+0x13
    fffff880`031cb598 fffff800`0324b1e6 nt!KiServiceLinkage
    fffff880`031cb5a0 fffff800`0324b5ac nt!MmCheckSystemImage+0x96
    fffff880`031cb6d0 fffff800`0324b7c7 nt!MiCreateSectionForDriver+0xcc
    fffff880`031cb780 fffff800`0325706a nt!MiObtainSectionForDriver+0xd7
    fffff880`031cb7e0 fffff800`032e9010 nt!MmLoadSystemImage+0x23a
    fffff880`031cb900 00000000`00000000 nt!NtSetSystemInformation+0x8e3

    this is still a RAM issue.

    Read here what Command Rate is:

    http://www.tomshardware.co.uk/forum/176007-12-dram-command-rate-explained

    Set it to 2 to have a stable Windows.


    André


    "A programmer is just a tool which converts caffeine into code" CLIP- Stellvertreter http://www.winvistaside.de/
    • Marked as answer by Leo Huang Friday, March 4, 2011 9:39 AM
    Monday, February 28, 2011 1:50 PM

All replies

  • A bugcheck (BSOD) is a mechanism to protect your PC from damage.

    To see the cause I have to take a look at the dumps with the Debugging Tools for Windows.

    Please start the Windows Explorer and go to the folder C:\Windows\Minidump. Next, copy the dmp files to your desktop, zip all dmp into 1 zip file and upload the zip file to your public Skydrive [1] folder and post a link here.

    André

    [1] http://social.technet.microsoft.com/Forums/en-US/w7itproui/thread/4fc10639-02db-4665-993a-08d865088d65
    "A programmer is just a tool which converts caffeine into code" CLIP- Stellvertreter http://www.winvistaside.de/
    Friday, February 25, 2011 9:35 PM
  • Here is some more information about the most recent blue screen:

    Problem signature:
      Problem Event Name:    BlueScreen
      OS Version:    6.1.7600.2.0.0.256.48
      Locale ID:    1033

    Additional information about the problem:
      BCCode:    3b
      BCP1:    00000000C0000005
      BCP2:    FFFFF80002FFCF8C
      BCP3:    FFFFF88003B2A700
      BCP4:    0000000000000000
      OS Version:    6_1_7600
      Service Pack:    0_0
      Product:    256_1

     

    Also, when I navigated to the Minidump folder, there was only one dump file.

    http://cid-16ed07791891c9db.office.live.com/self.aspx/Documents/022511-39327-01.dmp

    Friday, February 25, 2011 9:49 PM
  • SYSTEM_SERVICE_EXCEPTION (3b)
    An exception happened while executing a system service routine.
    Arguments:
    Arg1: 00000000c0000005, Exception code that caused the bugcheck

    FOLLOWUP_NAME:  Pool_corruption

    STACK_TEXT: 
    nt!ExDeferredFreePool+0x100

    This maybe RAM issues.

    Please download memtest86+ [1], burn a new bootable CD (use a CD-RW if possible) from the ISO (download and use ImgBurn [2][3] to do this or make double click on the ISO in Windows 7), reboot your PC and scan your RAM 4-5hours for errors. If memtest86+ detects errors, test each module its own and replace the faulty RAM.

    If the memtest tells no error, please download CPU-Z [4], look in the memory and SPD tab and verify that the current RAM Speed and the Timings match to the values that you see in the SPD tab. If your RAM run at CR (Command Rate) 1T, change the value into 2T in the BIOS. This should fix the crashes.

    André

    [1] http://www.memtest.org/download/4.20/memtest86+-4.20.iso.zip
    [2] http://www.imgburn.com/index.php?act=download
    [3] http://forum.imgburn.com/index.php?showtopic=61
    [4] http://www.cpuid.com/softwares/cpu-z.html


    "A programmer is just a tool which converts caffeine into code" CLIP- Stellvertreter http://www.winvistaside.de/
    • Proposed as answer by Andre.Ziegler Saturday, February 26, 2011 11:45 PM
    • Marked as answer by Leo Huang Friday, March 4, 2011 9:39 AM
    Friday, February 25, 2011 11:47 PM
  • I ran memtest with no errors.

    I wasn't sure what exactly I need to be looking at in CPU-Z, so I took some screenshots.

    http://xvaitg.blu.livefilestore.com/y1pKq_7y1SQIgkfUgW6dYMZxNGdXOXDq2dgwshJhkvK8mYwYWGv2enOM8VdqYJFqPxA0pbeQhyrGLS_E6EQk9x2cRkjmWFwtKb4/Untitled.png?psid=1

     

    Also, thank you for all your quick replys!

    Saturday, February 26, 2011 10:48 PM
  • Hi,

    please look at the Memory at and the value Command rate. This is 1 in your case. This is faster but causes stability issues. So go into the BIOS and change the option from 1 to 2. This fixes the crash.

    André


    "A programmer is just a tool which converts caffeine into code" CLIP- Stellvertreter http://www.winvistaside.de/
    Saturday, February 26, 2011 11:44 PM
  • Just out of curiosity, what exactly is the Command Rate and the difference between 1T and 2T.  Is it just different ways of accessing memory?

    I thought everything was fixed, I was able to use the computer for about 45 minutes.

    I shut it down and came back later.  When I turned it on and began using windows, after about 10 minutes I got a different blue screen:

    Problem signature:
      Problem Event Name:    BlueScreen
      OS Version:    6.1.7600.2.0.0.256.48
      Locale ID:    1033

    Additional information about the problem:
      BCCode:    1000007e
      BCP1:    FFFFFFFFC0000005
      BCP2:    FFFFF800031524E4
      BCP3:    FFFFF880031CA818
      BCP4:    FFFFF880031CA080
      OS Version:    6_1_7600
      Service Pack:    0_0
      Product:    256_1

    Here is the dump file: http://cid-16ed07791891c9db.office.live.com/self.aspx/Documents/022711-31371-01.dmp

    Once again, thank you for your help and quick replys.  This has been a bit of a frustrating experience.  I guess I shouldn't have expected everything to go according to plan on my first build.

     

    Sunday, February 27, 2011 7:31 PM
  • Just out of curiosity, what exactly is the Command Rate and the difference between 1T and 2T.  Is it just different ways of accessing memory?

    Child-SP          RetAddr           Call Site
    fffff880`031caa58 fffff800`031108a6 nt!RtlCompareUnicodeStrings+0x44
    fffff880`031caa60 fffff880`00d21445 nt!RtlCompareUnicodeString+0x26
    fffff880`031caaa0 fffff880`00d203dd CI!I_ReloadCatalogs+0x199
    fffff880`031cac40 fffff880`00d1e9cd CI!I_FindFileOrHeaderHashInCatalogs+0x101
    fffff880`031cace0 fffff880`00d1f381 CI!CipFindFileHash+0xf9
    fffff880`031cadb0 fffff880`00d1dfbb CI!CipValidateFileHash+0x311
    fffff880`031caf20 fffff800`030dbb6e CI!CiValidateImageHeader+0x213
    fffff880`031cb000 fffff800`030dba5c nt!SeValidateImageHeader+0x2e
    fffff880`031cb040 fffff800`0316aa95 nt!MiValidateImageHeader+0xa4
    fffff880`031cb100 fffff800`0315fd13 nt!MmCreateSection+0x8c9
    fffff880`031cb310 fffff800`02e70993 nt!NtCreateSection+0x162
    fffff880`031cb390 fffff800`02e6cf30 nt!KiSystemServiceCopyEnd+0x13
    fffff880`031cb598 fffff800`0324b1e6 nt!KiServiceLinkage
    fffff880`031cb5a0 fffff800`0324b5ac nt!MmCheckSystemImage+0x96
    fffff880`031cb6d0 fffff800`0324b7c7 nt!MiCreateSectionForDriver+0xcc
    fffff880`031cb780 fffff800`0325706a nt!MiObtainSectionForDriver+0xd7
    fffff880`031cb7e0 fffff800`032e9010 nt!MmLoadSystemImage+0x23a
    fffff880`031cb900 00000000`00000000 nt!NtSetSystemInformation+0x8e3

    this is still a RAM issue.

    Read here what Command Rate is:

    http://www.tomshardware.co.uk/forum/176007-12-dram-command-rate-explained

    Set it to 2 to have a stable Windows.


    André


    "A programmer is just a tool which converts caffeine into code" CLIP- Stellvertreter http://www.winvistaside.de/
    • Marked as answer by Leo Huang Friday, March 4, 2011 9:39 AM
    Monday, February 28, 2011 1:50 PM
  • I should have noted:  I received the second blue screen after changing the Command Rate to 2T.

    After changing the BIOS setting, I used the computer for a little while and shut it down.  I came  back later and turned it on, and after about 10 or so minutes, I got the second blue screen.

    Monday, February 28, 2011 7:08 PM
  • Have you run the memtest?

    "A programmer is just a tool which converts caffeine into code" CLIP- Stellvertreter http://www.winvistaside.de/
    Monday, February 28, 2011 8:13 PM
  • Will changing the Command Rate from 1T to 2T change how memtest works?

    If so, I will run memtest again and let you know what it says.

    Monday, February 28, 2011 8:21 PM
  • Will changing the Command Rate from 1T to 2T change how memtest works?

    no. run the test please and tell me the results

    "A programmer is just a tool which converts caffeine into code" CLIP- Stellvertreter http://www.winvistaside.de/
    Monday, February 28, 2011 9:55 PM