Computer dying

Benrith · October 4, 2014

Looks like I might be buying some more ram as well then lol. But to be fair its not just bf4 it's any game to be honest.

Benrith · October 4, 2014

For the most part. can any MB take quad channel memory?

Just in the mobo manual it just says:

DDR3 800/1066/133/1600 16GB max.

Doesn't talk about dual or quad channel memory so just wondering if any mobo can take quad channel?

MrBubbles · October 4, 2014

DDR3, the dual and quads are all the same and really so is the tripple channel, voltage runs a bit higher on tripple channel. For instance, I can take four ddr3 modules running in a system in dual channel mode over too a system that supports quad channel system mode, by inserting four ddr3 sticks into one bank. In two channel system you must use two banks with two sticks.

No worries, it doesn't exist!

Benrith · October 5, 2014

Ok. So is it just the number of modules running together that makes it either dual/tripple or quad?

iboomboom · October 5, 2014

Ok. So is it just the number of modules running together that makes it either dual/tripple or quad?

It's the motherboard that effectively gives you dual/tripple/quad channel access to memory effectively increasing ur memory bandwidth. You can have DDR2 in quad channel too if the motherboard supported it along with the processor. If it crashes in any game I suspect your GFX card or ur RAM instability. Make sure the correct voltage for the RAM is set in the BIOS. multi-channel configuration stresses your Memory Controller a lot.

Benrith · October 5, 2014

New GPU should arrive on Tuesday, i hope along with my new case. Looking forward to my upgrade and looking forward even more a stable computer again (I hope).

Benrith · October 6, 2014

I was right, it doesn't fit into my case. CRY CRY!!

Have to wait until tomorrow now when the case should arrive, 6am please! QQ

Benrith · October 7, 2014

Everything installed but problem not resolved. Memtest86+ completed and no errors, not one after 4 completed test which took 11 hrs 45 mins.

Guess it will be new memory now then?

mouselad · October 7, 2014

Everything installed but problem not resolved. Memtest86+ completed and no errors, not one after 4 completed test which took 11 hrs 45 mins.

Guess it will be new memory now then?

and you are still getting the exact same blue screen message?

Benrith · October 7, 2014

Random different ones. The last one was a

System_Service_Exception with no 0000000000 etc at the bottom

and before that was another one but with 000000000 etc, the below screen shot, once again i was in a rush and the photo is a bit blurred

I've done chkdsk and sfc.exe

Edited October 7, 2014 by Benrith

Benrith · October 7, 2014

here's a list of all the errors.

JohnnyNashville · October 7, 2014

I formatted and reinstalled on Tuesday and was still getting random errors. I've had a few different ones since that last screen shot.

I'll look up how to create a dump file etc.

To create a dump (.dmp) file for a process that shuts down with an exception

Run the Setup.exe program for your processor.

Notes
- By default, this Setup.exe program is included with the Userdump.exe tool in the C:\kktools\userdump8.1\Architecture folder.
- This Setup.exe program installs a kernel-mode driver, installs the Userdump.sys file, and creates the Process Dump icon in Control Panel.
- Unless you have a specific need, disable the "dump on process termination" feature when you run the Setup.exe program.
In Control Panel, double-click Process Dump.
On the Exception Monitoring tab, click New, add the appropriate program name to the Monitor list, and then click OK. For example, add a program name such as Lsass.exe, Winlogon.exe, Mtx.exe, or Dllhost.exe.
In the Monitor box, click the program name that you added in step 3, and then click Rules.
Click to select Custom Rules, select the type of error that you want to trigger for the program that you added in step 3 in the Custom rules list, and then click OK.

For example, select the Access violation (c0000005) error type.

When the monitored program generates an access violation error message, the Userdump.exe tool starts, and then the Userdump.exe tool creates a dump (.dmp) file in the %SystemRoot% folder. By analyzing this .dmp file, you may be able to isolate the cause of Winlogon access violation error messages.

To create a dump file for a hanging process

Run the Setup.exe program for your processor.

Notes
- By default, this Setup.exe program is included with the Userdump.exe tool in the C:\kktools\userdump8.1\architecture folder.
- This Setup.exe program installs a kernel-mode driver, installs the Userdump.sys file, and creates the Process Dump icon in Control Panel.
- Unless you have a specific need, disable the "dump on process termination" feature when you run the Setup.exe program.
When the program stops responding, move to the version of Userdump.exe for your processor at the command prompt, and then type the following command:
userdump PID
Note In this command, PID is a placeholder for the process ID (PID) of the program that has stopped responding. To obtain the PID of the program, open Task Manager, and then click the Process tab.

When you run the userdump PID command, a .dmp file is generated. You can use this dump file to perform post-mortem debugging with a program such as the Windbg.exe tool.

If you run Setup to install the Userdump.exe tool, some additional features are enabled. These additional features of the Userdump.exe tool are described in detail in the Userdocs.doc file that accompanies the Userdump.exe tool. These additional features include the following:

Process self-dumping. You can configure the Userdump.exe tool to automatically create a dump file for a certain program when that program encounters a certain kind of error, such as an exception handler block or a top-level unhandled exception filter.
Hot-key process snapshot. You can associate a single keystroke with an image binary to trigger the Userdump.exe tool to create a dump file.
Exception monitoring. The Userdump.exe tool can monitor programs for exceptions and can automatically generate dump files when certain exceptions occur. You can configure whether an exception triggers a dump file for each program by using the Process Dump utility. You can access the Process Dump utility from Control Panel.

Benrith · October 7, 2014

are these what you are looking for?

Microsoft ® Windows Debugger Version 6.3.9600.17237 AMD64

Loading Dump File [C:\Windows\Minidump\100714-22323-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

*** ERROR: Module load completed but symbols could not be loaded for ntoskrnl.exe

Windows 7 Kernel Version 7601 (Service Pack 1) MP (4 procs) Free x64

Product: WinNt, suite: TerminalServer SingleUserTS

Built by: 7601.18409.amd64fre.win7sp1_gdr.140303-2144

Machine Name:

Kernel base = 0xfffff800`02c05000 PsLoadedModuleList = 0xfffff800`02e48890

Debug session time: Tue Oct 7 20:30:06.408 2014 (UTC + 1:00)

System Uptime: 0 days 0:25:46.766

*********************************************************************

* 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

*** 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 3B, {c0000005, fffff88013150c30, fffff88007d61960, 0}

*** WARNING: Unable to verify timestamp for atikmdag.sys

*** ERROR: Module load completed but symbols could not be loaded for atikmdag.sys

***** 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 ***