Windows 10: BSOD caused by USB (?)

Hello all.Long Story Short:About 2 weeks ago lightning hit really close to my house, a spark went off in the PC and upon restart I found out that my Ethernet port and the network card weren't working anymore.So I bought a USB 3.0 Ethernet Adapter to use my ethernet cable again.I plugged in the adapter and after starting a download (so the adapter was under "heavy load" for like 5 mins) the USB 3.0 port stopped working and the yellow triangle with the exclamation mark popped up near it in the device manager.When I went and pressed "Scan for Hardware Changes" bam! BSOD.I tried multiple times again and it always happens in the same circustances, heavy load, USB 3.0 stops working, if I try to interact with it from device manager, BSOD.So logically I tried to use the USB 2.0 ports instead, since it's compatible with those aswell.Again, if under heavy load, the device stops working, but this time it's not the port, it's just the device, and unplugging it and plugging it back in makes it work again.To verify even further, I tried using another USB adapter, a wireless one. Using it and making it go under load in the 2.0 made the ports not recognize the device anymore (Yes, all of them).
In the 3.0 it replicated the same thing as with the Ethernet one, yellow triangle in device manager and BSOD if I try to interact with it.

I tried updating all drivers for these devices, rolling back to previous ones etc. but to no avail, I really don't know where to bash my head in anymore.

Could this be caused by a damaged PSU/Motherboard after the lightning hit?
Or is it totally something else?
At first I thought it could've been the ethernet adapter, but seeing how the same problem happens with the other one too, I really don't know anymore.

I also noticed that when I view the BSOD info in BlueScreenView there's no entry for the Bug Check String.

Attachment 143285

Sorry for the long post, but I tried to give as much info as possible to identify the problem, thanks to everyone who's gonna offer help!

:)

 

BSOD Caused by ntoskrnl.exe

It doesn't all of a sudden turn of, before it turns of the blue screen error thing pops up first then it restarts. Forgot to mention, blue screens are also much more frequent when I use it in battery saver for some
reason. I did fully remove avast as you posted. Am currently in University so I don't have any fans lying around, but I will go out to get one during the week. It did BSOD once yesterday link 031818-19750-01 1.dmp

 

BSOD Caused by ntoskrnl.exe

The crash dump says a Cache error in the processor was observed:

Error : DCACHEL0_EVICT_ERR (Proc 2 Bank 1)

Status : 0xbb80000000000174

Looks like the processor is either failing or overheating.

BCC124 General guide:

https://answers.microsoft.com/en-us/windows/wik...

Please run IPDT and post back the results:

https://downloadcenter.intel.com/download/19792...

 

The event log is in a foreign language. Please modify the default language to English and re-post the zip files so we can troubleshoot them.
Language - Add, Remove, and Change in Windows 10 Windows 10 General Tips Tutorials

 

Ugh, terribly sorry about that, here you go, should be fine now.

Attachment 143286

 

Code: BugCheck 124, {0, ffffd30bd644b8f8, 0, 0} Probably caused by : AuthenticAMD[/quote]
Code: WHEA_UNCORRECTABLE_ERROR (124) A fatal hardware error has occurred. Parameter 1 identifies the type of error source that reported the error. Parameter 2 holds the address of the WHEA_ERROR_RECORD structure that describes the error conditon. Arguments: Arg1: 0000000000000000, Machine Check Exception Arg2: ffffd30bd644b8f8, Address of the WHEA_ERROR_RECORD structure. Arg3: 0000000000000000, High order 32-bits of the MCi_STATUS value. Arg4: 0000000000000000, Low order 32-bits of the MCi_STATUS value.[/quote]
Code: The system failed to flush data to the transaction log. Corruption may occur in VolumeId: G:, DeviceName: \Device\HarddiskVolume5. (A device which does not exist was specified.)[/quote] Code: Crash dump initialization failed![/quote]
Code: The system failed to flush data to the transaction log. Corruption may occur in VolumeId: G:, DeviceName: \Device\HarddiskVolume5.[/quote]
Code: {Delayed Write Failed} Windows was unable to save all the data for the file \Device\HarddiskVolume5\Games\steamapps\downl .. inematics\videos\golden_path\outro\OUT_050.vib. The data has been lost. This error may be caused by a failure of your computer hardware or network connection. Please try to save this file elsewhere.[/quote]
Code: An error was detected on device \Device\Harddisk3\DR3 during a paging operation.[/quote] Open administrative command prompt and type or copy and paste:


1) winver (in the pop up about windows > view your windows version and build > type this information into the thread)


2) sfc /scannow


3) dism /online /cleanup-image /restorehealth


When these have completed > right click on the top bar or title bar of the administrative command prompt box > left click on edit then select all > right click on the top bar again > left click on copy > paste into the thread


4) chkdsk /x /f /r (this may take many hours to run so plan to run overnight)
Please find the report in eventvwr and post into the thread:
Read Chkdsk Log in Event Viewer in Windows 10 Windows 10 Performance Maintenance Tutorials


5) perform windows updates and post any failed KB# with error code.

Make sure that there is no over clocking while troubleshooting.


Sometimes there are problems in the bios that produce bsod.


The bios in your computer: BIOS Version/Date Award Software International, Inc. FA, 4/23/2013


Please check to see if this is the most up to date version.


To ensure that there are no improper bios settings please reset the bios.


Sometimes there can be failure to boot after resetting the bios.


So please make sure your files are backed up.


Please make a backup image with Macrium:

Macrium Software | Macrium Reflect Free: Macrium Software | Macrium Reflect Free


And please create a restore point.




How to Clear Your Computers CMOS to Reset BIOS Settings:


How to Clear Your Computers CMOS to Reset BIOS Settings


3 Ways to Reset Your BIOS - wikiHow:


3 Ways to Reset Your BIOS - wikiHow




When testing for WHEA hardware errors we need to systematically check CPU, GPU, memory and drive.




Once the bios is reset and there is no overclocking:


Choose one of the temperature monitoring software applications: Speecy, HW monitor, Speed fan:


Speccy - Free Download - Piriform: Speccy - System Information - Free Download


HWMONITOR | Softwares | CPUID: HWMONITOR | Softwares | CPUID


SpeedFan - Access temperature sensor in your computer: SpeedFan - Access temperature sensor in your computer


1) download and install the Intel Processor Diagnostic Tool


When the test completes please use the Microsoft snipping tool to post an image into the thread.


Download Intel® Processor Diagnostic Tool: Download Intel® Processor Diagnostic Tool
The Intel® Processor Diagnostic Tool: The Intel® Processor Diagnostic Tool








2) Run Prime95 - Stress Test Your CPU


Prime95 - Stress Test Your CPU Windows 10 Performance Maintenance Tutorials


Prime95 - Stress Test Your CPU Windows 10 Performance Maintenance Tutorials


Please use the Microsoft snipping tool to post images into the thread.




3) Run memtest86+ version 5.01 for at least 8 runs.


This may take hours so plan to run it overnight.


Memtest86+ - Advanced Memory Diagnostic Tool


Memory problems. - Microsoft Community

MemTest86+ - Test RAM Windows 10 BSOD Tutorials


When Memtest86+ has completed 8 or more runs make an image of the results to post into the thread.


4) Run HD Sentinel:


Hard Disk Sentinel - HDD health and temperature monitoring


When it has completed please use the Microsoft snipping to make an image and post into the thread.




5) Run FurMark - GPU Stress Test Windows 10 Performance Maintenance Tutorials


Please make note of the importance of temperature monitoring and aborting the test in the GPU link.


FurMark - GPU Stress Test Windows 10 Performance Maintenance Tutorials: FurMark - GPU Stress Test Windows 10 Performance Maintenance Tutorials


All of these test should be done with the bios reset and no over clocking.


For each of the above tests please record maximum temperatures.


And please make sure that you use the Microsoft snipping tool to post images of each into the thread.

 

The above post was updated after viewing the event log.

 

Also, the
Code: WHEA_UNCORRECTABLE_ERROR (124) A fatal hardware error has occurred. Parameter 1 identifies the type of error source that reported the error. Parameter 2 holds the address of the WHEA_ERROR_RECORD structure that describes the error conditon. Arguments: Arg1: 0000000000000000, Machine Check Exception Arg2: ffffd802f9b508f8, Address of the WHEA_ERROR_RECORD structure. Arg3: 0000000000000000, High order 32-bits of the MCi_STATUS value. Arg4: 0000000000000000, Low order 32-bits of the MCi_STATUS value.[/quote] Code: 0: kd> !errrec ffffd802f9b508f8 =============================================================================== Common Platform Error Record @ ffffd802f9b508f8 ------------------------------------------------------------------------------- Record Id : 01d2f90294b22510 Severity : Fatal (1) Length : 928 Creator : Microsoft Notify Type : Machine Check Exception Timestamp : 7/9/2017 22:27:44 (UTC) Flags : 0x00000002 PreviousError =============================================================================== Section 0 : Processor Generic ------------------------------------------------------------------------------- Descriptor @ ffffd802f9b50978 Section @ ffffd802f9b50a50 Offset : 344 Length : 192 Flags : 0x00000001 Primary Severity : Fatal Proc. Type : x86/x64 Instr. Set : x64 Error Type : BUS error Operation : Generic Flags : 0x00 Level : 3 CPU Version : 0x0000000000600f20 Processor ID : 0x0000000000000000 =============================================================================== Section 1 : x86/x64 Processor Specific ------------------------------------------------------------------------------- Descriptor @ ffffd802f9b509c0 Section @ ffffd802f9b50b10 Offset : 536 Length : 128 Flags : 0x00000000 Severity : Fatal Local APIC Id : 0x0000000000000000 CPU Id : 20 0f 60 00 00 08 06 00 - 0b 32 98 3e ff fb 8b 17 00 00 00 00 00 00 00 00 - 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 - 00 00 00 00 00 00 00 00 Proc. Info 0 @ ffffd802f9b50b10 =============================================================================== Section 2 : x86/x64 MCA ------------------------------------------------------------------------------- Descriptor @ ffffd802f9b50a08 Section @ ffffd802f9b50b90 Offset : 664 Length : 264 Flags : 0x00000000 Severity : Fatal Error : BUSLG_GENERIC_ERR_*_TIMEOUT_ERR (Proc 0 Bank 4) Status : 0xfe00000000070f0f Address : 0x00000000e0200000 Misc. : 0xc00a0fff01000000[/quote] shows a possible problem with processor 0, Are you over clocking? Are the voltages correct.

Here is a similar problem from a Windows 8.1 system with an AMD processor: http://www.tomshardware.com/answers/...s-64bytes.html

 

tasklist.txt

Line 29

 

Winver: Version 1703 (OS Build 15063.413)

sfc and dism:

Microsoft Windows [Version 10.0.15063](c) 2017 Microsoft Corporation. All rights reserved.C:\Windows\system32>sfc /scannowBeginning system scan. This process will take some time.Beginning verification phase of system scan.Verification 100% complete.Windows Resource Protection did not find any integrity violations.C:\Windows\system32>dism /online /cleanup-image /restorehealthDeployment Image Servicing and Management toolVersion: 10.0.15063.0Image Version: 10.0.15063.0[==========================100.0%==========================] The restore operation completed successfully.The operation completed successfully.C:\Windows\system32>

Windows Update: Says that I'm up to date.

Pretty sure that I never did any overclocking, resetted the BIOS settings aswell anyways.

Gonna run the rest of the tests tonight when I get back home, thanks for the help and the patience.

Also, why the Intel Processor Diag Tool if my processor is AMD?

 

For WHEA error hardware testing you will run:
CPU: Prime95;
GPU: Furmark;
Drive: HD Sentinel;
Memory: Memtest86+ version 5.01
Temperature monitoring: Speecy, HW monitor, or Speed fan

 

Sorry for the late answer but after resetting the BIOS settings I had no more errors, tried to put both the ethernet and wifi adapter under heavy load and they both returned no errors for almost the whole day, which is kinda weird since I didn't fiddle with any BIOS setting in the first place.

I'll keep it monitored for a bit more and mark this as solved if nothing pops up, thanks for the help!

 

Is there any news or did you fix the problem?