Benrith

not looking too good http://www.sevenforums.com/bsod-help-support/348094-bsod-help-please-i-m-novice-please-forgive-my-ignorance-2.html#post2905388

Yeah i got the 280x windforce edition.

This sucks. Just found out i'm working on the sat. wont get home until 6:30 GMT. by which time there will only be 1.5hrs left!!

Ouch. You're having as much fun as I am then!

Not any more boom, only on bf4 now. I was able to play for about 20 mins last night without it crashing after installing driver 13.9 instead of the current one as suggested by windows 7 professionals on their fourms. But i'm going to check it out for longer today and hope it's been resolved. They did say the current drivers for the R9 200 series is a little dodgy to say the least. They also said to uninstall all drivers apart from display which I've done. here's to hoping it's fixed.

All correct apart from HDD. Haven't bought a new HDD yet. Since I've installed the new GPU I seem to get the same error over and over... atikmdag.sys

are these what you are looking for? Microsoft ® Windows Debugger Version 6.3.9600.17237 AMD64 Copyright © Microsoft Corporation. All rights reserved. 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 *** *** *** ************************************************************************* ************************************************************************* *** *** *** *** *** 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 : atikmdag.sys ( atikmdag+c5c30 ) Followup: MachineOwner ---------

here's a list of all the errors.

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

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?

Sorry to hear it mouse!

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

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).

I'm OP, nuff said.

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

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?

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.

Haven't been playing to be honest. So don't know. I the main error I've noticed is the game just crashing without a bsod but some times it does go to a bsod. We'll see in a few more days.

That's too sophisticated, I use a hacksaw! Nah, looking at some new cases to be honest. they can be fairly cheap. Found this one. what do people think? http://www.scan.co.uk/products/zalman-z3-black-mid-tower-case-usb-30-w-o-psu Plenty of air flow.

oppps... not sure if my card is going to fit into my case now lol! I always thought I had a fairly large case but now I'm not sure sure!! It gets better everytime!!

Thanks for all the input guys. After I get my GPU delivered and if that hasn't resolved the issues then I will stress the memory for at least 12 hours, all night and day while at work and see what comes up. I will re sit the CPU as well.

As OJ said, i'm not worrying about anything now until my new GPU arrives. Once that's installed lets hope it's resolved it all.

I didn't sleep long last night as i wasn't feeling well but I did the memtest86 (not the + version) for about 4.5 hrs and 4 tests complete without any errors popping up. Not sure if the non + version makes a difference?

Did the mem test over night last night and nothing came up.

Well that's a shame, just got offered 780 GTX WIndforce for £190. Ahh well never mind. My budget was £150.00 so I guess I should be pleased that I haven't overspent. Esp as my new card is still a very good deal.