Author Topic: CPF 3.0.10.238 BETA BSODs[CLOSED]  (Read 1872 times)

Offline gibran

  • Average User
  • Comodo's Hero
  • *****
  • Posts: 5056
  • A bad workman always blames his tools
CPF 3.0.10.238 BETA BSODs[CLOSED]
« on: October 29, 2007, 04:37:34 AM »
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



Quote from: http://www.wintipz.com/XP/RebootFailure.htm
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'

Quote from: http://support.microsoft.com/kb/315263/en-us
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:
Quote from: http://support.microsoft.com/kb/130536
•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.
"In the beginning the Universe was created. This has made a lot of people very angry and has been widely regarded as a bad move."- Douglas Adams

Offline PJK

  • Comodo Member
  • **
  • Posts: 39
Re: CPF 3.0.10.238 BETA BSODs
« Reply #1 on: October 29, 2007, 03:40:51 PM »
Let me open the feedback with my usual BSOD report. And as usual no minidump, though I did write down the details.

1) Windows Vista Ultimate 32 bits edition. No service packs installed.
2) AVG Anti virus Free edition (v7.5.503), Teatimer (Spybot S&D 1.5.0.9)
3) -
4) BSOD as soon as Windows Vista wants to go to the desktop (glowing windows icon on black background has appeared and is gone again).

BSOD details :

BAD_POOL_CALLER

STOP: 0x000000c2 (0x00000007, 0x0000113D, 0x001C0000, 0x8A87D200)

This BSOD only happens when Defense+ is enabled. When I switch off Defense+ (disable, not the new mode) the BSOD doesn't occur (at least not on bootup, can't be certain a BSOD will not happen later. This was the case with the previous beta, which would BSOD after a random period somewhere between 4 hours and 3 days).

5) Just boot the system with Defense+ enabled and the crash occurs
6) Added below.

UPDATE

Stability is still an issue. My system uptime rarely makes it beyond 1 - 1.5 days before it BSOD's on me (usually BAD_POOL_CALLER). This with Defense+ set to Disabled (so installed, but not active, not the new don't install option).

And as always no minidumps for these crashes.

Also Windows Update doesn't seem to be able to install its patches/updates.
« Last Edit: November 06, 2007, 01:56:04 AM by PJK »

Offline egemen

  • Comodo Staff
  • Comodo's Hero
  • *****
  • Posts: 3329
Re: CPF 3.0.10.238 BETA BSODs
« Reply #2 on: November 07, 2007, 07:30:55 AM »
Let me open the feedback with my usual BSOD report. And as usual no minidump, though I did write down the details.

1) Windows Vista Ultimate 32 bits edition. No service packs installed.
2) AVG Anti virus Free edition (v7.5.503), Teatimer (Spybot S&D 1.5.0.9)
3) -
4) BSOD as soon as Windows Vista wants to go to the desktop (glowing windows icon on black background has appeared and is gone again).

BSOD details :

BAD_POOL_CALLER

STOP: 0x000000c2 (0x00000007, 0x0000113D, 0x001C0000, 0x8A87D200)

This BSOD only happens when Defense+ is enabled. When I switch off Defense+ (disable, not the new mode) the BSOD doesn't occur (at least not on bootup, can't be certain a BSOD will not happen later. This was the case with the previous beta, which would BSOD after a random period somewhere between 4 hours and 3 days).

5) Just boot the system with Defense+ enabled and the crash occurs
6) Added below.

UPDATE

Stability is still an issue. My system uptime rarely makes it beyond 1 - 1.5 days before it BSOD's on me (usually BAD_POOL_CALLER). This with Defense+ set to Disabled (so installed, but not active, not the new don't install option).

And as always no minidumps for these crashes.

Also Windows Update doesn't seem to be able to install its patches/updates.


Can you please try to enable minidumping according to the steps mentioned in the first message in this thread and try to sen us a memory dump?

Thx,
Egemen

 

Seo4Smf 2.0 © SmfMod.Com Smf Destek