Jump to content


  • Content Count

  • Joined

  • Last visited

Everything posted by skyviewe

  1. Turned on verifier, got another blue screen quick. Filename is MEMORY-2019-07-20.7z so you know you have the right one: https://mega.nz/#!mH5WVaxR!JNF1btkfXlGQ6li7CRpeTXURkFbFm5VyF7ql6sbQnMM Thanks again. -Jamie M.
  2. Done! Bluescreened about 1 hour after I turned on verifier, boy that makes the computer run slow, lol. Here's the new file: https://mega.nz/#!TbYAjSLb!jx8m9Pi_hevyHWVvn2tBULz_Z6_o_UHHjHFnkiZ04DM Thanks again. -Jamie M.
  3. Nod32 Antivirus version: Windows Version: Windows 10 Home 64 bit, 1903, build 18362.175 Full memory dump (1.7gb 7zip compressed, 6gb uncompressed): I installed new SSD hard drive, fresh install of Windows 10. Only software I installed was Chrome. Computer worked fine for 2 weeks then purchased Nod32 and installed it. The next day I got a BSOD so I ran WhoCrashed: This was probably caused by the following module: netio.sys (NETIO+0xEF80) Bugcheck code: 0xA (0x49, 0x2, 0x0, 0xFFFFF80501F34EDA) Error: IRQL_NOT_LESS_OR_EQUAL For some reason Windows 10 deleted the memory dump file the next day even though "delete memory dump if low space" wasn't enabled. A day later (approx 48 hours since the first crash) I got another BSOD: This was probably caused by the following module: ntkrnlmp.exe (nt!memset+0x4F21) Bugcheck code: 0x7E (0xFFFFFFFFC0000005, 0xFFFFF8021BA80EDA, 0xFFFFB6051CFD5018, 0xFFFFB6051CFD4860) Error: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED This time I backed up the memory dump file and uploaded it (link at at the top of this post). I ran MemTest Pro in Windows, no memory errors, no blue screen. Seems to just randomly bluescreen, i.e. just sitting on the screensaver with nothing open, surfing the web, youtube, etc. Before I axe and re-load the computer and test it good without Nod32, can you confirm based on the memory dump if it's Nod32 causing the BSOD's or not? Thanks. -Jamie M.
  • Create New...