balloonshark

Member
  • Content Count

    21
  • Joined

  • Last visited

Community Reputation

0 Neutral

About balloonshark

  • Rank
    Member

Profile Information

  • Gender
    Not Telling
  1. Sorry about that. I must have deleted the minidump when I ran ccleaner or the last crash didn't have one. Here is the 371MB compressed memory dump if it is useful. https://www.dropbox.com/s/zglwjyjsk5v337i/MEMORY.7z?dl=0 No other BSOD's to report but I haven't played the game since EIS updated to 11.0.0.5958 today.
  2. Thanks. I haven't tried the beta because I just saw your post. I just got another BSOD doing the same thing. I press esc to exit the game to its menu screen and then alt-tab because it freezes and then I get the BSOD. It doesn't happen all the time though and didn't happen before the release of EIS 11. Let me know if you want the new dumps and if you still want me to try the beta even though the bsod is not repeatable every time I exit the game.
  3. I used 7z on ultra for the dump file. It went from 2GB to 80MB. https://www.dropbox.com/s/zglwjyjsk5v337i/MEMORY.7z?dl=0 If you want me to configure anything differently in case of another bsod let me know.
  4. Here is the mini dump. I can't do the other until later if you need it. 111815-6000-01.dmp
  5. The dumps are set to auto and it is 2GB. It would take a while plus I have a bandwidth cap. I also can't do at this moment because the guys remodeling downstairs just started and I power off the computer once they start pounding. If you really need it I'll see what I can do but I can't start uploading for another 20 hours. Is the file size ok for uploading to a free dropbox account? I only used once for an OA related dump. Edit: Also, did you want the mini dump?
  6. I was playing a game on Steam and I got a BSOD when I exited the game. No other programs were open at the time and the computer has been stable since a clean install of Window 8.1 this year. The game has been working fine for the most part but no BSOD's. I also did a clean install of Emsisoft IS 11.0.0.5911 on the 13th. Here is what WhoCrashed said. System Information (local) Computer name: WOPRII Windows version: Windows 8.1 , 6.3, build: 9600 Windows dir: C:\Windows Hardware: ASRock, Z87 Extreme6 CPU: GenuineIntel Intel® Core i5-4670K CPU @ 3.40GHz Intel586, level: 6 4 logical processors, active mask: 15 RAM: 17105854464 bytes total Crash Dump Analysis Crash dump directory: C:\Windows\Minidump Crash dumps are enabled on your computer. On Wed 11/18/2015 9:50:44 AM GMT your computer crashed crash dump file: C:\Windows\Minidump\111815-6000-01.dmp This was probably caused by the following module: tcpip.sys (tcpip+0x508BE) Bugcheck code: 0x1000007E (0xFFFFFFFFC0000005, 0xFFFFF8014FA888BE, 0xFFFFD000A0E743B8, 0xFFFFD000A0E73BC0) Error: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M file path: C:\Windows\system32\drivers\tcpip.sys product: Microsoft® Windows® Operating System company: Microsoft Corporation description: TCP/IP Driver Bug check description: This indicates that a system thread 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 that cannot be identified at this time. On Wed 11/18/2015 9:50:44 AM GMT your computer crashed crash dump file: C:\Windows\memory.dmp This was probably caused by the following module: fwwfp764.sys (fwwfp764+0x6CED) Bugcheck code: 0x7E (0xFFFFFFFFC0000005, 0xFFFFF8014FA888BE, 0xFFFFD000A0E743B8, 0xFFFFD000A0E73BC0) Error: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED file path: C:\Program Files\Emsisoft Internet Security\fwwfp764.sys product: Emsisoft Firewall Engine company: Emsisoft Ltd description: Emsisoft Firewall Engine Bug check description: This bug check indicates that a system thread generated an exception that the error handler did not catch. 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: fwwfp764.sys (Emsisoft Firewall Engine, Emsisoft Ltd). Google query: Emsisoft Ltd SYSTEM_THREAD_EXCEPTION_NOT_HANDLED Conclusion 2 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: fwwfp764.sys (Emsisoft Firewall Engine, Emsisoft Ltd) If no updates for these drivers are available, try searching with Google on the names of these drivers in combination with the errors that have been reported for these drivers. Include the brand and model name of your computer as well in the query. This often yields interesting results from discussions on the web by users who have been experiencing similar problems.
  7. Nevermind. I guess all I needed to do is a quick scan to make everything green. Perhaps scanning shouldn't be tied to the protection status or have an automatic scan or a pop-up suggesting a scan. It would have been less confusing. Off topic: Please please please bring back Online Armor or let us activate OA. I'm going nuts without my system tray firewall status and allow once and block once firewall rules. If it wasn't for Online Armor and the firewall status I wouldn't have found out that Windows 8.1 "telemetry" was sending my data to Singapore. With Emsisoft Internet Security I'm completely in the dark. As it stands now I'm thinking about restoring a 4 month old image just so I can have OA back .
  8. Had problems with version 11.0.0.5911 after the update so I uninstalled and rebooted twice. I then did a clean install and rebooted and I see I have partial protection in the GUI. If I right click the system tray icon the 4 items say disable so they are ok. Everything also looks ok in Windows Action Center but updates which I disable and Network Access Protection is off for some reason.
  9. I'm seeing freezing whenever I have updated or installed a program. It seems everytime I get an OA pop-up and open OA's UI without answering the pop-up both the app and OA freeze. Yesterday I installed Battlefield 1942 and OA threw up a red message so I wanted to upload the file for scanning so I didn't answer the pop-up. The game install froze so I opened OA to check the history and it froze. I tried closing OA via the taskbar icon. It said it wasn't responding blah blah blah so I said to close it anyways. This left the game frozen. My only option was to reboot. This time I allowed the pop-up and everything went smoothly. I believe the same thing happened when updating Paintshop Pro X5 because I blocked IE internet access during the update (I don't like when installers open browsers). Here is the OA log and the EAM behavior blocker log. For the game install I think it starts at 10/18/13 at around 08:57. For the PSP update it was on 10/17/13 around 09:04.
  10. Thanks GT500. I uninstalled OA last night, did two reboots and used the computer normally afterwards. Today I got another BSOD when starting my browser sandboxed like the majority of my BSODs. Unless there are bits of OA leftover after uninstalling I think I have eliminated OA as the cause.
  11. This newest crash seems to point to oanet.sys according to the whocrashed log below. If you want the full dump file let me know. I'll keep it on my hdd for a little while longer. I'm also not sure what triggered the crash. All I know is I started my computer, the screen was black and it was using the sdd before I got to my motherboard logo. I guess it was writing the dump file from the last session. ________________________________________________________________________________________________________________ Welcome to WhoCrashed (HOME EDITION) v 4.02 This program checks for drivers which have been crashing your computer. If your computer has displayed a blue screen of death, suddenly rebooted or shut down then this program will help you find the root cause and possibly a solution. Whenever a computer suddenly reboots without displaying any notice or blue screen of death, the first thing that is often thought about is a hardware failure. In reality, on Windows most crashes are caused by malfunctioning device drivers and kernel modules. In case of a kernel error, many computers do not show a blue screen unless they are configured for this. Instead these systems suddenly reboot without any notice. This program will analyze your crash dumps with the single click of a button. It will tell you what drivers are likely to be responsible for crashing your computer. It will report a conclusion which offers suggestions on how to proceed in any situation while the analysis report will display internet links which will help you further troubleshoot any detected problems. To obtain technical support visit www.resplendence.com/support Click here to check if you have the latest version or if an update is available. Just click the Analyze button for a comprehensible report ... Home Edition Notice This version of WhoCrashed is free for use at home only. If you would like to use this software at work or in a commercial environment you should get the professional edition of WhoCrashed which also allows analysis of crashdumps on remote drives and computers on the network and offers a range of additional features. Click here for more information on the professional edition. Click here to buy the the professional edition of WhoCrashed. System Information (local) computer name: WOPRII windows version: Windows 8 , 6.2, build: 9200 windows dir: C:\Windows CPU: GenuineIntel Intel® Core i5-4670K CPU @ 3.40GHz Intel586, level: 6 4 logical processors, active mask: 15 RAM: 8516931584 total VM: 2147352576, free: 1923772416 Crash Dump Analysis Crash dump directory: C:\Windows\Minidump Crash dumps are enabled on your computer. On Mon 8/19/2013 4:17:22 AM GMT your computer crashed crash dump file: C:\Windows\Minidump\081913-13078-01.dmp This was probably caused by the following module: ntoskrnl.exe (nt+0x5A440) Bugcheck code: 0x139 (0x3, 0xFFFFF88003C061E0, 0xFFFFF88003C06138, 0x0) Error: KERNEL_SECURITY_CHECK_FAILURE file path: C:\Windows\system32\ntoskrnl.exe product: Microsoft® Windows® Operating System company: Microsoft Corporation description: NT Kernel & System Bug check description: The kernel has detected the corruption of a critical data structure. The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time. On Mon 8/19/2013 4:17:22 AM GMT your computer crashed crash dump file: C:\Windows\memory.dmp This was probably caused by the following module: oanet.sys (oanet+0x2463) Bugcheck code: 0x139 (0x3, 0xFFFFF88003C061E0, 0xFFFFF88003C06138, 0x0) Error: KERNEL_SECURITY_CHECK_FAILURE file path: C:\Windows\system32\drivers\oanet.sys product: OA Helper Driver company: Emsisoft description: OA Helper Driver Bug check description: The kernel has detected the corruption of a critical data structure. 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: oanet.sys (OA Helper Driver, Emsisoft). Google query: Emsisoft KERNEL_SECURITY_CHECK_FAILURE On Wed 8/14/2013 12:24:05 PM GMT your computer crashed crash dump file: C:\Windows\Minidump\081413-13109-01.dmp This was probably caused by the following module: ntoskrnl.exe (nt+0x5A440) Bugcheck code: 0x50 (0xFFFFF8A010DD4000, 0x0, 0xFFFFF8008A2D92A0, 0x0) Error: PAGE_FAULT_IN_NONPAGED_AREA 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 invalid system memory has been referenced. 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 the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time. On Wed 8/14/2013 10:11:58 AM GMT your computer crashed crash dump file: C:\Windows\Minidump\081413-13203-01.dmp This was probably caused by the following module: ntoskrnl.exe (nt+0x5A440) Bugcheck code: 0x50 (0xFFFFF8A00845000C, 0x0, 0xFFFFF8014C2CC49A, 0x0) Error: PAGE_FAULT_IN_NONPAGED_AREA 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 invalid system memory has been referenced. 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 the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time. On Sun 8/11/2013 8:40:15 AM GMT your computer crashed crash dump file: C:\Windows\Minidump\081113-13328-01.dmp This was probably caused by the following module: ntoskrnl.exe (nt+0x5A440) Bugcheck code: 0x50 (0xFFFFF8A009E4200C, 0x0, 0xFFFFF802804DA49A, 0x0) Error: PAGE_FAULT_IN_NONPAGED_AREA 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 invalid system memory has been referenced. 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 the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time. On Sun 8/11/2013 4:21:36 AM GMT your computer crashed crash dump file: C:\Windows\Minidump\081113-13187-01.dmp This was probably caused by the following module: ntoskrnl.exe (nt+0x5A440) Bugcheck code: 0x50 (0xFFFFF8A0095F2000, 0x0, 0xFFFFF801B8ED12A0, 0x0) Error: PAGE_FAULT_IN_NONPAGED_AREA 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 invalid system memory has been referenced. 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 the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time. On Mon 8/5/2013 10:15:42 AM GMT your computer crashed crash dump file: C:\Windows\Minidump\080513-13234-01.dmp This was probably caused by the following module: ntoskrnl.exe (nt+0x5A440) Bugcheck code: 0x139 (0x3, 0xFFFFF8800A1951E0, 0xFFFFF8800A195138, 0x0) Error: KERNEL_SECURITY_CHECK_FAILURE file path: C:\Windows\system32\ntoskrnl.exe product: Microsoft® Windows® Operating System company: Microsoft Corporation description: NT Kernel & System Bug check description: The kernel has detected the corruption of a critical data structure. The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time. On Mon 8/5/2013 4:10:57 AM GMT your computer crashed crash dump file: C:\Windows\Minidump\080513-14031-01.dmp This was probably caused by the following module: ntoskrnl.exe (nt+0x5A440) Bugcheck code: 0x50 (0xFFFFF8A0089F4000, 0x0, 0xFFFFF8020FA562A0, 0x0) Error: PAGE_FAULT_IN_NONPAGED_AREA 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 invalid system memory has been referenced. 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 the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time. On Sun 8/4/2013 2:23:30 PM GMT your computer crashed crash dump file: C:\Windows\Minidump\080413-14296-01.dmp This was probably caused by the following module: ntoskrnl.exe (nt+0x5A440) Bugcheck code: 0x50 (0xFFFFF8A010260000, 0x0, 0xFFFFF802D5AC42A0, 0x0) Error: PAGE_FAULT_IN_NONPAGED_AREA 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 invalid system memory has been referenced. 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 the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time. On Sat 8/3/2013 10:26:16 AM GMT your computer crashed crash dump file: C:\Windows\Minidump\080313-13234-01.dmp This was probably caused by the following module: ntoskrnl.exe (nt+0x5A440) Bugcheck code: 0x50 (0xFFFFF8A009E58000, 0x0, 0xFFFFF8039026B2A0, 0x0) Error: PAGE_FAULT_IN_NONPAGED_AREA 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 invalid system memory has been referenced. 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 the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time. On Tue 7/30/2013 3:08:30 AM GMT your computer crashed crash dump file: C:\Windows\Minidump\072913-13390-01.dmp This was probably caused by the following module: ntoskrnl.exe (nt+0x5A440) Bugcheck code: 0x139 (0x3, 0xFFFFF88003D6C1E0, 0xFFFFF88003D6C138, 0x0) Error: KERNEL_SECURITY_CHECK_FAILURE file path: C:\Windows\system32\ntoskrnl.exe product: Microsoft® Windows® Operating System company: Microsoft Corporation description: NT Kernel & System Bug check description: The kernel has detected the corruption of a critical data structure. The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time. On Mon 7/29/2013 1:21:36 AM GMT your computer crashed crash dump file: C:\Windows\Minidump\072813-13406-01.dmp This was probably caused by the following module: ntoskrnl.exe (nt+0x5A440) Bugcheck code: 0x50 (0xFFFFF8A008C45000, 0x0, 0xFFFFF800958692A0, 0x0) Error: PAGE_FAULT_IN_NONPAGED_AREA 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 invalid system memory has been referenced. 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 the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time. On Sat 7/27/2013 9:46:49 AM GMT your computer crashed crash dump file: C:\Windows\Minidump\072713-14203-01.dmp This was probably caused by the following module: ntoskrnl.exe (nt+0x5A440) Bugcheck code: 0x50 (0xFFFFF8A008E6600C, 0x0, 0xFFFFF800948C149A, 0x0) Error: PAGE_FAULT_IN_NONPAGED_AREA 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 invalid system memory has been referenced. 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 the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time. Conclusion 13 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: oanet.sys (OA Helper Driver, Emsisoft) 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.
  12. Thanks GT500. I'll pass the information on to Tzuk. Was it by chance a conflict between OA and Sbie? I've seen plenty of conflicts between the two in the past but never a BSOD.
  13. Thanks GT500. I uploaded the file to DropBox. I will send the details via PM.
  14. Ok, I just got another BSOD and this one was a full dump. It was 7.93GB and I have a ultra compressed 7z file ready to send. Its file size is 370MB. I just need somewhere to upload the file. What happened. I booted into windows and then got the bar across the screen telling me Windows had updates and I clicked cancel. I then went to my desktop and then double-clicked the palemoon icon (which if a forced sandbox program) and got the BSOD right after clicking the icon.