CFP 3.0.9.229 BETA BSODs[CLOSED]

[Guest]

[gibran]

Please DO remember to add those informations to all BSODs you post .

• Windows Version/Bit and Service Packs
• Your realtime Antivirus/version,Spyware remover/Version, other Security Software/Version
• Affected Driver/Software and Version (if the bug doesn't affect window itself)
• Brief description of the problem (Attach Diagnostic report or crash dumps if needed)
• Steps to reproduce the bug (if applicable)
• Gmer report (download) Only for 32bit platforms

Disable reboot on blue screen of death

Sometimes our computer restarts after showing us a blue screen of death. It might be important for us to note down the error message that caused the blue screen of death to troubleshoot the problem. To disable rebooting the computer after you see a blue screen of death follow the below steps:

1) Goto Control Panel ---> System ( or Press Windows key + Pause)

2) Click the Advanced Tab

3) Under the 'Startup and Recovery' section click on Settings

4) Under 'System Failure' section uncheck 'Automatically Restart'

5) Click on 'OK'

Configure the dump type
To configure startup and recovery options to use the small memory dump file, follow these steps.

Note Because there are several versions of Microsoft Windows, the following steps may be different on your computer.
If they are, see your product documentation to complete these steps.

1.   Click Start, point to Settings, and then click Control Panel.
2.   Double-click System.
3.   Click the Advanced tab, and then click Settings under Startup and Recovery.
4.   In the Write debugging information list, click Small memory dump (64k).

To change the folder location for the small memory dump files, type a new path in the Dump File box (or in the Small dump directory box, depending on your version of Windows).

Find your minidumps
Paste the Small dump directory string you found in Startup and Recovery Dialog  (eg. %SystemRoot%\Minidump) in explorer and hit go




NOTE: According to Microsoft, 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.

[MasterTB]

I got a BSOD after the firs reboot, could not capture thow... no memory dump avail.,  restarted and everything is working fine, so can't really say what happened other than it happened after installing Beta 3, I presume it was Defense+ because I'm behind a router so I usually don't have inbound problems ....

Running XP SP2 32bit Spanish, Nod32 full and CFP Beta 3.

Cannot reproduce the BSOD because It was a one time event, I can uninstall and try to install again if you want but if it messes up my system you'll see FIREBALLS 

[Arkangyal]

Hello MasterTB,

Can you got out any informations form the eventviewer? (start -> run... -> eventvwr.msc, especialy from System)

Arki

[MasterTB]

That's what's weird, NO RECORD of the error. The System log is clear of errors.

[PJK]

Ok, here we go again

Windows Vista Ultimate 32 bit
Core2Duo E6600
2 Gigabytes of RAM

Realtime Security software used

Tea Timer (A.K.A Spybot S&D Resident) v1.5.0.9
AVG Antivirus v7.5.488
AVG AntiSpy (free edition, starts at boottime but isn't really residential) v7.5.1.43
The stuff that comes with Vista itself (Windows defender I guess)

I get BSOD's at system start (just after the shiny windows logo, when Vista normally goes to the desktop screen) whenever I have Defense+ activated. The last time this happened the cause was BAD_POOL_HEADER, if I remember correctly.

I can activate Defense+ after a succesful boot with it disabled, but after a few hours I again get a BSOD (I think for the same reason) and then I have to boot into safe mode to disable Defense+ again otherwise I run into the initial BSOD at windows start.

The BSOD's don't result in memory dumps being made, and yes I did check the settings and they are set as they should be set.

I did try to disable Image Execution Control (as was suggested for one of the earlier Beta's), but that seems to have no positive effects.

At the moment I have Defense+ disabled, hopefully you can fix this problem for the next version.

UPDATE

Just experienced another BSOD. Again BAD_POOL_HEADER as the indicated cause. Again no minidump.

This was with Defense+ disabled, so I guess it must have happened via CPF itself.

[pykko]

Hello!

I'm using Windows XP(x32) SP2
I use Avira AntiVir security suite (firewall uninstalled).
I get a BSOD and here is what the Event view records:

Event Type:   Error
Event Source:   Service Control Manager
Event Category:   None
Event ID:   7000
Date:      9/29/2007
Time:      8:06:14 PM
User:      N/A
Computer:   RDR
Description:
The Plustek USB Scanner service failed to start due to the following error:
The service cannot be started, either because it is disabled or because it has no enabled devices associated with it.

For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.

Now you will say it's about the Plustek scanner but Comodo has the big role in this. No Comodo installed on my computer in 2 months, no BSOD, installed Comodo in one hour a BSOD, uninstalled Comodo, no BSOD again.

Edit: Now, anothe restart from nothing... the Plustek scanner was totally uninstalled now and there is no Error in the Event View this time.
I don't know what happens...

[pykko]

Now I hit Diagnostics button under Miscellanous and I got a new BSOD.

Is someone looking here at this thread ? I got also many BSODs with Beta 2 and it seems nothing has changed.

[gibran]

Now I hit Diagnostics button under Miscellanous and I got a new BSOD.

Is someone looking here at this thread ? I got also many BSODs with Beta 2 and it seems nothing has changed.

Yep I read it I found out that the Introduction post I made was a bit lacking in details. Maybe now that I rewrote it you can post more details in order to help developers to pinpoint the issue and solve it.

If you want the product to work and you feel inconfortable with betatesting in general you may wish to wait for a Release Candidate or the Final version.

Anyway It would be a great help if you continue testing it and for example uninstall your AV for a few hours in order to give a valuable proof that there is a compatibility issue with it.

If you still experience BSOD then the problem lies in another software/driver and a Microsoft System Information Report would be needed.

[pykko]

ok... I"ll uninstall it and see what happend. Then I'll post again. Thank you!

[pykko]

Sorry, but my system get totally screwed up. This Beta is very unstable and killed my system. I'll wait for the final version 

[egemen]

Sorry, but my system get totally screwed up. This Beta is very unstable and killed my system. I'll wait for the final version 

It is quite unlikely that CFP can cause such prsistent BSODs. If you can provide us a minidump, we can immediately identify the buggy piece and let you know.

Thx,
egemen

[toon]

Running XP SP2 32bit, CAVS beta 2, Spyware Terminator

BSOD occurred at the "configuring CPF" stage of installation, unfortunately no memory dump was created.

This error appears to have prevented the software from completing the install, upon reboot CPF did not load, and when I manually started it from its program folder it presented an error message, so I ran the diagnostics utility which apparently found and fixed some problems.

In addition, CPF is not listed it the start menu or add-remove programs (I assume it should be). So, Does anyone know how I can remove the software and try again and see if the same thing happens?

Thanks

[gibran]

Running XP SP2 32bit, CAVS beta 2, Spyware Terminator

BSOD occurred at the "configuring CPF" stage of installation, unfortunately no memory dump was created.

This error appears to have prevented the software from completing the install, upon reboot CPF did not load, and when I manually started it from its program folder it presented an error message, so I ran the diagnostics utility which apparently found and fixed some problems.

In addition, CPF is not listed it the start menu or add-remove programs (I assume it should be). So, Does anyone know how I can remove the software and try again and see if the same thing happens?

Thanks

Your only option ATM is to use system restore.

[toon]

Thanks for the quick reply gibran, I've done a system restore, reinstalled CPF and the same thing happened again.

The dump settings are exactly as stated in your first post, but again no dump file was created, and nothing appears in the event viewer either - odd.

I'll have to switch back to 2.4, but if you can think of anything else I can do to record the error info then let me know.

[gibran]

Thanks for the quick reply gibran, I've done a system restore, reinstalled CPF and the same thing happened again.

The dump settings are exactly as stated in your first post, but again no dump file was created, and nothing appears in the event viewer either - odd.

I'll have to switch back to 2.4, but if you can think of anything else I can do to record the error info then let me know.

What message you got on the BSOD?

[Tags:]