Sunday, March 20, 2016

[Anwsered] 4GB of RAM causes Computer to crash

4GB of RAM causes Computer to crash

When I try to use 4GB of RAM in my computer, it crashes
 
Either it will crash then load up fine the 2nd time around or it will crash constantly and give me a BSOD
 
The motherboard should be able to handle up to 8GB of RAM so I don't get why this is happening
 
It's an asrock n68-gs motherboard, with a 1.5 TB Hard Drive, Windows 7
 
Forgot to include the last dmp file sorry
 
---------------------------------------------------------------------------------------------------------------
Microsoft (R) Windows Debugger Version 6.12.0002.633 AMD64
Copyright (c) Microsoft Corporation.
All rights reserved.

Loading Dump File [C:\Windows\Minidump\032110-43250-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 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 7 Kernel Version 7600 MP (2 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Machine Name:
Kernel base = 0xfffff800`02818000 PsLoadedModuleList = 0xfffff800`02a55e50
Debug session time: Sun Mar 21 17:46:49.546 2010 (UTC + 0:00)
System Uptime: 0 days 0:01:17.000
*********************************************************************
* 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 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
....
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck A, fffffa800f184010, 2, 1, fffff80002946a57

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

*************************************************************************
***                                                                   ***
***                                                                   ***
***    Your debugger is not using the correct symbols                 ***
***                                                                   ***
***    In order for this command 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                                     ***
***                                                                   ***
*************************************************************************
*************************************************************************
***                                                                   ***
***                                                                   ***
***    Your debugger is not using the correct symbols                 ***
***                                                                   ***
***    In order for this command 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                                     ***
***                                                                   ***
*************************************************************************
*************************************************************************
***                                                                   ***
***                                                                   ***
***    Your debugger is not using the correct symbols                 ***
***                                                                   ***
***    In order for this command 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 : ntoskrnl.exe ( nt+12ea57 )

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

Anwsers to the Problem 4GB of RAM causes Computer to crash

Download Error Fixer for Free Now

What settings did you use with driver verifier? Did you reboot after running it?
The details you posted still indicate memory corruption.
Memory that passes a memory test isn't necessarily proven to be good - it's just memory that hasn't failed a test.
 Are you able to try different RAM (entirely new modules)?

This particular error can easily be resolved with a few simple steps. However, if you are not confident in your ability to use the methods below or they do not fully remove the issue on your computer, you may want to seek the assistance of a qualified repair technician who is well versed in fixing 4GB of RAM causes Computer to crash.

  1. Back-up the Registry of your operating system.
  2. Find the Registry Key: [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\WindowsUpdate\OSUpgrade]
  3. Note: this Registry Key should already exist, if it does not exist, create it.
  4. Create a brand new DWORD Value that is named AllowOsUpdate
  5. Set the Value to 0x00000001.
  6. Close and reopen your Control Panel.
  7. Restart the Microsoft Windows.

Another Safe way to Repair the Problem: 4GB of RAM causes Computer to crash:

 

 

How to Fix 4GB of RAM causes Computer to crash with SmartPCFixer?

1. Download Error Fixer. Install it on your system.

2. After the scan is done, you can see the errors and problems which need to be repaired.

3. When the Fixing part is done, your computer has been speeded up and the errors have been fixed


Related: How to Fix 3371 Errors in Windows XP,7,8&8.1?,Repair Corrupt Cab Files Error - How to Fix,Skchui.dll Error - How to Fix,Symantec Antivirus Slows Down Computer Error - How to Resolve,Error Windows Xp System Restore Incomplete Fix Solution,How to Fix - After updating from Internet Explorer 6 to Internet Explorer 9, my Favorites are lost?,How to Fix - Combination Stacked-Clustered Chart in Excel - Align data with horizontal tick marks?,Solution to Error: Macro to search and copy rows to different sheets based on cell value,Need solution to this problem in order to stop Vista from beeping.__"Your version of Microsoft Deprecated DLL Components isn't compatible with this version of Windows",Server Error in '/' Application.Site also runtime error [Solved]
Read More: Solution to Error: 4G issues and Wifi connection.,[Solved] 4in1 HP printer will not print,How to Fix - 4 x 6 index card in word does not print correctly?,[Solved] 7.Error \"7.2.241.1enRegInstaller.exe stropped working and was closed. A problem caused the application to stop working correctly. Windows will notify you if a solution is available\",Fast Solution to Problem: 64 bit SSD slow compared to my 32 bit & Internet no longer working,2 msn.com site,2007 Performance Issue / Very slow saves to network share,Can I use my HP D110A web service printer as a proxy server?,can i use a zoom 56k v.92/v.90 modem with 64b dileup? netzero said i might have the rong modem?,Can I downgrade to win 32-bit?

No comments:

Post a Comment