JakeHardy

Blue screen with internet security 9 beta

Recommended Posts

woe is me, after installing it it worked fine, but after i kept blue screening with a stop error, i went into safe mode and uninstalled is9 and no longer have the issue.

i ran a program called who crashed that reads dump files, which i'll put below, let me know if you need any more info.

Crash dump directory: C:\Windows\Minidump

Crash dumps are enabled on your computer.

On Wed 7/05/2014 10:19:12 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\050814-18408-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x75BC0)
Bugcheck code: 0xC5 (0x2BF0, 0x2, 0x0, 0xFFFFF8000360B123)
Error: DRIVER_CORRUPTED_EXPOOL
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that the system attempted to access invalid memory at a process IRQL that was too high.
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 that cannot be identified at this time.



On Wed 7/05/2014 10:19:12 PM GMT your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: vboxnetflt.sys (VBoxNetFlt+0x307E)
Bugcheck code: 0xC5 (0x2BF0, 0x2, 0x0, 0xFFFFF8000360B123)
Error: DRIVER_CORRUPTED_EXPOOL
file path: C:\Windows\system32\drivers\vboxnetflt.sys
product: Oracle VM VirtualBox
company: Oracle Corporation
description: VirtualBox Bridged Networking Driver
Bug check description: This indicates that the system attempted to access invalid memory at a process IRQL that was too high.
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: vboxnetflt.sys (VirtualBox Bridged Networking Driver, Oracle Corporation).
Google query: Oracle Corporation DRIVER_CORRUPTED_EXPOOL



On Wed 7/05/2014 9:55:55 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\050814-17986-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x75BC0)
Bugcheck code: 0xC5 (0x9BA8, 0x2, 0x0, 0xFFFFF80003609123)
Error: DRIVER_CORRUPTED_EXPOOL
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that the system attempted to access invalid memory at a process IRQL that was too high.
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 that cannot be identified at this time.



On Wed 7/05/2014 9:49:35 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\050814-18392-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x75BC0)
Bugcheck code: 0xC5 (0x6E5F, 0x2, 0x0, 0xFFFFF800029AB123)
Error: DRIVER_CORRUPTED_EXPOOL
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that the system attempted to access invalid memory at a process IRQL that was too high.
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 that cannot be identified at this time.



On Wed 7/05/2014 9:47:41 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\050814-20014-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x75BC0)
Bugcheck code: 0xC5 (0x2065, 0x2, 0x0, 0xFFFFF800035AD123)
Error: DRIVER_CORRUPTED_EXPOOL
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that the system attempted to access invalid memory at a process IRQL that was too high.
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 that cannot be identified at this time.



On Wed 7/05/2014 9:37:24 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\050814-18922-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x75BC0)
Bugcheck code: 0xC5 (0xB175, 0x2, 0x0, 0xFFFFF800035AF123)
Error: DRIVER_CORRUPTED_EXPOOL
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that the system attempted to access invalid memory at a process IRQL that was too high.
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 that cannot be identified at this time.



On Wed 7/05/2014 9:31:45 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\050814-12589-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x75BC0)
Bugcheck code: 0xC5 (0x1C6F, 0x2, 0x0, 0xFFFFF80003611123)
Error: DRIVER_CORRUPTED_EXPOOL
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that the system attempted to access invalid memory at a process IRQL that was too high.
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 that cannot be identified at this time.



On Wed 7/05/2014 9:30:20 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\050814-16224-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x75BC0)
Bugcheck code: 0xC5 (0x1C6F, 0x2, 0x0, 0xFFFFF800035C7123)
Error: DRIVER_CORRUPTED_EXPOOL
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that the system attempted to access invalid memory at a process IRQL that was too high.
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 that cannot be identified at this time.



On Wed 7/05/2014 9:29:05 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\050814-15506-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x75BC0)
Bugcheck code: 0xC5 (0x6318, 0x2, 0x0, 0xFFFFF80003603123)
Error: DRIVER_CORRUPTED_EXPOOL
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that the system attempted to access invalid memory at a process IRQL that was too high.
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 that cannot be identified at this time.


 

Share this post


Link to post
Share on other sites

The blue screen is caused by the VirtualBox NDIS driver. Their driver is unfortunately known for causing a whole bunch of issues with firewall and AV filter drivers. The only way to fix it is to install VirtualBox without Bridged Networking support at the moment, as Oracle refuses to fix that particular issue in their driver.

Share this post


Link to post
Share on other sites

The blue screen is caused by the VirtualBox NDIS driver. Their driver is unfortunately known for causing a whole bunch of issues with firewall and AV filter drivers. The only way to fix it is to install VirtualBox without Bridged Networking support at the moment, as Oracle refuses to fix that particular issue in their driver.

cause i am just learning linux, what would i lose if i removed the bridged networking?

Share this post


Link to post
Share on other sites

Bridged networking is where the virtualization software (in the case Virtual Box) sets up virtual network devices that act like they are connected directly to your network, so that they have IP addresses assigned by your router. The primary alternative to this is NAT (Network Address Translation) mode, where the virtualization software uses the network connection in a more traditional manner. In Virtual Box there can be some issues with UDP packets in NAT mode, but you only really see those issues when trying to run a game server in the virtual machine.

Share this post


Link to post
Share on other sites

Bridged networking is where the virtualization software (in the case Virtual Box) sets up virtual network devices that act like they are connected directly to your network, so that they have IP addresses assigned by your router. The primary alternative to this is NAT (Network Address Translation) mode, where the virtualization software uses the network connection in a more traditional manner. In Virtual Box there can be some issues with UDP packets in NAT mode, but you only really see those issues when trying to run a game server in the virtual machine.

awesome thank you

Share this post


Link to post
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.


  • Recently Browsing   0 members

    No registered users viewing this page.