Jump to content


  • Posts

  • Joined

  • Last visited

About grinr

  • Rank

Profile Information

  • Location
  1. Do you know what version of AI Suite was installed?
  2. Glad it helped. I'm curious about what exactly changed (and when) that caused this to "spontaneously" occur. An update to ESET? An update to the system software (APP center, AI Suite)? Windows update? Why would USB driver update (for me) resolve the issue? I've been trying to isolate this but with no success.
  3. I bet it's a Z97 chipset board. I had this problem as well. Here's a solution I posted in the NOD32 forum:
  4. Update: After uninstalling NOD32 AV, I tried installing BitDefender. BSOD, same error: Stop 0x00000101 "A clock interrupt was not received on a secondary processor within the allocated time interval" So, this made me curious and I decided to update my AI Suite software (as per Marcos' suggestion.) The newer version from Feb 2015 got halfway through and blew up on the USB driver install - BSOD again, this time a different error that disappeared too quickly for me to see it. Booted to Safe Mode, windows logs were not helpful so I tried rebooting to Normal mode. BSOD again, this time showing "asmtxhci.sys" as the culprit. Back to Safe Mode and looked it up - it's the Asmedia USB driver. As I couldn't get back to normal mode because of insta-BSOD on login, I ran a system restore to before the AI Suite installation. That worked and I got my desktop back. So I download the latest driver for Asmedia USB (v116230) install it without issue, then try installing the AI Suite again. This time, no crash, no problem. I tried again to reinstall BitDefender. No problem, installed fine. Uninstalled it and tried to reinstall ESET NOD32 AV. It fails but because it didn't uninstally properly, so I get the uninstaller app and deal with that. Reboot again and install NOD32 AV without issue. 30 minutes and so far so good. I hope this is helpful.
  5. Thanks Marcos for the feedback, it is appreciated.
  6. The crashes were caused by a hardware failure, ie. they couldn't have been caused by ESET. The fact that the crash doesn't occur with ESET installed doesn't mean that your system will be ok after uninstalling ESET as ESET acts only as a catalyst of the issue. The crash may return randomly in the future as long as the problematic software mentioned above is installed. It's in the interest of both ESET and Gigabyte and ASUS to work on the issue and fix it, otherwise the users will remain at risk no matter if ESET is installed or not (there are many examples when the mentioned software caused a crash and the users didn't have ESET installed). Ah, true, the multitude of possibilities is what keeps us on our toes. Anything could potentially cause a system crash randomly in the future. What is currently known, however, is that the systems reported on here today have Z97 chipsets from two different manufacturers (who naturally have different system software) and seem to have been fine for many months without issue. We also know that removing ESET solves the problem of persistent BSODs. We also know that installing alternative AV does not cause persistent BSODs. That said, I certainly agree that a discussion is merited between the various companies to sort this out. As I cannot be without AV protection, and will not be without system software, I have no choice at the moment but to use an alternative AV solution until you all sort it out. As a die-hard ESET customer, that's a painful conclusion to arrive at and I will be keeping an ear to the ground for word of when it may be safe to use ESET again.
  7. You can appreciate that uninstalling the software we use to manage our computers is not an ideal solution. Installing alternative AV products is a far more likely alternative. Do you have any of the motherboards available that have been mentioned (Z97 chipset) that you can test with to see if uninstalling the system software actually works? Can you identify what the conflict is? If the solution you're proposing is to QA software, especially system software, I'll reluctantly have to pass and select a new AV solution. It's my hope we can encourage ESET to investigate what the conflict is and resolve it from their end.
  8. I have an ASUS board (z97-pro ac wifi) and I have the same issue. Perhaps a z97 chipset issue? I am 100% certain there was no update to my system drivers or BIOS for at least two weeks before the issue emerged.
  9. I have the same story - NOD32 AV, Win7 64-bit, on a custom box (ASUS z78-pro, i7) I built about 6 months ago. Rock solid for all six months until Sunday night when the BSOD happened. Uninstalled (or disabled the service) ESET AV 8 and bingo, BSODs are gone.
  10. At around 1AM last night while I wasn't even using the PC (Windows7 x64, ASUS z97-pro, i7) I got a BSOD out of nowhere. I haven't installed or upgraded anything (manually, aside from Windows Updates) in months. The error I got was the following: Stop 0x00000101 "A clock interrupt was not received on a secondary processor within the allocated time interval" So naturally I suspected a CPU/hardware fault. I've spent all day trying to narrow this down, and only when discovering that I can run Prime95 for a few hours in safe mode without issue did I start to suspect it was a software problem. I disabled ESET in the services and am currently running in normal mode (sans ESET) and so far no BSOD. I'm thinking ESET NOD32 ran some kind of update recently and that borked the system.
  • Create New...