Hi Guys,
according to Driver Genius all of my drivers are up to date but I'm still getting BSODs while gaming.. I really do not have any idea about what's going on..
I also ran memtest - no errors found
Thanks for your help in advance
according to Driver Genius all of my drivers are up to date but I'm still getting BSODs while gaming.. I really do not have any idea about what's going on..
I also ran memtest - no errors found
Thanks for your help in advance
I feel the same. I'm getting BSoDs. Can you give us more details about the BSoD? Like the codes it gives you and the references it picks up. If this is still happening in a few days you could try backing up and then System Restoring back to before the first BSoD attack. If all fails there's always backup to external hard-drive and the reinstall Window. But that's a last resort.
DaTa82,
Welcome to 7 Forums.
Have you tried these?
Driver Verifier - Enable and Disable
and what Anti Virus are you using?
Welcome to 7 Forums.
Have you tried these?
Driver Verifier - Enable and Disable
and what Anti Virus are you using?
Hi Dapizz -
the problem exists from the very beginning on. I bought a brand new PC last year (September) and I have every time BSODs while gaming. ONLY while gaming - for working purposes and surfing on the net I can use my PC without any problems. But every time I want to play with some games there is a BSOD
I tried to format everything several times. I even reinstalled Windows at least 5-6 times. I really don't know what else I could do.
My latest minidumps files are attached in the zip file.
the problem exists from the very beginning on. I bought a brand new PC last year (September) and I have every time BSODs while gaming. ONLY while gaming - for working purposes and surfing on the net I can use my PC without any problems. But every time I want to play with some games there is a BSOD
I tried to format everything several times. I even reinstalled Windows at least 5-6 times. I really don't know what else I could do.
My latest minidumps files are attached in the zip file.
�� Quote: Originally Posted by The Howling Wolves 
DaTa82,
Welcome to 7 Forums.
Have you tried these?
Driver Verifier - Enable and Disable
and what Anti Virus are you using?
Welcome to 7 Forums.
Have you tried these?
Driver Verifier - Enable and Disable
and what Anti Virus are you using?
mycrosoft security esential - so that shouldn't be the problem
I haven't tried driver verifier yet - I'm not sure if I have enough PC knowledge for this..
I am using the same AV .....MSE
Did your system ever work when you played games on it?
If yes, then restore it back to date it was working for you.
Back up your system before and after making changes. IMHO
Did your system ever work when you played games on it?
If yes, then restore it back to date it was working for you.
Back up your system before and after making changes. IMHO
�� Quote: Originally Posted by The Howling Wolves I am using the same AV .....MSE
Did your system ever work when you played games on it?
If yes, then restore it back to date it was working for you.
Back up your system before and after making changes. IMHO
Did your system ever work when you played games on it?
If yes, then restore it back to date it was working for you.
Back up your system before and after making changes. IMHO
I tried to put in an other video card - same results (BSODs). I brought back my video card also to the store where I've bought my PC - they tested it for 1 week and could not detect any issues.
Have you done the basic things like:
1. Full AV Scan
2. Ran Malwarebytes Anti Malware
3. Memtest86+ - Advanced Memory Diagnostic Tool
These are just a few but hang in there and I will get more help coming your way.
1. Full AV Scan
2. Ran Malwarebytes Anti Malware
3. Memtest86+ - Advanced Memory Diagnostic Tool
These are just a few but hang in there and I will get more help coming your way.
�� Quote: Originally Posted by The Howling Wolves Have you done the basic things like:
1. Full AV Scan
2. Ran Malwarebytes Anti Malware
3. Memtest86+ - Advanced Memory Diagnostic Tool
These are just a few but hang in there and I will get more help coming your way.
1. Full AV Scan
2. Ran Malwarebytes Anti Malware
3. Memtest86+ - Advanced Memory Diagnostic Tool
These are just a few but hang in there and I will get more help coming your way.
2. Ran Malwarebytes Anti Malware - not in the last couple of weeks - which program do you recommend for it?
3. Memtest86+ - Advanced Memory Diagnostic Tool: I let it run for a whole night - no errors
thanks so much for your replies - this is really appreciated!
DaTa82,
Your appreciation is more than welcomed.
This is a free program but run the full scan.
Malwarebytes' Anti-Malware: Malwarebytes
I have asked for more help to come in as I am just getting my feet wet with BSOD's!
Your appreciation is more than welcomed.
This is a free program but run the full scan.
Malwarebytes' Anti-Malware: Malwarebytes
I have asked for more help to come in as I am just getting my feet wet with BSOD's!
thanks The Howling Wolves!
I ran a quick test with "Malwarebytes" now: nothing found
I will run a full test as well
I ran a quick test with "Malwarebytes" now: nothing found
I will run a full test as well
Test your GPU with the GPU test of OCCT
OCCT (OverClock Checking Tool) 3.0.0 download from Guru3D.com
http://www.sevenforums.com/crashes-d...tructions.html
OCCT (OverClock Checking Tool) 3.0.0 download from Guru3D.com
http://www.sevenforums.com/crashes-d...tructions.html
�� Quote: Originally Posted by yowanvista Test your GPU with the GPU test of OCCT
OCCT (OverClock Checking Tool) 3.0.0 download from Guru3D.com
http://www.sevenforums.com/crashes-d...tructions.html
OCCT (OverClock Checking Tool) 3.0.0 download from Guru3D.com
http://www.sevenforums.com/crashes-d...tructions.html
What do you mean with the posting instructions? I attached my files to my first post. Or did I miss something?
�� Quote: Originally Posted by yowanvista Test your GPU with the GPU test of OCCT
OCCT (OverClock Checking Tool) 3.0.0 download from Guru3D.com
http://www.sevenforums.com/crashes-d...tructions.html
OCCT (OverClock Checking Tool) 3.0.0 download from Guru3D.com
http://www.sevenforums.com/crashes-d...tructions.html
latest dump file attached
So I just ran Furmark GPU Stability test - no errors, everything seems to be fine. I'm totally lost with this...
Just got home so I am going to get you more help..
Hang in there as I want this fixed.
Hang in there as I want this fixed.
�� Quote: Originally Posted by The Howling Wolves Just got home so I am going to get you more help..
Hang in there as I want this fixed.
Hang in there as I want this fixed.
Will be back later so don't get disappointed. I don't quit at anything...Not an option!
�� Quote: Originally Posted by The Howling Wolves Will be back later so don't get disappointed. I don't quit at anything...Not an option!
Now I'm going to sleep as it's already 1:30 AM in Hungary - but the first thing I will do tomorrow is to check this forum 
Hi DaTa82. I looked at all five of your dumps and I see five different error codes. all five indicate memory corruption and two directly blame memory corruption. Unfortunately, they do not give us the specific cause of the memory corruption. The five different error codes or bugcheck codes generally indicate a hardware or hardware related problem. You stated your BSOD's only seem to occur when you are running games. This plus the the fact the two dumps blamed the Windows system Direct X driver and one blamed your video driver lead me to believe you definitely have a conflict.
I agree with The Howling Wolves suggestion to enable Driver Verifier. Carefully follow the instructions in this tutorial: Driver Verifier - Enable and Disable. If Driver Verifier encounters a faulty driver, it will trigger a BSOD. Use your computer normally while Verifier is running and upload any and all Verifier enabled dumps.
What firewall are you running and do you have any other security programs running besides your firewall and MSE? This would include any banking security program, gaming security program, etc.
Since one dump blames the Direct X Driver and one blames atikmpag.sys, your video driver, you might try removing the Catalyst Control Center and only install the Display Driver.
Let's see Driver Verifier shows and we will go from there.
I agree with The Howling Wolves suggestion to enable Driver Verifier. Carefully follow the instructions in this tutorial: Driver Verifier - Enable and Disable. If Driver Verifier encounters a faulty driver, it will trigger a BSOD. Use your computer normally while Verifier is running and upload any and all Verifier enabled dumps.
What firewall are you running and do you have any other security programs running besides your firewall and MSE? This would include any banking security program, gaming security program, etc.
Since one dump blames the Direct X Driver and one blames atikmpag.sys, your video driver, you might try removing the Catalyst Control Center and only install the Display Driver.
Let's see Driver Verifier shows and we will go from there.
Code:
Windows 7 Kernel Version 7601 (Service Pack 1) MP (4 procs) Free x64 Product: WinNt, suite: TerminalServer SingleUserTS Built by: 7601.17514.amd64fre.win7sp1_rtm.101119-1850 Machine Name: Kernel base = 0xfffff800`0301f000 PsLoadedModuleList = 0xfffff800`03264e90 Debug session time: Fri Apr 15 13:10:51.220 2011 (GMT-4) System Uptime: 0 days 0:27:01.796 Loading Kernel Symbols ............................................................... ................................................................ .................................... Loading User Symbols Loading unloaded module list ..... ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* Use !analyze -v to get detailed debugging information. BugCheck A, {31d0, 2, 1, fffff800030a81b3} Probably caused by : ntkrnlmp.exe ( nt!KiTimerWaitTest+2b3 ) Followup: MachineOwner --------- 2: kd> !analyze -v ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* IRQL_NOT_LESS_OR_EQUAL (a) An attempt was made to access a pageable (or completely invalid) address at an interrupt request level (IRQL) that is too high. This is usually caused by drivers using improper addresses. If a kernel debugger is available get the stack backtrace. Debug session time: Fri Apr 15 10:37:08.132 2011 (GMT-4) System Uptime: 0 days 0:16:35.709 Loading Kernel Symbols ............................................................... ................................................................ ..................................... Loading User Symbols Loading unloaded module list ..... ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* Use !analyze -v to get detailed debugging information. BugCheck 4E, {99, 10e3dc, 2, 12b3db} Probably caused by : memory_corruption ( nt!MiBadShareCount+4c ) Followup: MachineOwner --------- 3: kd> !analyze -v ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* PFN_LIST_CORRUPT (4e) Typically caused by drivers passing bad memory descriptor lists (ie: calling MmUnlockPages twice with the same list, etc). If a kernel debugger is available get the stack trace. Debug session time: Fri Apr 15 11:50:40.246 2011 (GMT-4) System Uptime: 0 days 1:12:32.822 Loading Kernel Symbols ............................................................... ................................................................ ..................................... Loading User Symbols Loading unloaded module list ..... ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* Use !analyze -v to get detailed debugging information. BugCheck 50, {fffff8a00cfcd160, 0, fffff8800432d586, 0} Could not read faulting driver name Probably caused by : dxgmms1.sys ( dxgmms1!VIDMM_GLOBAL::ReferenceDmaBuffer+636 ) Followup: MachineOwner --------- 3: kd> !analyze -v ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* PAGE_FAULT_IN_NONPAGED_AREA (50) Invalid system memory was referenced. This cannot be protected by try-except, it must be protected by a Probe. Typically the address is just plain bad or it is pointing at freed memory. Debug session time: Fri Apr 15 17:55:52.633 2011 (GMT-4) System Uptime: 0 days 0:35:12.210 Loading Kernel Symbols ............................................................... ................................................................ ..................................... Loading User Symbols Loading unloaded module list ..... ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* Use !analyze -v to get detailed debugging information. BugCheck 3B, {c0000005, fffff88004e8754b, fffff8800adfc790, 0} Probably caused by : atikmdag.sys ( atikmdag+3c254b ) Followup: MachineOwner --------- 2: kd> !analyze -v ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* SYSTEM_SERVICE_EXCEPTION (3b) An exception happened while executing a system service routine. Arguments: Arg1: 00000000c0000005, Exception code that caused the bugcheck Arg2: fffff88004e8754b, Address of the exception record for the exception that caused the bugcheck Arg3: fffff8800adfc790, Address of the context record for the exception that caused the bugcheck Arg4: 0000000000000000, zero. Debug session time: Fri Apr 15 17:19:32.456 2011 (GMT-4) System Uptime: 0 days 4:07:57.642 Loading Kernel Symbols ............................................................... ................................................................ ..................................... Loading User Symbols Loading unloaded module list ............. ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* Use !analyze -v to get detailed debugging information. BugCheck 1000007E, {ffffffffc0000005, fffff880053d3d90, fffff880027916a8, fffff88002790f00} Probably caused by : dxgmms1.sys ( dxgmms1!VIDMM_GLOBAL::ReferenceAllocationForPreparation+c4 ) Followup: MachineOwner --------- 2: kd> !analyze -v ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M (1000007e) This is a very common bugcheck. Usually the exception address pinpoints the driver/function that caused the problem. Always note this address as well as the link date of the driver/image that contains this address. Some common problems are exception code 0x80000003. This means a hard coded breakpoint or assertion was hit. Can you add your system specs?
In the lower left corner of any of your posts, "My System Specs".
This will help troubleshooting your system.
In the lower left corner of any of your posts, "My System Specs".
This will help troubleshooting your system.
�� Quote: Originally Posted by CarlTR6 I agree with The Howling Wolves suggestion to enable Driver Verifier. Carefully follow the instructions in this tutorial: Driver Verifier - Enable and Disable. If Driver Verifier encounters a faulty driver, it will trigger a BSOD. Use your computer normally while Verifier is running and upload any and all Verifier enabled dumps.
What firewall are you running and do you have any other security programs running besides your firewall and MSE? This would include any banking security program, gaming security program, etc.
Since one dump blames the Direct X Driver and one blames atikmpag.sys, your video driver, you might try removing the Catalyst Control Center and only install the Display Driver.
Let's see Driver Verifier shows and we will go from there.
[/code]
Thank you so much for checking my files. I will enable Driver Verifier today and let you know the results.
Im not aware of any other security programs installed on my PC. I have only the standard, Windows built-in Firewall - no other specific firewall program installed
Regarding the CCC: I tried this several times during the last couple of months and unfortunately it didn't help.
I will update my systems specs as well but in the meantime I attach for your reference a screenshot from my order confirmation back from October last year, maybe it will help you already.
Guys, thanks againg for all the help and for all your replies, it's a really good forum and definetely worth to recommend!
I updated my system specs and will enable driver verifier now. Will keep ya posted and I'm looking forward to hearing from you!
So verifierer enabled: I got immediately 2 BSODs, both with the same code. Windows doesn't launch at all, I will try to launch it in safe mode. I have never seen this error code before
UPDATE: So I was not able to launch windows in normal mode. In Safe mode I disabled verifier. I will remove and update the realtek driver as according to the google results RTKVHD64.SYS is related to realtek. Once done I will enable verifier again...
UPDATE2: I disabled verifier, launched Windows, removed one of the Realtek drivers, restarted the computer, enabled driver verifier again: now it's running, I can surf on the net, no BSODs so far... Fingers crossed...?
UPDATE: So I was not able to launch windows in normal mode. In Safe mode I disabled verifier. I will remove and update the realtek driver as according to the google results RTKVHD64.SYS is related to realtek. Once done I will enable verifier again...
UPDATE2: I disabled verifier, launched Windows, removed one of the Realtek drivers, restarted the computer, enabled driver verifier again: now it's running, I can surf on the net, no BSODs so far... Fingers crossed...?
while gaming I got a new BSOD. file attached
I let windows memory diagnostic run - no issues found...
maybe these screenshots are also useful
Seeing what you said and reading through recent comments, there's a possibility that your graphics card can't take certain games. You could try going to Can You Run It? and seeing if your system is supposedly up to the games you can't play. It could be that you just can't play them.
The CPUZ info is very useful.
Windows memory test is not very good.
Use Memtest86+, follow the tutorial linked below.
When you run memtest86+ you are looking for bad RAM cards, bad motherboard slots, so you need to follow the testing procedure in the tutorial.
Sometimes errors from these tests can be corrected by adjusting the settings.
RAM - Test with Memtest86+
Have you been checking your temperatures?
Use Core Temp , to check the CPU temps when at idle, under load and/or testing.
Let us know the minimum and maximum temps you get.
Go to your BIOS and tell us what the CPU, RAM and integrated memory controller voltages are.
Any RAM that says 'Value' on it will likely cause you problems when stressed, like playing games.
Windows memory test is not very good.
Use Memtest86+, follow the tutorial linked below.
When you run memtest86+ you are looking for bad RAM cards, bad motherboard slots, so you need to follow the testing procedure in the tutorial.
Sometimes errors from these tests can be corrected by adjusting the settings.
RAM - Test with Memtest86+
Have you been checking your temperatures?
Use Core Temp , to check the CPU temps when at idle, under load and/or testing.
Let us know the minimum and maximum temps you get.
Go to your BIOS and tell us what the CPU, RAM and integrated memory controller voltages are.
Any RAM that says 'Value' on it will likely cause you problems when stressed, like playing games.
�� Quote: Originally Posted by Dapizz Seeing what you said and reading through recent comments, there's a possibility that your graphics card can't take certain games. You could try going to Can You Run It? and seeing if your system is supposedly up to the games you can't play. It could be that you just can't play them.
this shouldn't be a problem - see a screenshot below for 1 of the games which use to cause BSODs during every battle
I let my PC build especially for gaming so everything should run smoothly. For working porpuses I have my company laptop, so this PC was meant for gaming
�� Quote: Originally Posted by Dave76 The CPUZ info is very useful.
Windows memory test is not very good.
Use Memtest86+,
Have you been checking your temperatures?
Use Core Temp , to check the CPU temps when at idle, under load and/or testing.
Let us know the minimum and maximum temps you get.
Go to your BIOS and tell us what the CPU, RAM and integrated memory controller voltages are.
Any RAM that says 'Value' on it will likely cause you problems when stressed, like playing games.
Windows memory test is not very good.
Use Memtest86+,
Have you been checking your temperatures?
Use Core Temp , to check the CPU temps when at idle, under load and/or testing.
Let us know the minimum and maximum temps you get.
Go to your BIOS and tell us what the CPU, RAM and integrated memory controller voltages are.
Any RAM that says 'Value' on it will likely cause you problems when stressed, like playing games.
Thank you for the comment. I ran memtest86+ about 1,5 month ago for a whole night - it didn't detect any issues. But I will give it a try again later on. I will make some photos of my BIOS and upload them soon
here are the first photos
and the rest
can I disable driver verifier already or shall this continue running in the background?
temperature seems to be also ok
68C is high for an AMD, they usually run cool.
Let Driver Verifier run for a while longer, see if it can force a driver failure.
Running three RAM cards in a four card motherboard is not ideal, at best one of the cards will be in single channel mode.
Is this memory on your motherboard compatibility list?
A 3x2GB RAM set is usually for an Intel x58 motherboard. Sometimes they will run in an AMD board and sometimes will give you errors.
Best to get RAM specifically designed for AMD CPU/motherboards.
Do you have the Geil part number?
In your BIOS check voltages for:
Normal CPU Vcore
CPU NB VID control
It will be the same BIOS page as the first BIOS picture posted above, just scroll down to find this information.
If CPU NB VID control only shows 'Auto' then select it and increase the voltage by the smallest amount available, this should give you a voltage number to post.
With 6GB RAM you will need to make a small voltage increase to the CPU integrated memory controller, which is 'CPU NB VID control'.
Let us know the voltage setting and we can try adjusting.
Let Driver Verifier run for a while longer, see if it can force a driver failure.
Running three RAM cards in a four card motherboard is not ideal, at best one of the cards will be in single channel mode.
Is this memory on your motherboard compatibility list?
A 3x2GB RAM set is usually for an Intel x58 motherboard. Sometimes they will run in an AMD board and sometimes will give you errors.
Best to get RAM specifically designed for AMD CPU/motherboards.
Do you have the Geil part number?
In your BIOS check voltages for:
Normal CPU Vcore
CPU NB VID control
It will be the same BIOS page as the first BIOS picture posted above, just scroll down to find this information.
If CPU NB VID control only shows 'Auto' then select it and increase the voltage by the smallest amount available, this should give you a voltage number to post.
With 6GB RAM you will need to make a small voltage increase to the CPU integrated memory controller, which is 'CPU NB VID control'.
Let us know the voltage setting and we can try adjusting.
In your BIOS check voltages for:
Normal CPU Vcore
CPU NB VID control
Thanks Dave! It's on my second screenshot, can you pelase check that?
Hm, I got fatal error while running prime test
I see it now, it says 'Auto'.
If CPU NB VID control only shows 'Auto' then select it and increase the voltage by the smallest amount available, this should give you a voltage number to post.
When running Prime95 did you first go to the Advanced tab and select 'Round off checking'?
Did you check the stress.txt file?
If CPU NB VID control only shows 'Auto' then select it and increase the voltage by the smallest amount available, this should give you a voltage number to post.
When running Prime95 did you first go to the Advanced tab and select 'Round off checking'?
Did you check the stress.txt file?
�� Quote: Originally Posted by Dave76 I see it now, it says 'Auto'.
If CPU NB VID control only shows 'Auto' then select it and increase the voltage by the smallest amount available, this should give you a voltage number to post.
If CPU NB VID control only shows 'Auto' then select it and increase the voltage by the smallest amount available, this should give you a voltage number to post.
�� Quote: Originally Posted by Dave76 When running Prime95 did you first go to the Advanced tab and select 'Round off checking'?
Did you check the stress.txt file?
That's the result.. is it the correct test to run?
I see in post #33 that your CPU Voltage control is 1.3500v this is OK, no need to change.
For the CPU NB VID control, integrated memory controller, we need to know the auto/stock setting, should be 1.10v.
Select the +0.025v, the smallest increase, this should show a voltage number of 1.125v.
Post the new CPU NB VID voltage.
Yes, the Prime95 torture test - Blend is the right test in order to test the CPU and some of the RAM.
For the CPU NB VID control, integrated memory controller, we need to know the auto/stock setting, should be 1.10v.
Select the +0.025v, the smallest increase, this should show a voltage number of 1.125v.
Post the new CPU NB VID voltage.
Yes, the Prime95 torture test - Blend is the right test in order to test the CPU and some of the RAM.
�� Quote: Originally Posted by Dave76 I see in post #33 that your CPU Voltage control is 1.3500v this is OK, no need to change.
For the CPU NB VID control, integrated memory controller, we need to know the auto/stock setting, should be 1.10v.
Select the +0.025v, the smallest increase, this should show a voltage number of 1.125v.
Post the new CPU NB VID voltage.
Yes, the Prime95 torture test - Blend is the right test in order to test the CPU and some of the RAM.
For the CPU NB VID control, integrated memory controller, we need to know the auto/stock setting, should be 1.10v.
Select the +0.025v, the smallest increase, this should show a voltage number of 1.125v.
Post the new CPU NB VID voltage.
Yes, the Prime95 torture test - Blend is the right test in order to test the CPU and some of the RAM.
see the screenshot attached, please. Should this be correct now? What is the next step?
Thanks!!
latest file attached..
This just confirms that the stock CPU NB VID control is 1.10v.
Now you need to make it as close to 1.20v as possible.
Select the +0.100v increase.
Then run the memtest86+ test overnight or the Prime95 Torture test-Blend test for an hour.
If you run the Prime95 test be sure to watch the CPU temps.
Now you need to make it as close to 1.20v as possible.
Select the +0.100v increase.
Then run the memtest86+ test overnight or the Prime95 Torture test-Blend test for an hour.
If you run the Prime95 test be sure to watch the CPU temps.
So CPU NB VID control was setup to 1.125 and I ran memtest.. it detected indeed errors. Shall I make CPU NB VID close to 1.20 v and let the memtest run again or...?
Any memory test errors are too many, the voltage adjustment will help.
Yes, set the 'CPU NB VID' 1.200v and run memtest86+ again.
Run it for at least 7 passes or overnight.
There is still the issue of running three RAM cards.
Two will be in dual channel mode and the other one will be in single channel mode or it will have all three RAM cards running in single channel mode, this will depend on the motherboard and BIOS.
You will have better RAM performance in dual channel mode.
Can you post the Geil part number for the RAM you have?
If it is 'Intel' RAM, you might still have issues getting it to run stable.
Yes, set the 'CPU NB VID' 1.200v and run memtest86+ again.
Run it for at least 7 passes or overnight.
There is still the issue of running three RAM cards.
Two will be in dual channel mode and the other one will be in single channel mode or it will have all three RAM cards running in single channel mode, this will depend on the motherboard and BIOS.
You will have better RAM performance in dual channel mode.
Can you post the Geil part number for the RAM you have?
If it is 'Intel' RAM, you might still have issues getting it to run stable.
Hi Dave76,
'CPU NB VID' is set to 1.200 V. but I still have memory test error. See attached the 3 photos - also you will find the GEIL partnumber. What to do now? Thanks!
'CPU NB VID' is set to 1.200 V. but I still have memory test error. See attached the 3 photos - also you will find the GEIL partnumber. What to do now? Thanks!
Can you please advise me what to do now? Thanks so much for all your help!
Change the 'CPU NB VID' to 1.300v and run the memtest86+ again.
Looks like you are getting less errors than last time, this voltage should stabilize it.
Just looked up your RAM, it is for an Intel CPU X58 motherboard.
Sometimes Intel RAM will run on an AMD board and sometimes (most of the time) it won't.
Best thing you can do is return this for AMD optimized RAM.
If returning the RAM is going to be difficult, we can try to get it stable, but may need to come back to this.
Looks like you are getting less errors than last time, this voltage should stabilize it.
Just looked up your RAM, it is for an Intel CPU X58 motherboard.
Sometimes Intel RAM will run on an AMD board and sometimes (most of the time) it won't.
Best thing you can do is return this for AMD optimized RAM.
If returning the RAM is going to be difficult, we can try to get it stable, but may need to come back to this.
�� Quote: Originally Posted by Dave76 Change the 'CPU NB VID' to 1.300v and run the memtest86+ again.
Looks like you are getting less errors than last time, this voltage should stabilize it.
Just looked up your RAM, it is for an Intel CPU X58 motherboard.
Sometimes Intel RAM will run on an AMD board and sometimes (most of the time) it won't.
Best thing you can do is return this for AMD optimized RAM.
If returning the RAM is going to be difficult, we can try to get it stable, but may need to come back to this.
Looks like you are getting less errors than last time, this voltage should stabilize it.
Just looked up your RAM, it is for an Intel CPU X58 motherboard.
Sometimes Intel RAM will run on an AMD board and sometimes (most of the time) it won't.
Best thing you can do is return this for AMD optimized RAM.
If returning the RAM is going to be difficult, we can try to get it stable, but may need to come back to this.
Thank you for your answer. Once I'm at home I will change the voltage to 1.300 and run memtest again.
Returning the RAM will be a bit difficult so I want to avoid this if possible, so let's try to get it stable first. Will keep you posted in the evening about the new memtest result with the changed voltage.
Dave76, thanks again for your help, I was so annoyed and dissapointed but now at least I see the light at the end of the tunnel
Hi Dave!
according to this document this RAM should be working well on my AMD board so I really hope increasing the voltage to 1.3v will solve the issue. Fingers crossed!!!
according to this document this RAM should be working well on my AMD board so I really hope increasing the voltage to 1.3v will solve the issue. Fingers crossed!!!
Hope the 'CPU NB VID' voltage bump helps.
Problem with the Geil RAM listed in the Gigabyte Memory Support list is that it's not the same as your RAM.
Yours is GV36GB1600C8TC
The Gigabyte list is GV32GB1600C8DC
Let us know the memtest86+ results.
Problem with the Geil RAM listed in the Gigabyte Memory Support list is that it's not the same as your RAM.
Yours is GV36GB1600C8TC
The Gigabyte list is GV32GB1600C8DC
Let us know the memtest86+ results.
bad news It's set to 1.3 V but again Memtest errors even already after 30 minutes
What I really don't understand is the fact, that about 2 month ago I could run memtest for a whole night without having any errors, and now....
GV36 iso GV32 should be 2 GB vs 6 GB
TC iso DC should be double vs Triple
I guess... so this seems to be the same serie only the nr of GBs is differemt?
It's set to 1.3 V but again Memtest errors even already after 30 minutesWhat I really don't understand is the fact, that about 2 month ago I could run memtest for a whole night without having any errors, and now....
GV36 iso GV32 should be 2 GB vs 6 GB
TC iso DC should be double vs Triple
I guess... so this seems to be the same serie only the nr of GBs is differemt?
First, change the 'DRAM Voltage Control' to 1.550v.
Second, You need to run memtest86+ as detailed in this tutorial, RAM - Test with Memtest86+
When you run memtest86+ you are looking for bad RAM cards, bad motherboard slots, so you need to follow the testing procedure in the tutorial.
Number the RAM cards, mark with tape, and right down the tests done with which card in which motherboard slot.
Run the test with one card installed at a time, start with card #1 in slot #1. If you get any errors you can stop the test and move to the next step.
If you get errors with card #1, write down the info, run the same card in slot #2.
If you still get errors, run a different card, card #2, in slot #1.
If you get errors, move card #2 to slot #2, etc.
Be methodical and write down the results, then post your progress here.
Another option is to install some different RAM, if you have some or can borrow, then run memtest86+ to check for errors.
As for the RAM part numbers, the 6&2 aren't so important, but the TC and DC are.
On the Geil site they have a motherboard compatible list, only Intel x58 motherboards are listed. This means the RAM is optimized for Intel x58 motherboards.
Although it is possible (but not always possible) to get Intel RAM to run on an AMD motherboard, it may be a very long process and may come up with more errors again later. It may not ever be stable.
Second, You need to run memtest86+ as detailed in this tutorial, RAM - Test with Memtest86+
When you run memtest86+ you are looking for bad RAM cards, bad motherboard slots, so you need to follow the testing procedure in the tutorial.
Number the RAM cards, mark with tape, and right down the tests done with which card in which motherboard slot.
Run the test with one card installed at a time, start with card #1 in slot #1. If you get any errors you can stop the test and move to the next step.
If you get errors with card #1, write down the info, run the same card in slot #2.
If you still get errors, run a different card, card #2, in slot #1.
If you get errors, move card #2 to slot #2, etc.
Be methodical and write down the results, then post your progress here.
Another option is to install some different RAM, if you have some or can borrow, then run memtest86+ to check for errors.
As for the RAM part numbers, the 6&2 aren't so important, but the TC and DC are.
On the Geil site they have a motherboard compatible list, only Intel x58 motherboards are listed. This means the RAM is optimized for Intel x58 motherboards.
Although it is possible (but not always possible) to get Intel RAM to run on an AMD motherboard, it may be a very long process and may come up with more errors again later. It may not ever be stable.
�� Quote: Originally Posted by Dave76 First, change the 'DRAM Voltage Control' to 1.550v.
I changed the DRAM Voltage control to 1.550v and it seems to resolve all the issues. I could run memtest for a whole night without having any errors. Also I could play today morning for about 2 hours with some games and I didn't get one single BSOD..
So everything seems to be working fine now. Thank you soooo much for your help, Dave76, you made my day...
You're welcome, Glad it's running stable.
Come back in another 4-5 days and let us know if it's still running stable and we'll mark the thread solved.
Come back in another 4-5 days and let us know if it's still running stable and we'll mark the thread solved.
Hi Dave76,
you can mark the thread solved as I could play in the last days for hours and hours without having any issues, so I'm extremly happy as the system is running totally stable. Thanks again for all your help!
you can mark the thread solved as I could play in the last days for hours and hours without having any issues, so I'm extremly happy as the system is running totally stable. Thanks again for all your help!
Your Welcome, glad to hear it's running stable.
Thanks for the feed back, enjoy your system.
Thanks for the feed back, enjoy your system.
Không có nhận xét nào:
Đăng nhận xét