locked
Several Blue Screens since installing 8 gigs of RAM. RRS feed

  • Question

  • Hello, I recently bought 8 gigs of RAM and have got several blue screens right after installing and have gotten them since. I didn't have any problems with my old RAM, so this is confusing. I'm almost positive my RAM is compatible, the pin is correct, I've set the correct timings, everything i can think of compatibly wise. The last few times its blue screened, i have left my computer running and it eventually sleeps, but i come back to an crashed computer.

    The Blue Screen message is:

      BCCode: a
      BCP1: 0000000000000000
      BCP2: 0000000000000002
      BCP3: 0000000000000001
      BCP4: FFFFF800034D96EC
      OS Version: 6_1_7601
      Service Pack: 1_0
      Product: 256_1

    I'm not sure if this is a driver issue, or whatever else. All i know is that my computer was working before so my computer does not like this RAM in some way. 

    Specs: Windows 7

    AMD Phenom IIx4 955 processor

    mobo: Gigabyte GA-MA785MT-UD2H  

    Video card: Gigabyte gtx 470 fermi

    RAM: PNY XLR8 8GB (2 x 4GB) 240-Pin DDR3 SDRAM DDR3 1600 (PC3 12800)

    Just tell me if you need the dump files from the Blue screens. I would greatly appreciate any help. Thanks in advance.

    Friday, March 2, 2012 12:09 AM

All replies

  • Windows comes with it's own memory tester.
    Type memory in Start's search box and choose Memory Diagnostic then Reboot.
    Run both Normal and Advanced. This will take a few minutes.
     
     
    --
    ..
    --
    "HellzJanitor" wrote in message news:c6aae601-fc9a-440e-9ea8-8c97654dc175...
    > Hello, I recently bought 8 gigs of RAM and have got several blue screens
    > right after installing and have gotten them since. I didn't have any
    > problems with my old RAM, so this is confusing. I'm almost positive my RAM
    > is compatible, the pin is correct, I've set the correct timings,
    > everything i can think of compatibly wise. The last few times its blue
    > screened, i have left my computer running and it eventually sleeps, but i
    > come back to an crashed computer.
    >
    > The Blue Screen message is:
    >
    > BCCode: a
    > BCP1: 0000000000000000
    > BCP2: 0000000000000002
    > BCP3: 0000000000000001
    > BCP4: FFFFF800034D96EC
    > OS Version: 6_1_7601
    > Service Pack: 1_0
    > Product: 256_1
    >
    >
    > I'm not sure if this is a driver issue, or whatever else. All i know is
    > that my computer was working before so my computer does not like this RAM
    > in some way.
    >
    > Specs: Windows 7
    >
    > AMD Phenom IIx4 955 processor
    >
    > mobo: Gigabyte GA-MA785MT-UD2H
    >
    > Video card: Gigabyte gtx 470 fermi
    >
    > RAM: PNY XLR8 8GB (2 x 4GB) 240-Pin DDR3 SDRAM DDR3 1600 (PC3 12800)
    >
    > Just tell me if you need the dump files from the Blue screens. I would
    > greatly appreciate any help. Thanks in advance.
    >
     
     
    Friday, March 2, 2012 5:59 AM
  • Yea, I ran memtest right when i got the ram, I let it run for many passes with zero errors. The memory doesn't seem defective, plus this is the second set of memory that i have bought that doesn't work correctly, but both came up fine on memtest. I think this goes deeper than the RAM being just defective. Thanks for the responses though.
    Monday, March 5, 2012 9:21 PM
  • Run Memory Diagnostic in both normal and advanced mode. One runs the test
    using the memory cache and one runs the test without.
     
    Memory cache is high speed memory.
     
    Upload your dump files somewhere and post a link and I'll analyse them.
    --
    ..
    --
    "HellzJanitor" wrote in message news:3b3384c3-b72a-4452-9777-fa16f717662f...
    > Yea, I ran memtest right when i got the ram, I let it run for many passes
    > with zero errors. The memory doesn't seem defective, plus this is the
    > second set of memory that i have bought that doesn't work correctly, but
    > both came up fine on memtest. I think this goes deeper than the RAM being
    > just defective. Thanks for the responses though.
     
     
    Tuesday, March 6, 2012 6:53 AM
  • If you want to analyse your own dump files.
     
    Download and install Debugging Tools for Windows
    http://msdn.microsoft.com/en-us/windows/hardware/hh852363
    Install theWindows SDK but just choose the debugging tools.
     
    Create a folder called Symbols in C:\
     
    Start Windbg. File menu - Symbol File Path and enter
    srv*C:\symbols*http://msdl.microsoft.com/download/symbols
     
    Close and reopen WinDbg. File menu - Open Crash Dump
     
    This will analyse the crash dump. You need to close and reopen WinDbg for
    each dump file analysed. Because you are downloading symbols from the
    internet WinDbg will appear to be doing nothing. But it's downloading. Be
    patient.
     
    Type in theWinDbg command prompt
     
    !analyze -v
     
    -v stands for Vernose and if it's caused by a program it will appear in the
    middle of the listing.
    --
    ..
    --
    "HellzJanitor" wrote in message news:3b3384c3-b72a-4452-9777-fa16f717662f...
    > Yea, I ran memtest right when i got the ram, I let it run for many passes
    > with zero errors. The memory doesn't seem defective, plus this is the
    > second set of memory that i have bought that doesn't work correctly, but
    > both came up fine on memtest. I think this goes deeper than the RAM being
    > just defective. Thanks for the responses though.
     
     
    Tuesday, March 6, 2012 7:18 AM
  • -v stands for Vernose
     
    is supposed to read
     
    -v stands for Verbose
    --
    ..
    --
    "DavidMCandy" wrote in message news:52033900-4c1f-49cd-9ac4-2fe0fcc24c61...
    > If you want to analyse your own dump files.
    >
    > Download and install Debugging Tools for Windows
    > http://msdn.microsoft.com/en-us/windows/hardware/hh852363
    > Install theWindows SDK but just choose the debugging tools.
    >
    > Create a folder called Symbols in C:\
    >
    > Start Windbg. File menu - Symbol File Path and enter
    > srv*C:\symbols*http://msdl.microsoft.com/download/symbols
    >
    > Close and reopen WinDbg. File menu - Open Crash Dump
    >
    > This will analyse the crash dump. You need to close and reopen WinDbg for
    > each dump file analysed. Because you are downloading symbols from the
    > internet WinDbg will appear to be doing nothing. But it's downloading. Be
    > patient.
    >
    > Type in theWinDbg command prompt
    >
    > !analyze -v
    >
    > -v stands for Vernose and if it's caused by a program it will appear in
    > the
    > middle of the listing.
    > --
    > ..
    > --
    > "HellzJanitor" wrote in message
    > news:3b3384c3-b72a-4452-9777-fa16f717662f...
    >> Yea, I ran memtest right when i got the ram, I let it run for many passes
    >> with zero errors. The memory doesn't seem defective, plus this is the
    >> second set of memory that i have bought that doesn't work correctly, but
    >> both came up fine on memtest. I think this goes deeper than the RAM being
    >> just defective. Thanks for the responses though.
    >
    >
     
     
    Tuesday, March 6, 2012 7:34 AM
  • Debugging Tools for Windows
    Bug Check 0xA: IRQL_NOT_LESS_OR_EQUAL
    The IRQL_NOT_LESS_OR_EQUAL bug check has a value of 0x0000000A. This
    indicates that Microsoft Windows or a kernel-mode driver accessed paged
    memory at DISPATCH_LEVEL or above.
     
    Parameters
    The following parameters are displayed on the blue screen.
     
    Parameter Description
    1 Memory referenced
    2 IRQL at time of reference
    3 0: Read
    1: Write
    4 Address which referenced memory
     
     
    Cause
    This bug check is issued if paged memory (or invalid memory) is accessed
    when the IRQL is too high.
     
    The error that generates this bug check usually occurs after the
    installation of a faulty device driver, system service, or BIOS.
     
    If you encounter bug check 0xA while upgrading to a later version of
    Windows, this error might be caused by a device driver, a system service, a
    virus scanner, or a backup tool that is incompatible with the new version.
     
    Resolving the Problem
    If a kernel debugger is available, obtain a stack trace.
     
    To resolve an error caused by a faulty device driver, system service, or
    BIOS
    Restart your computer.
    Press F8 at the character-based menu that displays the operating system
    choices.
    Select the Last Known Good Configuration option from the Windows Advanced
    Options menu. This option is most effective when only one driver or service
    is added at a time.
     
    To resolve an error caused by an incompatible device driver, system service,
    virus scanner, or backup tool
    Check the System Log in Event Viewer for error messages that might identify
    the device or driver that caused the error.
    Try disabling memory caching of the BIOS.
    Run the hardware diagnostics supplied by the system manufacturer, especially
    the memory scanner. For details on these procedures, see the owner's manual
    for your computer.
    Make sure the latest Service Pack is installed.
    If your system has small computer system interface (SCSI) adapters, contact
    the adapter manufacturer to obtain updated Windows drivers. Try disabling
    sync negotiation in the SCSI BIOS, checking the cabling and the SCSI IDs of
    each device, and confirming proper termination.
    For integrated device electronics (IDE) devices, define the onboard IDE port
    as Primary only. Also, check each IDE device for the proper
    master/slave/stand-alone setting. Try removing all IDE devices except for
    hard disks.
     
    If the message appears during an installation of Windows, make sure that the
    computer and all installed peripherals are listed in the Microsoft Windows
    Marketplace Tested Products List.
     
    --
    ..
    --
    "HellzJanitor" wrote in message news:3b3384c3-b72a-4452-9777-fa16f717662f...
    > Yea, I ran memtest right when i got the ram, I let it run for many passes
    > with zero errors. The memory doesn't seem defective, plus this is the
    > second set of memory that i have bought that doesn't work correctly, but
    > both came up fine on memtest. I think this goes deeper than the RAM being
    > just defective. Thanks for the responses though.
     
     
    Tuesday, March 6, 2012 7:43 AM
  • What is a good file upload website, or easier way. Or i could email you if you like.

    Wednesday, March 7, 2012 1:57 AM
  • Skydrive is Microsoft's Windows Live file upload site.
    http://explore.live.com/skydrive
     
    If you have downloaded any of the Live applications or have a web based live
    mail account you already have access to your Skydrive.
     
    Put your dumps in the public folder and copy the link from the address bar.
    --
    ..
    --
    "HellzJanitor" wrote in message news:3b2a0407-bdde-4ed1-91bd-d39cc86520d7...
    > What is a good file upload website, or easier way. Or i could email you if
    > you like.
    >
     
     
    Wednesday, March 7, 2012 6:46 AM
  • https://skydrive.live.com/#cid=BF90C7C43FDFECF9&id=BF90C7C43FDFECF9%21103&sc=documents
    O
    kay, i think i uploaded them correctly, if not, i'll try again. Thanks!

    Wednesday, March 7, 2012 11:45 PM
  • btw, i uploaded only 5 because the others were really old. These five were all in the last month with all the current hardware.
    Wednesday, March 7, 2012 11:47 PM
  • *******************************************************************************
    *
    *
    * Bugcheck Analysis
    *
    *
    *
    *******************************************************************************
     
    Use !analyze -v to get detailed debugging information.
     
    BugCheck A, {0, 2, 1, fffff800034d56ec}
     
    Unable to load image \SystemRoot\system32\DRIVERS\scmndisp.sys, Win32 error
    2
    *** WARNING: Unable to verify timestamp for scmndisp.sys
    *** ERROR: Module load completed but symbols could not be loaded for
    scmndisp.sys
    Probably caused by : scmndisp.sys ( scmndisp+16d1 )
     
    Followup: MachineOwner
    ---------
    *******************************************************************************
    *
    *
    * Bugcheck Analysis
    *
    *
    *
    *******************************************************************************
     
    Use !analyze -v to get detailed debugging information.
     
    BugCheck 3B, {c0000005, fffff800034ac4db, fffff8800788be10, 0}
     
    Probably caused by : ntkrnlmp.exe ( nt!RtlDeleteNoSplay+93 )
     
    Followup: MachineOwner
     
    PROCESS_NAME: svchost.exe
    ---------
    *******************************************************************************
    *
    *
    * Bugcheck Analysis
    *
    *
    *
    *******************************************************************************
     
    Use !analyze -v to get detailed debugging information.
     
    BugCheck A, {ffffffffffffffd0, 2, 1, fffff80003482471}
     
    Unable to load image \SystemRoot\System32\Drivers\sptd.sys, Win32 error 2
    *** WARNING: Unable to verify timestamp for sptd.sys
    *** ERROR: Module load completed but symbols could not be loaded for
    sptd.sys
    Probably caused by : sptd.sys ( sptd+46570 )
     
    Followup: MachineOwner
     
    PROCESS_NAME: System
    ---------
     
    c:\windows\system32\DRIVERS\scmndisp.sys
    c:\windows\System32\Drivers\sptd.sys
     
    Are the two third party files referenced. Are they from the same driver
    package.
     
    The 0xa error is trying to read or write to memory address 0. Addresses 0 to
    64K are unused and will generate an error.
    --
    ..
    --
    "HellzJanitor" wrote in message news:9da062f3-a448-49bf-8b05-28b8d3c8dde9...
    >
    > https://skydrive.live.com/#cid=BF90C7C43FDFECF9&id=BF90C7C43FDFECF9%21103&sc=documents
    > Okay, i think i uploaded them correctly, if not, i'll try again. Thanks!
    >
     
     
    Thursday, March 8, 2012 7:05 AM
  • PS I meant to add right click - Properties the two files and see what the
    details say about the file.
     
    PPS The reason why 0 is an invalid address is that common programming errors
    mean programs will try to access memory address 0. So Windows puts it off
    limit so programmers catch their errors rather than the program running wild
    and corrupting data.
    --
    ..
    --
    "DavidMCandy" wrote in message news:4fa35c21-6ea4-4d9c-9f07-9a58b07f86f8...
    > *******************************************************************************
    > *
    > *
    > * Bugcheck Analysis
    > *
    > *
    > *
    > *******************************************************************************
    >
    > Use !analyze -v to get detailed debugging information.
    >
    > BugCheck A, {0, 2, 1, fffff800034d56ec}
    >
    > Unable to load image \SystemRoot\system32\DRIVERS\scmndisp.sys, Win32
    > error
    > 2
    > *** WARNING: Unable to verify timestamp for scmndisp.sys
    > *** ERROR: Module load completed but symbols could not be loaded for
    > scmndisp.sys
    > Probably caused by : scmndisp.sys ( scmndisp+16d1 )
    >
    > Followup: MachineOwner
    > ---------
    > *******************************************************************************
    > *
    > *
    > * Bugcheck Analysis
    > *
    > *
    > *
    > *******************************************************************************
    >
    > Use !analyze -v to get detailed debugging information.
    >
    > BugCheck 3B, {c0000005, fffff800034ac4db, fffff8800788be10, 0}
    >
    > Probably caused by : ntkrnlmp.exe ( nt!RtlDeleteNoSplay+93 )
    >
    > Followup: MachineOwner
    >
    > PROCESS_NAME: svchost.exe
    > ---------
    > *******************************************************************************
    > *
    > *
    > * Bugcheck Analysis
    > *
    > *
    > *
    > *******************************************************************************
    >
    > Use !analyze -v to get detailed debugging information.
    >
    > BugCheck A, {ffffffffffffffd0, 2, 1, fffff80003482471}
    >
    > Unable to load image \SystemRoot\System32\Drivers\sptd.sys, Win32 error 2
    > *** WARNING: Unable to verify timestamp for sptd.sys
    > *** ERROR: Module load completed but symbols could not be loaded for
    > sptd.sys
    > Probably caused by : sptd.sys ( sptd+46570 )
    >
    > Followup: MachineOwner
    >
    > PROCESS_NAME: System
    > ---------
    >
    > c:\windows\system32\DRIVERS\scmndisp.sys
    > c:\windows\System32\Drivers\sptd.sys
    >
    > Are the two third party files referenced. Are they from the same driver
    > package.
    >
    > The 0xa error is trying to read or write to memory address 0. Addresses 0
    > to
    > 64K are unused and will generate an error.
    > --
    > ..
    > --
    > "HellzJanitor" wrote in message
    > news:9da062f3-a448-49bf-8b05-28b8d3c8dde9...
    >>
    >> https://skydrive.live.com/#cid=BF90C7C43FDFECF9&id=BF90C7C43FDFECF9%21103&sc=documents
    >> Okay, i think i uploaded them correctly, if not, i'll try again. Thanks!
    >>
    >
    >
     
     
    Thursday, March 8, 2012 7:38 AM
  • So.. This is a driver issue? Or you couldn't read the dump files? Sorry, I'm not that familiar with this sort of stuff.
    Thursday, March 8, 2012 9:33 PM
  • I posted the output from the Debugging Tools for Windows built-in automated
    dump file analyser called !analyze. Did you see it and my summary at the
    bottom?
     
    Out of your 5 files there were 5 seperate errors with 3 causes. So seperate
    two errors had the same cause as identified by
    !analyze command.
     
    One cause pointed to a windows file (c:\windows\system32\NTdll.dll). This
    doesn't necessarily mean there is a problem with that file, it may be
    elsewhere and just surface in NTdll.
     
    The other two errors pointed to drivers with similar names, They may be
    related drivers. The two files are
     
    c:\windows\system32\DRIVERS\scmndisp.sys
    c:\windows\System32\Drivers\sptd.sys
     
    Right click - Properties the two files and see what the details tab say
    about the files.
     
    This doesn't mean it can't be memory. But lets see where those two drivers
    come from.
    --
    ..
    --
    "HellzJanitor" wrote in message news:ea3d0c3e-0171-460c-8e6f-c24141f299c0...
    > So.. This is a driver issue? Or you couldn't read the dump files? Sorry,
    > I'm not that familiar with this sort of stuff.
     
     
    Friday, March 9, 2012 9:44 AM
  • Well, I checked those 2 drivers, One had the name netgear, which is my wireless card. I've noticed that after I turn my pc off and on, the card fails, so that makes sense. The other driver I couldn't get any information on, It just said it was a system file and was in use. So, not to sure about the second one. Also, I've had alot of times where my PC will just restart itself without a blue screen. It actually just happened about 10 mins ago, so I don't know whats causing that, or caused by the same problems as the blue screen dumps. Thanks.
    Friday, March 9, 2012 6:26 PM
  • The two major causes of computers rebooting for no reason are heat or a
    faulty power supply. Memory (or a driver) might also cause it.
     
    For heat - vaccum the dust out of the fans. Fans wear out especially cheap
    fans. Make sure they are spinning. If you feel comfortable doing this try
    removing the case and check the fan on the CPU for dust and make sure it's
    spinning. But the case fans are the ones that fill up with dust first.
     
    I don't know how to test for a failing power supply. Power supplies are
    cheap. The cost of replacing the power supply is cheaper than testing it
    (around $20 for a cheap power supply).
     
    For the driver you identified see if there is an update at
    http://downloadcenter.netgear.com/ .
     
    For the driver you didn't identify open in Notepad (make sure Word Wrap is
    on in Notepad's Format menu) and scan through the random characters looking
    for English saying what the file is.
     
    --
    ..
    --
    "HellzJanitor" wrote in message news:50dba002-a102-48d8-8899-7d5f06b3f7ae...
    > Well, I checked those 2 drivers, One had the name netgear, which is my
    > wireless card. I've noticed that after I turn my pc off and on, the card
    > fails, so that makes sense. The other driver I couldn't get any
    > information on, It just said it was a system file and was in use. So, not
    > to sure about the second one. Also, I've had alot of times where my PC
    > will just restart itself without a blue screen. It actually just happened
    > about 10 mins ago, so I don't know whats causing that, or caused by the
    > same problems as the blue screen dumps. Thanks.
     
     
    Friday, March 9, 2012 9:00 PM
  • PS. When working on Desktop computers leave them plugged into the powerpoint
    but turn the powerpoint off.
     
    This leaves the computer earthed so static electricity won't be a problem.
     
    --
    ..
    --
    "HellzJanitor" wrote in message news:50dba002-a102-48d8-8899-7d5f06b3f7ae...
    > Well, I checked those 2 drivers, One had the name netgear, which is my
    > wireless card. I've noticed that after I turn my pc off and on, the card
    > fails, so that makes sense. The other driver I couldn't get any
    > information on, It just said it was a system file and was in use. So, not
    > to sure about the second one. Also, I've had alot of times where my PC
    > will just restart itself without a blue screen. It actually just happened
    > about 10 mins ago, so I don't know whats causing that, or caused by the
    > same problems as the blue screen dumps. Thanks.
     
     
    Friday, March 9, 2012 9:05 PM
  • Okay, I installed the new netgear driver. I'm almost positive the random restarts are not caused by cooling or the PSU, My case causes all my components to run at pretty cool temps, and I just got a new power supply about 2 months ago. It would have to be caused by this new memory, or a driver. But, when i try to analyse this other driver with notepad, I'm not able to because its always in use because its a system driver. Is there a way I can get around this? I'm guessing this might be the main driver causing my problem, if not the netgear driver. Thanks.
    Saturday, March 10, 2012 2:41 AM
  • That's curious. A running file does not prevent you from opening it in a program like notepad. Something else is going on.
     
    Type in a command prompt substituting the correct driver name at the end of the command.
    reg query "HKLM\SYSTEM\CurrentControlSet\Services" /s /f "sptd.sys"
     

    --
    .
    --
    "HellzJanitor" wrote in message news:434e2e32-a11a-47a6-8c48-fe46e7b99e7f...
    > Okay, I installed the new netgear driver. I'm almost positive the random restarts are not caused by cooling or the PSU, My case causes all my components to run at pretty cool temps, and I just got a new power supply about 2 months ago. It would have to be caused by this new memory, or a driver. But, when i try to analyse this other driver with notepad, I'm not able to because its always in use because its a system driver. Is there a way I can get around this? I'm guessing this might be the main driver causing my problem, if not the netgear driver. Thanks.
    Saturday, March 10, 2012 3:56 AM
  • hmm, I didn't really get how to use command prompt like that but, I did find out that the driver sptd.sys has to do with stuff like daemon tools or alcohol 120, Virtual drives. I've dealt with daemon tools and creating virtual drives before. Don't know what i could of done to harm anything but, who knows.
    Saturday, March 10, 2012 11:41 PM
  • Ok. Do this instead.
     
    Click Start - All Programs - Accessories - Right click Command Prompt and choose Run As Administrator.
     
    Type
     
    Regedit
    Go to HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services
     
    Select the Services key and click Edit menu then Find.
     
    Enter the first filename scmndisp.sys. Click Find Next.

    When it finds the file it will be in a subkey of the Services key. Select that subkey. Right click it and choose Export. Save it to your desktop (or anywhere you want).
     
    Delete the subkey.
     
    Repeat for sptd.sys.
     
    Reboot. Operate your computer and see if the error has gone. Your hardware won't work as the drivers won't be loaded.
     
    To undo what we've done double click the two files we saved and reboot.
     
     
    --
    .
    --
    "HellzJanitor" wrote in message news:e17d3c25-a599-4f08-99f2-b3d1a5a71020...
    > hmm, I didn't really get how to use command prompt like that but, I did find out that the driver sptd.sys has to do with stuff like daemon tools or alcohol 120, Virtual drives. I've dealt with daemon tools and creating virtual drives before. Don't know what i could of done to harm anything but, who knows.
    Tuesday, March 13, 2012 8:08 AM
  • Sorry I haven't responded in a while. I've deleted both of the drivers. I haven't got a blue screen in a while. Seems like its running well (hopefully). I really appreciate all of your help, thank you very much. 
    Monday, March 26, 2012 10:05 PM
  • Good
     
    --
    ..
    --
    "HellzJanitor" wrote in message news:d25691ab-1d65-4628-8075-7e37787fd186...
    > Sorry I haven't responded in a while. I've deleted both of the drivers. I
    > haven't got a blue screen in a while. Seems like its running well
    > (hopefully). I really appreciate all of your help, thank you very much.
     
     
    Tuesday, March 27, 2012 6:51 AM