Dalai wrote:Sure, it's possible that there's a correlation. Could it be one of the Windows Updates? Sure. Could it be WSUS Offline? I highly doubt that. WSUS Offline uses official interfaces and mechanisms to install updates. I even think that it's likely that you would have gotten the BSOD if you had used Windows Update itself.
Regards
Dalai
Alright, interesting. So I checked with Crystal Disk Info and it says that my drives are in Good condition. I am not really sure how to read Windows Event Viewer. I do however have my BSOD information saved from Bluescreenviewer:
==================================================
Dump File : 122916-7347-01.dmp
Crash Time : 12/29/2016 11:14:42 AM
Bug Check String : KMODE_EXCEPTION_NOT_HANDLED
Bug Check Code : 0x0000001e
Parameter 1 : 00000000`00000000
Parameter 2 : 00000000`00000000
Parameter 3 : 00000000`00000000
Parameter 4 : 00000000`00000000
Caused By Driver : ataport.SYS
Caused By Address : ataport.SYS+15594
File Description :
Product Name :
Company :
File Version :
Processor : x64
Crash Address : ntoskrnl.exe+703d0
Stack Address 1 :
Stack Address 2 :
Stack Address 3 :
Computer Name :
Full Path : C:\Windows\Minidump\122916-7347-01.dmp
Processors Count : 8
Major Version : 15
Minor Version : 7601
Dump File Size : 275,816
Dump File Time : 12/29/2016 11:15:16 AM
==================================================
I understand that this forum is devoted to WSUS, and I apologize if I am starting to go off topic. I am just trying to figure out if this is a driver issue or a hardware issue.
Also, I have not experienced another BSOD since those two incidents.
Thank you for your time.
Edit: One more thing: On various websites I have read that this could be a potential rootkit. I have scanned my PC with Malwarebytes and TDDSKiler, and both have claimed that my PC is clean from Malware. At this point malware may still be a possibility but I kind of doubt it.