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
*
* 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
*
* 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 SmartPCFixer to Fix It (Free)
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)?
Check Windows System Requirements
This error can be due to some configuration requirements for you system. If your PC hardware is not up to par, then make sure you upgrade where necessary before continuing:
Microsoft Windows Requirements :
- 1 gigahertz (GHz) or faster 32-bit (x86) or 64-bit (x64) processor
- 16 GB available hard disk space (32-bit) or 20 GB (64-bit)
Another Safe way to Fix the Problem: 4GB of RAM causes Computer to crash:
How to Fix 4GB of RAM causes Computer to crash with SmartPCFixer?
1. Click the button to download Error Fixer . Install it on your system. Open it, and it will perform a scan for your computer. The junk files will be shown in the scan result.
2. After the scan is done, you can see the errors and problems need to be fixed. Click Fix All.
3. When the Fixing part is finished, your computer has been speeded up and the errors have been removed
Related:
Read More: How Can You Fix - 2013 Excel does not work?,[Solved] 10\/4\/2013 Com surrogate has stopped working i have tried all other posts nothing works,2 much svchost running on my computer [Anwsered],1220c+driver+windows 7+x64,Troubleshoot:2007 single-language proofing pack for Russian,2 BSODs On WINDOWS 7 HOME PREMIUM 64 BIT,2 problems with Vista and mail on new laptop,500 gb iomega external hard drive,32-bit Shell extension error in drive,7n feature pack
No comments:
Post a Comment