If you come across with a BSOD
or an instant reboot (silent BSOD), and you suspect the cause of the problem was CFP, please report it here.
You need to give some additional info:
1. Attach the minidump file. You will find it under C:\windows\minidump\
2. The version of CFP that you are using
3. Give some info about your OS, processor, ram and your network card.
edit: for activating windows to create the minidump report take a look at the following images
According to MS:
There are several reasons why the Memory.dmp file is not being created when your computer encounters a STOP message:
•The Memory.dmp file already exists and the option Overwrite Any Existing File (found in Control Panel System) is not selected. It is a good idea to leave this box checked and to move or copy the current Memory.dmp file.
•The paging file on the boot drive is not large enough. To use the "Write Debugging Information To" feature to obtain a complete memory dump file, the paging file on the boot drive must be at least as large as physical memory + 1 MB. When you create a kernel memory dump file, the file is usually around one-third the size of the physical memory on the system. Of course, this quantity will vary, depending on your circumstances.
•The paging file is not on the %systemroot% partition. When the STOP error occurs, the system crash dump is written out to the pagefile on the root of the %systemroot% drive.
•There is not room for the Memory.dmp file in the path specified in Control Panel for writing the memory dump.
•It is possible that the SCSI controller is bad or the system crash is caused by a bad SCSI controller board.
•If you specify a non-existent path, a dump file will not be written. For example, if you specify the path as C:\Dumpfiles\Memory.dmp and no C:\Dumpfiles folder exists, a dump file will not be written.
[attachment deleted by admin]