Dalai wrote:I don't see any way, WSUS Offline could be responsible for this. All WSUS Offline does is to install Windows updates. It's possible that the driver was updated by some Windows update, but that doesn't necessarily mean that it's responsible for the BSODs. BSODs of this kind may be caused by faulty cables, dying drives, perhaps even corrupt file-systems.
You should check Windows Event Log for any errors and warnings related to the disks. You should also check the SMART attributes of your drives with something like CrystalDiskInfo (the normal portable version is enough).
techgenius wrote:I just did not receive this BSOD until after I began installing updates from WSUS, so I figured there may be some correlation.
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.
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 :
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
aker wrote:As far as I can see, you are running Windows 7 on a Skylake platform (Core i7 6xxx processor). All Windows 7 drivers (and there I mean the internal ones) do not natively support Skylake. Maybe that's the problem.
I needed about 1 week to install Windows 7 on my Skylake notebook (includes the time required for making it not BSODing all the time).
Please make sure, you've got all chipset drivers (including the SerialIO ones, if it is an Intel based motherboard).
Users browsing this forum: No registered users and 5 guests