Author Topic: BSODs: Please add your minidump files here [CLOSED]  (Read 165631 times)

Offline gibran

  • Average User
  • Comodo's Hero
  • *****
  • Posts: 5056
  • A bad workman always blames his tools
BSODs: Please add your minidump files here [CLOSED]
« on: November 20, 2007, 12:37:42 PM »
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 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.
« Last Edit: October 29, 2008, 02:16:08 AM by 3xist »
"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 Polish CPF Supporter

  • Newbie
  • *
  • Posts: 10
Re: BSODs: Please add your minidump files here
« Reply #1 on: November 20, 2007, 06:22:15 PM »
I have a big problem with CFP 3. When I run installation process, during kernel install, i'm getting bluescreen and my pc reboots. I turned off any programm that could cause the problem but it didn't help. I didnt habe an other firewall, only avast, spybot and windows defender as realtime scanner( ofcource I turned them off). I managed to install comodo in windows safe mode, but when i boot up my system in normal mode, my system crushes again, Why is that? [!]? I have vista 32 bit. Any idea what's causing the problem?
« Last Edit: November 20, 2007, 07:11:35 PM by Polish CPF Supporter »

Offline landsker

  • Comodo Family Member
  • ***
  • Posts: 62
    • Costa del Sol, Spain
Re: BSODs: Please add your minidump files here
« Reply #2 on: November 21, 2007, 09:56:26 AM »
Probably something I did or didn't enable properly in Defence + set-up.
I have just created a CD with .jpg images on it and when attempting to eject the disc, either manually or electronically, I get the BSOD & restart.
If I disable Defence Plus this does not happen,
(XP Home).
Advice?
« Last Edit: November 22, 2007, 06:22:48 PM by jasper2408 »

Offline egemen

  • Comodo Staff
  • Comodo's Hero
  • *****
  • Posts: 3321
Re: BSODs: Please add your minidump files here
« Reply #3 on: November 21, 2007, 01:51:42 PM »
I have a big problem with CFP 3. When I run installation process, during kernel install, i'm getting bluescreen and my pc reboots. I turned off any programm that could cause the problem but it didn't help. I didnt habe an other firewall, only avast, spybot and windows defender as realtime scanner( ofcource I turned them off). I managed to install comodo in windows safe mode, but when i boot up my system in normal mode, my system crushes again, Why is that? [!]? I have vista 32 bit. Any idea what's causing the problem?

Hello There,

It seems Microsoft Wireless Zero Configuration driver is causing a BSOD in this computer. We will be analyzing the memory dumps in detail to make sure CFP does not trigger such a bug.

Can you tell me about your Computer's Ethernet and Wireless Card manifacturer and versions?

Thanks,
Egemen

Offline gibran

  • Average User
  • Comodo's Hero
  • *****
  • Posts: 5056
  • A bad workman always blames his tools
Re: BSODs: Please add your minidump files here
« Reply #4 on: November 21, 2007, 03:45:00 PM »
I have a P4 HT, My system internet browser is Firefox, OS: XP sp2 32bit, Other Security Apps: Comodo Memory Guardian 1.6b
I was currently testing a fuzzer related issue so I uninstalled Avast and Daemon Tools 4.10 X86
At the time I was browsing this forum and I opened the Log From CFP GUI.

Regards,
gibran

"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 Polish CPF Supporter

  • Newbie
  • *
  • Posts: 10
Re: BSODs: Please add your minidump files here
« Reply #5 on: November 21, 2007, 05:13:30 PM »
Hello There,

It seems Microsoft Wireless Zero Configuration driver is causing a BSOD in this computer. We will be analyzing the memory dumps in detail to make sure CFP does not trigger such a bug.

Can you tell me about your Computer's Ethernet and Wireless Card manifacturer and versions?

Thanks,
Egemen
Hi. So my wifi is causing bsod? I have ralink rt2400, and as i can remember, in alpha version of comodo 3 I havent this kind of crushes. Thanks for help. I hope that soon I will have working CFP3 on my pc.

Offline egemen

  • Comodo Staff
  • Comodo's Hero
  • *****
  • Posts: 3321
Re: BSODs: Please add your minidump files here
« Reply #6 on: November 22, 2007, 09:34:18 PM »
I have a P4 HT, My system internet browser is Firefox, OS: XP sp2 32bit, Other Security Apps: Comodo Memory Guardian 1.6b
I was currently testing a fuzzer related issue so I uninstalled Avast and Daemon Tools 4.10 X86
At the time I was browsing this forum and I opened the Log From CFP GUI.

Regards,
gibran



Hi,

This dump shows memory guardian's driver caused the crash.  What do you mean by fuzzer related issue? You were running some testing tool?

Egemen

Offline gibran

  • Average User
  • Comodo's Hero
  • *****
  • Posts: 5056
  • A bad workman always blames his tools
Re: BSODs: Please add your minidump files here
« Reply #7 on: November 23, 2007, 02:37:18 AM »
Hi,

This dump shows memory guardian's driver caused the crash.  What do you mean by fuzzer related issue? You were running some testing tool?

Egemen

I guess I posted in the wrong board  :P. I used bsodhook. I asked some Mod to test this too but usually I got NO BSOD but my system becomes unresposive (apps fails to load, system cannot be shutdown but mouse and onscreen apps seems ok). I'm not really capable to comment about such tests but one thing that worths mention, I think, is that only CPF hooked functions are tested. If you have any suggestion to use that tool properly please tell me.
"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 b19387

  • Newbie
  • *
  • Posts: 1
Re: BSODs: Please add your minidump files here
« Reply #8 on: November 23, 2007, 01:43:09 PM »
I tried to install Comodo Personal Firewall 3. Before installation is finished I get a Bluescreen.
I can start Vista in Protected Mode with Network and then start Comodo Personal Firewall -> No Bluescreen.
But when I reboot Vista in Normal Mode I get the Blue Screen again.
Currently I have deinstalled Comodo Personal Firewall 3 and reinstalled Zonealarm.

Windows Version/Bit and Service Packs = Vista/32, all Vista Updates are installed.
Avira Antivir Personal Edition Class - Product Version 7.06.00.270. Updated today
WinPatrol v12.2.2007.0
Sandboxie 3.20.01

See attachments (Minidump and Everest Hardware Report).

Any idea what could have casued the crash? Thanks for your support.

Offline pandlouk

  • I love Comodo
  • Comodo's Hero
  • *****
  • Posts: 2240
  • Retired Mod
Re: BSODs: Please add your minidump files here
« Reply #9 on: November 24, 2007, 11:46:08 AM »
Conflict of cmdguard.sys and nx6000.sys

Probably the same problem with the one reported here http://forums.comodo.com/comodo_memory_guardian_beta_corner/bsod_with_the_drivers_of_vx7000_webcam-t15466.0.html

But this time caused by the sandbox driver of CFP. Fresh BSOD and fresh minidump. (:AGY)  (:AGY)  (:AGY)

Panagiotis

Offline egemen

  • Comodo Staff
  • Comodo's Hero
  • *****
  • Posts: 3321
Re: BSODs: Please add your minidump files here
« Reply #10 on: November 24, 2007, 02:59:27 PM »
These seems to be a conflict with nx6000.sys. But all of these crashes show that nx6000.sys is producing the BSOD. Not CFP Sandbox Driver.

"Deactivating Defense+" should fix the issue temporarily.

Egemen

Offline pandlouk

  • I love Comodo
  • Comodo's Hero
  • *****
  • Posts: 2240
  • Retired Mod
Re: BSODs: Please add your minidump files here
« Reply #11 on: November 24, 2007, 05:22:43 PM »
These seems to be a conflict with nx6000.sys. But all of these crashes show that nx6000.sys is producing the BSOD. Not CFP Sandbox Driver.

"Deactivating Defense+" should fix the issue temporarily.

Egemen
Thanks egemen,

I have Defence+ disabled (not totally deactivated) and it's ok. Can it be that is not the driver itself that conflicts, but somewhere else in the code?

Offline Phoenix2005

  • Newbie
  • *
  • Posts: 3
Re: BSODs: Please add your minidump files here
« Reply #12 on: November 25, 2007, 08:50:13 AM »
Olldbg1.10 Plugin PhantOm 1.20

Offline NTxLS

  • Comodo Loves me
  • ****
  • Posts: 141
Re: BSODs: Please add your minidump files here
« Reply #13 on: November 29, 2007, 08:30:33 PM »
"Gibran,"

The information you have provided in the following link has been very helpful to me:

https://forums.comodo.com/index.php?action=post;quote=104336;topic=14909.0;num_replies=12;sesc=f83c76e638dba07fdc4c3a3dcb773f21

maybe should be displayed in a more accessable area like "Help for v3" as well as here in the Roach (bug) area.  As a Newby and not really knowing much about this software or even my system, yet, I stay away from these areas where more important work is conducted.  I missed this message of yours until "AOwL" sent me here.

Also discovered my system is setup correctly as far as where the "Minidump" folder is supposed to be, and it is, but; my system is saving those files, "Memory.dmp," in my Windows folder.

Just checked with a EditPadLite and found that file to be MT (empty).  Now I will make all necessary attempts to fulfill your requirements for reporting my problem.  I will be OFF here for awhile while I attempt to complete that task or take a shot at it.

Thank you for reading my Poster toastie,
 
TIA, CU L8R,
NTxLS Dell Inspiron AMD Athlon x2 64 bit Dual Core Processor 2.3GigHz, 4Gig RAM; 64Bit Win7; IE8.0; FF3.6.3/w PassWordMaker1.7.2.

Offline NTxLS

  • Comodo Loves me
  • ****
  • Posts: 141
Re: BSODs: Please add your minidump files here
« Reply #14 on: December 03, 2007, 05:54:35 PM »
Greetings from LeonSprings, Texas USofA,

I have only one MiniDump file and that is included here.  Plus my copy of CFP is popping up a bunch of Notices of attempts to modify some files that are not being used nor should not even be on my system, some are in a ZIP format and are in storage.

Here is my report:

In addition to the "Tech Info" I also followed the instructions to clear all 'Cache and Shadow' settings in the BIOS.

Was collecting the data for the following report for you.  When the GMER was run to collect that data my system crashed with the BSOD.  All data collected was lost, new "Technical Information:" was displayed on screen and is as follows:

***STOP:0x0000000F4, (0x00000003,0x81E74DA0,0x81E74F14,0x805FA160)

The above crash did produce a minidump file and it is included as attachment.

Previous three crashes did not produce any MiniDump files.  The "Tecnical Information:" for all three is as follows:

***STOP:0x000000050, (0xBAD0V154,0x00000000,0x8058188F,0x00000000)


* Windows Version/Bit and Service Packs>XP Home Edition v5.1 32bit (2600.xpsp_sp2_gdr.070227-2254 Service Pack 2)
* Your realtime Antivirus/version,Spyware remover/Version, other Security Software/Version>Avira AntiVir v7.0x, SpyBot Search & Destroy/w TeaTimer v1.5.1.15, HiJackThis v1.99.1, Windows Defender by Microsoft Eng/v1.1.3007.0 Sig v1.23.4310.0
* Affected Driver/Software and Version (if the bug doesn't affect window itself)>? Unknown.
* Brief description of the problem (Attach Diagnostic report or crash dumps if needed)
* Steps to reproduce the bug (if applicable)> Use my computer, last crash occurred when looking at GMER reports to maybe included some info.  Will NOT run GMER again until you tell me to do same.
* Gmer report (download) Only for 32bit platforms>Running this program to attempt to extract more info is when last crash occurred.

My sig also contains my installed O/S and more,
TIA, CU L8R,
NTxLS Dell Inspiron AMD Athlon x2 64 bit Dual Core Processor 2.3GigHz, 4Gig RAM; 64Bit Win7; IE8.0; FF3.6.3/w PassWordMaker1.7.2.

 

Seo4Smf 2.0 © SmfMod.Com | Smf Destek