Sign in with
Sign up | Sign in
Your question
Solved

Questionable CPU failure

Last response: in CPUs
Share
January 26, 2014 10:46:42 AM

Hello, I've been having a BSoD problem for a couple months now, and it seems like whenever I have a game on for a while, minimize it, leave for a bit, and come back and exit the game, BSoD comes up. I ran crystal disk info and saw that I was having sector failures on it, so I bought a new one (I needed a bigger internal anyways...) and re installed windows 7, but BSoD kept coming up. I'm thinking its the possessor only because its kind of old, but not too old that BSoD would be expected... Before I buy a new anything, I want to make sure I have diagnosed it correctly (which I am spectacle on, lol). There are also random times where windows color scheme seems to fail and I'm left with this blue window border, and then randomly sets its self back to normal... I'm thinking about re installing windows once more, but I'm sure that wont fix anything.... If anyone has incite to this, it would be much appreciated! Thanks!
a b à CPUs
January 26, 2014 11:06:31 AM

Pretty hard to say, at a guess.

In 25 years, every time I think I have symptom nailed down, the next time it comes up, it is a different cause.

The only real way to test, is try known good parts in your computer, one at a time, or try your parts in a running computer one at a time.

The only way to test the board, is through the process of ilimitation.

Even a computer shop, tests this way, as only the factory would have direct test equipment.

Edit.
Processors don't get old, you can kill them, but not because they are old, like a hard drive.

m
0
l

Best solution

a b à CPUs
January 26, 2014 11:27:31 AM

There are a few software tests you can do first, but that is just memory, and the hard drive.
http://www.memtest.org/

The hard drive test you get from the hard drive manufacturer sight.

Then there is a program who crashed, that might give you some insight.
http://www.resplendence.com/whocrashed
Share
Related resources
January 26, 2014 11:38:42 AM

millwright said:
There are a few software tests you can do first, but that is just memory, and the hard drive.
http://www.memtest.org/

The hard drive test you get from the hard drive manufacturer sight.

Then there is a program who crashed, that might give you some insight.
http://www.resplendence.com/whocrashed


Thanks for suggusting the whocrashed program, I got this many times:

crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: ntfs.sys (Ntfs+0xF1C7C)
Bugcheck code: 0xD1 (0xFFFFF88001104C7C, 0x0, 0x8, 0xFFFFF88001104C7C)
Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
file path: C:\Windows\system32\drivers\ntfs.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT File System Driver
Bug check description: This indicates that a kernel-mode driver attempted to access pageable memory at a process IRQL that was too high.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system that cannot be identified at this time.

I will try to figure it out from here, thanks for you're help!
m
0
l
a b à CPUs
January 26, 2014 11:43:48 AM

Welcome, and yah, figuring out what it is saying is a problem in itself.:) 
m
0
l
!