BSOD every 30minutes ntoskml.exe+74, error

[Julianiscool123]

Hey I've been having BSOD every 30 minutes for past few days haven't been able to fix it here's my minidump file

 

[Arc]

:ar: Blue Screen of Death (BSOD) Posting Instructions

 

[Julianiscool123]

:ar: Blue Screen of Death (BSOD) Posting Instructions

Sorry, fixed it.

 

[Arc]

Multiple different BSODs, pointing to nothing special, but most of them took place when OSBuddy was running. What is OSBuddy, by the way? Please let me know?

Test your RAM modules for possible errors.

How to Test and Diagnose RAM Issues with Memtest86+
​

Run memtest86+ for at least 8 consecutive passes.

If it start showing errors/red lines, stop testing. A single error is enough to determine that something is going bad there.

Stress test the Graphics Card using Furmark.

Video Card - Stress Test with Furmark
​

Take a screenshot of the furmark window before closing it. Upload the screenshot for us. Also let us know if you have experienced any crash/BSOD and/or artifacts during the test.

Stress test the CPU.

Hardware - Stress Test With Prime95
​

It saves the result as a .txt file in the prime95's folder. Upload the file for us.

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. Alternatively, you can publish a Speccy snapshot too: http://www.sevenforums.com/tutorials/311593-speccy-publish-snapshot-your-system-specs.html .
_____________________________________

BugCheck 3B, {c0000005, fffff96000153aef, fffff88009f42240, 0}

Probably caused by : hardware ( win32k!XCLIPOBJ::cEnumStart+1f )

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

BugCheck D1, {1, 2, 8, 1}

Probably caused by : ntkrnlmp.exe ( nt!KiPageFault+260 )

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

BugCheck A, {fffffaa006301138, 2, 0, fffff80003ad8f1b}

*** WARNING: Unable to verify timestamp for cdd.dll
*** ERROR: Module load completed but symbols could not be loaded for cdd.dll
Probably caused by : cdd.dll ( cdd+5824 )

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

 

[Julianiscool123]

Multiple different BSODs, pointing to nothing special, but most of them took place when OSBuddy was running. What is OSBuddy, by the way? Please let me know?

Test your RAM modules for possible errors.

How to Test and Diagnose RAM Issues with Memtest86+
​

Run memtest86+ for at least 8 consecutive passes.

If it start showing errors/red lines, stop testing. A single error is enough to determine that something is going bad there.

Stress test the Graphics Card using Furmark.

Video Card - Stress Test with Furmark
​

Take a screenshot of the furmark window before closing it. Upload the screenshot for us. Also let us know if you have experienced any crash/BSOD and/or artifacts during the test.

Stress test the CPU.

Hardware - Stress Test With Prime95
​

It saves the result as a .txt file in the prime95's folder. Upload the file for us.

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. Alternatively, you can publish a Speccy snapshot too: http://www.sevenforums.com/tutorials/311593-speccy-publish-snapshot-your-system-specs.html .
_____________________________________

BugCheck 3B, {c0000005, fffff96000153aef, fffff88009f42240, 0}

Probably caused by : hardware ( win32k!XCLIPOBJ::cEnumStart+1f )

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

BugCheck D1, {1, 2, 8, 1}

Probably caused by : ntkrnlmp.exe ( nt!KiPageFault+260 )

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

BugCheck A, {fffffaa006301138, 2, 0, fffff80003ad8f1b}

*** WARNING: Unable to verify timestamp for cdd.dll
*** ERROR: Module load completed but symbols could not be loaded for cdd.dll
Probably caused by : cdd.dll ( cdd+5824 )

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

Osbuddy is just a game client I have been using for over 2 years already so I don't think that is the problem and I will do those steps first thing in the morning

 

[Arc]

Osbuddy is just a game client I have been using for over 2 years already so I don't think that is the problem and I will do those steps first thing in the morning

I am not saying that OSBuddy has caused the BSODs till now, but what you said is not an argument but puts some restrictions and resistances there only.

Keep your mind open.

 

[Julianiscool123]

Osbuddy is just a game client I have been using for over 2 years already so I don't think that is the problem and I will do those steps first thing in the morning

I am not saying that OSBuddy has caused the BSODs till now, but what you said is not an argument but puts some restrictions and resistances there only.

Keep your mind open.

Yeah I know, sorry if I was coming off rude I was just letting you know what it is I will keep you updated on the memory check thank you for helping me

 

[Arc]

You know why it is not an argument? As per this statement, you are using this computer for a reasonably long time too, so that computer also cannot cause any problem.

Report us when the tests are done. No hurry, take your time.

 

[Julianiscool123]

You know why it is not an argument? As per this statement, you are using this computer for a reasonably long time too, so that computer also cannot cause any problem.

Report us when the tests are done. No hurry, take your time.

Ok I just did this test going to try the others now.

Edit: just ran a prime95 test and it said there was an error but my computer crashed so here were the results I got.

 

[Arc]

[Tue Jun 09 16:38:13 2015]
FATAL ERROR: Rounding was 0.5, expected less than 0.4
[COLOR=Red]Hardware failure detected[/COLOR], consult stress.txt file.

A quick failure, apparently.

It may be an error from the part of the CPU itself, or it may be due to overheating. So now do this part ....

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. Alternatively, you can publish a Speccy snapshot too: Speccy - Publish Snapshot of your System Specs .

We will be able to arrive at the decision after seeing the speccy report.

 

[Julianiscool123]

[Tue Jun 09 16:38:13 2015]
FATAL ERROR: Rounding was 0.5, expected less than 0.4
[COLOR=Red]Hardware failure detected[/COLOR], consult stress.txt file.

A quick failure, apparently.

It may be an error from the part of the CPU itself, or it may be due to overheating. So now do this part ....

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. Alternatively, you can publish a Speccy snapshot too: Speccy - Publish Snapshot of your System Specs .

We will be able to arrive at the decision after seeing the speccy report.

alright here you go.

 

[Arc]

The CPU is visually overheating.

Open the computer. Clean the inside carefully. Clean all the air vents and fan grills so that it can blow the hot air out effectively. While re-seating, apply new thermal paste to the CPU.



If you are using the stock CPU cooler, get a custom one, either air or water cooler.

If you cannot do those jobs yourself, get it done by some professional, but get it done at once, as early as possible.

Then observe the situation after controlling the heat. If the same BSOD continues, run prime95 again. If it still reports hardware error, you will need to replace the CPU.