• We’re currently investigating an issue related to the forum theme and styling that is impacting page layout and visual formatting. The problem has been identified, and we are actively working on a resolution. There is no impact to user data or functionality, this is strictly a front-end display issue. We’ll post an update once the fix has been deployed. Thanks for your patience while we get this sorted.

Please help diagnose my BSOD problem

F

futurefields

Diamond Member
In the last month or so my BSOD's are becoming too frequent too live with. But I can't tell what is wrong because the error message goes so fast, the computer resets itself before I can read it. And when I open WhoCrashed, there aren't any crash logs which seems odd to me. I have this screenshot of event viewer it seems like it is something power or memory related but that's just a hunch

r6zrqs.png
 
Windows has an error reporting service providing logs of errors in a WER folder . Read the logs for some info.

"WER stands for Windows Error Reporting (WER). Windows Error Reporting collects and offers to send post-error debug information (a memory dump), using the Internet, to the developer of an application that crashes or stops responding on a user's desktop. No data is sent without the user's consent."

You can delete the files from \Windows\WER.

Also, run CCleaner. It offers up error logs primarily for deletion but which could help locate the problem.
 
Running Windows 7 x64, i5 2500k, 8gb RAM, GTX 970

WhoCrashed did pick up some new info from a crash today:

On Mon 3/27/2017 2:19:59 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\032617-16317-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x6F400)
Bugcheck code: 0xF4 (0x3, 0xFFFFFA800A04D060, 0xFFFFFA800A04D340, 0xFFFFF800033D0E40)
Error: CRITICAL_OBJECT_TERMINATION
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that a process or thread crucial to system operation has unexpectedly exited or been terminated.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem. This problem might be caused by a thermal issue.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.



On Mon 3/27/2017 2:19:59 AM GMT your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: ntkrnlmp.exe (nt!KeBugCheckEx+0x0)
Bugcheck code: 0xF4 (0x3, 0xFFFFFA800A04D060, 0xFFFFFA800A04D340, 0xFFFFF800033D0E40)
Error: CRITICAL_OBJECT_TERMINATION
Bug check description: This indicates that a process or thread crucial to system operation has unexpectedly exited or been terminated.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem. This problem might be caused by a thermal issue.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.




And was able to grab this photo of the BSOD:

1zbqob7.jpg
 
What 3rd-party (non-Microsoft) software and hardware do you have hooked up? Could be a kernel driver bug. It could be malware too, maybe. Couldn't hurt to check out both.
 
Reset my cmos and reseated my RAM to slots 2 and 4

Restarted PC and BSOD's are much worse now, thinking its because I moved the RAM

Gonna try a stick at a time now

@VirtualLarry im not seeing where to set that SATA mode
 
Trying one stick but I cant get into Windows. It says the configuration has changed and Windows needs to repair something, but then it fails. I try to run the memory diagnostic on that menu and it says it cannot check the memory. I try to boot from my Windows 7 disc but I have no mouse functionality in those menus.
 
futurefields said:
Trying one stick but I cant get into Windows. It says the configuration has changed and Windows needs to repair something, but then it fails. I try to run the memory diagnostic on that menu and it says it cannot check the memory. I try to boot from my Windows 7 disc but I have no mouse functionality in those menus.
Click to expand...
It's not really good idea to re-seat RAM to other slots, most mobos won't even post if slot 1 and then 3 are not populated first.
Reverse RAM and test it with cpu on stock.
Other reasons you might not boot is changed SATA mode if it is changed from what it was during first Win7 setup by BIOS clearance, it won't boot.
 
If you overclock and BSOD many times, Windows registry database can be corrupted/damaged to a degree that you can't get into Windows at all. Repair also doesn't work.

The only way probably is to reinstall Windows.
 
I had a problem that looked just like yours (same kernel type error). First thought it was a PSU, but ultimately traced to a piece of software related to encryption security (secudisk).

Did you install or use any kind of security/protection/DRM involving DvD or USB security?

There are a number of ways to approach diagnosing your issue. Pretty sure it's going to be a piece of software.

Fresh boot the system and just continue to do a limited number of simple things to see if the problem exhibits. If it continues to run successfully, add another operation into the mix of OS operations such as read from DvD or plug in and read & write to a USB thumb drive, etc.

I would be very suspicious of any relatively new piece of hardware such as an external HDD or USB thumb that came with encryption capability/software on it. Uninstall in the OS anything related to such devices and dont use any external type drives in your initial testing.
 
mxnerd said:
If you overclock and BSOD many times, Windows registry database can be corrupted/damaged to a degree that you can't get into Windows at all. Repair also doesn't work.

The only way probably is to reinstall Windows.
Click to expand...

I mean it's not like I just OC and the problems started. I built the system in 2012 and its been running at 4.2 the entire time, over four years stable. I have a CM 212+ cooler and my cpu never goes above 65 degrees. Problems only started about a week ago. I hope its just a RAM stick but probably not.

I use this system for gaming and music production.
 
From your own post.
Bug check description: This indicates that a process or thread crucial to system operation has unexpectedly exited or been terminated.

This appears to be a typical software driver bug and is not likely to be caused by a hardware problem. This problem might be caused by a thermal issue.
Click to expand...

OK. Since you already build the system for 4 years, the CPU thermal paste maybe hardened over time.

Take the cooler off, remove old paste and apply new thermal paste. CPU probably does overheat, but you did not notice it. Especially you overclock it. Like what other member have said, overclock for a long period of time can also degrade CPU.

It's also possible motherboard become unstable after 4 years of usage. Hard to tell.
 
Last edited:
futurefields said:
I mean it's not like I just OC and the problems started. I built the system in 2012 and its been running at 4.2 the entire time, over four years stable. I have a CM 212+ cooler and my cpu never goes above 65 degrees. Problems only started about a week ago. I hope its just a RAM stick but probably not.

I use this system for gaming and music production.
Click to expand...
That's how everything breaks down, it works for a long time and then suddenly it isn't, don't know what is hard to understand that overclocking and playing games is causing major stress to components and decreasing their life-span. 5 Years is long time for an overclocked CPU, or RAM or Graphics card or any other thing, and 2500Ks do degrade after few years when overclocked. By degradation I mean they lose stability of the OC and require increased Vcore to maintain the same frequency which is very unlikely to work long-term.
 
mxnerd said:
From your own post.


OK. Since you already build the system for 4 years, the CPU thermal paste maybe hardened over time.

Take the cooler off, remove old paste and apply new thermal paste. CPU probably does overheat, but you did not notice it. Especially you overclock it. Like what other member have said, overclock for a long period of time can also degrade CPU.

It's also possible motherboard become unstable after 4 years of usage. Hard to tell.
Click to expand...

My cpu temps never go above the 60's, I monitor them all the time. If thermal paste was bad, I would see high temps no?
 
Hardware/software/OS trouble shooting is hard even for engineers,

CPU probably degrades to a point where it was stable at 60-65 degree but it requires lower temperature now because of the degradation.

I'm just offering my thoughts/experiences, you can take them or leave them.
 
Last edited:
You must log in or register to reply here.

TRENDING THREADS

Back
Top