Do I Have Bad Memory (RAM)?

oXObsidianXo · Nov 28, 2014

So lately I've been having issues with boot loops before posting, sudden frame rate drops, and recently crashes.

I checked my BIOS settings and found that my RAM was clocked at 1333, it is 1866mhz RAM. I enabled XMP which set the timing's, voltage, and frequency to what they should have been, played a game of BF4, and immediately after, the game crashed and I blue screened.

Here is the minidump file from the crash that occurred right after I set my RAM to stock settings:

Microsoft (R) Windows Debugger Version 6.3.9600.17298 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.

Loading Dump File [C:\Windows\Minidump\112814-18296-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: *** Invalid ***
****************************************************************************
* Symbol loading may be unreliable without a symbol search path. *
* Use .symfix to have the debugger choose a symbol path. *
* After setting your symbol path, use .reload to refresh symbol locations. *
****************************************************************************
Executable search path is:
*********************************************************************
* Symbols can not be loaded because symbol path is not initialized. *
* *
* The Symbol Path can be set by: *
* using the _NT_SYMBOL_PATH environment variable. *
* using the -y <symbol_path> argument when starting the debugger. *
* using .sympath and .sympath+ *
*********************************************************************
Unable to load image \SystemRoot\system32\ntoskrnl.exe, Win32 error 0n2
*** WARNING: Unable to verify timestamp for ntoskrnl.exe
*** ERROR: Module load completed but symbols could not be loaded for ntoskrnl.exe
Windows 8 Kernel Version 9600 MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 9600.17415.amd64fre.winblue_r4.141028-1500
Machine Name:
Kernel base = 0xfffff803`17e77000 PsLoadedModuleList = 0xfffff803`18150250
Debug session time: Fri Nov 28 16:15:09.566 2014 (UTC - 8:00)
System Uptime: 0 days 0:25:18.191
*********************************************************************
* Symbols can not be loaded because symbol path is not initialized. *
* *
* The Symbol Path can be set by: *
* using the _NT_SYMBOL_PATH environment variable. *
* using the -y <symbol_path> argument when starting the debugger. *
* using .sympath and .sympath+ *
*********************************************************************
Unable to load image \SystemRoot\system32\ntoskrnl.exe, Win32 error 0n2
*** WARNING: Unable to verify timestamp for ntoskrnl.exe
*** ERROR: Module load completed but symbols could not be loaded for ntoskrnl.exe
Loading Kernel Symbols
...............................................................
................................................................
.............................................
Loading User Symbols
Loading unloaded module list
...................

************* Symbol Loading Error Summary **************
Module name Error
ntoskrnl The system cannot find the file specified

You can troubleshoot most symbol related issues by turning on symbol loading diagnostics (!sym noisy) and repeating the command that caused symbols to be loaded.
You should also verify that your symbol search path (.sympath) is correct.
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 1A, {41792, fffff6804440fbf8, 8000000000000000, 0}

***** Kernel symbols are WRONG. Please fix symbols to do analysis.

*************************************************************************
*** ***
*** ***
*** Either you specified an unqualified symbol, or your debugger ***
*** doesn't have full symbol information. Unqualified symbol ***
*** resolution is turned off by default. Please either specify a ***
*** fully qualified symbol module!symbolname, or enable resolution ***
*** of unqualified symbols by typing ".symopt- 100". Note that ***
*** enabling unqualified symbol resolution with network symbol ***
*** server shares in the symbol path may cause the debugger to ***
*** appear to hang for long periods of time when an incorrect ***
*** symbol name is typed or the network symbol server is down. ***
*** ***
*** For some commands to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!_KPRCB ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** Either you specified an unqualified symbol, or your debugger ***
*** doesn't have full symbol information. Unqualified symbol ***
*** resolution is turned off by default. Please either specify a ***
*** fully qualified symbol module!symbolname, or enable resolution ***
*** of unqualified symbols by typing ".symopt- 100". Note that ***
*** enabling unqualified symbol resolution with network symbol ***
*** server shares in the symbol path may cause the debugger to ***
*** appear to hang for long periods of time when an incorrect ***
*** symbol name is typed or the network symbol server is down. ***
*** ***
*** For some commands to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!KPRCB ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** Either you specified an unqualified symbol, or your debugger ***
*** doesn't have full symbol information. Unqualified symbol ***
*** resolution is turned off by default. Please either specify a ***
*** fully qualified symbol module!symbolname, or enable resolution ***
*** of unqualified symbols by typing ".symopt- 100". Note that ***
*** enabling unqualified symbol resolution with network symbol ***
*** server shares in the symbol path may cause the debugger to ***
*** appear to hang for long periods of time when an incorrect ***
*** symbol name is typed or the network symbol server is down. ***
*** ***
*** For some commands to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!_KPRCB ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** Either you specified an unqualified symbol, or your debugger ***
*** doesn't have full symbol information. Unqualified symbol ***
*** resolution is turned off by default. Please either specify a ***
*** fully qualified symbol module!symbolname, or enable resolution ***
*** of unqualified symbols by typing ".symopt- 100". Note that ***
*** enabling unqualified symbol resolution with network symbol ***
*** server shares in the symbol path may cause the debugger to ***
*** appear to hang for long periods of time when an incorrect ***
*** symbol name is typed or the network symbol server is down. ***
*** ***
*** For some commands to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!KPRCB ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** Either you specified an unqualified symbol, or your debugger ***
*** doesn't have full symbol information. Unqualified symbol ***
*** resolution is turned off by default. Please either specify a ***
*** fully qualified symbol module!symbolname, or enable resolution ***
*** of unqualified symbols by typing ".symopt- 100". Note that ***
*** enabling unqualified symbol resolution with network symbol ***
*** server shares in the symbol path may cause the debugger to ***
*** appear to hang for long periods of time when an incorrect ***
*** symbol name is typed or the network symbol server is down. ***
*** ***
*** For some commands to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!_KPRCB ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** Either you specified an unqualified symbol, or your debugger ***
*** doesn't have full symbol information. Unqualified symbol ***
*** resolution is turned off by default. Please either specify a ***
*** fully qualified symbol module!symbolname, or enable resolution ***
*** of unqualified symbols by typing ".symopt- 100". Note that ***
*** enabling unqualified symbol resolution with network symbol ***
*** server shares in the symbol path may cause the debugger to ***
*** appear to hang for long periods of time when an incorrect ***
*** symbol name is typed or the network symbol server is down. ***
*** ***
*** For some commands to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!_KPRCB ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** Either you specified an unqualified symbol, or your debugger ***
*** doesn't have full symbol information. Unqualified symbol ***
*** resolution is turned off by default. Please either specify a ***
*** fully qualified symbol module!symbolname, or enable resolution ***
*** of unqualified symbols by typing ".symopt- 100". Note that ***
*** enabling unqualified symbol resolution with network symbol ***
*** server shares in the symbol path may cause the debugger to ***
*** appear to hang for long periods of time when an incorrect ***
*** symbol name is typed or the network symbol server is down. ***
*** ***
*** For some commands to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!_KPRCB ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** Either you specified an unqualified symbol, or your debugger ***
*** doesn't have full symbol information. Unqualified symbol ***
*** resolution is turned off by default. Please either specify a ***
*** fully qualified symbol module!symbolname, or enable resolution ***
*** of unqualified symbols by typing ".symopt- 100". Note that ***
*** enabling unqualified symbol resolution with network symbol ***
*** server shares in the symbol path may cause the debugger to ***
*** appear to hang for long periods of time when an incorrect ***
*** symbol name is typed or the network symbol server is down. ***
*** ***
*** For some commands to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!_KPRCB ***
*** ***
*************************************************************************
Probably caused by : memory_corruption ( ONE_BIT )

Followup: MachineOwner
---------

It says "Probably caused by: memory_corruption" at the bottom which leads me to believe that my RAM is the problem, but I don't know what the rest means. So what do you guys think? Do I need to replace my RAM? Or could the problem be software related?

Thank you very much to anyone who replies.

Tradesman1 · Nov 28, 2014

What mobo, CPU and model # of the DRAM?

oXObsidianXo · Nov 29, 2014

Tradesman1 :

MOBO: MSI Z87 GD65
CPU: Intel Core i5-4670K @ 3.4ghz
DRAM: Corsair Vengeance CMZ8GX3M2A1866C9B

RAM Specs: 1866MHz, 9-10-9-27, 1.50V

http://www.corsair.com/en-ca/vengeance-8gb-dual-channel-ddr3-memory-kit-cmz8gx3m2a1866c9

Tradesman1 · Nov 29, 2014

Do you have the latest BIOS? Sticks in slots 1-3 from CPU? If yes to both, try raising DRAM voltage to 1.56

oXObsidianXo · Nov 29, 2014

Tradesman1 :

Yes, I updated my BIOS today. I'm currently playing on a single stick of RAM to see if one of my sticks is bad. If I still have problems after testing both, I will try raising DRAM voltage and let you know what happens.

Tradesman1 · Nov 29, 2014

Will be waiting to hear 😉

oXObsidianXo · Nov 29, 2014

So I tested one stick and it seemed ok, then as I was swapping the sticks I noticed on my Mobo it had a diagram like this:

Dimm 1------
---------------
Dimm 2--->F
---------------I
Dimm 3-----R
---------------S
Dimm 4--->T

I was running my RAM in Dimms 3 and 4. Would that cause any problems? I noticed in your previous post you mentioned slots 1 and 3. Does the which slots the RAM is in make a difference?

P.S. Sorry, this is the first PC I've ever built.

Tradesman1 · Nov 29, 2014

Typically (from CPU the slots are A1 A2 B1 B2 , the A slots being Channel A and the B Slots being Channel B - for dual channel you populat A1 and B1 or A2 and B2, putting both sticks in say B1 and B2 has the DRAM running in single channel mode

oXObsidianXo · Nov 29, 2014

Tradesman1 :

Ok, I will update you once I have more data regarding the current RAM configuration.

oXObsidianXo · Dec 3, 2014

Tradesman1 :

Update: So since putting my RAM sticks in the correct Dimm slots, I no longer have any boot loops and my overall system stability has greatly increased. This includes my ability to overclock both my RAM and my CPU.

However, I am still having a problem with memory usage while my computer is running. Here are 2 example that have both occurred within the past 24 hours.

1) While playing BF4, I will start out around 120-144 FPS. However, as I play consecutive games, my FPS gradually decrease. Within 3-5 games my FPS will be 25-45. Exiting the game does not help, my computer must be restarted, which only restarts the problem.

2) Last night, I turned my computer on in order to continue reinstalling BF4 DLC's. When I first booted my computer my memory usage was a roughly 27-30%. This was with only EA Origin running, as well as drivers and AVG (Anti-Virus). 6 hours later, when I woke up, I checked my memory usage again, 65%. I then went and did some work for 4-5 hours, and when I returned my memory usage was at 89%. The last time I returned, my computer was running very slowly and when I tried to open Google Chrome my PC froze completely and needed to be rebooted physically.

Tradesman1 · Dec 3, 2014

Might try increasing the size of your page file and see if it helps, also clean out anything in start up that's not needed

oXObsidianXo · Dec 4, 2014

Tradesman1 :

I set my page file on my SSD to "System Managed" and I have an 8000Mb page file on my SSD. I also, cleaned out my start up programs, but I'm still having problems.

oXObsidianXo · Dec 5, 2014

Tradesman1 :

My PC just crashed and boot looped. The boot loop only lasted 2 reboots, but that still leads me to believe that one or both of my RAM sticks are bad. Any thoughts?

Tradesman1 · Dec 5, 2014

COuld be, try each individually, if both run OK migth be voltage or timings are off, can get that info w/ CPU-Z in the memory tab

oXObsidianXo · Dec 5, 2014

Tradesman1 :

Timings are fine (9-10-9-27), and according to HWiNFO64 the voltage is 1.5V which is what it should be. I'll be ordering new RAM, when it is installed and I have some data, I will update.

Tradesman1 · Dec 5, 2014

Will be looking for your update

oXObsidianXo · Dec 11, 2014

Tradesman1 :

Update: So my new RAM got here Tuesday, and it seems to have improved my system stability. However, I am almost certain at this point that I have a memory leak. Below is a screenshot on RamMap and Windows Performance Toolkit, and as you can see, with only a few programs open, a process listed as "Unknown" (-1) is taking up over 3GB while idle.

In another forum, someone had previously posted that updating their monitor driver solved there problem. I have done so, and will update again on the results of that.

Do you have any thoughts?

Tradesman1 · Dec 11, 2014

Is this Win8? Might look at this for Perf View

http://stackoverflow.com/questions/17690452/newer-versions-of-xperfview-dont-have-a-summary-option

oXObsidianXo · Dec 11, 2014

Tradesman1 :

Yes, this is Windows 8.1. I checked the link you posted, but I am unable to find "xperfview.exe".

oXObsidianXo · Dec 17, 2014

While restarting today, I encountered a temporary failure to boot along side this error code: 0xc000000e

Any idea what might be happening? I'm going to do a full reinstall of windows in the next couple days if I cannot figure this out.

Tradesman1 · Dec 17, 2014

That might be the best approach at this point......

oXObsidianXo · Dec 25, 2014

Tradesman1 :

Windows reinstall seems to have solved my issue. PC has been on for 2 days straight (previously impossible), and my RAM usage stays below 50% except when gaming.

My boot loops are solved, and the "Failure to Boot" seems to have a relation to my CPU overclock. Resetting my BIOS solves that, and haven't had a boot up failure in 3-4 days.

Tradesman1 · Dec 25, 2014

Glad to hear 😉

Do I Have Bad Memory (RAM)?

Honorable

Legenda in Aeternum

Honorable

Legenda in Aeternum

Honorable

Legenda in Aeternum

Honorable

Legenda in Aeternum

Honorable

Honorable

Legenda in Aeternum

Honorable

Honorable

Legenda in Aeternum

Honorable

Legenda in Aeternum

Honorable

Legenda in Aeternum

Honorable

Honorable

Legenda in Aeternum

Honorable

Legenda in Aeternum

Share this page