Since I installed the x64 version of BOINC, I have been getting Windows abends to the blue screen of death.
Message something along the line of "KERNEL MEMORY ......", and always the same.
Have troubleshot this in as far as it happens in the first 5 minutes of BOINC running SETI as a screensaver; I only run SETI.
Does not occur with BOINC removed from PC.

Anyone else having this problem? Any ideas?

SYSTEM:
Windows 7 Home Premium (x64) Service Pack 1 (build 7601)
full 64 bit platform hardware;
8Gb RAM on 2 matched DDR3's;
8Gb Paging file.
3.10 gigahertz AMD Athlon II X4 645
64-bit ready
Multi-core (4 total)
Not hyper-threaded.
ASUSTeK Computer INC. M4A88T-M Rev X.0x,
Bus Clock: 200 megahertz,
BIOS: American Megatrends Inc. 2403 12/23/2010.
OCZ-VERTEX2 [Hard drive] (40.02 GB) -- drive 0, rev 1.29, SMART Status: Healthy
ST310003 33AS USB Device [Hard drive] (1000.20 GB) -- drive 1, s/n 
ST310003 33AS USB Device [Hard drive] (1000.20 GB) -- drive 2, s/n 

---

How about the actual error message? That wold help greatly in deciphering what is going on considering there about literally hundreds of different error codes in Windows that all get presented as a Blue Screen of Death (technically referred to as a STOP error).

Does it only stay on screen for a blink (just enough to see the first couple of words)?
I had much the same. Turned out to be a combination of a sick HD and a bad memory stick. Try removing one memory stick then swap for the other Also try in the other slots.
Good fishing

---

Bob Smith
Member of Seti PIPPS (Pluto is a Planet Protest Society)
Somewhere in the (un)known Universe?

Further info:

KERNEL_DATA_INPAGE_ERROR

It stays on the screen, no auto-reboot...

---

http://technet.microsoft.com/en-us/library/cc957628.aspx says:
Explanation:

This Stop message indicates that the requested page of kernel data from the paging file could not be read into memory. This Stop message is usually caused by a bad block (sector) in a paging file, a virus, a disk controller error, or failing RAM. In rare cases, it is caused when nonpaged pool resources run out. It is also caused by defective hardware.

User Action:

- If the I/O status is C0000185 and the paging file is on a SCSI disk, the disk cabling and SCSI termination should be checked for problems.
- Check your computer for viruses, using any up-to-date, commercial virus scanning software that examines the Master Boot Record of the hard disk.
- An I/O status code of 0xC000009C or 0xC000016A normally indicates the data cannot be read from the disk due to a bad block (sector). If you can restart the system after the error, Autochk runs automatically and attempts to map out the bad sector. If Autochk does not scan the hard disk for errors, manually launch the disk scanner. Run Chkdsk /f /r on the system partition. Restart the system before the disk scan begins.
- If you cannot start the system due to the error, use the Recovery Console and run Chkdsk /r . Caution: If your system partition is formatted with the FAT file system, the long file names used by Windows 2000 can be damaged if Scandisk or another MS-DOSbased hard disk tool is used to verify the integrity of your hard disk from an MS-DOS prompt. (An MS-DOS prompt is typically derived from an MS-DOS startup disk or from starting MS-DOS on a multiboot system.) Always use the Windows 2000 version of Chkdsk on Windows 2000 disks.
- Another common cause of this Stop message is failing RAM. Run hardware diagnostics supplied by the system manufacturer, especially the memory scanner. For details on these procedures, see the owners manual for your computer.
- Check that all network adapters in the computer are properly seated.
- Use an ink eraser or an electrical contact treatment, available at electronics supply stores, to ensure network adapter contacts are clean.
- Check the System Log in Event Viewer for additional error messages that might help pinpoint the device causing the error.
- Disabling memory caching of the BIOS might also resolve it.
- Finally, if all the above steps fail to resolve the error, take the system motherboard to a repair facility for diagnostic testing. A crack, a scratched trace, or a defective component on the motherboard can also cause this error.

---

Thanks to all.
I am currently running many rootkit and other software items to check.
I have run chkdsk.

Later I will switch off and reseat all contact in PC, reseat RAM, etc...

Having done a bit of research just now, I am wondering if I have a Power Supply problem....? Event viewer shows Critical error "Kernel-Power", but I could be wrong...

Anyone know of a programme that can tell me what the load is on my PSU?

---

the chkdsk and running memtest64 should be the most likely culprits. the BOINC program isn't CPU intensive not a power hog so the CPU and PSU are unlikely to be a problem.

---

In a rich man's house there is no place to spit but his face.
Diogenes Of Sinope

The power supply could be a problem if, while running BOINC (which in turn runs your system pretty hard) the power supply is unable to provide the required level of power to all the components, all sorts of random shutdowns and crashes can happen.

However, since the power supply is not software controlled (for the most part), power supply issues are not written to the even log, and certainly not under "KERNEL-POWER..."

I think the information given in Jord's post contains the appropriate steps to locate the problem. I wouldn't be surprised if it turns out to be a bad hard drive or failing RAM.

Okay!

Thanks to all that replied. Found the fault.

After the M/B and RAM and CPU was returned to supplier for barebones testing, there was no fault found.

However, when I re-assembled the system barebones at home, including the SSD hard drive by OCZ, I noticed that the OCZ SSD had a green functioning light AT IT'S REAR. But, when the system hung or blue screen of death'ed, it was joined by a RED light.

Supplier took it back and concurred. New SSD supplied. Apparently OCZ early drives are becoming notorious for failures. I also didn't know about the system lights on the back... did many of you?

Regards.

---

Having zero experience with SSDs, I can't say I am aware of any manufacturing details other than the technology behind how they work.

I have been very tempted to buy one for myself, and I've done a lot of research into what makes one model more expensive than the other, and I've found that generally Samsung, Intel, and Plextor seem to be the top brands with the most reliability in a few specific higher-end models. I was aware that OCZ, SanDisk, AData and a few other lower end models have notoriously high failure rates.

Good info, thanks.

---