Results 1 to 1 of 1
  1. #1
    Elite Member boyq's Avatar
    Join Date
    Apr 2008
    Gender
    Male
    Posts
    1,367

    Default BSOD due to faulty firewall driver


    Hi.

    I keep on having BSOD lately. The same error code. As stated by the dump analysis, it's related to Comodo Internet Security Driver.
    Anyone here who experienced the same? My Comodo Internet Security is already updated. I have searched for similar problems but I didn't find any. Should I just re-install CIS? But I would appreciate your inputs regarding this one..


    I'm using Whocrashed (Home Edition) v3.06
    Here's the log:

    System Information (local)
    --------------------------------------------------------------------------------

    computer name: xxxx-PC
    windows version: Windows 7 Service Pack 1, 6.1, build: 7601
    windows dir: C:\Windows
    CPU: AuthenticAMD AMD Phenom(tm) II X2 555 Processor AMD586, level: 16
    2 logical processors, active mask: 3
    RAM: 1878253568 total
    VM: 2147352576, free: 1958379520

    --------------------------------------------------------------------------------
    Crash Dump Analysis:
    Code:
    On Sun 12/30/2012 12:29:20 PM GMT your computer crashed
    crash dump file: C:\Windows\Minidump\123012-14133-01.dmp
    This was probably caused by the following module: inspect.sys (inspect+0x1D45) 
    Bugcheck code: 0x4E (0x7, 0x52C81, 0x1, 0x0)
    Error: PFN_LIST_CORRUPT
    file path: C:\Windows\system32\drivers\inspect.sys
    product: COMODO Internet Security Firewall Driver
    company: COMODO
    description: COMODO Internet Security Firewall Driver
    Bug check description: This indicates that the page frame number (PFN) list is corrupted.
    This appears to be a typical software driver bug and is not likely to be caused by a hardware problem. This might be a case of memory corruption. More often memory corruption happens because of software errors in buggy drivers, not because of faulty RAM modules. 
    A third party driver was identified as the probable root cause of this system error. It is suggested you look for an update for the following driver: inspect.sys (COMODO Internet Security Firewall Driver, COMODO). 
    Google query: inspect.sys COMODO PFN_LIST_CORRUPT
    
    
    
    
    On Sun 12/30/2012 12:29:20 PM GMT your computer crashed
    crash dump file: C:\Windows\memory.dmp
    This was probably caused by the following module: inspect.sys (inspect+0x1D45) 
    Bugcheck code: 0x4E (0x7, 0x52C81, 0x1, 0x0)
    Error: PFN_LIST_CORRUPT
    file path: C:\Windows\system32\drivers\inspect.sys
    product: COMODO Internet Security Firewall Driver
    company: COMODO
    description: COMODO Internet Security Firewall Driver
    Bug check description: This indicates that the page frame number (PFN) list is corrupted.
    This appears to be a typical software driver bug and is not likely to be caused by a hardware problem. This might be a case of memory corruption. More often memory corruption happens because of software errors in buggy drivers, not because of faulty RAM modules. 
    A third party driver was identified as the probable root cause of this system error. It is suggested you look for an update for the following driver: inspect.sys (COMODO Internet Security Firewall Driver, COMODO). 
    Google query: inspect.sys COMODO PFN_LIST_CORRUPT
    
    
    
    
    On Sat 12/29/2012 9:13:06 AM GMT your computer crashed
    crash dump file: C:\Windows\Minidump\122912-21840-01.dmp
    This was probably caused by the following module: inspect.sys (inspect+0x1D45) 
    Bugcheck code: 0x4E (0x7, 0x245B1, 0x1, 0x0)
    Error: PFN_LIST_CORRUPT
    file path: C:\Windows\system32\drivers\inspect.sys
    product: COMODO Internet Security Firewall Driver
    company: COMODO
    description: COMODO Internet Security Firewall Driver
    Bug check description: This indicates that the page frame number (PFN) list is corrupted.
    This appears to be a typical software driver bug and is not likely to be caused by a hardware problem. This might be a case of memory corruption. More often memory corruption happens because of software errors in buggy drivers, not because of faulty RAM modules. 
    A third party driver was identified as the probable root cause of this system error. It is suggested you look for an update for the following driver: inspect.sys (COMODO Internet Security Firewall Driver, COMODO). 
    Google query: inspect.sys COMODO PFN_LIST_CORRUPT
    
    
    
    
    On Mon 12/17/2012 12:01:41 PM GMT your computer crashed
    crash dump file: C:\Windows\Minidump\121712-16972-01.dmp
    This was probably caused by the following module: inspect.sys (inspect+0x1D45) 
    Bugcheck code: 0x44 (0xFFFFFFFF88731490, 0xEAE, 0x0, 0x0)
    Error: MULTIPLE_IRP_COMPLETE_REQUESTS
    file path: C:\Windows\system32\drivers\inspect.sys
    product: COMODO Internet Security Firewall Driver
    company: COMODO
    description: COMODO Internet Security Firewall Driver
    Bug check description: This indicates that a driver has tried to requested an IRP be completed that is already complete.
    This appears to be a typical software driver bug and is not likely to be caused by a hardware problem. 
    A third party driver was identified as the probable root cause of this system error. It is suggested you look for an update for the following driver: inspect.sys (COMODO Internet Security Firewall Driver, COMODO). 
    Google query: inspect.sys COMODO MULTIPLE_IRP_COMPLETE_REQUESTS
    
    
    
    
    On Sun 12/16/2012 11:04:35 AM GMT your computer crashed
    crash dump file: C:\Windows\Minidump\121612-18345-01.dmp
    This was probably caused by the following module: win32k.sys (win32k+0x78035) 
    Bugcheck code: 0x1000008E (0xFFFFFFFFC0000005, 0xFFFFFFFF9DA18035, 0xFFFFFFFFA70802C0, 0x0)
    Error: KERNEL_MODE_EXCEPTION_NOT_HANDLED_M
    file path: C:\Windows\system32\win32k.sys
    product: Microsoft® Windows® Operating System
    company: Microsoft Corporation
    description: Multi-User Win32 Driver
    Bug check description: This indicates that a kernel-mode program generated an exception which the error handler did not catch.
    This appears to be a typical software driver bug and is not likely to be caused by a hardware problem. 
    The crash took place in a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system which cannot be identified at this time. 
    
    
    On Sat 12/15/2012 2:56:20 AM GMT your computer crashed
    crash dump file: C:\Windows\Minidump\121512-17160-01.dmp
    This was probably caused by the following module: inspect.sys (inspect+0x1D45) 
    Bugcheck code: 0x4E (0x7, 0x6FA51, 0x1, 0x0)
    Error: PFN_LIST_CORRUPT
    file path: C:\Windows\system32\drivers\inspect.sys
    product: COMODO Internet Security Firewall Driver
    company: COMODO
    description: COMODO Internet Security Firewall Driver
    Bug check description: This indicates that the page frame number (PFN) list is corrupted.
    This appears to be a typical software driver bug and is not likely to be caused by a hardware problem. This might be a case of memory corruption. More often memory corruption happens because of software errors in buggy drivers, not because of faulty RAM modules. 
    A third party driver was identified as the probable root cause of this system error. It is suggested you look for an update for the following driver: inspect.sys (COMODO Internet Security Firewall Driver, COMODO). 
    Google query: inspect.sys COMODO PFN_LIST_CORRUPT
    
    
    
    
    On Fri 12/14/2012 2:18:15 PM GMT your computer crashed
    crash dump file: C:\Windows\Minidump\121412-20701-01.dmp
    This was probably caused by the following module: bckd.sys (bckd+0x6292) 
    Bugcheck code: 0x1000008E (0xFFFFFFFFC0000005, 0xFFFFFFFF8FF39C82, 0xFFFFFFFF93B47978, 0x0)
    Error: KERNEL_MODE_EXCEPTION_NOT_HANDLED_M
    file path: C:\Windows\system32\drivers\bckd.sys
    product: K9 Web Protection
    company: Blue Coat Systems, Inc.
    description: K9 Web Protection Driver
    Bug check description: This indicates that a kernel-mode program generated an exception which the error handler did not catch.
    This appears to be a typical software driver bug and is not likely to be caused by a hardware problem. 
    A third party driver was identified as the probable root cause of this system error. It is suggested you look for an update for the following driver: bckd.sys (K9 Web Protection Driver, Blue Coat Systems, Inc.). 
    Google query: bckd.sys Blue Coat Systems, Inc. KERNEL_MODE_EXCEPTION_NOT_HANDLED_M
    
    
    
    
    On Fri 12/14/2012 2:13:25 PM GMT your computer crashed
    crash dump file: C:\Windows\Minidump\121412-19484-01.dmp
    This was probably caused by the following module: inspect.sys (inspect+0x1D45) 
    Bugcheck code: 0x4E (0x7, 0x829B, 0x1, 0x0)
    Error: PFN_LIST_CORRUPT
    file path: C:\Windows\system32\drivers\inspect.sys
    product: COMODO Internet Security Firewall Driver
    company: COMODO
    description: COMODO Internet Security Firewall Driver
    Bug check description: This indicates that the page frame number (PFN) list is corrupted.
    This appears to be a typical software driver bug and is not likely to be caused by a hardware problem. This might be a case of memory corruption. More often memory corruption happens because of software errors in buggy drivers, not because of faulty RAM modules. 
    A third party driver was identified as the probable root cause of this system error. It is suggested you look for an update for the following driver: inspect.sys (COMODO Internet Security Firewall Driver, COMODO). 
    Google query: inspect.sys COMODO PFN_LIST_CORRUPT
    
    
    
    
    On Fri 12/14/2012 12:42:32 PM GMT your computer crashed
    crash dump file: C:\Windows\Minidump\121412-18891-01.dmp
    This was probably caused by the following module: inspect.sys (inspect+0x1D45) 
    Bugcheck code: 0x44 (0xFFFFFFFF8794A3A0, 0xEAE, 0x0, 0x0)
    Error: MULTIPLE_IRP_COMPLETE_REQUESTS
    file path: C:\Windows\system32\drivers\inspect.sys
    product: COMODO Internet Security Firewall Driver
    company: COMODO
    description: COMODO Internet Security Firewall Driver
    Bug check description: This indicates that a driver has tried to requested an IRP be completed that is already complete.
    This appears to be a typical software driver bug and is not likely to be caused by a hardware problem. 
    A third party driver was identified as the probable root cause of this system error. It is suggested you look for an update for the following driver: inspect.sys (COMODO Internet Security Firewall Driver, COMODO). 
    Google query: inspect.sys COMODO MULTIPLE_IRP_COMPLETE_REQUESTS
    
    
    
    
    On Thu 12/13/2012 10:11:03 AM GMT your computer crashed
    crash dump file: C:\Windows\Minidump\121312-22651-01.dmp
    This was probably caused by the following module: inspect.sys (inspect+0x1D45) 
    Bugcheck code: 0x44 (0xFFFFFFFFAA6A2E18, 0xEAE, 0x0, 0x0)
    Error: MULTIPLE_IRP_COMPLETE_REQUESTS
    file path: C:\Windows\system32\drivers\inspect.sys
    product: COMODO Internet Security Firewall Driver
    company: COMODO
    description: COMODO Internet Security Firewall Driver
    Bug check description: This indicates that a driver has tried to requested an IRP be completed that is already complete.
    This appears to be a typical software driver bug and is not likely to be caused by a hardware problem. 
    A third party driver was identified as the probable root cause of this system error. It is suggested you look for an update for the following driver: inspect.sys (COMODO Internet Security Firewall Driver, COMODO). 
    Google query: inspect.sys COMODO MULTIPLE_IRP_COMPLETE_REQUESTS
    
    
    
    
    On Wed 12/12/2012 2:15:07 PM GMT your computer crashed
    crash dump file: C:\Windows\Minidump\121212-17518-01.dmp
    This was probably caused by the following module: inspect.sys (inspect+0x1D45) 
    Bugcheck code: 0x4E (0x7, 0x6D4B3, 0x1, 0x0)
    Error: PFN_LIST_CORRUPT
    file path: C:\Windows\system32\drivers\inspect.sys
    product: COMODO Internet Security Firewall Driver
    company: COMODO
    description: COMODO Internet Security Firewall Driver
    Bug check description: This indicates that the page frame number (PFN) list is corrupted.
    This appears to be a typical software driver bug and is not likely to be caused by a hardware problem. This might be a case of memory corruption. More often memory corruption happens because of software errors in buggy drivers, not because of faulty RAM modules. 
    A third party driver was identified as the probable root cause of this system error. It is suggested you look for an update for the following driver: inspect.sys (COMODO Internet Security Firewall Driver, COMODO). 
    Google query: inspect.sys COMODO PFN_LIST_CORRUPT
    
    
    
    
    On Tue 12/11/2012 5:45:31 PM GMT your computer crashed
    crash dump file: C:\Windows\Minidump\121212-34991-01.dmp
    This was probably caused by the following module: ntkrnlpa.exe (nt+0x122996) 
    Bugcheck code: 0x19 (0x3, 0xFFFFFFFFA95E2810, 0xFFFFFFFFA95E2810, 0xFFFFFFFFA94E2810)
    Error: BAD_POOL_HEADER
    file path: C:\Windows\system32\ntkrnlpa.exe
    product: Microsoft® Windows® Operating System
    company: Microsoft Corporation
    description: NT Kernel & System
    Bug check description: This indicates that a pool header is corrupt.
    This appears to be a typical software driver bug and is not likely to be caused by a hardware problem. This might be a case of memory corruption. More often memory corruption happens because of software errors in buggy drivers, not because of faulty RAM modules. 
    The crash took place in the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time. 
    
    
    On Tue 12/11/2012 11:59:10 AM GMT your computer crashed
    crash dump file: C:\Windows\Minidump\121112-21247-01.dmp
    This was probably caused by the following module: ntfs.sys (Ntfs+0x81DEA) 
    Bugcheck code: 0xDE (0x2, 0xFFFFFFFFC1838650, 0xFFFFFFFFBF0ED181, 0x47B8C0)
    Error: POOL_CORRUPTION_IN_FILE_AREA
    file path: C:\Windows\system32\drivers\ntfs.sys
    product: Microsoft® Windows® Operating System
    company: Microsoft Corporation
    description: NT File System Driver
    Bug check description: This indicates that a driver has corrupted pool memory that is used for holding pages destined for disk.
    The crash took place in a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system which cannot be identified at this time. 
    
    
    On Thu 12/6/2012 12:45:22 PM GMT your computer crashed
    crash dump file: C:\Windows\Minidump\120612-20654-01.dmp
    This was probably caused by the following module: inspect.sys (inspect+0x1D45) 
    Bugcheck code: 0x4E (0x7, 0x5BCDD, 0x1, 0x0)
    Error: PFN_LIST_CORRUPT
    file path: C:\Windows\system32\drivers\inspect.sys
    product: COMODO Internet Security Firewall Driver
    company: COMODO
    description: COMODO Internet Security Firewall Driver
    Bug check description: This indicates that the page frame number (PFN) list is corrupted.
    This appears to be a typical software driver bug and is not likely to be caused by a hardware problem. This might be a case of memory corruption. More often memory corruption happens because of software errors in buggy drivers, not because of faulty RAM modules. 
    A third party driver was identified as the probable root cause of this system error. It is suggested you look for an update for the following driver: inspect.sys (COMODO Internet Security Firewall Driver, COMODO). 
    Google query: inspect.sys COMODO PFN_LIST_CORRUPT
    And also, could this be related to this? https://www.istorya.net/forums/networ...network-2.html
    Sorry I'm no expert in firewalls/networking issues.
    Last edited by boyq; 12-30-2012 at 09:08 PM.

Similar Threads

 
  1. RP Loses Bid to Host NCLEX due to Leakage
    By samsungster in forum Politics & Current Events
    Replies: 30
    Last Post: 08-23-2006, 09:06 PM
  2. inquiry about sound cards.. how to update audio driver?
    By whoopz in forum Computer Hardware
    Replies: 23
    Last Post: 07-06-2006, 11:10 AM
  3. Replies: 0
    Last Post: 01-06-2006, 03:52 PM
  4. Unstable internet connection due to router or ISP?
    By junjiejoan in forum Networking & Internet
    Replies: 16
    Last Post: 11-24-2005, 12:18 AM
  5. Replies: 0
    Last Post: 08-05-2005, 05:33 PM

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •  
about us
We are the first Cebu Online Media.

iSTORYA.NET is Cebu's Biggest, Southern Philippines' Most Active, and the Philippines' Strongest Online Community!
follow us
#top