BSOD playing Total War Rome II, error 0x00000101

[arsene]

Hello to everyone in SevenForums, this is my first post in this forum but it´s not the first time I´ve seeked help for windows related problems here. So just let me express my gratitude to you all.

Now I´ll proceed explaining my most recents troubles. Everytime I try playing TWRII, usually after 10~15 min of running, my computer gets this BSOD. This also happens with games like Assassin´s Creed III or, but less frequently, Metro 2033. In other games, like Shogun II: Fall of the samurai or Elder Scroll V, it doesn´t happen.

Bluescreenview shows me that the Bc Code is 0x00000101, and sometimes it is caused by driver:

a) atikmdag.sys( Adress: atikmdag.sys+825a3)-----> For this, according to some advices given to similar cases in this forum if I´m not mistaken, I uninstalled amd catalyst driver with amd_cleanup_utility_1.2.1.0. Then reinstalled the latest amd catalyst driver(13-4_win7_win8_64_dd_ccc_whql.exe) but didn´t install catalyst control center. After doing this I tried to play again and the result was getting the same BOSD after 10~15 min, but now the driver at fault was:

B) ntoskrnl.exe( Adress: ntoskrnl.exe+72f40)------> And since this happened I decided to post in the forum .

The info required is uploaded in a .zip file like requested in the forum rules. I decided to ask for help since I believe it was better to present my problem and specific information.

Well, thanks to everyone who reads this post and I hope someone helps me resolve this. Any help will be most appreciated.

My specs are:
MB: P8P67-M PRO (BIOS: 37.01)
CPU: i5-2500k
RAM: Corsair Vengeance CMZ8GX3M2A1600C9 (2X 4GB)
GPU: AMD RADEON HD 6850 (XFX)
OS: Windows 7 ultimate 64 (6.1, compilation 7601)

If any information is missing pleaselet me know and I add it.

Thanks again. Arsene.

 

[Arc]

Hi arsene.

Are you overclocking? As you are getting BSODs, you should stop overclocking and run all the hardware components like CPU, GPU and RAM to their default settings. Also set the BIOS to default, too.
How To Clear CMOS (Reset BIOS)

Is the computer hot? Report us the heat of the computer after a couple of hours of your normal usage. Upload a screenshot of the summery tab of Speccy.

Check if the Power Supply Unit (PSU) supplying adequate power to the computer or not.
eXtreme Power Supply Calculator
Also let us know about the wattage of the PSU.

Test your RAM modules for possible errors.
How to Test and Diagnose RAM Issues with Memtest86+
Run memtest for at least 8 passes, preferably overnight.

Stress test the Graphics Card using Furmark.
Video Card - Stress Test with Furmark

Stress test the CPU.
Hardware - Stress Test With Prime95

Let us know the results.
______________________________________________________________
BSOD ANALYSIS:

*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 101, {31, 0, fffff88003365180, 2}

Probably caused by : Unknown_Image ( ANALYSIS_INCONCLUSIVE )

Followup: MachineOwner
---------

0: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

CLOCK_WATCHDOG_TIMEOUT (101)
An expected clock interrupt was not received on a secondary processor in an
MP system within the allocated interval. This indicates that the specified
processor is hung and not processing interrupts.
Arguments:
Arg1: 0000000000000031, Clock interrupt time out interval in nominal clock ticks.
Arg2: 0000000000000000, 0.
Arg3: fffff88003365180, The PRCB address of the hung processor.
Arg4: 0000000000000002, 0.

Debugging Details:
------------------


BUGCHECK_STR:  CLOCK_WATCHDOG_TIMEOUT_4_PROC

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT

PROCESS_NAME:  Rome2.exe

CURRENT_IRQL:  d

STACK_TEXT:  
fffff880`0d432678 fffff800`02ed388a : 00000000`00000101 00000000`00000031 00000000`00000000 fffff880`03365180 : nt!KeBugCheckEx
fffff880`0d432680 fffff800`02e85ae7 : 00000000`00000000 fffff800`00000002 00000000`00002710 fffffa80`00040004 : nt! ?? ::FNODOBFM::`string'+0x4e5e
fffff880`0d432710 fffff800`033fa895 : fffff800`03420460 fffff880`0d4328c0 fffff800`03420460 fffff800`00000000 : nt!KeUpdateSystemTime+0x377
fffff880`0d432810 fffff800`02e78493 : fffffa80`0699c220 fffff880`0d432af8 00000000`00000000 fffff8a0`11df9000 : hal!HalpHpetClockInterrupt+0x8d
fffff880`0d432840 fffff800`02e82c59 : 00000000`000004c4 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiInterruptDispatchNoLock+0x163
fffff880`0d4329d0 fffff800`031762be : fffff880`0d432b00 fffffa80`00000006 00000000`00000001 00000000`00000000 : nt!KeWaitForSingleObject+0x69
fffff880`0d432a70 fffff800`02e7b1d3 : fffffa80`06e13b50 00000000`000004c4 fffff880`0d432ab8 fffffa80`0699c220 : nt!NtWaitForSingleObject+0xde
fffff880`0d432ae0 00000000`73b12e09 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
00000000`11e9ed08 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x73b12e09


STACK_COMMAND:  kb

SYMBOL_NAME:  ANALYSIS_INCONCLUSIVE

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: Unknown_Module

IMAGE_NAME:  Unknown_Image

DEBUG_FLR_IMAGE_TIMESTAMP:  0

FAILURE_BUCKET_ID:  X64_CLOCK_WATCHDOG_TIMEOUT_4_PROC_ANALYSIS_INCONCLUSIVE

BUCKET_ID:  X64_CLOCK_WATCHDOG_TIMEOUT_4_PROC_ANALYSIS_INCONCLUSIVE

Followup: MachineOwner
---------

 

[arsene]

Sorry, my mistake, don´t know how to delete posts and this was repetition.

 

[arsene]

Hi Arc.

First of all, thanks for replying. I really appreciate your guidance.

So, I´ve cleared the CMOs. I´ve runned all the tests and uploaded the results in the tests.zip file.

Anyway, I´ll summarize some of the results here:

1.- About Speccy, in the zip file I uploaded two screenshots, one showing the summary under regular conditions( using firefox, aimp) and a second one taken while playing Rome II. I guessed that would be useful.

2.- My PSU is a Sentey SDP750-SS (750W). And the eXtreme Power Suplpy Calculator recommended a 351W PSU, so mine should be ok. (There´s a .pdf file with the results in the zip file).

3.-I runned Memtest86+ v.4.20 for 18 hours and the results were 15 passes and 0 errors. (There´s a snapshot in the zip file).

4.- I stressed my video card with FurMark 1.11.0 (Resolution 1920x1080, no fullscreen, with the following settings checked: Dynamic background, Burn-in, Xtreme burn-in and Post-FX) just like the tutorial stated. I did it for 30 minutes, the temperature remained between 65~66 °C, being 66 the maximun. It showed no artifacts or errors of any kind. (The screenshot I uploaded in the zip file shows the test at minute 12, I meant to take another one at minute 30 but messed that up and the screenshot wasn´t taken, but the temperature remained stable at 65°C)

5.- Finally I stressed the CPU with Prime 95 v279 for 2hours nad 20 minutes. It didn´t reported any errors. In addition to that I used RealTemp 3.70 to check the temperatures, the maximun per core were: 75°C, 78°C,79°C, 76°C. And the average, this is my appreciation, were: 72°C, 75°C, 76°c, 73°C. (The test results are in the zip file)

In the test.zip there are five folders, each containiing the results or snaoshots of their respective tests.

Well, that´s everything I´ve tested so far, I hoped everything was done according to the instructions, if there´s anything wrong please tell me and I´ll do it again.

Thanks for everything again. I´m waiting to read your opinion, Arc, and the opinions or advices of anyone in the forum who wants to help me.

Bye. Arsene.

Hi arsene.

Are you overclocking? As you are getting BSODs, you should stop overclocking and run all the hardware components like CPU, GPU and RAM to their default settings. Also set the BIOS to default, too.
How To Clear CMOS (Reset BIOS)

Is the computer hot? Report us the heat of the computer after a couple of hours of your normal usage. Upload a screenshot of the summery tab of Speccy.

Check if the Power Supply Unit (PSU) supplying adequate power to the computer or not.
eXtreme Power Supply Calculator
Also let us know about the wattage of the PSU.

Test your RAM modules for possible errors.
How to Test and Diagnose RAM Issues with Memtest86+
Run memtest for at least 8 passes, preferably overnight.

Stress test the Graphics Card using Furmark.
Video Card - Stress Test with Furmark

Stress test the CPU.
Hardware - Stress Test With Prime95

Let us know the results.
______________________________________________________________
BSOD ANALYSIS:

*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 101, {31, 0, fffff88003365180, 2}

Probably caused by : Unknown_Image ( ANALYSIS_INCONCLUSIVE )

Followup: MachineOwner
---------

0: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

CLOCK_WATCHDOG_TIMEOUT (101)
An expected clock interrupt was not received on a secondary processor in an
MP system within the allocated interval. This indicates that the specified
processor is hung and not processing interrupts.
Arguments:
Arg1: 0000000000000031, Clock interrupt time out interval in nominal clock ticks.
Arg2: 0000000000000000, 0.
Arg3: fffff88003365180, The PRCB address of the hung processor.
Arg4: 0000000000000002, 0.

Debugging Details:
------------------


BUGCHECK_STR:  CLOCK_WATCHDOG_TIMEOUT_4_PROC

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT

PROCESS_NAME:  Rome2.exe

CURRENT_IRQL:  d

STACK_TEXT:  
fffff880`0d432678 fffff800`02ed388a : 00000000`00000101 00000000`00000031 00000000`00000000 fffff880`03365180 : nt!KeBugCheckEx
fffff880`0d432680 fffff800`02e85ae7 : 00000000`00000000 fffff800`00000002 00000000`00002710 fffffa80`00040004 : nt! ?? ::FNODOBFM::`string'+0x4e5e
fffff880`0d432710 fffff800`033fa895 : fffff800`03420460 fffff880`0d4328c0 fffff800`03420460 fffff800`00000000 : nt!KeUpdateSystemTime+0x377
fffff880`0d432810 fffff800`02e78493 : fffffa80`0699c220 fffff880`0d432af8 00000000`00000000 fffff8a0`11df9000 : hal!HalpHpetClockInterrupt+0x8d
fffff880`0d432840 fffff800`02e82c59 : 00000000`000004c4 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiInterruptDispatchNoLock+0x163
fffff880`0d4329d0 fffff800`031762be : fffff880`0d432b00 fffffa80`00000006 00000000`00000001 00000000`00000000 : nt!KeWaitForSingleObject+0x69
fffff880`0d432a70 fffff800`02e7b1d3 : fffffa80`06e13b50 00000000`000004c4 fffff880`0d432ab8 fffffa80`0699c220 : nt!NtWaitForSingleObject+0xde
fffff880`0d432ae0 00000000`73b12e09 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
00000000`11e9ed08 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x73b12e09


STACK_COMMAND:  kb

SYMBOL_NAME:  ANALYSIS_INCONCLUSIVE

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: Unknown_Module

IMAGE_NAME:  Unknown_Image

DEBUG_FLR_IMAGE_TIMESTAMP:  0

FAILURE_BUCKET_ID:  X64_CLOCK_WATCHDOG_TIMEOUT_4_PROC_ANALYSIS_INCONCLUSIVE

BUCKET_ID:  X64_CLOCK_WATCHDOG_TIMEOUT_4_PROC_ANALYSIS_INCONCLUSIVE

Followup: MachineOwner
---------

 

[Arc]

All the tests are successfully passed.

Now let us know how it is running there.

 

[arsene]

Hi Arc,

First of all thaks for your guidance. I´m glad all the test were ook.

Well, today i´ve tried playing Rome II twice and in both occassions my pc just stopped working, the image just freezes, it keeps showing whatever the games was showing at the moment, and doesn´t play any sound. Nothing responds, not any command. The weird thing is that it doesn´t show any BSOD, and after 5 minutes I decided to turn off the PC.

I don´t have any dump file to show you. Any ideas?.

Thanks you, Arc.

Bye. Arsene.

All the tests are successfully passed.

Now let us know how it is running there.

 

[Arc]

I have asked for some more help.

 

[ICIT2LOL]

Hello Artsene now assuming this PSU is not new but in any case that in itself does not men it is not malfunctioning the one thing you haven't tried I see is the PSU test.

See these two

http://www.sevenforums.com/tutorials/86648-psu-jump-start.html
then this
http://www.sevenforums.com/tutorials/301799-psu-test-dc-output-voltage.html

Now just keep in mind that correct volts does not mean correct or sufficient current (amps therefore watts) Fro example a car might have 12-13v at the terminals but turn the engine over and it might not have enough charge (amps on tap) to do that and power up the ignition.

PS I meant to add DO NOT under any circumstances interfere with the PSU by trying to look inside by dismantling it.

 

[DustSailor]

Does event viewer say anything about errors? http://www.sevenforums.com/tutorials/226084-event-viewer-open-use-windows-7-a.html

Extra :info:
Reading and understanding event viewer to track down slow boot times: Use Windows 7 Event Viewer to track down issues that cause slower boot times - TechRepublic

 

[essenbe]

arsene, It would help us to help you if you would fill out your system specs. http://www.sevenforums.com/tutorials/180324-system-info-see-your-system-specs.html
We will need to know what hardware you have. Fill them out as completely as possible. To see what we'd like, at the bottom left of this post, click 'My System Specs' and you will see mine. Also, please go into bios and look at the hardware monitor and give us the readings of your +12V, +5V and +3.3V.
Also, if you are overclocking anything please set it back to default levels.

 

[arsene]

Hello Arc.

Once again thanks for your help so far and thanks for bringing reinforcements, that´s very kind of you.

I hope we manage to solve this riddle together.

Bye. Arsene.

I have asked for some more help.

 

[arsene]

Hello, ICit2lol.

I´d like to thank you for your lending me a hand in this matter.

Well,, About the test, I was able to jump start my PSU and I´d like to show you the results:

1.- The CPU 12V 4+4 pin : 12.19 V

2.- The SATA 5 pins : 12.19~12.20 V

3.- The PCIE6 pins : 12.18 V

4.- The Motherboard 20+4 pin: About this particular one, I found it easier to put it in a picture that´s uploaded in this post.

These are the readings, would you take a look at them and tell me your opinion please?

Thank you very much, ICit2lol.

Arsene.

Hello Artsene now assuming this PSU is not new but in any case that in itself does not men it is not malfunctioning the one thing you haven't tried I see is the PSU test.

See these two

http://www.sevenforums.com/tutorials/86648-psu-jump-start.html
then this
http://www.sevenforums.com/tutorials/301799-psu-test-dc-output-voltage.html

Now just keep in mind that correct volts does not mean correct or sufficient current (amps therefore watts) Fro example a car might have 12-13v at the terminals but turn the engine over and it might not have enough charge (amps on tap) to do that and power up the ignition.

PS I meant to add DO NOT under any circumstances interfere with the PSU by trying to look inside by dismantling it.

 

[ICIT2LOL]

Yep they are ok I was going to ask about that pin 8 (grey) as that is the ok to power up the board and should be between 2.4 - 6v so no probs there.

 

[arsene]

Hello, essenbe.

Thanks for taking the time to help me.
About filling my specs, that´s done, as thoroughly as I could.
The readings I could get at my bios are:

1.- +12 V : 12.19 V
2.- +5 V : 5.12 V
3.- +3.3 V : 3.312 V
4.- CPU : 1.130 V

And finally, I don´t know if I´m overclocking something, recently I clear my CMOS so everything in bios should be by default. Just like it came from factory. But I took some shots of my Bios. I hope that helps you or any other of the kind people who are helping me.

Good bye and thanks again.

Arsene.

arsene, It would help us to help you if you would fill out your system specs. http://www.sevenforums.com/tutorials/180324-system-info-see-your-system-specs.html
We will need to know what hardware you have. Fill them out as completely as possible. To see what we'd like, at the bottom left of this post, click 'My System Specs' and you will see mine. Also, please go into bios and look at the hardware monitor and give us the readings of your +12V, +5V and +3.3V.
Also, if you are overclocking anything please set it back to default levels.

 

[arsene]

This are the rest of the shots.

Thanks you. Arsene.

arsene, It would help us to help you if you would fill out your system specs. http://www.sevenforums.com/tutorials/180324-system-info-see-your-system-specs.html
We will need to know what hardware you have. Fill them out as completely as possible. To see what we'd like, at the bottom left of this post, click 'My System Specs' and you will see mine. Also, please go into bios and look at the hardware monitor and give us the readings of your +12V, +5V and +3.3V.
Also, if you are overclocking anything please set it back to default levels.

 

[essenbe]

arsene, What CPU cooler do you have? You already have Prime. If you do not have it, please download and install Core Temp and CPUZ download v 1.66 from the right column. With your system at idle, open CPUZ and show pictures of the CPU, Mainboard, Memory and SPD tab. If the SPD tab is blank, in the top left there is a dropdown menu, select dimm 2 and the numbers should appear. Please post screenshots of that.

I would also like you to open CPUZ, Core temp and run Prime 95. At the 30 minute mark use the snipping tool and post a screenshot of all three windows, cpu on the CPU tab, Core temp and Prime 95. You can shut down Prime95 after the screenshot. That may give us some more ifo that will help diagnose your problems.

Unfortunately for you, hardware problems are difficult to diagnose and take a lot of testing and a lot of your time. I understand your position, I have been there before several times. If you will stick with us, we will resolve your issue if at all possible. We have some of the best experts on the internet right here. I'm sure I will be asking you to do several more tests. Just bare with us. We only ask you to run tests if it helps diagnose your problems. Thank you for being so cooperative. We appreciate it more than you know. I would also like to make sure your system is set up to create mini dumps if you get a BSOD. Please follow this tutorial and make sure your image is exactly like the one in the picture except the operaling system. Pay particular attention to part # 6 to create small memory dumps.http://www.sevenforums.com/tutorials/174459-dump-files-configure-windows-create-bsod.html

Next, please go to C:/Windows/ Minidump and make sure there is a folder there called mini dumps. if not, create one ( you will have to provide admin permission) It should look like this in C:/Windows

View attachment 286975

 

[arsene]

Hi, ICit2lol.

Thanks so much for helping me discard a possible electrical malfunction. It´s a relief to know the PSU it´s working well.
If you have any suggestion or test you think I should run please do tell me.

Thanks again for your cooperation.

Arsene.

Yep they are ok I was going to ask about that pin 8 (grey) as that is the ok to power up the board and should be between 2.4 - 6v so no probs there.

 

[arsene]

Hello, Essenbe.

First of all thanks you and all of the people in this forum who have been so kind to me, I´m really grateful to you all. And of course I´ll gladly perform any test you or the people of the forum need me to run, after all I´m the one asking for help, and doing that and being grateful it´s the least I can do. Everyone have been great to me.

Now, about the test and info you needed:

1.- My cooler is the one provided by intel in the box of the processor.
2.- I checked the guide you linked me about Dumps, I happened to realize that it was set to perform "Kernel memory dumps" instead of "Small memory dump (256 kb)". So that´s taken care of. (Weird thing, since till a week or so ago it was performing minidumps after every BSOD).
3.-About the shots of CPU-Z and the combination of CPU-z, Core Temp & Prime, I´ll upload them to this post so you can take a look at them.

I hope everything you needed is done rigth, if you need me to correct something or do some more test just ask me. I´ll be waiting to read your opinion.

One more thing, about your question about me overclocking anything, were the shots of my Bios useful?. Sadly I don´t have any knowledge about OCing and those shots were the only thing that came to mind to offer you some information.

Thank you very much. Till next time.

Arsene.

arsene, What CPU cooler do you have? You already have Prime. If you do not have it, please download and install Core Temp and CPUZ download v 1.66 from the right column. With your system at idle, open CPUZ and show pictures of the CPU, Mainboard, Memory and SPD tab. If the SPD tab is blank, in the top left there is a dropdown menu, select dimm 2 and the numbers should appear. Please post screenshots of that.

I would also like you to open CPUZ, Core temp and run Prime 95. At the 30 minute mark use the snipping tool and post a screenshot of all three windows, cpu on the CPU tab, Core temp and Prime 95. You can shut down Prime95 after the screenshot. That may give us some more ifo that will help diagnose your problems.

Unfortunately for you, hardware problems are difficult to diagnose and take a lot of testing and a lot of your time. I understand your position, I have been there before several times. If you will stick with us, we will resolve your issue if at all possible. We have some of the best experts on the internet right here. I'm sure I will be asking you to do several more tests. Just bare with us. We only ask you to run tests if it helps diagnose your problems. Thank you for being so cooperative. We appreciate it more than you know. I would also like to make sure your system is set up to create mini dumps if you get a BSOD. Please follow this tutorial and make sure your image is exactly like the one in the picture except the operaling system. Pay particular attention to part # 6 to create small memory dumps.http://www.sevenforums.com/tutorials/174459-dump-files-configure-windows-create-bsod.html

Next, please go to C:/Windows/ Minidump and make sure there is a folder there called mini dumps. if not, create one ( you will have to provide admin permission) It should look like this in C:/Windows

View attachment 286975

 

[essenbe]

That's exactly what I wanted. Everything looks OK except for CPUz while running Prime. Notice the multiplier setting. It says 34 (16-37). That means it should idle at 16 or 1600MHz and when turbo kicks in should go to 3700MHz. But yours is running at 3400MHz. It should be running at 3700MHz. A multiplier of 37 is stock for your CPU. What I would like you to do is go to bios, and pay close attention to this. AI Overclock tuner click that and you should have a choice of ayto, XMP and Manual, click XMP. For turbo ratio Click it and type in 37 and press enter. Under CPU voltage leave offset for now, offset sign + ( as it is now) and offset voltage click that and put .005 and press enter. Be sure to put the . in front and 005 after. So, it should say .005. Save and exit. Run Prime again and see what it says. Please post the same screenshot and keep a close eye on temps. If it gets to 85 stop the test. Otherwise post another screenshot of CPUz and core temp while Prime is running. If you have any questions, please ask.

 

[arsene]

Hi Essenbe.

Thanks for your answer, and truth be told I have some questions. I was able to set XMP and also the offset voltage to .005. But about turbo ratio it doesn´t give me the chance to set it to 37. At this point I decided to take a shot of the screen. It just give the choice to set by all cores or by per core. In addition to that it says I can adjust it in OS.
Then, in OS, I checked an application of AI suite called TurboV EVO, there I found it is alredy set to 37(as shown in the picture uploaded). Is everything set according to your instructions? If so I´ll proceed with the test.

Another thing, about OC Tuner in the AI Tweaker section of Bios, should it be enabled?

And finally, I gave it another try to Rome II, and even thoug I did set the system to create minidumps and checked the minidump folder, it just froze and didn´t show a BSOD or created a minidump.

That is everything, thanks for your patience and guidance.

Arsene.

That's exactly what I wanted. Everything looks OK except for CPUz while running Prime. Notice the multiplier setting. It says 34 (16-37). That means it should idle at 16 or 1600MHz and when turbo kicks in should go to 3700MHz. But yours is running at 3400MHz. It should be running at 3700MHz. A multiplier of 37 is stock for your CPU. What I would like you to do is go to bios, and pay close attention to this. AI Overclock tuner click that and you should have a choice of ayto, XMP and Manual, click XMP. For turbo ratio Click it and type in 37 and press enter. Under CPU voltage leave offset for now, offset sign + ( as it is now) and offset voltage click that and put .005 and press enter. Be sure to put the . in front and 005 after. So, it should say .005. Save and exit. Run Prime again and see what it says. Please post the same screenshot and keep a close eye on temps. If it gets to 85 stop the test. Otherwise post another screenshot of CPUz and core temp while Prime is running. If you have any questions, please ask.