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

Offline Tir

  • Newbie
  • *
  • Posts: 4
Re: BSODs: Please add your minidump files here
« Reply #45 on: December 19, 2007, 11:15:11 PM »
^ How nice for you, but I have *never* installed anything that's messed up my system so much and given so many BSODs, and the new version did nothing to fix it. To me it feels like an Alpha version. And I can't use the older bug free versions on Vista.

I even made a separate topic about my problems and it still has 0 replies from anyone, so excuse me for not singing praises as highly as you.

Offline NTxLS

  • Comodo Loves me
  • ****
  • Posts: 141
Re: BSODs: Please add your minidump files here
« Reply #46 on: December 20, 2007, 09:20:59 PM »
^ How nice for you, but I have *never* installed anything that's messed up my system so much and given so many BSODs, and the new version did nothing to fix it. To me it feels like an Alpha version. And I can't use the older bug free versions on Vista.

I even made a separate topic about my problems and it still has 0 replies from anyone, so excuse me for not singing praises as highly as you.

Tir,

Excuse me for singing, not a very good one at that, the praises about this FireWall, but; this is the first program that I have had a problem, major at that, and had it fixed so completely.  Any information will help in getting any problem solved.  You would not believe the extent of searchings I had to do to find any help for them to work on that problem.  My system, and that is mostly because I am a NEWB and do not really understand much about XP, would not give any crash dumps or MiniDump files or I just could not find any even with guidance from all of the HELPers on here.  As you can tell from my LONGWINDED messages here I do not know what I am doing.  They were able to extract enough information from my ramblings to do a very fine job.  Too much information is not a problem, too little and they do not know where to work.

Give as many details and what you were doing when the problems occur.  Sharing more than enough information is better than just saying a very simple complaint.  Give the information as though you are explaining to someone that has not a clue as to what you are doing or why.

Now for my latest question: Why is COMODO giving the version as 3.0.14.276?  When all that BelArc can do is use the version numbers in 'cfp.exe,' 'cfpconfig.exe,' & 'cmdagent.exe' and each one is different.  Note as follows:

COMODO Firewall Pro Version 1.0.0.1 *
COMODO Firewall Pro Version 3.0.9.220 *
Comodo Firewall Version 2.4.0.0 *

A copy/paste from BelArc Adivsor in the same order as mentioned above.  Note also my sig for the latest versions of my installs.

I await your return,
« Last Edit: December 20, 2007, 09:24:38 PM by NTxLS »
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 Phoenix2005

  • Newbie
  • *
  • Posts: 3
Re: BSODs: Please add your minidump files here
« Reply #47 on: December 21, 2007, 06:09:58 AM »
Olldbg1.10 Plugin PhantOm 1.20 

--------------------------------------------------------------------------------
 Mini112407-01.rar (16.45 KB - downloaded 2 times.)
 
 

This piece complete Guard32.dll Ring3 Hook control, lead to the fact OperationKeServiceDescriptorTable ble appear when can solve issue of BSOD ?

Offline rbeyl

  • Newbie
  • *
  • Posts: 1
Re: BSODs: Please add your minidump files here
« Reply #48 on: December 21, 2007, 10:57:14 AM »
I am having the same issue.  I am running Vista Ultimate and cannot even get connected to my network, local or internet.  I cannot find any uninstall information in the Add/Remove Programs applet either.  I can find the program folder but none of the application files will do anything if you try to load them manually. 

Please help in trying to figure this out.  The only option I am going to have is to restore my computer from a clean install.  System restore is not working, when it is tried it BSOD with the same information.  Each time the stop error comes up it has a related file of ndisuio.sys.  Found on some searches that htis file is for NDIS User I/O.  It is used for wi-fi ability and is a valid Windows System file.

Offline MLReynolds

  • Newbie
  • *
  • Posts: 17
Re: BSODs: Please add your minidump files here
« Reply #49 on: December 22, 2007, 01:09:50 AM »
Gibran,

Does the following satisfy your required information?

OS
MS Windows XP
32 bit
Home Edition
Version 2002
Service Pack 2
All MS security updates are kept current

Anti-virus
Avast
Version 4.7 Home Edition
VPS files are kept current

Other Security Apps
Comodo Firewall (V2 currently)
Comodo BOClean (Check for update several times a week)

Spyware Terminator
Version 2.0.1.224
Definition files kept current
Real-time protection enabled
HIPS active
Note: These Spyware Terminator services were disabled during installation of Comodo v3, and remained disabled while Defense+ was active.

Misc Security Software

Spybot - Search & Destroy 1.3
Tea Time Not Active

Ad-Aware SE Personal, Build 1.06r1
(free version)

SuperAntiSpyware (free version), Version 3, 9, 0, 1008

Note: One or more of these three are used for a system scan (after ensuring the definition files are current) after performing a system scan by Spyware Terminator.

About the Gmer report - It isn't clear to me which report is required. It appears as though there are several that can be created. I'm sure I could provide one, just let me know what you require.

Memory Dump File is attached.

Again; problem occurred only when ejecting a CD-RW with data on it. An empty CD and a store bought music CD could be ejected without incident. Comodo was in learning Safe mode.

[attachment deleted by admin]
« Last Edit: December 22, 2007, 05:56:26 AM by MLReynolds »

Offline NTxLS

  • Comodo Loves me
  • ****
  • Posts: 141
Re: BSODs: Please add your minidump files here
« Reply #50 on: December 27, 2007, 04:50:49 PM »
I just came across this site that reads minidumps for us  ;D
http://www.zacksdomain.com/?page=tools&t=bugcheck

Wicked!


Ron_75,

Are you having any luck going to ZacksDomain dot com that you have given as a website that reads minidumps?  I have been trying to access it for a couple of days with failures with timeouts.

I await your return,
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 alexutd

  • Newbie
  • *
  • Posts: 1
Re: BSODs: Please add your minidump files here
« Reply #51 on: December 29, 2007, 07:34:56 AM »
System: Vista32, DrWeb 4.44

BSOD during installation of CFP_Setup_3.0.14.276_XP_Vista_x32.exe.
Installed succesfully in safe mode, upon restat  - inevitable BSODs during startup.
Uninstalled in safe mode, no BSODs after that.

Minidump is attached.

Minidump details (from WinDbg):

FAULTING_IP:
ndisuio!NdisuioReceiveNetBufferLists+82
ceb3cf7c 8b4e14           mov     ecx,[esi+0x14]

EXCEPTION_RECORD:  dde599e0 -- (.exr ffffffffdde599e0)
ExceptionAddress: ceb3cf7c (ndisuio!NdisuioReceiveNetBufferLists+0x00000082)
   ExceptionCode: c0000005 (Access violation)
  ExceptionFlags: 00000000
NumberParameters: 2
   Parameter[0]: 00000000
   Parameter[1]: 00000014
Attempt to read from address 00000014

STACK_TEXT: 
dde59ad4 c89980b0 c37b5638 c270c4d8 00000000 ndisuio!NdisuioReceiveNetBufferLists+0x82
dde59b08 c898ad7d 007c0650 c270c4d8 00000000 ndis!ndisMIndicateNetBufferListsToOpen+0xab
dde59b38 c898a822 00000001 c37c0650 00000001 ndis!ndisIndicateAllNetBufferLists+0x56
dde59cb8 c88d251e c295b488 00000000 00000000 ndis!ndisMDispatchReceiveNetBufferLists+0x132
dde59cd4 c899d2c4 c295b488 c270c4d8 00000000 ndis!ndisMTopReceiveNetBufferLists+0x24
dde59d20 ccc22a98 0095b488 dde59d50 00000001 ndis!ndisMIndicatePacketsToNetBufferLists+0xe9
WARNING: Stack unwind information not available. Following frames may be wrong.
dde59d48 ccc295d6 c377c058 00000000 c5ad89e0 inspect+0x2a98
dde59d60 ccc2a360 c64dd9c8 00000000 c3771d78 inspect+0x95d6
dde59d7c e21afbad 00000000 dde52680 00000000 inspect+0xa360
dde59dc0 e209a346 ccc2a2fc 00000000 00000000 nt!PspSystemThreadStartup+0x9d
00000000 00000000 00000000 00000000 00000000 nt!KiThreadStartup+0x16


[attachment deleted by admin]

Offline Ron_75

  • Comodo's Hero
  • *****
  • Posts: 322
Re: BSODs: Please add your minidump files here
« Reply #52 on: December 29, 2007, 08:06:53 AM »
Ron_75,

Are you having any luck going to ZacksDomain dot com that you have given as a website that reads minidumps?  I have been trying to access it for a couple of days with failures with timeouts.

I await your return,


Hi NTxLS, I just came across your post,

I just tried that link, aint been back to it since that day i wanted to read a couple of minidump files to see what they said in english lol.

anyway saw your post so i just tried the site, it won't load anymore :S and with firefox it gives a timeout. looks like the site is down  :-\ no idea if its permanently down, I will have a look around and see if I can find another site like it that anyone can upload their minidump files too and it converts it into readable text
-------------------------------------------------------------------------------------------
I tried having a look to see if there is any other site like it, but I can't find any  :-\
« Last Edit: December 29, 2007, 08:24:26 AM by Ron_75 »

Offline frazzled

  • Comodo Member
  • **
  • Posts: 48
Re: BSODs: Please add your minidump files here
« Reply #53 on: December 30, 2007, 03:28:32 AM »
Upon installing the latest version on WindowsXP, everything seemed fine ~~ I checked the various features/tabs of the app, created a local trusted network... and as soon as I launched Internet Explorer and responded "allow" to the popup (Comodo firewall was set to Custom/AlwaysAsk mode), got a BSOD stating

A device driver attempting to corrupt the system has been caught...
inspect.sys
memory address BA4714D0 base BA463000

After 8 repeated restarts, the PC would not boot to windows ~~ it stopped at the blank WinXP "Welcome" startup screen each time, with no visible hard drive activity. I was forced boot to SafeMode and uninstall the Comodo Firewall to in order to resolve the problem.

Free? Time-wise, it's been a pretty damn expensive trial. I wasted several weeks this past spring dealing with Comodo Firewall bugs and visiting the forum to carefully detail each one in a post, or in tickets to support staff. I'm loathe to repeat that ordeal and intend to avoid future versions.

Offline NTxLS

  • Comodo Loves me
  • ****
  • Posts: 141
Re: BSODs: Please add your minidump files here
« Reply #54 on: December 30, 2007, 01:47:19 PM »
Hi NTxLS, I just came across your post,

I just tried that link, aint been back to it since that day i wanted to read a couple of minidump files to see what they said in english lol.

-------------------------------------------------------------------------------------------
I tried having a look to see if there is any other site like it, but I can't find any  :-\

Ron_75,

Thank you, was a little concerned because I could not get there, just needed that re-assurance.   I will just wait a little and try again.  With the problems I have been having with this one, there is a little bit of a problem with confidence in my system.  Still chasing the BSOD problems and they seem to be not involving CFP.  They are erratic not consistent with any operations that I can identify.

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 Ron_75

  • Comodo's Hero
  • *****
  • Posts: 322
Re: BSODs: Please add your minidump files here
« Reply #55 on: December 31, 2007, 06:32:21 AM »
thats alright NTxLS, I know how you feel :-\ when I first installed CFP 3.0.13.268 then 3.0.14.273, my computer would keep having eratic behaviours, sometimes it would load up fine, but more often it would crash or freeze and sometimes BSOD, i was frustrated as hell with it and not knowing why it was being like that until i installed CFP 3, so i was utterly dismayed and regarded it as CFP 3's fault.

An admin called egemen on here got me to post a minidump file he checked the minidump file out and said one of the programs i had that loads during startup called Folder XP 3.6 the dump file said its *.sys was the cause of the crash.

I wanted to check it out myself so i came across that bugcheck online site and uploaded a couple of my dump files and that site straight away debugged it automatically and outputted the results in english saying Folder XP 3.6 caused each crash.  i had some insight then as to what to do. i uninstalled that program and found 1 better and my problems went away straight away :)

I have tried looking for an alternative bug check site, but seems that was the only 1. using a debug tool for most of us isn't simple so a site that does it is real good. I've come across this post in this site, seems this guy is the author of that debug script tool. it looks like his server is down, one can only hope that his site comes back on or he finds another one and puts that tool he made on it, otherwise ugh!  https://www.techspot.com/vb/topic40865.html

Offline NTxLS

  • Comodo Loves me
  • ****
  • Posts: 141
Re: BSODs: Please add your minidump files here
« Reply #56 on: January 01, 2008, 12:11:09 PM »
thats alright NTxLS, I know how you feel :-\ when I first installed CFP 3.0.13.268 then 3.0.14.273, my computer would keep having eratic behaviours, sometimes it would load up fine, but more often it would crash or freeze and sometimes BSOD, i was frustrated as hell with it and not knowing why it was being like that until i installed CFP 3, so i was utterly dismayed and regarded it as CFP 3's fault.

An admin called egemen on here got me to post a minidump file he checked the minidump file out and said one of the programs i had that loads during startup called Folder XP 3.6 the dump file said its *.sys was the cause of the crash.

I wanted to check it out myself so i came across that bugcheck online site and uploaded a couple of my dump files and that site straight away debugged it automatically and outputted the results in english saying Folder XP 3.6 caused each crash.  i had some insight then as to what to do. i uninstalled that program and found 1 better and my problems went away straight away :)

I have tried looking for an alternative bug check site, but seems that was the only 1. using a debug tool for most of us isn't simple so a site that does it is real good. I've come across this post in this site, seems this guy is the author of that debug script tool. it looks like his server is down, one can only hope that his site comes back on or he finds another one and puts that tool he made on it, otherwise ugh!  https://www.techspot.com/vb/topic40865.html
Ron_75,

My FF just gave a waring about the sites certificate expired 12/1/2005 and it is given as a different website as owner. 
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 rloyed

  • Newbie
  • *
  • Posts: 5
Re: BSODs: Please add your minidump files here
« Reply #57 on: January 01, 2008, 01:17:31 PM »
I think i posted my .dmp file in the wrong place,sorry guys.I made the post in bug reports and not in here.Im adding my .dmp files here for ya to check out and copy/pasting my previous posts.And ill go back to my last post and delete it.
**Okay,i tried to delete the last post in bug reports and it told me i couldnt.So this post is on the forums 2 times.

MY ORIGINAL POST FOLLOWS AS BELOW::
I have the m2n32-sli deluxe wireless MBoard with the realtek rtl8187 wireless 802.11g 54 Mbps usb 2.0 network adaptor,with the wireless able to run in windows zero config or in the MBoard supplied ASUS WIFI-AP SOLO(which takes control of the windows zero config).
I have tried different versions of the wireless network adaptor drivers with different versions of comodo firewall and everything i have tried has resulted in a bluescreen error and shut down of my pc during the wireless detection and enable process after doing a fresh install.
I also get the bluescreen when the wireless is being initialized after i have it all installed.
If i install comodo firewall on a fresh system it installs fine and works great,right up to the time my wireless kicks in and starts,then its bluescreen again.
If i install my wireless and get it all setup and working on a fresh install then install comodo firewall i get a bluescreen and shut down during the kernal install of comodo firewall.the last 3 versions of comodo were tested along with the latest version.
I have installed The comodo software on my system with windows xp pro x64 and x86,windows xp home x86 and x64,Vista business edition x86 and vista ultimate x64 and have the same problem on all of the operating systems tested with comodo and my wireless adaptor.I have tinkered with this MBoard and Comodo for 2 weeks or so,installed my apps in different orders after doing fresh installs,I have installed comodo after getting my windows updates and before doing them as well,before and after other software i use.
The only time i have the bluescreen is when i have comodo installed and working and my wireless adaptor tries to start(initialize) ,or i have my wireless adaptor in and working correctly and then try to install comodo(the BLUESCREEN and shut down ALWAYS occurs during the kernal install).
I can install and run comodo and my wireless and both of them work great,JUST NOT TOGETHER at the same time,and i cant install comodo after i install my wireless adaptor.
My bluescreen error says: IRQL_NOT_LESS_THAN_OR_EQUAL
and tells me to remove any newly install software(which would be comodo or my wireless adaptor),the most common cause of this error is misbehaving drivers.

My System:
ASUS m2n32-sli wireless deluxe mboard
amd 64 athlon x2
2 gig sli ready mem
nvidia geforce 8800 gt alpha dog edition
asus wifi-ap solo wireless
realtek wireless rtl 8187 adaptor
3-320g sata harddrives(not on raid setup)
benq dvd player
liteon dvd burner
verbatim cd burner
hp external dvd/lightscribe burner
epson stylus c84 printer
usb mic
belkin 4 port hub
logitech 5.1 true surround system
usb scanner
belkin nostromo n52 speedpad
netgear rangemax wireless router
Microsoft windows xp pro x64
service pack2
I have symantec antivirus 10.1.7.7000 as antivirus software(and have installed comodo with and without symantec AV installed)

I didnt install in safe mode.
Didnt matter what i did or how i did it,Comodo firewall will not run on my pc at any time if i use my built in wireless adaptor to connect at the same time comodo is running or installed.Comodo will run on my system if i disable my wireless adaptor and dont use it.


Quote from: AnotherOne on December 30, 2007, 06:11:33 PM
Hi rloyed - Do any of your drives use an eSATA interface?  That appears to be a bug that has not yet been fixed yet.  Since you actually had a Blue Screen, you should have a .dmp file with the details of the crash.  It would be valuable if you could post your last message in the bug reports thread:
http://forums.comodo.com/bug_reports-b106.0/
and attach your .dmp file (Assuming that you have logging on) in a zipped format to the post.



MY LAST POST BEFORE GETTING THE .DMP FILE FOR YA.:::
I havent got any esata connected drives..
I use acronis for easy restore feature to a fresh installed image when i get my tinkering done,if the log file will be of any help i can restore back and reinstall comodo to get the .dmp file for ya and then post it.ill restore tomorrow after work and get it posted..
As far as firewalls go in windows xp x64 there arent very many of them that allow total user control over what apps connect to the internet(im sure there are some of us out there that dont want certain apps to connect to the internet!!),and outpost is the one with the best features and controls until i can get my comodo back in and working right..This outpost firewall im using is a result of several weeks of testing various firewalls and coming to the realization that comodo wasnt gonna work right now,so it is a temporary thing for me.
Symantec Endpoint Protection provided good protection but the firewall doesnt work right in x64 windows xp,and i couldnt connect thru the wireless until i disabled the firewall.For some reason they built the software for administrators systems and it doesnt have CLIENT protection and configurability any more..
I did use the ghost firewall for a minute and took it out when i couldnt figure individual program access.
Zone alarm is 1 that i didnt test this time around,i did some beta testing on it some yrs back and didnt like it so i havent put it back in.
This outpost is okay for now,give it a fair shake b4 you guys condemn it altogether,at least it works with everything and has some good features..It is good for a TEMPORARY fix till we get comodo working even if i cant update it. 
Kaspersky wasnt too bad,nod32 was good but you have to pay a yearly price,and symantec client security doesnt support x64 systems..
You shouldnt go out and buy a firewall right now or pay for a subscription to 1.Im sure Comodo will be fixed very soon to work with our hardware.I know the people at comodo are working on it and i am tinkering with it at home and doing a lot of reading.Hopefully it will help when i get my logfile to them and they will know where we need to start working to get it fixed.
I have tried the install with defense+ and without it as well.
 


[attachment deleted by admin]
« Last Edit: January 01, 2008, 02:03:55 PM by rloyed »
FLOORMAN1

Offline Llordus

  • Newbie
  • *
  • Posts: 4
Re: BSODs: Please add your minidump files here
« Reply #58 on: January 05, 2008, 11:40:09 AM »
Hi,
this is an archive with few of my minidumps.
Problem and way to reproduce it is detailed in this thread:
http://forums.comodo.com/help_for_v3/avast_comodo_firewall_bsod-t17965.0.html

My system configuration:
Lenovo 3000 n100, with Core2Duo T5300, 2x1GB RAM, GF Go 7300, 120GB HDD, Windows Vista Home Premium 32 with some updates but without SP1 RC.

Antivirus: Avast Home Edition 4.7, compilation 4.7.1098, with Extreme toolkit 1.9.4.0
Firewall: Comodo Firewall Professional, versioni 3.0.14.276








[attachment deleted by admin]

Offline cjberg

  • Newbie
  • *
  • Posts: 1
Re: BSODs: Please add your minidump files here
« Reply #59 on: January 07, 2008, 04:57:56 AM »
Hi,

I've experienced a BSOD caused Comodo Firewall 3.0.14.276 today. I have included the following information:

  • A brief description of the system and relevant applications
  • Attached minidump
  • The "!analyze -v" output from WinDBG (Windows symbol support is enabled, but I don't have any symbols for Comodo itself)

Hope it helps!

// C-J Berg


=== System ===

Windows System: Microsoft Windows Vista Ultimate (with all public hotfixes available to date)
Platform Compliance: Win64 x64

No anti-virus product has yet been installed on this system.
VMware Workstation 6.0.2 is installed.

System: LENOVO 6457-7XG
Processor Model: Intel(R) Core(TM)2 Duo CPU T7800  [at] 2.60GHz
Bus(es): PCI PCIe IMB PCMCIA CardBus USB FireWire/1394 i2c/SMBus
Total Memory: 4 GB DDR2

Network Adapters:
Intel(R) 82566MM Gigabit Network Connection
Intel(R) Wireless WiFi Link 4965AGN


A thourough system description can be found here:
http://www-307.ibm.com/pc/support/site.wss/quickPath.do?quickPathEntry=64577XG


=== WinDBG ===

BAD_POOL_CALLER (c2)
The current thread is making a bad pool request.  Typically this is at a bad IRQL level or double freeing the same allocation, etc.
Arguments:
Arg1: 0000000000000007, Attempt to free pool which was already freed
Arg2: 000000000000113d, (reserved)
Arg3: 0000000004380000, Memory contents of the pool block
Arg4: fffffa8008b48010, Address of the block of pool being deallocated

Debugging Details:
------------------

POOL_ADDRESS:  fffffa8008b48010

FREED_POOL_TAG:  aPmI

BUGCHECK_STR:  0xc2_7_aPmI

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

PROCESS_NAME:  System

CURRENT_IRQL:  0

LAST_CONTROL_TRANSFER:  from fffff80001d3c475 to fffff80001c4dc90

STACK_TEXT: 
fffff980`00e22158 fffff800`01d3c475: 00000000`000000c2 00000000`00000007 00000000`0000113d 00000000`04380000: nt!KeBugCheckEx
fffff980`00e22160 fffff980`00864011: fffff980`008a2110 fffff980`008a2110 fffff800`01d69200 fffff980`6370444e: nt!ExDeferredFreePool+0x9ca
fffff980`00e22220 fffff980`055eaf49: fffff980`055fa320 00000000`00000000 fffffa80`06cc0b28 fffffa80`0000002e: ndis!NdisFreeMemory+0x11
fffff980`00e22250 fffff980`055fa320: 00000000`00000000 fffffa80`06cc0b28 fffffa80`0000002e fffff980`055fa320: inspect+0x1f49
fffff980`00e22258 00000000`00000000: fffffa80`06cc0b28 fffffa80`0000002e fffff980`055fa320 fffff800`00000002: inspect+0x11320
fffff980`00e22260 fffffa80`06cc0b28: fffffa80`0000002e fffff980`055fa320 fffff800`00000002 fffffa80`06f47d00: 0x0
fffff980`00e22268 fffffa80`0000002e: fffff980`055fa320 fffff800`00000002 fffffa80`06f47d00 fffffa80`08b48010: 0xfffffa80`06cc0b28
fffff980`00e22270 fffff980`055fa320: fffff800`00000002 fffffa80`06f47d00 fffffa80`08b48010 fffffa80`06cc0b28: 0xfffffa80`0000002e
fffff980`00e22278 fffff800`00000002: fffffa80`06f47d00 fffffa80`08b48010 fffffa80`06cc0b28 00000000`00000000: inspect+0x11320
fffff980`00e22280 fffffa80`06f47d00: fffffa80`08b48010 fffffa80`06cc0b28 00000000`00000000 00000000`00000000: 0xfffff800`00000002
fffff980`00e22288 fffffa80`08b48010: fffffa80`06cc0b28 00000000`00000000 00000000`00000000 fffff800`01eb54b1: 0xfffffa80`06f47d00
fffff980`00e22290 fffffa80`06cc0b28: 00000000`00000000 00000000`00000000 fffff800`01eb54b1 fffffa80`08b48010: 0xfffffa80`08b48010
fffff980`00e22298 00000000`00000000: 00000000`00000000 fffff800`01eb54b1 fffffa80`08b48010 fffffa80`045610e8: 0xfffffa80`06cc0b28
fffff980`00e222a0 00000000`00000000: fffff800`01eb54b1 fffffa80`08b48010 fffffa80`045610e8 fffffa80`05f62010: 0x0
fffff980`00e222a8 fffff800`01eb54b1: fffffa80`08b48010 fffffa80`045610e8 fffffa80`05f62010 fffffa80`00000000: 0x0
fffff980`00e222b0 fffff800`01eb4ead: 00000000`0000121c fffffa80`03bde080 fffffa80`03bbc970 fffff800`01e20990: nt!ObpCloseHandleTableEntry+0x271
fffff980`00e22360 fffffa80`06cac1a0: fffffa80`06f47d20 fffff980`00860203 fffff980`008a2690 fffff980`008a2690: nt!ObpCloseHandle+0x9d
fffff980`00e223b0 fffffa80`06f47d20: fffff980`00860203 fffff980`008a2690 fffff980`008a2690 00000000`00000000: 0xfffffa80`06cac1a0
fffff980`00e223b8 fffff980`00860203: fffff980`008a2690 fffff980`008a2690 00000000`00000000 fffff980`00874eb0: 0xfffffa80`06f47d20
fffff980`00e223c0 fffff980`009c7205: fffffa80`07b7fbf0 fffff800`01c34c83 ffff0000`05bd8763 fffff980`008a2110: ndis!ndisDereferencePackage+0x13
fffff980`00e223f0 fffff980`009d7ec7: fffffa80`06cac1a0 fffffa80`06cac1a0 fffffa80`06cc0b28 00000000`00000801: ndis!ndisProtocolAlreadyBound+0xa5
fffff980`00e22430 fffff980`009d82fc: fffffa80`043f8b80 00000000`00000001 fffff980`c0000001 00000000`00000000: ndis!ndisInitializeBinding+0x2a7
fffff980`00e22550 fffff980`009e0122: fffffa80`043f8b80 00000000`00000000 fffffa80`07b7f010 fffffa80`06c0ac00: ndis!ndisCheckAdapterBindings+0x23c
fffff980`00e22680 fffff980`009e0320: fffff980`008a2110 fffffa80`07b7f010 fffffa80`06c0ace0 fffffa80`06cac1a0: ndis!ndisIMInitializeDeviceInstance+0xc2
fffff980`00e226c0 fffff980`04c0a0e1: 00000000`00000100 00000000`00000001 fffffa80`07b7f068 fffffa80`07b7f068: ndis!NdisIMInitializeDeviceInstanceEx+0x140
fffff980`00e22720 00000000`00000100: 00000000`00000001 fffffa80`07b7f068 fffffa80`07b7f068 fffff980`00000000: VMNetSrv+0x30e1
fffff980`00e22728 00000000`00000001: fffffa80`07b7f068 fffffa80`07b7f068 fffff980`00000000 fffffa80`00000001: 0x100
fffff980`00e22730 fffffa80`07b7f068: fffffa80`07b7f068 fffff980`00000000 fffffa80`00000001 fffffa80`06b9ac00: 0x1
fffff980`00e22738 fffffa80`07b7f068: fffff980`00000000 fffffa80`00000001 fffffa80`06b9ac00 fffffa80`07b7f010: 0xfffffa80`07b7f068
fffff980`00e22740 fffff980`00000000: fffffa80`00000001 fffffa80`06b9ac00 fffffa80`07b7f010 fffffa80`069ee568: 0xfffffa80`07b7f068
fffff980`00e22748 fffffa80`00000001: fffffa80`06b9ac00 fffffa80`07b7f010 fffffa80`069ee568 fffffa80`00000000: WMILIB!WmiCompleteRequest <PERF> (WMILIB+0x0)
fffff980`00e22750 fffffa80`06b9ac00: fffffa80`07b7f010 fffffa80`069ee568 fffffa80`00000000 00000000`00000000: 0xfffffa80`00000001
fffff980`00e22758 fffffa80`07b7f010: fffffa80`069ee568 fffffa80`00000000 00000000`00000000 00000000`2079654b: 0xfffffa80`06b9ac00
fffff980`00e22760 fffffa80`069ee568: fffffa80`00000000 00000000`00000000 00000000`2079654b 00000000`00000000: 0xfffffa80`07b7f010
fffff980`00e22768 fffffa80`00000000: 00000000`00000000 00000000`2079654b 00000000`00000000 fffffa80`05fbfaf0: 0xfffffa80`069ee568
fffff980`00e22770 00000000`00000000: 00000000`2079654b 00000000`00000000 fffffa80`05fbfaf0 fffffa80`07b7f010: 0xfffffa80`00000000
fffff980`00e22778 00000000`2079654b: 00000000`00000000 fffffa80`05fbfaf0 fffffa80`07b7f010 00000000`00000000: 0x0
fffff980`00e22780 00000000`00000000: fffffa80`05fbfaf0 fffffa80`07b7f010 00000000`00000000 00000000`c0000001: 0x2079654b
fffff980`00e22788 fffffa80`05fbfaf0: fffffa80`07b7f010 00000000`00000000 00000000`c0000001 c0000001`c0000001: 0x0
fffff980`00e22790 fffffa80`07b7f010: 00000000`00000000 00000000`c0000001 c0000001`c0000001 fffffa80`04659940: 0xfffffa80`05fbfaf0
fffff980`00e22798 00000000`00000000: 00000000`c0000001 c0000001`c0000001 fffffa80`04659940 00000009`c0000001: 0xfffffa80`07b7f010
fffff980`00e227a0 00000000`c0000001: c0000001`c0000001 fffffa80`04659940 00000009`c0000001 fffffa80`06cae490: 0x0
fffff980`00e227a8 c0000001`c0000001: fffffa80`04659940 00000009`c0000001 fffffa80`06cae490 fffff800`01eb54b1: 0xc0000001
fffff980`00e227b0 fffffa80`04659940: 00000009`c0000001 fffffa80`06cae490 fffff800`01eb54b1 fffffa80`03bbc900: 0xc0000001`c0000001
fffff980`00e227b8 00000009`c0000001: fffffa80`06cae490 fffff800`01eb54b1 fffffa80`03bbc900 fffffa80`07fe6078: 0xfffffa80`04659940
fffff980`00e227c0 fffffa80`06cae490: fffff800`01eb54b1 fffffa80`03bbc900 fffffa80`07fe6078 fffffa80`03be5040: 0x9`c0000001
fffff980`00e227c8 fffff800`01eb54b1: fffffa80`03bbc900 fffffa80`07fe6078 fffffa80`03be5040 fffffa80`03be5040: 0xfffffa80`06cae490
fffff980`00e227d0 00000000`00000000: 00000000`00000000 00000000`00000000 fffff980`04c0d050 00000000`00000000: nt!ObpCloseHandleTableEntry+0x271


STACK_COMMAND:  kb

FOLLOWUP_IP:
inspect+1f49
fffff980`055eaf49 ??              ???

SYMBOL_STACK_INDEX:  3

SYMBOL_NAME:  inspect+1f49

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: inspect

IMAGE_NAME:  inspect.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  475c6c64

FAILURE_BUCKET_ID:  X64_0xc2_7_aPmI_inspect+1f49

BUCKET_ID:  X64_0xc2_7_aPmI_inspect+1f49

Followup: MachineOwner
---------


[attachment deleted by admin]

 

Free Endpoint Protection
Seo4Smf 2.0 © SmfMod.Com Smf Destek