I have bought a new computer in late december 2009 and from the beginning I´ve been having two problems, the computer randomly restarts and more seldom but still a problem, the computer freezes. These events can happen with a frequency less than one time each
day and sometimes as often as three times a day. The computer can be on reasonable load or hardly any load at all when it happens.
My computer parts looks like the following and I´ve got Windows on one of my two SSDs:
Western Digital Caviar Black WD2001FASS 64MB 2TB
Corsair Dominator GT DDR3 PC12800/1600MHz CL8 4x2GB
Gainward GeForce GTX 275 896MB PhysX PCI-Express 2.0, 2xDVI
Gigabyte GeForce 210 OC HDMI 512MB
Asus P7P55D-E Premium
Antec CP-850 850W
Microsoft Windows 7 Ultimate Eng
Intel Core i7 860
Intel X25-M G2 160GB
Logitech Wave Keyboard (SV)
The first time I´ve recieved a message when windows was shutting down was just a while ago, and it said something about the moemory. I have run memtest86 which showed no problems earlier. I can´t open the minidum file but got hte following message this one
time (have not had any messages like these before and the event viewer hasn´t given me any useful information).
Problem Event Name: BlueScreen
OS Version: 6.1.7600.2.0.0.256.1
Locale ID: 1053
Additional information about the problem:
OS Version: 6_1_7600
Service Pack: 0_0
Files that help describe the problem:
Bugcheck 1a is related to a problem with memory. This could be problems with physical RAM, or memory corruption. If memory corruption is triggering the bugcheck, the hope is that driver verifier may be able to provide additional details (at the time
of the bugcheck) about what the cause may be. To enable driver verifier, run verifier.exe. Choose to "Create standard settings", click Next, choose to "Select driver names from a list", click Next, sort by the Provider column, and check all non-Microsoft
drivers. Click Finish, and reboot.
In the event the system is not able to boot successfully after enabling driver verifier, boot into safe mode and run verifier.exe again. Choose to "Delete existing settings", Finish, and then reboot. This means that a system-start or boot-start driver
is triggering a bugcheck.
I understand you've tested the memory with memtest86; unfortunately, memory that does not fail a memory test is not necessarily "good" memory - it is simply memory that hasn't failed a test. Consider swapping memory modules to see if that affects the behavior
(e.g., use 2 instead of 4 modules, etc.).
Did this solve your problem?
Sorry this didn't help.
Great! Thanks for marking this as the answer.
How satisfied are you with this reply?
Thanks for your feedback, it helps us improve the site.
Boot the computer in ‘Safe Mode’ and keep it under observation.
Below are the steps which talks about how to get into ‘Safe Mode’:
1. Restart your computer if it is powered on.
2. Tap the F8 key after your computer initially powers on.
3. Once you see the Advanced Boot Options menu you can stop tapping.
4. Use the up/down arrow keys to highlight your selection.
5. Select Safe Mode and press Enter.
6. You should see drivers loading, and then please wait.
7. You should then be at the Welcome Screen.
8. Logon to your computer using an account with Administrator privileges.
If the issue does not persist in Safe Mode, you have to put the computer in a Clean Boot state to check if any of the third party service is causing the issue. Below are the steps to put the computer in a Clean Boot State:
To perform a Clean Boot on a computer that is running Windows 7:
1. Click Start, type msconfig in the Start Search box, and then press ENTER. If you are prompted for an administrator password or for a confirmation, type the password, or click Continue.
2. On the General tab, click Selective Startup.
3. Under Selective Startup, click to clear the Load Startup Items check box.
4. Click the Services tab, click to select the Hide All Microsoft Services check box, and then click Disable All.
5. Click OK.
6. When you are prompted, click Restart.
7. After the computer starts, check if the issue is fixed.
If your issue is resolved after performing Clean Boot, then follow the steps mentioned in the following KB article to narrow down the exact source: