JakeHardy

Member
  • Content Count

    15
  • Joined

  • Last visited

Community Reputation

0 Neutral

About JakeHardy

  • Rank
    Member
  1. 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.
  2. Hello, the update to 8.0.0.10 has fixed my issue and i am no longer getting prompted for updated executable
  3. yes i can confirm that the issue is still happening and that i am running version 8.0.0.7
  4. Online Armor? my issue is with Emsisosft Anti-Malware
  5. Hello, i have been monitoring that forum you linked but that issue is still yet to be fixed, do you have a eta?
  6. Hello, attached is the file you required, i ran the program planetside2.exe
  7. Hello, i only have windows 7 x64 and it is every program the updates has the issue
  8. Hey everyone, i have a small problem with Emsisosft anti-malware, when a alert pop up saying the the program has changed i tick (Don't alert for update to this executable file), then press ok, but during the next update it happens again, i have gone to the guard and found the exe's(Don't alert for update to this executable file) is not ticked, when i do maunally tick it i think it stops alerting me