Results 1 to 6 of 6

Thread: Windows 7 64 Bit Blue Screen

  1. #1
    Join Date
    May 2010
    Posts
    16

    Default Windows 7 64 Bit Blue Screen

    Is ZoneAlarm the only problem here?
    Or is there some other driver? CheckPoint claims that ZoneAlarm supports 64 bit Windows7 but perhaps there are still some problems.
    I did a full ram test with MEMTEST booted of a USB disk, which was a really cool learning experience-- but no problems were detected.

    Here is my bluescreen

    This is my log report from WhoCrashed

    Code:
    System Information (local)
    --------------------------------------------------------------------------------
    
    computer name: #################
    windows version: Windows 7 , 6.1, build: 7600
    windows dir: C:\Windows
    CPU: GenuineIntel Intel(R) Core(TM) i3 CPU 540 @ 3.07GHz Intel586, level: 6
    4 logical processors, active mask: 15
    RAM: 4294967295 total
    VM: 2147352576, free: 1986609152
    
    
    
    --------------------------------------------------------------------------------
    Crash Dump Analysis
    --------------------------------------------------------------------------------
    
    Crash dump directory: C:\Windows\Minidump
    
    Crash dumps are enabled on your computer.
    
    
    On Sun 12/12/2010 1:20:01 AM GMT your computer crashed
    crash dump file: C:\Windows\Minidump\121110-18829-01.dmp
    This was probably caused by the following module: ntoskrnl.exe (nt+0x70740) 
    Bugcheck code: 0x7F (0x8, 0x80050031, 0x6F8, 0xFFFFF80002C80D91)
    Error: UNEXPECTED_KERNEL_MODE_TRAP
    file path: C:\Windows\system32\ntoskrnl.exe
    product: Microsoft® Windows® Operating System
    company: Microsoft Corporation
    description: NT Kernel & System
    Bug check description: This bug check indicates that the Intel CPU generated a trap and the kernel failed to catch this trap.
    The crash took place in the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time. 
    
    
    On Sun 12/12/2010 1:20:01 AM GMT your computer crashed
    crash dump file: C:\Windows\memory.dmp
    This was probably caused by the following module: vsdatant.sys (vsdatant+0x16387) 
    Bugcheck code: 0x7F (0x8, 0x80050031, 0x6F8, 0xFFFFF80002C80D91)
    Error: UNEXPECTED_KERNEL_MODE_TRAP
    file path: C:\Windows\system32\drivers\vsdatant.sys
    product: ZoneAlarm Firewalling Driver
    company: Check Point Software Technologies LTD
    description: ZoneAlarm Firewalling Driver
    Bug check description: This bug check indicates that the Intel CPU generated a trap and the kernel failed to catch this trap.
    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: vsdatant.sys (ZoneAlarm Firewalling Driver, Check Point Software Technologies LTD). 
    Google query: vsdatant.sys Check Point Software Technologies LTD UNEXPECTED_KERNEL_MODE_TRAP
    
    
    
    
    On Sat 12/11/2010 7:08:54 PM GMT your computer crashed
    crash dump file: C:\Windows\Minidump\121110-36207-01.dmp
    This was probably caused by the following module: ntoskrnl.exe (nt+0x70740) 
    Bugcheck code: 0x7F (0x8, 0x80050031, 0x6F8, 0xFFFFF80002CDAD91)
    Error: UNEXPECTED_KERNEL_MODE_TRAP
    file path: C:\Windows\system32\ntoskrnl.exe
    product: Microsoft® Windows® Operating System
    company: Microsoft Corporation
    description: NT Kernel & System
    Bug check description: This bug check indicates that the Intel CPU generated a trap and the kernel failed to catch this trap.
    The crash took place in the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time. 
    
    
    On Fri 12/10/2010 4:04:43 PM GMT your computer crashed
    crash dump file: C:\Windows\Minidump\121010-20498-01.dmp
    This was probably caused by the following module: ntoskrnl.exe (nt+0x70740) 
    Bugcheck code: 0x7F (0x8, 0x80050031, 0x6F8, 0xFFFFF80002CD2D91)
    Error: UNEXPECTED_KERNEL_MODE_TRAP
    file path: C:\Windows\system32\ntoskrnl.exe
    product: Microsoft® Windows® Operating System
    company: Microsoft Corporation
    description: NT Kernel & System
    Bug check description: This bug check indicates that the Intel CPU generated a trap and the kernel failed to catch this trap.
    The crash took place in the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time. 
    
    
    On Wed 12/8/2010 8:35:20 AM GMT your computer crashed
    crash dump file: C:\Windows\Minidump\120810-21980-01.dmp
    This was probably caused by the following module: ntoskrnl.exe (nt+0x70740) 
    Bugcheck code: 0x7F (0x8, 0x80050031, 0x6F8, 0xFFFFF80002CCBD91)
    Error: UNEXPECTED_KERNEL_MODE_TRAP
    file path: C:\Windows\system32\ntoskrnl.exe
    product: Microsoft® Windows® Operating System
    company: Microsoft Corporation
    description: NT Kernel & System
    Bug check description: This bug check indicates that the Intel CPU generated a trap and the kernel failed to catch this trap.
    The crash took place in the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time. 
    
    
    
    --------------------------------------------------------------------------------
    Conclusion
    --------------------------------------------------------------------------------
    
    5 crash dumps have been found and analyzed. A third party driver has been identified to be causing system crashes on your computer. It is strongly suggested that you check for updates for these drivers on their company websites. Click on the links below to search with Google for updates for these drivers: 
    
    vsdatant.sys (ZoneAlarm Firewalling Driver, Check Point Software Technologies LTD)
    
    If no updates for these drivers are available, try searching with Google on the names of these drivers in combination the errors that have been reported for these drivers and include the brand and model name of your computer as well in the query. This often yields interesting results from discussions from users who have been experiencing similar problems.
    
    
    Read the topic general suggestions for troubleshooting system crashes for more information. 
    
    Note that it's not always possible to state with certainty whether a reported driver is actually responsible for crashing your system or that the root cause is in another module. Nonetheless it's suggested you look for updates for the products that these drivers belong to and regularly visit Windows update or enable automatic updates for Windows. In case a piece of malfunctioning hardware is causing trouble, a search with Google on the bug check errors together with the model name and brand of your computer may help you investigate this further.

  2. #2
    Join Date
    Aug 2007
    Location
    South Carolina
    Posts
    2,503

    Default

    My Rig:
    Corsair Obsidian 450D | EVGA SuperNova G3 650W | Asus Prime Z270-A | Intel i7-7700K | Cryorig H7 | G.Skill TridentZ 16gb (2x8gb) DDR4 3200 | MSI GTX1070 Gaming X 8G | Crucial MX300 SSD | Windows 10 Pro 64-bit | Asus VW246H

  3. #3
    Join Date
    May 2010
    Posts
    16

    Default

    I can't track the problem down and fix it.
    Everything works fine for a few hours-- then bam
    bluescreen

    Nothing is done to cause it.
    So random. I've never seen anything like this before on a mac.

  4. #4
    Join Date
    Aug 2007
    Location
    South Carolina
    Posts
    2,503

    Default

    Uninstall ZoneAlarm and see if that helps.
    What are your complete system specs?
    My Rig:
    Corsair Obsidian 450D | EVGA SuperNova G3 650W | Asus Prime Z270-A | Intel i7-7700K | Cryorig H7 | G.Skill TridentZ 16gb (2x8gb) DDR4 3200 | MSI GTX1070 Gaming X 8G | Crucial MX300 SSD | Windows 10 Pro 64-bit | Asus VW246H

  5. #5
    Join Date
    May 2010
    Posts
    16

    Default

    Solution:
    Control Panel
    View Network status and tasks
    Change adapter settings
    Right Click -> Properties on LAN
    right click Internet Protocol 4
    Click properties
    Advanced
    WINS
    Disable NetBIOS over TCP/IP

    Done.
    I miss apple.

  6. #6
    Join Date
    Aug 2007
    Location
    South Carolina
    Posts
    2,503

    Default

    Glad you got it worked out.
    My Rig:
    Corsair Obsidian 450D | EVGA SuperNova G3 650W | Asus Prime Z270-A | Intel i7-7700K | Cryorig H7 | G.Skill TridentZ 16gb (2x8gb) DDR4 3200 | MSI GTX1070 Gaming X 8G | Crucial MX300 SSD | Windows 10 Pro 64-bit | Asus VW246H

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •