Windows 7 likes to crash on me about every week
I have Windows 7 Pro 64-bit edition and it seems like every week I get a blue screen since it crashed for some reason.
I have no clue what is causing this.
I have 4 gigs of RAM with 2 of them not 100% sure if they work as they should. I say this because it was on some computer that suffered a power surge and I was given the RAM that was still working for free. So I am not sure if this could cause a problem.
Before I went to Windows 7 Pro 64-bit I had Windows XP Pro. I was able to overclock my Intel E2180 dual core CPU to 3GHz, but now I can't do this anymore and have had to lower it to 2.8GHz.
When I tried to have it at 3GHz my computer would turn on and it would try to power up and it would just fail and shutoff. It made this clicking sound that always followed a shutdown.
So I lowered it to 2.8, used prime95, did a 30 min torture test and it never crashed once. I don't think the temps went past 60 degrees.
However, once in a while I here the same clicking sound as if the computer was just about to lose power but then quickly regains the power. I am not sure if this is because it was about to go into hibernate mode or what.
How can I take a screenshot of the blue screen so that when it happens again (probably next week) I can post something up to show what it says? Thanks.
Here are all my blue screen I have encountered.
A problem has been detected and Windows has been shut down to prevent damage to your computer.
The problem seems to be caused by the following file: ntoskrnl.exe
IRQL_NOT_LESS_OR_EQUAL
If this is the first time you've seen this stop error screen, restart your computer. If this screen appears again, follow these steps:
Check to make sure any new hardware or software is properly installed. If this is a new installation, ask your hardware or software manufacturer for any Windows updates you might need.
If problems continue, disable or remove any newly installed hardware or software. Disable BIOS memory options such as caching or shadowing. If you need to use safe mode to remove or disable components, restart your computer, press F8 to select Advanced Startup Options, and then select Safe Mode.
Technical Information:
*** STOP: 0x0000000a (0x0000000000000028, 0x0000000000000002, 0x0000000000000000, 0xfffff80002b18090)
*** ntoskrnl.exe - Address 0xfffff80002ad5f00 base at 0xfffff80002a64000 DateStamp 0x4a5bc600
// I had 3 of the following
A problem has been detected and Windows has been shut down to prevent damage
to your computer.
The problem seems to be caused by the following file: Ntfs.sys
SYSTEM_SERVICE_EXCEPTION
If this is the first time you've seen this stop error screen,
restart your computer. If this screen appears again, follow
these steps:
Check to make sure any new hardware or software is properly installed.
If this is a new installation, ask your hardware or software manufacturer
for any Windows updates you might need.
If problems continue, disable or remove any newly installed hardware
or software. Disable BIOS memory options such as caching or shadowing.
If you need to use safe mode to remove or disable components, restart
your computer, press F8 to select Advanced Startup Options, and then
select Safe Mode.
Technical Information:
*** STOP: 0x0000003b (0x00000000c0000005, 0xfffff80002d48b9b, 0xfffff88008e9d080,
0x0000000000000000)
*** Ntfs.sys - Address 0xfffff880012aea20 base at 0xfffff88001247000 DateStamp
0x4a5bc14f
A problem has been detected and Windows has been shut down to prevent damage to your computer.
The problem seems to be caused by the following file: ntoskrnl.exe
KMODE_EXCEPTION_NOT_HANDLED
If this is the first time you've seen this stop error screen,
restart your computer. If this screen appears again, follow
these steps:
Check to make sure any new hardware or software is properly installed.
If this is a new installation, ask your hardware or software manufacturer
for any Windows updates you might need.
If problems continue, disable or remove any newly installed hardware
or software. Disable BIOS memory options such as caching or shadowing.
If you need to use safe mode to remove or disable components, restart
your computer, press F8 to select Advanced Startup Options, and then
select Safe Mode.
Technical Information:
*** STOP: 0x0000001e (0x0000000000000000, 0x0000000000000000, 0x0000000000000000,
0x0000000000000000)
*** ntoskrnl.exe - Address 0xfffff80002ad1ed0 base at 0xfffff80002a60000 DateStamp
0x4a5bc600
Not sure what they really are. Quick good search shows the first one to be a critical file but not sure how to get a new one if it is really corrupted.
Checkdisk
C:\Windows\system32>chkdsk
The type of the file system is NTFS.
WARNING! F parameter not specified.
Running CHKDSK in read-only mode.
CHKDSK is verifying files (stage 1 of 3)...
160000 file records processed.
File verification completed.
165 large file records processed.
0 bad file records processed.
2 EA records processed.
62 reparse records processed.
CHKDSK is verifying indexes (stage 2 of 3)...
234340 index entries processed.
Index verification completed.
0 unindexed files scanned.
0 unindexed files recovered.
CHKDSK is verifying security descriptors (stage 3 of 3)...
160000 file SDs/SIDs processed.
Security descriptor verification completed.
37171 data files processed.
CHKDSK is verifying Usn Journal...
36260256 USN bytes processed.
Usn Journal verification completed.
Windows has checked the file system and found no problems.
102406310 KB total disk space.
41217544 KB in 121145 files.
73576 KB in 37172 indexes.
0 KB in bad sectors.
265510 KB in use by the system.
65536 KB occupied by the log file.
60849680 KB available on disk.
4096 bytes in each allocation unit.
25601577 total allocation units on disk.
15212420 allocation units available on disk.
Update
Got another crash to add to the list. I guess my computer is trying to go through every different crash it can go through
A problem has been detected and Windows has been shut down to prevent damage
to your computer.
The problem seems to be caused by the following file: Ntfs.sys
NTFS_FILE_SYSTEM
If this is the first time you've seen this stop error screen,
restart your computer. If this screen appears again, follow
these steps:
Check to make sure any new hardware or software is properly installed.
If this is a new installation, ask your hardware or software manufacturer
for any Windows updates you might need.
If problems continue, disable or remove any newly installed hardware
or software. Disable BIOS memory options such as caching or shadowing.
If you need to use safe mode to remove or disable components, restart
your computer, press F8 to select Advanced Startup Options, and then
select Safe Mode.
Technical Information:
*** STOP: 0x00000024 (0x00000000001904fb, 0xfffff880096d3d98, 0xfffff880096d35f0,
0xfffff80002ae2167)
*** Ntfs.sys - Address 0xfffff880012233d8 base at 0xfffff88001202000 DateStamp
0x4a5bc14f
You don't need to take a screenshot of the blue screen (although the easiest way is with a digital camera).
You can use BlueScreenView to recreate the BSOD, so please analyze the problem as much as possible on your side, before posting more info.
BlueScreenView scans all your minidump files created during 'blue screen of death' crashes, and displays the information about all crashes in one table. For each crash, BlueScreenView displays the minidump filename, the date/time of the crash, the basic crash information displayed in the blue screen (Bug Check Code and 4 parameters), and the details of the driver or module that possibly caused the crash (filename, product name, file description, and file version). For each crash displayed in the upper pane, you can view the details of the device drivers loaded during the crash in the lower pane. BlueScreenView also mark the drivers that their addresses found in the crash stack, so you can easily locate the suspected drivers that possibly caused the crash.
I start a new answer. First to comment on the 3 types of crash info.
1. In IRQL_NOT_LESS_OR_EQUAL Microsoft Support says:
This error usually occurs after the installation of a buggy device driver, system service, or BIOS. To resolve it quickly, restart your computer, and press F8 at the character-mode menu that displays the operating system choices. At the resulting Windows 2000 Advanced Options menu, choose the Last Known Good Configuration option. This option is most effective when only one driver or service is added at a time.
2. In SYSTEM_SERVICE_EXCEPTION they say:
It indicates an exception was raised in a system service which was not handled by the system service.
From your info, the faulting service is Ntfs.sys, meanining the hard disk!
3. In KMODE_EXCEPTION_NOT_HANDLED
This Stop message indicates that a kernel-mode process tried to execute an incorrect or unknown processor instruction.
Here the faulting process is the Windows kernel itself. Bad, very bad.
Analysis:
Either a hardware problem caused by over-clocking, or a bad driver is executing on kernel-level.
Recommendations:
- Follow the instructions here: How to Use the Memory Diagnostics Tool in Vista
- Do chkdsk
and we'll see how we go from here.
Going by the symptoms you listed: clicking noise and BSODs with ntfs.sys; this would most likely point to a hard drive going bad. That of course is assuming the clicking noise is coming from your hard drive. I'm not sure of anything else that has a clicking noise in a computer that isn't a fan or hard drive, but you may want to try throwing in something like Ultimate Boot CD and running a full check disk on the hard drive. Barring any of these not fixing the issue, you can do the following, in recommended order:
- Reinstall the operating system
- Try each memory stick separately, in each memory slot.
- Replace the hard drive
- If you have spare memory, try those
- Sacrifice a goat
These are the cheapest solutions to try. After this you start getting into the really expensive components like the motherboard or the processor.
According to the Intel Processor E2000 Series Datasheet your maximum operating temperature should be 73.3 degrees celsius. Since you stated that your maximum temperature is 60 degrees I would guess that shouldn't be a problem.
When you ran prime95 did you run two tests at the same time or just one? Since your processor is dual core, you may not have stressed it 100% and your 60 degrees could point to the problem.
That being said, in my personal experience, I was having random BSODs with Vista x64. Each message was different and occurred at different times. When that happens it is usually a hardware issue. In my case, my water pump had broken and the processor kept stalling itself to keep from overheating. Once I fixed the water pump, all of the BSODs went away. My BSODs had an IRQL_NOT_LESS_OR_EQUAL, one referencing the USB driver, and the KMODE_EXCEPTION_NOT_HANDLED.
Honestly I would check your heatsink and re-seat it. Once you have confirmed that I would run a test like the Windows Memory Diagnostic or memtest86+ to confirm your memory is ok. Again, random BSODs that are unrelated usually have to deal with hardware corruption.
ANSWER : REDUCE OVERCLOCKING LEVEL
According to the specs of Intel E2180 your CPU speed is 2 GHZ, which you're currently overclocking at 2.8 GHZ !
I quote from OverClocking Risks:
Usually processors in the lower range are produced with the same manufacturing process as the CPUs sold in the mid to high range. The higher rated CPUs are factory overclocked and tested, then sold for a premium. Many users will buy the cheaper processor and over clock it to nearly the same speeds of the premium CPUs. This is a great deal if and only if you are lucky enough to get a CPU that just missed the premium cut during initial factory testing. Sometimes, you will be stuck with a CPU that only over clocks slightly above its rating.
In other words, the processor that you have was factory-tested and found to be incapable of sustaining in the long-term much higher clock-rates than what the specs say. If it could, it would have been sold as another model and a different price.
Apparently, you are lucky to have a CPU is of such a good quality that it still works even when cranked up all the way from 2 GHZ to 2.8. Be thankful that it only crashes on you about once a week, maybe when it heats up to unsustainable levels.
However, if you continue overclocking, you risk one day to burn-out completely your CPU.
I suggest that you go down in the overclocking, doing a binary search for the correct level. Meaning that you try 2.4GHZ, and if it still crashes go to 2.2, and if not then try 2.6. We already know from your data that 2.8 is too high.