StephDragon
Member
Thanks. I'll perform Memtest this night and if nothing comes back I'll try the Driver Verifier the nigh after. So I get back to you tomorrow or in two days with fresh (and I hope interesting) news / dumpfiles.
Looking at the drivers associated with that device, I don't see rtwlanu.sys.
Step #1) Please run these free hardware diagnostics: Hardware Diagnostics
Please run ALL of the tests and let us know the results. (If you can't run all the tests, then at least run these free, bootable diagnostics: Initial Hardware Diagnostics )
FYI - These are the tests and what we usually see for the reports:
1 - Antivirus/antimalware scans: In short, if there are Trojans or other serious malware - start over in the Am I Infected forums
2 - Memory diagnostics: Run MemTest86+ for at least 3 passes. If booting from UEFI, run MemTest86 instead. Let us know if there were any errors reported
3 - Hard Drive diagnostics: Don't sweat the details here. In short, run the Seagate Seatools Long/Extended test from a bootable disk. If unable to run it from a bootable disk (UEFI and some others), then run the Seagate Seatools for Windows from within Windows. There are no diagnostics for SSD's, just run the Crystal Mark tests and let us know if there were any failures
4 - Furmark: run the test until the temperature stabilizes. Don't let it get much over 90ÂşC. Let us know the temp it stabilizes at and if there were any problems running the test (other than slowness).
5 - Prime95: run the Blend test for 24 hours (this may not be possible, but run it as long as you can. Look for errors in the output, or for problems running the test (freezes/crashes)
6 - Video 2 (other video tests): there's several tests here. Run all of them. I'm especially interested in the Video Memory Test. Let us know the results of the test(s)
- A - simtek.org memtest
- B - Video memory stress test
- C - Artifact Locator
- D - OCCT - 4 built in tests for CPU, GPU, PSU
- E - Video Memory Stress Test
7 - CPU tests: run at least one test on your CPU and let us know the result.
Step #2) If all the tests pass, then try to perform a clean install of Windows:A clean install is:
- Windows is installed to a freshly partitioned hard drive with legitimate installation media (W10: Download Windows 10 ).
- 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).
- The BIOS/UEFI is updated to the latest available version (this presumes that the system is compatible w/Windows 10 also).
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: Backup, Imaging, and Disk Management Software Forum - BleepingComputer.com
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.
Step #3) Then, if the clean install confirms the hardware problem, try this procedure to isolate the problem device(s): Hardware Stripdown Troubleshooting
Please run this report collecting tool so that we can provide a complete analysis: (from the pinned topic at the top of the forum) Blue Screen of Death (BSOD) Posting Instructions - Windows 10, 8.1, 8, 7 & Vista - Windows Crashes, BSOD, and Hangs Help and Support
NOTE: On problem systems it can take up to 20 minutes for the log files to complete. Please be patient and let it run.
If you still have problems with it running, there's an alternate tool here (direct download link): https://github.com/blueelvis/BSOD-Inspector/releases/download/1.0.5/BSODInspector-1.0.5.exe
NOTE:
Please zip up the (.ZIP) files - do not use .RAR, .7z or other compression utilities.
.ZIP is the type file that can be uploaded to the forums.
**************************Mon Feb 26 14:36:07.235 2018 (UTC - 5:00)**************************
SSPORT.sys Thu Aug 11 19:07:32 2005 (42FBDA34)
intelppm.sys Thu Sep 22 06:43:11 2011 (4E7B113F)
QIOMem.sys Tue May 5 01:40:35 2015 (554857D3)
RtsP2Stor.sys Mon Jun 1 05:43:03 2015 (556C2927)
Thotkey.sys Tue Aug 4 14:38:15 2015 (55C10697)
TVALZ_O.SYS Wed Sep 9 11:41:43 2015 (55F05337)
CHDRT64.sys Thu Oct 22 02:49:01 2015 (562886DD)
tosrfec.sys Mon Mar 7 04:43:53 2016 (56DD4D59)
ETD.sys Thu May 19 23:19:59 2016 (573E825F)
ETDSMBus.sys Thu May 19 23:24:02 2016 (573E8352)
IntcDAud.sys Thu Dec 1 05:15:06 2016 (583FF82A)
igdkmd64.sys Fri Dec 23 15:04:23 2016 (585D8347)
iaStorA.sys Tue Jun 6 12:27:18 2017 (5936D7E6)
TeeDriverW8x64.sys Sun Nov 19 06:39:59 2017 (5A116D8F)
aswbuniva.sys Mon Dec 4 08:30:42 2017 (5A254E02)
aswbidsdrivera.sys Mon Dec 4 08:30:42 2017 (5A254E02)
aswbidsha.sys Mon Dec 4 08:30:43 2017 (5A254E03)
aswbloga.sys Mon Dec 4 08:30:44 2017 (5A254E04)
nvvad64v.sys Thu Dec 14 00:40:29 2017 (5A320ECD)
ibtusb.sys Fri Jan 5 02:07:36 2018 (5A4F2438)
Netwtw04.sys Wed Jan 10 13:20:55 2018 (5A565987)
nvlddmkm.sys Tue Jan 23 17:24:56 2018 (5A67B638)
rtwlanu.sys Tue Jan 30 20:48:54 2018 (5A712086)
aswArPot.sys Wed Jan 31 13:13:08 2018 (5A720734)
aswRvrt.sys Wed Jan 31 13:13:08 2018 (5A720734)
aswRdr2.sys Wed Jan 31 13:13:37 2018 (5A720751)
aswSnx.sys Wed Jan 31 13:13:38 2018 (5A720752)
aswMonFlt.sys Wed Jan 31 13:30:41 2018 (5A720B51)
aswVmm.sys Wed Jan 31 13:30:43 2018 (5A720B53)
aswSP.sys Wed Jan 31 13:31:01 2018 (5A720B65)
aswHdsKe.sys Wed Jan 31 13:39:09 2018 (5A720D4D)
aswStm.sys Wed Jan 31 13:41:03 2018 (5A720DBF)
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
**************************Sun Feb 25 05:30:24.648 2018 (UTC - 5:00)**************************
rt640x64.sys Thu Jul 14 05:04:28 2016 (5787559C)
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
**************************Sat Feb 24 14:10:15.000 2018 (UTC - 5:00)**************************
lpsport.SYS Tue Jun 6 07:53:57 2017 (593697D5)
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
**************************Fri Feb 23 15:01:22.350 2018 (UTC - 5:00)**************************
rt640x64.sys Tue May 5 12:21:03 2015 (5548EDEF)
TeeDriverW8x64.sys Mon Aug 31 15:49:07 2015 (55E4AFB3)
ibtusb.sys Fri Sep 2 15:37:28 2016 (57C9D4F8)
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
**************************Thu Feb 22 06:03:09.269 2018 (UTC - 5:00)**************************
aswKbd.sys Tue Aug 22 14:02:36 2017 (599C71BC)
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
**************************Wed Feb 21 16:11:39.207 2018 (UTC - 5:00)**************************
RtsP2Stor.sys Mon Aug 15 03:38:21 2016 (57B1716D)
Netwtw04.sys Wed Dec 13 11:22:19 2017 (5A3153BB)
StephDragon,Hi guys,
A huge thanks for your message Usasma. I need some time to perform the recommended actions. I'll get back to you with a first detailed answer very soon.
Yes you can try turning it off there but you can also actually disable the device in the bios and i think that is what John is referring to.Kemical, just to be sure, is it that I need to turn off?
Yes you can try turning it off there but you can also actually disable the device in the bios and i think that is what John is referring to.