Jump to content

usasma

BSOD Kernel Dump Expert
  • Content count

    394
  • Joined

  • Last visited

1 Follower

About usasma

  • Rank
    BSOD Kernel Dump Expert

Contact Methods

  • Website URL
    http://www.carrona.org/

Profile Information

  • Location
    At home in front of my computer
  • Interests
    Computers - naturally! :0)

Recent Profile Visitors

5,847 profile views
  1. I would continue to work with the support team to see if they can fix it for you. Their BSOD fix is only a beta - and it may need further work to fix them all. I'm not real worried that this is a hardware problem - so, if you don't want to run the hardware tests, then don't. In most cases there's no problem with the tests: - most often there is no problem, as the system cools itself properly and doesn't overheat (85ºC is getting too warm - but (IMO) isn't sufficient to damage the system. In most cases you can actually reach 100ºC without any damage occurring. As I recall, some Intel processors are set to shut down at 105ºC (I haven't looked this up recently) - next most often is that the user sees a problem with the test and shuts it off. - next most often is that the system does overheat, but the automatic fail-safe features in the hardware cause the system to shutdown when it overheats - and then, least likely, is that the fail-safe's don't work - and the system melts down due to overheating. That's why we work cautiously with this - but I must say that I don't think that I've ever seen this in all my years working with computers (but I may have stopped it before it got this bad)>
  2. usasma

    BSOD when MBAM is Activated

    Do you still need help with this? See this topic for more info:
  3. DISCLAIMER: I am not a trained malware removal expert. I do this at work, but our resources are limited and we just don’t have the time to do thorough removals (like they do in the Malware Removal forums) That being said, I’d start with the rescue disks offered by the different anti-virus/anti-malware companies. I have a listing of some on my website, but the links haven’t been updated in years Heres’s the link: http://www.carrona.org/malware.html Please remember that the system may not be able to boot into Windows after attempting the removals. As such, I’d suggest backing up your data before trying this. Also, you may wish to make a disk image of the entire hard drive before starting - to preserve everything as it exists today.
  4. There's several different ways to handle this: - tap F11 at boot to enterthe HP Recovery Manager and restore the system to the state it was when it left the factory. You'll lose everything that's saved on the computer, so a backup is suggested before doing this. - use bootable media and portable antivirus/antimalware software to attempt to remove things from outside of Windows. Then, if you're able to boot back into Windows, you may be able to finish the scans then. - post over in the https://forums.malwarebytes.com/forum/7-windows-malware-removal-help-support/ forums for help with removing the infections/issues
  5. usasma

    BSOD netio.sys driver failure

    I would suggest turning Driver Verifier off now Open up verifier.exe and select “Delete existing settings” then click on “Finish” and reboot for the changes to take effect Sent fm my phone
  6. I'd suggest opening a support case with MalwareBytes: https://support.malwarebytes.com/community/consumer/pages/contact-us They may be able to suggest other steps that don't involve disabling Web Protection
  7. IMO the Web Protection of MalwareBytes is a bit finicky in how it acts around other drivers. Yours is the first time I've seen that an uninstall then reinstall of MalwareBytes has fixed the issue. I'll keep that in mind the next time we see those sort of issues here. Thanks for keeping us informed!
  8. Looked like you only did one pass of the Memtest. Three is needed to be sure that random errors are picked up (some techs suggest 5 or even 7 passes)
  9. A bit of discussion here.... Back in the old days (Windows XP time frame). BSOD's were easy to detect and fix. BSOD's most often were caused by a single driver and were easy to identify in the memory dumps. Most of our techniques for troubleshooting were developed during this time frame. As the OS has matured, it's become more complicated. Drivers have also become more complicated and they interact with other drivers more. We run more programs simultaneously, and as such, even more drivers are loaded into memory. So now we see a lot of unknown crashes, and due to the increased complexity of the drivers, they become even more difficult to diagnose. Most recently, I'm seeing a lot of BSOD's that seem to be hardware related - but end up being due to driver problems. Unfortunately, more and more of the "fixes" are done by wiping the system and reinstalling Windows 'clean' - then installing the other drivers one-by-one to see if the problem returns. There are easier ways to do this, but unfortunately they take experienced developers to run (and they may not even be able to diagnose some 3rd party drivers) - and their services cost much, much more than several new computers would cost you (a long time ago, I heard a random quote of $10,000 (US) or more) So, in short, this looks like it's the cumulative effect of several drivers conflicting. So, you've got IDM and AdblockPlus involved in this. MalwareBytes is also in on it - as is Windows. All of these affect your connection to the internet also. Can you test without MalwareBytes being installed and see if that helps? Also, you may want to test with just the MalwareBytes Web Protection being disabled (if you're using the Premium version) Beyond that, I'd experiment with disabling different things - so that you can download without crashing, and then re-enable whatever you needed to disable
  10. Please run this memory diagnostic: https://www.memtest86.com/download.htm Run the test for at least 3 full passes Then run this free hard drive diagnostic from within Windows: https://www.seagate.com/support/downloads/seatools/seatools-win-master/ Then run several online antimalware scanning tools (use the online tools in case your system has been infected) Then run this video stress tool: https://www.majorgeeks.com/files/details/furmark.html Select the stress test and make sure you monitor the temps while the stress test is running. If the video temp gets over 100ºC, stop the test Otherwise, run the test until the video temp levels out - and let us know what that temp was If there are no video temps available, run the test for 5-10 minutes and let us know the temps for the rest of the system (the rest of the system shouldn't go over 90ºC) If the system/video starts spitting errors or has video artifacts of any sort - terminate the test and let us know what happened (include the temps) Then run Prime96 (just stress testing) for up to 24 hours (or until the system temps level out) You can get it from here: http://www.mersenne.org/freesoft/ Again, if the system starts spitting errors or has video artifacts/strange behavior - terminate the test and let us know what happened (include the temps) Then run these Video Stress Tests: 1. Thanks to VirGnarus for finding this video memory test: https://simtk.org/home/memtest Alternate download link (w/o registration) located here: http://folding.stanford.edu/English/DownloadUtils 2. Two other video stress tests (may be more stressful than FurMark): NOTE: I have had reports that some ISP's will block this website Video Memory stress Test - http://nvworld.ru/utilities/vmt/ Download the memory test from this link: http://nvworld.ru/files/downloads/utils/vmt.zip (be sure to scan anything downloaded from the internetwith an antivirus BEFORE opening it) Extract it and double click on the vmt.eng.bat file in order to run the English version. Artifact Locator - http://nvworld.ru/utilities/alocator/ Sorry, but I don't read the language that this website is made in. 3. Another interesting test that came to my attention (in English): http://www.ocbase.com/perestroika_en/index.php?Download USE AT YOUR OWN RISK - the program doesn't have a whole bunch of safety features to protect you from yourself![/quote] 4. Dunno if this is a duplicate of one of the above tests - but try this bootable Video Memory Stress Test: http://mikelab.kiev.ua/index_en.php?page=PROGRAMS/vmt_en Then run at least one of these CPU stress tests: Only need to run 1 or 2 of the tests under most circumstances. I haven't used any of the tests myself, so I listed all that I was able to find. - Intel Processor Diagnostic Tool (works in Windows) x64 - http://downloadcenter.intel.com/Detail_Desc.aspx?agr=Y&DwnldID=19792&keyword="cpu+stress+test"&DownloadType=Utilities%2c+Tools+and+Examples&lang=eng x86 - http://downloadcenter.intel.com/Detail_Desc.aspx?agr=Y&DwnldID=19791&keyword="cpu+stress+test"&DownloadType=Utilities%2c+Tools+and+Examples&lang=eng Burn Test - http://downloads.guru3d.com/IntelBurnTest-v2.3-download-2047.html - AMD OverDrive is the recommended solution from AMD - BUT I've seen issues with this program causing BSOD's. Use at your own risk!!! http://sites.amd.com/us/game/downloads/amd-overdrive/pages/overview.aspx - Other Stress Tests: - http://7byte.com/index.php?page=hotcpu - http://www.7byte.com/index.php?page=burnin64 - http://www.overclock.net/general-processor-discussions/657486-cpu-stress-test.html - http://www.fossiltoys.com/cpuload.html - http://www.pcworld.com/downloads/file/fid,7146-order,1-page,1-c,alldownloads/description.html - http://www.overclock.net/general-processor-discussions/657486-cpu-stress-test.html - http://majorgeeks.com/CPU_Stability_Test_d215.html - http://www.xtremesystems.org/forums/showthread.php?t=201670 - the test(s) suggested at this link are bootable: http://www.techsupportforum.com/forums/f15/headless-cpu-stress-testing-393435.html#post2232929
  11. Analysis: The following is for information purposes only. The following information contains the relevant information from the blue screen analysis: **************************Fri Jul 20 14:43:57.533 2018 (UTC - 4:00)************************** Loading Dump File [C:\Users\john\SysnativeBSODApps\072118-8125-01.dmp] Windows 10 Kernel Version 17134 MP (8 procs) Free x64 Built by: 17134.1.amd64fre.rs4_release.180410-1804 System Uptime:0 days 4:42:29.547 *** WARNING: Unable to verify timestamp for mwac.sys *** ERROR: Module load completed but symbols could not be loaded for mwac.sys Probably caused by :memory_corruption BugCheck D1, {50, 2, 0, fffff801ba5d7304} BugCheck Info: DRIVER_IRQL_NOT_LESS_OR_EQUAL (d1) Arguments: Arg1: 0000000000000050, memory referenced Arg2: 0000000000000002, IRQL Arg3: 0000000000000000, value 0 = read operation, 1 = write operation Arg4: fffff801ba5d7304, address which referenced memory BUGCHECK_STR: AV DEFAULT_BUCKET_ID: CODE_CORRUPTION PROCESS_NAME: MBAMService.exe FAILURE_BUCKET_ID: MEMORY_CORRUPTION_LARGE CPUID: "Intel(R) Core(TM) i5-8250U CPU @ 1.60GHz" MaxSpeed: 1600 CurrentSpeed: 1800 Processor may be overclocked! Expected Frequency: 1600 Actual Frequency: 1800 Overclock Ratio: 1.125 BIOS Version V1.05 BIOS Release Date 11/28/2017 Manufacturer Acer Baseboard Manufacturer KBL Product Name Swift SF315-51 Baseboard Product Budweiser_KL ¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨`` 3rd Party Drivers: The following is for information purposes only. My recommendations were given above. The drivers that follow belong to software or devices that were not developed by Microsoft. You can find links to the driver information and where to update the drivers in the section after the code box: **************************Fri Jul 20 14:43:57.533 2018 (UTC - 4:00)************************** MpKsled1dd2ff.sys Mon Feb 27 20:54:41 1989 (2409FBE1) SgrmAgent.sys Thu Feb 2 09:30:36 2012 (4F2A9E0C) SynRMIHID.sys Fri Sep 2 11:55:28 2016 (57C9A0F0) TeeDriverW8x64.sys Tue Apr 4 03:02:36 2017 (58E3450C) afunix.sys Tue Apr 18 10:12:59 2017 (58F61EEB) IntcDAud.sys Tue May 2 10:07:08 2017 (5908928C) igdkmd64.sys Fri Jun 2 10:01:14 2017 (59316FAA) iaStorA.sys Tue Jun 6 12:27:18 2017 (5936D7E6) iaLPSS2_I2C.sys Wed Jun 14 08:13:03 2017 (5941284F) IntcAudioBus.sys Wed Jan 10 10:26:49 2018 (5A5630B9) IntcOED.sys Wed Jan 10 10:28:36 2018 (5A563124) RTKVHD64.sys Thu Feb 8 06:07:31 2018 (5A7C2F73) RtsUer.sys Tue Feb 27 05:55:57 2018 (5A95393D) idmwfp.sys Wed Feb 28 14:33:36 2018 (5A970410) mbamswissarmy.sys Wed Mar 7 10:54:57 2018 (5AA00B51) Netwtw04.sys Tue May 1 03:51:11 2018 (5AE81C6F) ibtusb.sys Fri May 4 12:49:23 2018 (5AEC8F13) RadioShim.sys Sun May 6 23:27:08 2018 (5AEFC78C) LMDriver.sys Sun May 6 23:27:08 2018 (5AEFC78C) mbam.sys Thu May 24 03:32:55 2018 (5B066AA7) mbae64.sys Wed May 30 07:20:29 2018 (5B0E88FD) MbamChameleon.sys Thu Jun 14 17:21:45 2018 (5B22DC69) farflt.sys Thu Jun 14 18:32:25 2018 (5B22ECF9) mwac.sys Tue Jul 3 14:20:18 2018 (5B3BBE62) dump_dumpstorport.sys Fri Aug 8 06:06:57 2025 (6895CC41) dump_stornvme.sys Sat May 13 20:35:07 2028 (6DC8D13B) intelppm.sys ***** Invalid 2019 Invalid 2019 Invalid MpKsled1dd2ff.sys - this driver hasn't been added to the DRT as of this run. Please search Google/Bing for the driver if additional information is needed. SgrmAgent.sys - this driver hasn't been added to the DRT as of this run. Please search Google/Bing for the driver if additional information is needed. http://www.carrona.org/drivers/driver.php?id=SynRMIHID.sys http://www.carrona.org/drivers/driver.php?id=TeeDriverW8x64.sys afunix.sys - this driver hasn't been added to the DRT as of this run. Please search Google/Bing for the driver if additional information is needed. http://www.carrona.org/drivers/driver.php?id=IntcDAud.sys http://www.carrona.org/drivers/driver.php?id=igdkmd64.sys http://www.carrona.org/drivers/driver.php?id=iaStorA.sys iaLPSS2_I2C.sys - this driver hasn't been added to the DRT as of this run. Please search Google/Bing for the driver if additional information is needed. IntcAudioBus.sys - this driver hasn't been added to the DRT as of this run. Please search Google/Bing for the driver if additional information is needed. IntcOED.sys - this driver hasn't been added to the DRT as of this run. Please search Google/Bing for the driver if additional information is needed. http://www.carrona.org/drivers/driver.php?id=RTKVHD64.sys http://www.carrona.org/drivers/driver.php?id=RtsUer.sys http://www.carrona.org/drivers/driver.php?id=idmwfp.sys http://www.carrona.org/drivers/driver.php?id=mbamswissarmy.sys Netwtw04.sys - this driver hasn't been added to the DRT as of this run. Please search Google/Bing for the driver if additional information is needed. http://www.carrona.org/drivers/driver.php?id=ibtusb.sys http://www.carrona.org/drivers/driver.php?id=RadioShim.sys http://www.carrona.org/drivers/driver.php?id=LMDriver.sys http://www.carrona.org/drivers/driver.php?id=mbam.sys http://www.carrona.org/drivers/driver.php?id=mbae64.sys http://www.carrona.org/drivers/driver.php?id=MbamChameleon.sys http://www.carrona.org/drivers/driver.php?id=farflt.sys http://www.carrona.org/drivers/driver.php?id=mwac.sys dump_dumpstorport.sys - this driver hasn't been added to the DRT as of this run. Please search Google/Bing for the driver if additional information is needed. dump_stornvme.sys - this driver hasn't been added to the DRT as of this run. Please search Google/Bing for the driver if additional information is needed. http://www.carrona.org/drivers/driver.php?id=intelppm.sys Ensure that Chrome, IDM, AdblockPlus, and MalwareBytes are fully updated to the most recent version(s). Test to figure if it's IDM/AdblockPlus/or a combination of the two. Disable/uninstall AdblockPlus and see if the error occurs w/IDM Disable/uninstall IDM (with AdblockPlus reinstalled) and see if the error occurs w/AdblockPlus You've also had several BSOD's that are related to video, and one related to USB3 Due to the variety of BSOD's, I also have to wonder about hardware problems. I''d start with the stuff I suggested in the first 2 paragraphs. After that, I'd try hardware diagnostics. Start with these tests first: http://www.carrona.org/hwdiag.html
  12. usasma

    BSOD netio.sys driver failure

    The last 2 memory dumps are Driver Verifier enabled dumps One still blames NETIO.sys, while the other blames igdkmd64.sys So, the possibilities are: - XBox stuff is still installed - please uninstall it. - an unknown driver/program is performing a function that causes the BSOD - a hardware problem - a Windows problem (least likely) Have you run the hardware diagnostics? If so, what were the results? Have you disabled the devices that I suggested? Did you disable/remove everything, or just some of it? I would suggest running a Clean Boot to see if that helps at all: Perform a Clean Boot: http://www.thewindowsclub.com/what-is-clean-boot-state-in-windows If that stops the problem, then re-enable things a few at a time until you figure out what's causing it. Then uninstall the problem program (from Start...Settings...Apps...Apps & Features - if you don't find it there, check the right sidebar for Programs and Features and see if you can remove it from there). If it does not stop the problem, then we're looking at a clean install of Windows to help rule out problems: A clean install is: - Windows is installed to a freshly partitioned hard drive with legitimate installation media (W10: https://www.microsoft.com/en-us/software-download/windows10 ). - The installation media is only a copy of Windows, not the OEM recovery disks that you can make on some systems. - Windows is fully updated after it's installed. That's ALL updates - none excepted. - NO 3rd party software is installed. - There are no errors in Device Manager (if you find any, post back for suggestions). This will wipe everything off of the computer, so it's advisable to backup your stuff first. Also, it will wipe out all the special software that the OEM added to the system, so if you rely on any of that - let us know what it is so we can figure out a way to save/download it (the easiest way is to create/obtain the OEM;s recovery media) If unable to find recovery media that has the software (or if you suspect that this is a hardware problem), you can make an image of your system that'll preserve everything in the state that it was in when you made the image. You can also do this if you don't want to try another hard drive - yet you want to be able to return to the current system state. One drawback to this is that you're making an image of a malfunctioning system - so, if there are errors in the system software, you'll have a nice copy of them Another drawback is that the image of the system will be very large - so you'll most likely need a large external drive to store it on. But, this will allow you to save everything on the hard drive (although you'll need an image viewer to get things out of the image). The point here is that, if it's a hardware problem, then you can restore the system to the point it was when you made the image - after you repair the hardware problem. You can obtain more info on imaging in the Backup/Imaging/DiskMgmt forums located here: http://www.bleepingcomputer.com/forums/f/238/backup-imaging-and-disk-management-software/ The point of doing this (the clean install) is to: - rule out Windows as a problem (if the problem continues, it's not a Windows problem as you completely replaced Windows - rule out 3rd party software (if the problem continues, it's not a 3rd party software problem as you didn't install any 3rd party software) - so, if the problem continues, it must be a hardware problem. OTOH, if the problem stops, then it was either a Windows or 3rd party software problem. If the problem doesn't come back, then you've fixed it. Then all that remains is setting the computer back up the way that you'd like it and importing your data from the backup you made. Analysis: The following is for information purposes only. The following information contains the relevant information from the blue screen analysis: **************************Wed Jul 18 11:17:21.056 2018 (UTC - 4:00)************************** Loading Dump File [C:\Users\john\SysnativeBSODApps\071918-90546-01.dmp] Windows 10 Kernel Version 17134 MP (8 procs) Free x64 Built by: 17134.1.amd64fre.rs4_release.180410-1804 System Uptime:0 days 8:23:30.050 *** WARNING: Unable to verify timestamp for igdkmd64.sys *** ERROR: Module load completed but symbols could not be loaded for igdkmd64.sys Probably caused by :memory_corruption BugCheck C4, {140, 0, ffff9601415f0540, fffff80daf982000} BugCheck Info: DRIVER_VERIFIER_DETECTED_VIOLATION (c4) DRIVER_VERIFIER_DETECTED_VIOLATION (c4) Arguments: Arg1: 0000000000000140, subclass of driver violation. Arg2: 0000000000000000 Arg3: ffff9601415f0540 Arg4: fffff80daf982000 BUGCHECK_STR: 0xc4_140 PROCESS_NAME: plugin-container.exe FAILURE_BUCKET_ID: MEMORY_CORRUPTION_LARGE ¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨`` **************************Wed Jul 18 02:53:05.245 2018 (UTC - 4:00)************************** Loading Dump File [C:\Users\john\SysnativeBSODApps\071818-71687-01.dmp] Windows 10 Kernel Version 17134 MP (8 procs) Free x64 Built by: 17134.1.amd64fre.rs4_release.180410-1804 System Uptime:0 days 5:31:32.686 *** WARNING: Unable to verify timestamp for mwac.sys *** ERROR: Module load completed but symbols could not be loaded for mwac.sys Probably caused by :NETIO.SYS ( NETIO!StreamInvokeCalloutAndNormalizeAction+214 ) BugCheck D1, {50, 2, 0, fffff8063e077304} BugCheck Info: DRIVER_IRQL_NOT_LESS_OR_EQUAL (d1) Arguments: Arg1: 0000000000000050, memory referenced Arg2: 0000000000000002, IRQL Arg3: 0000000000000000, value 0 = read operation, 1 = write operation Arg4: fffff8063e077304, address which referenced memory BUGCHECK_STR: AV DEFAULT_BUCKET_ID: VERIFIER_ENABLED_VISTA_MINIDUMP PROCESS_NAME: MBAMService.exe FAILURE_BUCKET_ID: AV_VRF_NETIO!StreamInvokeCalloutAndNormalizeAction ¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨`` 3rd Party Drivers: The following is for information purposes only. My recommendations were given above. The drivers that follow belong to software or devices that were not developed by Microsoft. You can find links to the driver information and where to update the drivers in the section after the code box: **************************Wed Jul 18 11:17:21.056 2018 (UTC - 4:00)************************** DevAuthE.sys Thu Aug 12 04:11:43 1971 (0307A53F) xinputhid.sys Tue Sep 1 23:44:29 2009 (4A9DEA1D) SgrmAgent.sys Thu Feb 2 09:30:36 2012 (4F2A9E0C) HWiNFO64A.SYS Tue Mar 31 05:51:32 2015 (551A6E24) ctxusbm.sys Mon Aug 29 09:14:23 2016 (57C4352F) teVirtualMIDI64.sys Wed Aug 31 05:56:57 2016 (57C6A9E9) ETDSMBus.sys Mon Sep 12 03:17:41 2016 (57D65695) iLokDrvr.sys Mon Dec 12 17:33:49 2016 (584F25CD) afunix.sys Tue Apr 18 10:12:59 2017 (58F61EEB) iaLPSS2_I2C.sys Thu Jun 22 21:13:54 2017 (594C6B52) igdkmd64.sys Tue Oct 17 21:39:02 2017 (59E6B0B6) hpdskflt.sys Sun Nov 19 23:26:13 2017 (5A125965) Accelerometer.sys Sun Nov 19 23:26:28 2017 (5A125974) dptf_cpu.sys Mon Nov 27 17:50:59 2017 (5A1C96D3) esif_lf.sys Mon Nov 27 17:51:12 2017 (5A1C96E0) TeeDriverW8x64.sys Tue Jan 16 09:29:38 2018 (5A5E0C52) iaStorAC.sys Wed Feb 7 03:30:57 2018 (5A7AB941) dump_iaStorAC.sys Wed Feb 7 03:30:57 2018 (5A7AB941) nvvad64v.sys Wed Feb 21 02:45:27 2018 (5A8D2397) SynTP.sys Fri Feb 23 18:39:17 2018 (5A90A625) mbamswissarmy.sys Wed Mar 7 10:54:57 2018 (5AA00B51) RTKVHD64.sys Thu Mar 8 05:57:34 2018 (5AA1171E) WRkrn.sys Mon Mar 19 13:39:19 2018 (5AAFF5C7) paeusbaudio.sys Thu Mar 22 02:51:10 2018 (5AB3525E) paeusbaudioks.sys Thu Mar 22 02:51:41 2018 (5AB3527D) wrUrlFlt.sys Wed Mar 28 07:35:20 2018 (5ABB7DF8) Netwtw04.sys Tue May 1 03:51:11 2018 (5AE81C6F) ibtusb.sys Fri May 4 12:49:23 2018 (5AEC8F13) IntcDAud.sys Mon May 7 07:03:23 2018 (5AF0327B) WirelessButtonDriver64.sys Thu May 10 02:56:38 2018 (5AF3ED26) rt640x64.sys Fri May 11 02:07:38 2018 (5AF5332A) mbam.sys Thu May 24 03:32:55 2018 (5B066AA7) mbae64.sys Wed May 30 07:20:29 2018 (5B0E88FD) MbamChameleon.sys Thu Jun 14 17:21:45 2018 (5B22DC69) farflt.sys Thu Jun 14 18:32:25 2018 (5B22ECF9) nvlddmkm.sys Sun Jun 24 11:38:02 2018 (5B2FBADA) mwac.sys Tue Jul 3 14:20:18 2018 (5B3BBE62) dc1-controller.sys Fri Jan 11 13:42:33 2019 (5C38E399) xboxgip.sys Thu Mar 21 06:51:40 2030 (714497BC) intelppm.sys ***** Invalid 2019 Invalid 2019 Invalid http://www.carrona.org/drivers/driver.php?id=DevAuthE.sys http://www.carrona.org/drivers/driver.php?id=xinputhid.sys SgrmAgent.sys - this driver hasn't been added to the DRT as of this run. Please search Google/Bing for the driver if additional information is needed. http://www.carrona.org/drivers/driver.php?id=HWiNFO64A.SYS http://www.carrona.org/drivers/driver.php?id=ctxusbm.sys teVirtualMIDI64.sys - this driver hasn't been added to the DRT as of this run. Please search Google/Bing for the driver if additional information is needed. http://www.carrona.org/drivers/driver.php?id=ETDSMBus.sys http://www.carrona.org/drivers/driver.php?id=iLokDrvr.sys afunix.sys - this driver hasn't been added to the DRT as of this run. Please search Google/Bing for the driver if additional information is needed. iaLPSS2_I2C.sys - this driver hasn't been added to the DRT as of this run. Please search Google/Bing for the driver if additional information is needed. http://www.carrona.org/drivers/driver.php?id=igdkmd64.sys http://www.carrona.org/drivers/driver.php?id=hpdskflt.sys http://www.carrona.org/drivers/driver.php?id=Accelerometer.sys http://www.carrona.org/drivers/driver.php?id=dptf_cpu.sys http://www.carrona.org/drivers/driver.php?id=esif_lf.sys http://www.carrona.org/drivers/driver.php?id=TeeDriverW8x64.sys iaStorAC.sys - this driver hasn't been added to the DRT as of this run. Please search Google/Bing for the driver if additional information is needed. dump_iaStorAC.sys - this driver hasn't been added to the DRT as of this run. Please search Google/Bing for the driver if additional information is needed. http://www.carrona.org/drivers/driver.php?id=nvvad64v.sys http://www.carrona.org/drivers/driver.php?id=SynTP.sys http://www.carrona.org/drivers/driver.php?id=mbamswissarmy.sys http://www.carrona.org/drivers/driver.php?id=RTKVHD64.sys http://www.carrona.org/drivers/driver.php?id=WRkrn.sys paeusbaudio.sys - this driver hasn't been added to the DRT as of this run. Please search Google/Bing for the driver if additional information is needed. paeusbaudioks.sys - this driver hasn't been added to the DRT as of this run. Please search Google/Bing for the driver if additional information is needed. http://www.carrona.org/drivers/driver.php?id=wrUrlFlt.sys Netwtw04.sys - this driver hasn't been added to the DRT as of this run. Please search Google/Bing for the driver if additional information is needed. http://www.carrona.org/drivers/driver.php?id=ibtusb.sys http://www.carrona.org/drivers/driver.php?id=IntcDAud.sys http://www.carrona.org/drivers/driver.php?id=WirelessButtonDriver64.sys http://www.carrona.org/drivers/driver.php?id=rt640x64.sys http://www.carrona.org/drivers/driver.php?id=mbam.sys http://www.carrona.org/drivers/driver.php?id=mbae64.sys http://www.carrona.org/drivers/driver.php?id=MbamChameleon.sys http://www.carrona.org/drivers/driver.php?id=farflt.sys http://www.carrona.org/drivers/driver.php?id=nvlddmkm.sys http://www.carrona.org/drivers/driver.php?id=mwac.sys http://www.carrona.org/drivers/driver.php?id=dc1-controller.sys http://www.carrona.org/drivers/driver.php?id=xboxgip.sys http://www.carrona.org/drivers/driver.php?id=intelppm.sys
  13. usasma

    BSOD netio.sys driver failure

    The wife’s ankle isn’t as painful as where the horse stepped on her inner thighs/pelvis. That left a hematoma the size of a cantaloupe! i’d leave verifier running simply because it should make BSODs occur faster/more frequently. That way you won’t have to wait as long to see if the things (that you’ve tried) have worked. Sent fm my phone
  14. usasma

    BSOD netio.sys driver failure

    Sorry for the delay in responding. The wife broke her ankle and I've had to take over her chores at the barn for a while. Only 1 of the memory dumps was an actual Verifier enabled dump - but they all blamed the same thing - NETIO.sys There's traces of a MalwareBytes driver in the stack text, but it also has unidentified addresses/functions - which may be the actual cause. It's also possible that this could be a hardware issue. Unfortunately, that makes things very difficult to troubleshoot. I'd start by removing all the XBox stuff - as those drivers are older and are known to be a bit quirky at times. I also wonder about the USB audio stuff (their drivers tend to be a bit quirky also). I'd suggest temporarily removing all of it to see if that helps. Then the easiest route would be to: 1) perform these free hardware diagnostics: http://www.carrona.org/hwdiag.html 2) then try a clean boot ( Perform a Clean Boot: http://www.thewindowsclub.com/what-is-clean-boot-state-in-windows ) If that stops the problem, then re-enable things a few at a time until you figure out what's causing it. Then uninstall the problem program (from Start...Settings...Apps...Apps & Features - if you don't find it there, check the right sidebar for Programs and Features and see if you can remove it from there). Analysis: The following is for information purposes only. The following information contains the relevant information from the blue screen analysis: **************************Sat Jul 14 22:04:15.362 2018 (UTC - 4:00)************************** Loading Dump File [C:\Users\john\SysnativeBSODApps\071518-79109-01.dmp] Windows 10 Kernel Version 17134 MP (8 procs) Free x64 Built by: 17134.1.amd64fre.rs4_release.180410-1804 System Uptime:0 days 0:11:14.337 *** WARNING: Unable to verify timestamp for mwac.sys *** ERROR: Module load completed but symbols could not be loaded for mwac.sys Probably caused by :NETIO.SYS ( NETIO!StreamInvokeCalloutAndNormalizeAction+214 ) BugCheck D1, {50, 2, 0, fffff808e8dd7304} BugCheck Info: DRIVER_IRQL_NOT_LESS_OR_EQUAL (d1) Arguments: Arg1: 0000000000000050, memory referenced Arg2: 0000000000000002, IRQL Arg3: 0000000000000000, value 0 = read operation, 1 = write operation Arg4: fffff808e8dd7304, address which referenced memory BUGCHECK_STR: AV DEFAULT_BUCKET_ID: VERIFIER_ENABLED_VISTA_MINIDUMP PROCESS_NAME: MBAMService.exe FAILURE_BUCKET_ID: AV_VRF_NETIO!StreamInvokeCalloutAndNormalizeAction ¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨`` **************************Sat Jul 14 21:51:33.845 2018 (UTC - 4:00)************************** Loading Dump File [C:\Users\john\SysnativeBSODApps\071518-88890-01.dmp] Windows 10 Kernel Version 17134 MP (8 procs) Free x64 Built by: 17134.1.amd64fre.rs4_release.180410-1804 System Uptime:0 days 20:24:01.814 *** WARNING: Unable to verify timestamp for mwac.sys *** ERROR: Module load completed but symbols could not be loaded for mwac.sys Probably caused by :memory_corruption BugCheck D1, {50, 2, 0, fffff80a15817304} BugCheck Info: DRIVER_IRQL_NOT_LESS_OR_EQUAL (d1) Arguments: Arg1: 0000000000000050, memory referenced Arg2: 0000000000000002, IRQL Arg3: 0000000000000000, value 0 = read operation, 1 = write operation Arg4: fffff80a15817304, address which referenced memory BUGCHECK_STR: AV DEFAULT_BUCKET_ID: CODE_CORRUPTION PROCESS_NAME: MBAMService.exe FAILURE_BUCKET_ID: MEMORY_CORRUPTION_LARGE ¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨`` **************************Thu Jul 12 06:48:07.070 2018 (UTC - 4:00)************************** Loading Dump File [C:\Users\john\SysnativeBSODApps\071218-52140-01.dmp] Windows 10 Kernel Version 17134 MP (8 procs) Free x64 Built by: 17134.1.amd64fre.rs4_release.180410-1804 System Uptime:0 days 22:39:28.317 *** WARNING: Unable to verify timestamp for mwac.sys *** ERROR: Module load completed but symbols could not be loaded for mwac.sys Probably caused by :NETIO.SYS ( NETIO!StreamInvokeCalloutAndNormalizeAction+5c ) BugCheck D1, {8, 2, 0, fffff8043b36714c} BugCheck Info: DRIVER_IRQL_NOT_LESS_OR_EQUAL (d1) Arguments: Arg1: 0000000000000008, memory referenced Arg2: 0000000000000002, IRQL Arg3: 0000000000000000, value 0 = read operation, 1 = write operation Arg4: fffff8043b36714c, address which referenced memory BUGCHECK_STR: AV DEFAULT_BUCKET_ID: VERIFIER_ENABLED_VISTA_MINIDUMP PROCESS_NAME: MBAMService.exe FAILURE_BUCKET_ID: AV_VRF_NETIO!StreamInvokeCalloutAndNormalizeAction CPUID: "Intel(R) Core(TM) i7-6700HQ CPU @ 2.60GHz" MaxSpeed: 2600 CurrentSpeed: 2592 BIOS Version F.48 BIOS Release Date 06/22/2018 Manufacturer HP Product Name OMEN by HP Laptop Baseboard Product 825B ¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨`` 3rd Party Drivers: The following is for information purposes only. My recommendations were given above. The drivers that follow belong to software or devices that were not developed by Microsoft. You can find links to the driver information and where to update the drivers in the section after the code box: **************************Sat Jul 14 22:04:15.362 2018 (UTC - 4:00)************************** DevAuthE.sys Thu Aug 12 04:11:43 1971 (0307A53F) xinputhid.sys Tue Sep 1 23:44:29 2009 (4A9DEA1D) SgrmAgent.sys Thu Feb 2 09:30:36 2012 (4F2A9E0C) dptf_cpu.sys Wed Aug 10 14:43:11 2016 (57AB75BF) esif_lf.sys Wed Aug 10 14:43:26 2016 (57AB75CE) ctxusbm.sys Mon Aug 29 09:14:23 2016 (57C4352F) teVirtualMIDI64.sys Wed Aug 31 05:56:57 2016 (57C6A9E9) iaStorA.sys Tue Sep 13 10:45:46 2016 (57D8111A) iLokDrvr.sys Mon Dec 12 17:33:49 2016 (584F25CD) RTKVHD64.sys Tue Dec 20 05:28:35 2016 (585907D3) afunix.sys Tue Apr 18 10:12:59 2017 (58F61EEB) iaLPSS2i_I2C.sys Wed Jun 14 00:00:59 2017 (5940B4FB) igdkmd64.sys Tue Oct 17 21:39:02 2017 (59E6B0B6) TeeDriverW8x64.sys Sun Nov 19 06:39:59 2017 (5A116D8F) hpdskflt.sys Sun Nov 19 23:26:13 2017 (5A125965) Accelerometer.sys Sun Nov 19 23:26:28 2017 (5A125974) ibtusb.sys Tue Dec 5 23:53:12 2017 (5A2777B8) SynTP.sys Fri Feb 23 18:39:17 2018 (5A90A625) Smb_driver_Intel.sys Fri Feb 23 18:44:42 2018 (5A90A76A) mbamswissarmy.sys Wed Mar 7 10:54:57 2018 (5AA00B51) Netwtw04.sys Wed Mar 14 08:51:04 2018 (5AA91AB8) WRkrn.sys Mon Mar 19 13:39:19 2018 (5AAFF5C7) paeusbaudio.sys Thu Mar 22 02:51:10 2018 (5AB3525E) paeusbaudioks.sys Thu Mar 22 02:51:41 2018 (5AB3527D) wrUrlFlt.sys Wed Mar 28 07:35:20 2018 (5ABB7DF8) WirelessButtonDriver64.sys Thu May 10 02:56:38 2018 (5AF3ED26) rt640x64.sys Fri May 11 02:07:38 2018 (5AF5332A) mbam.sys Thu May 24 03:32:55 2018 (5B066AA7) mbae64.sys Wed May 30 07:20:29 2018 (5B0E88FD) MbamChameleon.sys Thu Jun 14 17:21:45 2018 (5B22DC69) farflt.sys Thu Jun 14 18:32:25 2018 (5B22ECF9) nvlddmkm.sys Sun Jun 24 11:38:02 2018 (5B2FBADA) mwac.sys Tue Jul 3 14:20:18 2018 (5B3BBE62) dc1-controller.sys Fri Jan 11 13:42:33 2019 (5C38E399) xboxgip.sys Thu Mar 21 06:51:40 2030 (714497BC) intelppm.sys ***** Invalid 2019 Invalid 2019 Invalid ¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨`` **************************Thu Jul 12 06:48:07.070 2018 (UTC - 4:00)************************** mbae64.sys Tue Mar 27 11:15:46 2018 (5ABA6022) audientusbaudio.sys Wed Mar 28 06:19:23 2018 (5ABB6C2B) audientusbaudioks.sys Wed Mar 28 06:19:58 2018 (5ABB6C4E) mbam.sys Sat Apr 7 14:55:35 2018 (5AC91427) MbamChameleon.sys Wed Apr 25 15:39:20 2018 (5AE0D968) IntcDAud.sys Mon May 7 07:03:23 2018 (5AF0327B) farflt.sys Mon May 14 11:15:27 2018 (5AF9A80F) mwac.sys Wed May 16 09:52:49 2018 (5AFC37B1) http://www.carrona.org/drivers/driver.php?id=DevAuthE.sys http://www.carrona.org/drivers/driver.php?id=xinputhid.sys SgrmAgent.sys - this driver hasn't been added to the DRT as of this run. Please search Google/Bing for the driver if additional information is needed. http://www.carrona.org/drivers/driver.php?id=dptf_cpu.sys http://www.carrona.org/drivers/driver.php?id=esif_lf.sys http://www.carrona.org/drivers/driver.php?id=ctxusbm.sys teVirtualMIDI64.sys - this driver hasn't been added to the DRT as of this run. Please search Google/Bing for the driver if additional information is needed. http://www.carrona.org/drivers/driver.php?id=iaStorA.sys http://www.carrona.org/drivers/driver.php?id=iLokDrvr.sys http://www.carrona.org/drivers/driver.php?id=RTKVHD64.sys afunix.sys - this driver hasn't been added to the DRT as of this run. Please search Google/Bing for the driver if additional information is needed. http://www.carrona.org/drivers/driver.php?id=iaLPSS2i_I2C.sys http://www.carrona.org/drivers/driver.php?id=igdkmd64.sys http://www.carrona.org/drivers/driver.php?id=TeeDriverW8x64.sys http://www.carrona.org/drivers/driver.php?id=hpdskflt.sys http://www.carrona.org/drivers/driver.php?id=Accelerometer.sys http://www.carrona.org/drivers/driver.php?id=ibtusb.sys http://www.carrona.org/drivers/driver.php?id=SynTP.sys http://www.carrona.org/drivers/driver.php?id=Smb_driver_Intel.sys http://www.carrona.org/drivers/driver.php?id=mbamswissarmy.sys Netwtw04.sys - this driver hasn't been added to the DRT as of this run. Please search Google/Bing for the driver if additional information is needed. http://www.carrona.org/drivers/driver.php?id=WRkrn.sys paeusbaudio.sys - this driver hasn't been added to the DRT as of this run. Please search Google/Bing for the driver if additional information is needed. paeusbaudioks.sys - this driver hasn't been added to the DRT as of this run. Please search Google/Bing for the driver if additional information is needed. http://www.carrona.org/drivers/driver.php?id=wrUrlFlt.sys http://www.carrona.org/drivers/driver.php?id=WirelessButtonDriver64.sys http://www.carrona.org/drivers/driver.php?id=rt640x64.sys http://www.carrona.org/drivers/driver.php?id=mbam.sys http://www.carrona.org/drivers/driver.php?id=mbae64.sys http://www.carrona.org/drivers/driver.php?id=MbamChameleon.sys http://www.carrona.org/drivers/driver.php?id=farflt.sys http://www.carrona.org/drivers/driver.php?id=nvlddmkm.sys http://www.carrona.org/drivers/driver.php?id=mwac.sys http://www.carrona.org/drivers/driver.php?id=dc1-controller.sys http://www.carrona.org/drivers/driver.php?id=xboxgip.sys http://www.carrona.org/drivers/driver.php?id=intelppm.sys http://www.carrona.org/drivers/driver.php?id=mbae64.sys audientusbaudio.sys - this driver hasn't been added to the DRT as of this run. Please search Google/Bing for the driver if additional information is needed. audientusbaudioks.sys - this driver hasn't been added to the DRT as of this run. Please search Google/Bing for the driver if additional information is needed. http://www.carrona.org/drivers/driver.php?id=mbam.sys http://www.carrona.org/drivers/driver.php?id=MbamChameleon.sys http://www.carrona.org/drivers/driver.php?id=IntcDAud.sys http://www.carrona.org/drivers/driver.php?id=farflt.sys http://www.carrona.org/drivers/driver.php?id=mwac.sys
  15. usasma

    BSOD netio.sys driver failure

    Why weren't you prompted by the Support Assistant to download a BIOS update? Well, first there's the debate between technicians about updating the BIOS. Some believe it's not necessary, while others believe it is. IMO it is necessary simply because the newer BIOS's (UEFI's) communicate more with the OS than previously. At work I update the BIOS's on all W8 and W10 systems. I carefully choose whether to update the BIOS on W7 and earlier systems based on the problems that the system is having. I've been working on computers since the days of DOS, and have been employed as a technician since the days of XP. I've witnessed the OEM updater software improving over the years. HP, Dell, and Lenovo currenty have the best updaters IMO - but they are far from perfect. They're also affected by their ability to obtain updates released by the device developers (Intel, AMD, Realtek, etc) At work we manually update the BIOS, and let Windows Update and the OEM updaters handle the rest of the updates. You can manually check for updates as jcgriff2 states - but that's beyond what most users want to do with their systems. That's why we set Windows Updates and OEM Updates to work automatically on systems at work. You'll notice that quite a few of the drivers that the OEM uses (such as HP) are customized after they get them from the developer. If you use these customized features, then you'll need to get the drivers from HP. If you don't use the customized features, then you can get them from the developers support site (if available). Next, Windows Update is becoming a much more important source of driver updates as manufacturers and developers are providing driver packages to Microsoft on a more regular basis. It's such a good program (IMO) that the OEM's will refer you to Windows Update if they don't want to provide the drivers themselves. Finally, I've seen this sort of work done with USB audio cards in the past. There's 2 sets of problems that you have to be aware of: 1) That USB audio cards are touchy when it comes to software. Using outdated software can cause many different problems - so it's important to keep ALL audio programs updated (such as the BOME MIDI utility). If not, then you'll end up having problems that will blame the USB drivers or the USB audio drivers 2) Any devices that are disabled in Device Manager will still load their drivers when Windows starts. Later on in the startup process, the drivers will be disabled - but still occupy memory and can be interacted with (in a limited way since they are disabled). The point here is that these drivers can still cause problems (we've seen BSOD's caused by disable drivers in the past) and you need to continue to update them also - or you may find yourself having problems due to the disable drivers. Good luck!
×

Important Information

This site uses cookies - We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue.