Welcome, Guest. Please login or register.
March 18, 2010, 06:32:25 AM

Login with username, password and session length

372351 Posts
41267 Topics
93919 Members

Latest Member: petelomax

Search:     Advanced search | Tag Cloud
+  Welcome to the Comodo Forum
|-+  Desktop Security Products & Services
| |-+  Comodo Internet Security - CIS
| | |-+  Bug Report - CIS
| | | |-+  BSODs: Please add your minidump files here (CIS v4.x)
« previous next »
Pages: [1] Go Down Print
Author Topic: BSODs: Please add your minidump files here (CIS v4.x)  (Read 55165 times)
gibran
Average User
Comodo's Hero
*****
Offline Offline

Posts: 5063


A bad workman always blames his tools


« on: September 11, 2008, 07:39:03 AM »

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.


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)
  • 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.
« Last Edit: March 11, 2010, 10:31:43 AM by Arkangyal » Logged

"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
bequick
Comodo's Hero
*****
Online Online

Posts: 659



WWW
« Reply #1 on: March 07, 2010, 04:35:44 PM »

CIS crashed under Windows 7 x 86.Pictures and dump file attached.
Logged


asus
Newbie
*
Offline Offline

Posts: 9



« Reply #2 on: March 08, 2010, 11:34:50 AM »

Some will want to take into account the crash reports? In vain I send bug?
Also reports is sent here and expect a reply email that you have taken any measures.
Please refer to your e-mail sent to you at CRASH,reports here also is sent : cpfbugs[at]comodo.com
Logged
bequick
Comodo's Hero
*****
Online Online

Posts: 659



WWW
« Reply #3 on: March 08, 2010, 12:20:14 PM »

CIS crashed under Windows 7 x 86.Pictures and dump file attached.


Anybody ??
Logged


bequick
Comodo's Hero
*****
Online Online

Posts: 659



WWW
« Reply #4 on: March 10, 2010, 03:01:48 AM »

Anybody ??
C'mon.I can't believe it.3 days-0 downloads.Does anybody cares about that?Why is CIS crashing, for example...
Logged


asus
Newbie
*
Offline Offline

Posts: 9



« Reply #5 on: March 10, 2010, 04:03:12 PM »

Team are not interested: ( Huh
Do not close section that no one enter?
Logged
Daniel Jackson
Comodo Loves me
****
Offline Offline

Posts: 105



« Reply #6 on: March 10, 2010, 04:08:02 PM »

I also would like my issue be fixed. I am waiting more than two weeks without any response. And my computer is still crashing...
Logged
Daniel Jackson
Comodo Loves me
****
Offline Offline

Posts: 105



« Reply #7 on: March 15, 2010, 02:34:22 PM »

1. Windows Vista Home Premium 32bit, SP2

2. realtime Eset NOD 32 Antivirus v. 4, CIS v. 4 (installed firewall with D+, proactive security, firewall security level: custom, D+ security level: safe pc mode, sandbox enabled)

3. N/A

4 and 5. as soon as I connect my pc to the internet (via lan) I got BSOD with the folloving message: DRIVER_IRQL_NOT_LESS_OR_EQUAL. But whe I connect my PC to the internet via wifi, everything is ok. I got the same BSOD with CIS v. 3.14. Please, see minidump attached.

Thanks
Logged
Tags:
Pages: [1] Go Up Print 
« previous next »
Jump to:  

SSL Certificate Free Virus Removal Firewall
Page created in 0.058 seconds with 17 queries.
Powered by SMF 1.1.11 | SMF © 2006, Simple Machines LLC
Seo4Smf v0.2 © Webmaster's Talks
Design by 7dana.com