|
Hello,
I have the problem for some months now. If I put my 2 RAM-Sticks into the Mainboard on lane 1 and 2, so according to the manual dual channel is enabled, I get a bluescreen after some minutes or hours. The fix is to just put them in 1 & 3 so it doesn't enable Dual Channel. But that is a performance loss.
Today I finally updated my BIOS to the latest non-beta-version but still I got a bluescreen. How can I find out if it's the RAM or the mainboard, since the first one is pretty cheap right now. Or do you have an idea to fix this?
This is my setup:
Windows 7 64 Bit
Gigabyte 770TA-UD3 (Biosversion: F3)
AMD Phenom X4 955 3,2 Ghz
AMD Radeon HD 5870 1 GB
4gb-kit A-Data Value DDR3 U-DIMM 1333 (2*2GB)
HL-DT-ST DVDRAM GH22NS40 ATA Device
488GB SAMSUNG SAMSUNG HD502HJ ATA Device (SATA)
+ Show Spoiler [Bluescreen Information] +Problemsignatur: Problemereignisname: BlueScreen Betriebsystemversion: 6.1.7601.2.1.0.768.3 Gebietsschema-ID: 1031 Zusatzinformationen zum Problem: BCCode: 50 BCP1: FFFFF8000B5160F0 BCP2: 0000000000000000 BCP3: FFFFF800032F4756 BCP4: 0000000000000002 OS Version: 6_1_7601 Service Pack: 1_0 Product: 768_1 Dateien, die bei der Beschreibung des Problems hilfreich sind: C:\Windows\Minidump\020112-16832-01.dmp C:\Users\Flaiker\AppData\Local\Temp\WER-43352-0.sysdata.xml Lesen Sie unsere Datenschutzbestimmungen online: http://go.microsoft.com/fwlink/?linkid=104288&clcid=0x0407Wenn die Onlinedatenschutzbestimmungen nicht verfügbar sind, lesen Sie unsere Datenschutzbestimmungen offline: C:\Windows\system32\de-DE\erofflps.txt ![[image loading]](http://i.imgur.com/GuseL.jpg)
|
0x01E - KMODE_EXCEPTION_NOT_HANDLED
These errors usually happen due to:
- Hardware failure (memory, processor, or motherboard).
- Anti-virus software that is running on your computer.
- Drivers installed by third-party software.
Easy fixes:
- Replace the faulty hardware. You may be able to determine the faulty hardware by running diagnostics provided by the manufacturer. Check in with the hardware manufacturer for more information.
- Disable any anti-virus software that is running on your computer. If the STOP errors no longer occur, either update the anti-virus program, remove and replace it, or check with the company that made it to see if there are compatibility issues.
- Disable any third-party drivers that may be running. These include any drivers that Windows did not install automatically via Windows Update. If the STOP errors no longer occur, contact the third-party manufacturer about a possible upgrade.
I have a guide for Blue Screens if this doesn't help. You can check it out here http://www.teamliquid.net/forum/viewmessage.php?topic_id=226562. Please let me know if you need further assistance.
|
On February 02 2012 01:41 HackBenjamin wrote:0x01E - KMODE_EXCEPTION_NOT_HANDLED These errors usually happen due to: - Hardware failure (memory, processor, or motherboard). - Anti-virus software that is running on your computer. - Drivers installed by third-party software. Easy fixes: - Replace the faulty hardware. You may be able to determine the faulty hardware by running diagnostics provided by the manufacturer. Check in with the hardware manufacturer for more information. - Disable any anti-virus software that is running on your computer. If the STOP errors no longer occur, either update the anti-virus program, remove and replace it, or check with the company that made it to see if there are compatibility issues. - Disable any third-party drivers that may be running. These include any drivers that Windows did not install automatically via Windows Update. If the STOP errors no longer occur, contact the third-party manufacturer about a possible upgrade. I have a guide for Blue Screens if this doesn't help. You can check it out here http://www.teamliquid.net/forum/viewmessage.php?topic_id=226562. Please let me know if you need further assistance.
Thanks for the answer. The problem exists since I got my computer (actually I got a bluescreen while the windows installation, but that was with a different RAM and I reinstalled severeal times since then), so I don't think it has something to do with 3rd party drivers. I used to use Kaspersky and now I have MSE, so it is propably not my antivirus either. So I guess it's most likely a hardware failure, either from the mainboard, which may be defect or doesn't support my RAM (especially since the problem only exists when I try Dual Channel) or the RAM itself is broken. I guess I'll try Memtest86 and see how it goes?
Edit: By the way, after I updated my BIOS I could play SC2 for about an hour without a bluescreen and I noticed a difference in the reaction time and it ran overall more fluently. Is this just a placebo effect or can dual channel make that much of a difference?
|
Sounds good. I would lean towards a faulty motherboard, if it was giving you Blue Screens during the Windows install.
Also, if you are able to get a copy of the .dmp file uploaded somewhere, I'd be happy to look through it to see if I can narrow down the problem 
|
dual channel doesn't really add much performance (was the article iirc)
to test if it is your ram or your mobo just lend/buy some RAM (from a friend or something, preferably the same brand/speed) and put it in your motherboard.
the other way around just toss your RAM in the mainboard of a friend (preferably same brand etc.)
but since your RAM works fine without dual channel, I guess the sticks itself aren't broken. and iirc on your CPU isn't the memory controller (like in modern intel CPUs) so the only source of error left is your motherboard.
|
On February 02 2012 02:08 Askr wrote:
[...] so the only source of error left is your motherboard.
Well, I don't like that at all, since it isn't easily swappable and much more expensive 
@HackBenjamin: I pm'ed you the link
|
Usual troubleshooting:
1. Check that each stick passes memtest86 and prime95 individually (not both in one channel).
2. Try using slots 3&4 instead of 1&2.
3. Try reducing the memory clock speed in the BIOS.
4. Try using some memory that doesn't suck quite so much. Yeah, I haven't had good experiences with A-DATA.
5. Try reseating the CPU.
|
So the current status is, that I will send my motherboard to repair, once I do not need my pc as much. In the meantime I try if there are other ways to fix it.
So I updated my chipset driver and tested again, got a bluescreen after half an hour but this time with a filename (atikmpag.sys):
+ Show Spoiler +
Does this say, it is a driver issue after all?
Edit: Now its ntfs.sys
Edit2: Some more bluescreens, yey http://imgur.com/a/bGxCd
|
Have you tried running chkdsk ? could be bad HDD sector. My friend have the same HDD and BSoD keep occuring after replacing other hardware / reformating windows several times.
Open the "Computer" window
Right-click on the drive in question
Select the "Tools" tab
In the Error-checking area, click <Check Now>.
|
When you do a full (as opposed to a quick) reformat, it automatically runs a chkdsk. I really don't think it's the hard drive, especially since he was getting bluescreens during the installation of Windows.
|
If you're getting BSODs in a wide range of different drivers, and only when you try to run dual-channel, it's definitely a memory-related hardware problem.
|
Well, that was nearly 2 years ago and with other RAM. I cant really remember but I came to the conclusion that the RAM was defect and so I bought the one that I have right now. I'll do the hdd test anyways
|
On February 03 2012 00:55 C4rLui wrote:
Have you tried running chkdsk ? could be bad HDD sector. My friend have the same HDD and BSoD keep occuring after replacing other hardware / reformating windows several times.
Open the "Computer" window
Right-click on the drive in question
Select the "Tools" tab
In the Error-checking area, click <Check Now>.
Did that, got this after an hour:
+ Show Spoiler +
Btw, why is there always a different file in the bluescreen mentioned? I guess thats an indicator that it isn't a software issue right?
|
Check the memory sticks individually with a memory tester / prime95 like software. I'd bet money one of them is messed up.
|
|
|
Your RAM is faulty or is being run at the wrong voltage / timings.
|
I never overcloked anything. In the bios I have everything on automatic, the only thing I changed is the screen that comes up when you start the pc.
I'll do a RAM test and try to find out if the bios settings aren't detected correctly. Thanks for the help so far
|
On February 03 2012 15:14 Flaiker wrote:
I never overcloked anything. In the bios I have everything on automatic, the only thing I changed is the screen that comes up when you start the pc.
I'll do a RAM test and try to find out if the bios settings aren't detected correctly. Thanks for the help so far
Check the recommended voltage on ur sticks and just set it manually in BIOS. I'm pretty sure that's ur problem.
|
On February 03 2012 16:08 slytown wrote:Show nested quote +On February 03 2012 15:14 Flaiker wrote:
I never overcloked anything. In the bios I have everything on automatic, the only thing I changed is the screen that comes up when you start the pc.
I'll do a RAM test and try to find out if the bios settings aren't detected correctly. Thanks for the help so far Check the recommended voltage on ur sticks and just set it manually in BIOS. I'm pretty sure that's ur problem.
Okay, according to the site where I bought it (linked in first post) it's 1,5 V, so I went to BIOS, set the whole Voltage control to manuell and set DRAM from normal to 1.5V, which was the suggested value anyway and propably automatic took that value as well, but let's see.
Edit: Result and bios settings regarding RAM if thats of any use: http://imgur.com/a/gkxuT
I'll run prime tester tonight, so then I know if it is just broken
|
So I did run Prime86 all night and tested each RAM stick individually for ~5 hours in channel 1 and 2. These are the results:
+ Show Spoiler [results] +
So first thing is that there are errors on the first one. Second is the RAM settings on the second test are reilly weird (200Mhz, DDR400 instead of 666Mhz, DDR1333). I don't know why the test did that, I didn't change any setting.
So what does this mean? Is it my RAMs fault now?
|
|
|
|
|
|
EPT![[image loading]](http://i.imgur.com/2jhro.jpg)
![[image loading]](http://i.imgur.com/2GEdG.jpg)
![[image loading]](http://i.imgur.com/9rqUW.jpg)
![[image loading]](http://i.imgur.com/Vyu4D.jpg)
