Hi yant28 ,
Welcome to the Ten Forums BSOD forum.
BSOD can be caused by problems with hardware or software drivers or hardware.
One of the BSOD displayed WHEA 0x124 which is typically a hardware problem.
The other BSOD displayed hardware drivers.
The plan is the fix the hardware drivers and check the computer's major hardware components.
This includes CPU, GPU, Drives, and RAM.
The PSU will all be checked.
For all tests please make sure that images are posted into the thread.
If you have difficulty posting an image please use one drive or drop box share links.
Open administrative command prompt and type or copy and paste:
1) sfc /scannow
2) dism /online /cleanup-image /restorehealth
3) 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 edit then copy > paste into the thread
4) Make sure that there is no over clocking while troubleshooting.
5) Sometimes there are problems in the bios that produce bsod.
The BIOS: Version/Date American Megatrends Inc. 2702, 2015-10-27
6) Please check to see if this is the most up to date version.
When you check the status of the bios please post a URL into the thread for the drivers.
7) To ensure that there are no improper bios settings please reset the bios.
8) Sometimes there can be failure to boot after resetting the bios.
9) So please make sure your files are backed up.
10) Please make a backup image with Macrium:
Macrium Software | Macrium Reflect Free:
Macrium Software | Your Image is Everything
Macrium Software | Macrium Reflect Free
11) And please create a brand new 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
12) 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:
13) Choose one of the temperature monitoring software applications: Speecy, HW monitor, Speed fan:
Speccy - Free Download - Piriform: Speccy - System Information - Free
Speccy - System Information - Free Download
HWMONITOR | Softwares | CPUID: HWMONITOR | Softwares | CPUID
HWMONITOR | Softwares | CPUID
SpeedFan - Access temperature sensor in your computer: SpeedFan - Access temperature sensor in your computer
SpeedFan - Access temperature sensor in your computer
14) Run Prime95 - Stress Test Your CPU
Prime95 - Stress Test Your CPU Windows 10 Performance Maintenance Tutorials
Prime95 - Stress Test Your CPU Performance Maintenance Tutorials
Aim to test for > 3 hours.
15) Record maximum temperatures and duration of testing.
16) Please use the Microsoft snipping tool to post images into the thread.
Take Screenshot in Windows 10 Windows 10 General Tips Tutorials
Take Screenshot in Windows 10 General Tips Tutorials
17) Run memtest86+ version 5.01 for at least 8 passes.
Memtest86+ - Advanced Memory Diagnostic Tool
This may take hours so plan to run it overnight.
Please make sure you use the Memtest86+ version 5.01 with the link below.
Memtest86+ - Advanced Memory Diagnostic Tool
The testing is done not by time but by passes.
The more passes the better.
There are a significant number of false negatives if fewer than 8 passes are made.
A false negative is a test pass when there is malfunctioning RAM.
There is 16 GB of RAM on the computer.
Memtest86+ version 5.01 testing takes approximately 1 - 2 hours /GB RAM
Just 1 error is a fail and you can abort testing.
Then test 1 RAM module at a time in the same DIMM each for 8 or more passes.
When Memtest86+ has completed 8 or more passes use a camera or smart phone camera to take a picture and post an image into the thread.
Memory problems. - Microsoft Community
MemTest86+ - Test RAM BSOD Tutorials
19) Run HD Sentinel: (free or trial edition)
Hard Disk Sentinel - HDD health and temperature monitoring
When it has completed please use the Microsoft snipping to make images and post them into the thread.
Please post images for overview, smart, and disk performance tabs.
Click on disk > surface test > post image
Click on disk > extended self test > post image (if extended is not available run short) > post image
Take Screenshot in Windows 10 Windows 10 General Tips Tutorials
Take Screenshot in Windows 10 General Tips Tutorials
20) 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.
Aim to test for 1 hour.
FurMark - GPU Stress Test Windows 10 Performance Maintenance Tutorials:
FurMark - GPU Stress Test Performance Maintenance Tutorials
21) All of these test should be done with the bios reset and no over clocking.
22) For each of the above tests please record maximum temperatures and test duration.
24) And please make sure that you use the Microsoft snipping tool to post images of each into the thread.
Take Screenshot in Windows 10 Windows 10 General Tips Tutorials
24) Open administrative command prompt and type or copy and paste: chkdsk /x /f /r
This may take many hours to run so plan to run it overnight.
25) Post the chkdsk results into the thread:
Read Chkdsk Log in Event Viewer in Windows 10 Windows 10 Performance Maintenance Tutorials
26) The best way to fix the misbehaving Nvidia driver is to uninstall everything Nvidia using Display driver uninstaller and install new drivers from the computer manufacturer's website or from the Nvidia website.
The computer manufacturer's web site is preferred. Enter the computer's serial or product number and the operating system to view available drivers.
If you use the Nvidia web site be sure the "clean install" box is checked and only install the graphics driver and the physx driver.
Official Display Driver Uninstaller DDU Download
Display Driver Uninstaller Download version 17.0.7.2
Display Driver Uninstaller: How to use - Windows 7 Help Forums
NVIDIA
27) Update Rtwlanu.sys: Realtek Wireless LAN
Updating a driver: Updating a driver. - Microsoft Community
Code:
2017-10-29 5:58 PM Windows Error Reporting Fault bucket 0x124_GenuineIntel_PROCESSOR_CACHE, type 0
Event Name: BlueScreen
Response: Non disponible
Cab Id: 2da78f08-69e3-4a8a-8e4f-5e33f1d1aad4
Problem signature:
P1: 124
P2: 0
P3: ffff9e0d613a8028
P4: bf800000
P5: 124
P6: 10_0_16299
P7: 0_0
P8: 768_1
P9:
P10:
Attached files:
\\?\C:\Windows\Minidump\102917-3578-01.dmp
\\?\C:\Windows\TEMP\WER-7203-0.sysdata.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER253B.tmp.WERInternalMetadata.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER254A.tmp.csv
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER255B.tmp.txt
These files may be available here:
C:\ProgramData\Microsoft\Windows\WER\ReportArchive\Kernel_124_7df3b5ff8aca1325d3c9122943605e29e52c3b57_00000000_cab_1c41bc46
Analysis symbol:
Rechecking for solution: 0
Report ID: a7088762-5ebb-42f9-ba76-202db775222e
Report Status: 268435456
Hashed bucket:2017-10-28 8:59 PM Windows Error Reporting Fault bucket 0x124_GenuineIntel_PROCESSOR_CACHE, type 0
Event Name: BlueScreen
Response: Non disponible
Cab Id: 4af87283-58c9-4a59-8c74-777dc408014f
Problem signature:
P1: 124
P2: 0
P3: ffffa98860d40028
P4: bf800000
P5: 124
P6: 10_0_16299
P7: 0_0
P8: 768_1
P9:
P10:
Attached files:
\\?\C:\Windows\Minidump\102817-3796-01.dmp
\\?\C:\Windows\TEMP\WER-7484-0.sysdata.xml
\\?\C:\Windows\MEMORY.DMP
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER26A2.tmp.WERInternalMetadata.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER26B2.tmp.csv
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER2711.tmp.txt
These files may be available here:
C:\ProgramData\Microsoft\Windows\WER\ReportArchive\Kernel_124_9cafa386c5d2e2b3abb2e9fd13c01c75e67ba784_00000000_cab_16284af3
Analysis symbol:
Rechecking for solution: 0
Report ID: eb85698a-94f2-4f1b-8b8b-e5b6b018f91c
Report Status: 268435456
Hashed bucket:
2017-10-29 5:59 PM Windows Error Reporting Fault bucket 0x9F_3_POWER_DOWN_ndis!ndisQuerySetMiniportEx, type 0
Event Name: BlueScreen
Response: Non disponible
Cab Id: 145c18ac-5ab4-49db-acea-f00685baa262
Problem signature:
P1: 9f
P2: 3
P3: ffffdd04c0a42be0
P4: ffffd907b60378f0
P5: ffffdd04c1f4ba20
P6: 10_0_16299
P7: 0_0
P8: 768_1
P9:
P10:
Attached files:
\\?\C:\Windows\Minidump\102917-12781-01.dmp
\\?\C:\Windows\TEMP\WER-16312-0.sysdata.xml
\\?\C:\Windows\MEMORY.DMP
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER496C.tmp.WERInternalMetadata.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER497C.tmp.csv
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER499C.tmp.txt
These files may be available here:
C:\ProgramData\Microsoft\Windows\WER\ReportArchive\Kernel_9f_e594296b98c1dbee9eeda3deead191e43dfb79b_00000000_cab_1c4222c0
Analysis symbol:
Rechecking for solution: 0
Report ID: 5cef172a-dbf9-4a28-a1f5-52f406fe2187
Report Status: 268435456
Hashed bucket:
Code:
2017-10-28 9:44 PM Windows Error Reporting Fault bucket LKD_0x141_Tdr:6_IMAGE_nvlddmkm.sys_Maxwell, type 0
Event Name: LiveKernelEvent
Response: Non disponible
Cab Id: 782e7c05-9289-48fe-bd01-a7574b14a3ce
Problem signature:
P1: 141
P2: ffff9e0d76d204a0
P3: fffff808bcab6478
P4: 0
P5: 2044
P6: 10_0_16299
P7: 0_0
P8: 768_1
P9:
P10:
Attached files:
\\?\C:\Windows\LiveKernelReports\WATCHDOG\WATCHDOG-20171028-1744.dmp
\\?\C:\Windows\TEMP\WER-105171-0.sysdata.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERA524.tmp.WERInternalMetadata.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERA526.tmp.csv
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERA537.tmp.txt
\\?\C:\Windows\Temp\WERD00D.tmp.WERDataCollectionStatus.txt
These files may be available here:
C:\ProgramData\Microsoft\Windows\WER\ReportArchive\Kernel_141_b42eacccca731e7df55830455bcffc9bdaf9da_00000000_cab_1d9dd174
Analysis symbol:
Rechecking for solution: 0
Report ID: 5173ca43-2efd-4029-8cfa-927fd1c96b6e
Report Status: 268435456
Hashed bucket:2017-10-29 5:59 PM Windows Error Reporting Fault bucket LKD_0x15E_MINI_StuckOID_D010311_rtwlanu!unknown_function, type 0
Event Name: LiveKernelEvent
Response: Non disponible
Cab Id: e01a2b17-fcf2-4a0e-8cbb-094626b844f7
Problem signature:
P1: 1000015e
P2: 25
P3: 23
P4: ffffdd04c6a36238
P5: d010311
P6: 10_0_16299
P7: 0_0
P8: 768_1
P9:
P10:
Attached files:
\\?\C:\Windows\LiveKernelReports\NDIS\NDIS-20171029-0109.dmp
\\?\C:\Windows\TEMP\WER-1401578-0.sysdata.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER6962.tmp.WERInternalMetadata.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER6962.tmp.csv
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER6963.tmp.txt
\\?\C:\Windows\Temp\WERFF9A.tmp.WERDataCollectionStatus.txt
These files may be available here:
C:\ProgramData\Microsoft\Windows\WER\ReportArchive\Kernel_1000015e_c3c3a9965d4b98d936d0a067eb9de876c6812adb_00000000_cab_1c42019c
Analysis symbol:
Rechecking for solution: 0
Report ID: e0e46f89-f5f3-4595-953c-4518c3108e40
Report Status: 268435456
Hashed bucket:
Code:
2017-10-29 4:46 AM Windows Error Reporting Fault bucket , type 0
Event Name: BlueScreen
Response: Non disponible
Cab Id: 0
Problem signature:
P1: 124
P2: 0
P3: ffff9e0d613a8028
P4: bf800000
P5: 124
P6: 10_0_16299
P7: 0_0
P8: 768_1
P9:
P10:
Attached files:
\\?\C:\Windows\Minidump\102917-3578-01.dmp
\\?\C:\Windows\TEMP\WER-7203-0.sysdata.xml
\\?\C:\Windows\MEMORY.DMP
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER253B.tmp.WERInternalMetadata.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER254A.tmp.csv
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER255B.tmp.txt
These files may be available here:
C:\ProgramData\Microsoft\Windows\WER\ReportQueue\Kernel_124_7df3b5ff8aca1325d3c9122943605e29e52c3b57_00000000_cab_02fc255a
Analysis symbol:
Rechecking for solution: 0
Report ID: a7088762-5ebb-42f9-ba76-202db775222e
Report Status: 4
Hashed bucket:2017-10-28 8:58 PM Windows Error Reporting Fault bucket , type 0
Event Name: BlueScreen
Response: Non disponible
Cab Id: 0
Problem signature:
P1: 124
P2: 0
P3: ffffa98860d40028
P4: bf800000
P5: 124
P6: 10_0_16299
P7: 0_0
P8: 768_1
P9:
P10:
Attached files:
\\?\C:\Windows\Minidump\102817-3796-01.dmp
\\?\C:\Windows\TEMP\WER-7484-0.sysdata.xml
\\?\C:\Windows\MEMORY.DMP
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER26A2.tmp.WERInternalMetadata.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER26B2.tmp.csv
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER2711.tmp.txt
These files may be available here:
C:\ProgramData\Microsoft\Windows\WER\ReportQueue\Kernel_124_9cafa386c5d2e2b3abb2e9fd13c01c75e67ba784_00000000_cab_03182710
Analysis symbol:
Rechecking for solution: 0
Report ID: eb85698a-94f2-4f1b-8b8b-e5b6b018f91c
Report Status: 4
Hashed bucket:
2017-10-29 5:57 PM Windows Error Reporting Fault bucket , type 0
Event Name: BlueScreen
Response: Non disponible
Cab Id: 0
Problem signature:
P1: 9f
P2: 3
P3: ffffdd04c0a42be0
P4: ffffd907b60378f0
P5: ffffdd04c1f4ba20
P6: 10_0_16299
P7: 0_0
P8: 768_1
P9:
P10:
Attached files:
\\?\C:\Windows\Minidump\102917-12781-01.dmp
\\?\C:\Windows\TEMP\WER-16312-0.sysdata.xml
\\?\C:\Windows\MEMORY.DMP
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER496C.tmp.WERInternalMetadata.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER497C.tmp.csv
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER499C.tmp.txt
These files may be available here:
C:\ProgramData\Microsoft\Windows\WER\ReportQueue\Kernel_9f_e594296b98c1dbee9eeda3deead191e43dfb79b_00000000_cab_0314499b
Analysis symbol:
Rechecking for solution: 0
Report ID: 5cef172a-dbf9-4a28-a1f5-52f406fe2187
Report Status: 4
Hashed bucket:
Code:
Event[1374]: Log Name: System Source: Display Date: 2017-10-28T17:44:19.145 Event ID: 4101 Task: N/A Level: Warning Opcode: Info Keyword: Classic User: N/A User Name: N/A Computer: DESKTOP-8AU9TNL Description: Display driver nvlddmkm stopped responding and has successfully recovered.
Code:
Event[479]: Log Name: System Source: ACPI Date: 2017-10-28T15:51:15.061 Event ID: 15 Task: N/A Level: Warning Opcode: N/A Keyword: Classic User: N/A User Name: N/A Computer: DESKTOP-8AU9TNL Description: : The embedded controller (EC) returned data when none was requested. The BIOS might be trying to access the EC without synchronizing with the operating system. This data will be ignored. No further action is necessary; however, you should check with your computer manufacturer for an upgraded BIOS.
Code:
Event[1528]: Log Name: System Source: Microsoft-Windows-NDIS Date: 2017-10-29T01:12:36.011 Event ID: 10400 Task: N/A Level: Warning Opcode: Info Keyword: N/A User: N/A User Name: N/A Computer: DESKTOP-8AU9TNL Description: The network interface "ASUS USB-AC56 802.11ac Wireless USB Adapter" has begun resetting. There will be a momentary disruption in network connectivity while the hardware resets. Reason: The network driver did not respond to an OID request in a timely fashion. This network interface has reset 95 time(s) since it was last initialized.
Code:
Event[1966]: Log Name: System Source: Microsoft-Windows-NDIS Date: 2017-10-29T01:27:44.660 Event ID: 10400 Task: N/A Level: Warning Opcode: Info Keyword: N/A User: N/A User Name: N/A Computer: DESKTOP-8AU9TNL Description: The network interface "ASUS USB-AC56 802.11ac Wireless USB Adapter" has begun resetting. There will be a momentary disruption in network connectivity while the hardware resets. Reason: The network driver did not respond to an OID request in a timely fashion. This network interface has reset 494 time(s) since it was last initialized.
Code:
1: kd> !errrec ffff9e0d613a8028===============================================================================
Common Platform Error Record @ ffff9e0d613a8028
-------------------------------------------------------------------------------
Record Id : 01d35035a9df99fb
Severity : Fatal (1)
Length : 928
Creator : Microsoft
Notify Type : Machine Check Exception
Timestamp : 10/29/2017 4:45:46 (UTC)
Flags : 0x00000000
===============================================================================
Section 0 : Processor Generic
-------------------------------------------------------------------------------
Descriptor @ ffff9e0d613a80a8
Section @ ffff9e0d613a8180
Offset : 344
Length : 192
Flags : 0x00000001 Primary
Severity : Fatal
Proc. Type : x86/x64
Instr. Set : x64
Error Type : Cache error
Operation : Generic
Flags : 0x00
Level : 0
CPU Version : 0x00000000000306c3
Processor ID : 0x0000000000000001
===============================================================================
Section 1 : x86/x64 Processor Specific
-------------------------------------------------------------------------------
Descriptor @ ffff9e0d613a80f0
Section @ ffff9e0d613a8240
Offset : 536
Length : 128
Flags : 0x00000000
Severity : Fatal
Local APIC Id : 0x0000000000000001
CPU Id : c3 06 03 00 00 08 10 01 - bf fb fa 7f ff fb eb bf
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 @ ffff9e0d613a8240
===============================================================================
Section 2 : x86/x64 MCA
-------------------------------------------------------------------------------
Descriptor @ ffff9e0d613a8138
Section @ ffff9e0d613a82c0
Offset : 664
Length : 264
Flags : 0x00000000
Severity : Fatal
Error : DCACHEL0_WR_ERR (Proc 1 Bank 1)
Status : 0xbf80000000000124
Address : 0x000000015448a640
Misc. : 0x0000000000000086
Code:
Name [00000004] Linksys WUSB6300Adapter Type Ethernet 802.3
Product Type Linksys WUSB6300
Installed Yes
PNP Device ID USB\VID_13B1&PID_003F\34
Last Reset 10/28/2017 12:17 AM
Index 4
Service Name RtlWlanu
IP Address 192.168.1.239, fe80::951f:cca8:8ab1:f23c
IP Subnet 255.255.255.0, 64
Default IP Gateway 192.168.1.1
DHCP Enabled Yes
DHCP Server 192.168.1.1
DHCP Lease Expires 1/1/1970 8:00 PM
DHCP Lease Obtained 12/31/1969 8:00 PM
MAC Address C8:D7:19:C1:12:1A
Driver c:\windows\system32\drivers\rtwlanu.sys (1030.19.103.2017, 6.35 MB (6,663,640 bytes), 10/19/2017 11:21 PM)
Code:
Name NVIDIA GeForce GTX 970PNP Device ID PCI\VEN_10DE&DEV_13C2&SUBSYS_85081043&REV_A1\4&3834D97&0&0008
Adapter Type GeForce GTX 970, NVIDIA compatible
Adapter Description NVIDIA GeForce GTX 970
Adapter RAM (1,048,576) bytes
Installed Drivers C:\Windows\System32\DriverStore\FileRepository\nv_dispi.inf_amd64_2e44aad2706ac9ff\nvldumdx.dll,C:\Windows\System32\DriverStore\FileRepository\nv_dispi.inf_amd64_2e44aad2706ac9ff\nvldumdx.dll,C:\Windows\System32\DriverStore\FileRepository\nv_dispi.inf_amd64_2e44aad2706ac9ff\nvldumdx.dll,C:\Windows\System32\DriverStore\FileRepository\nv_dispi.inf_amd64_2e44aad2706ac9ff\nvldumdx.dll
Driver Version 23.21.13.8800
INF File oem67.inf (Section110 section)
Colour Planes Not Available
Colour Table Entries 4294967296
Resolution 1920 x 1080 x 60 hertz
Bits/Pixel 32
Memory Address 0xDE000000-0xDEFFFFFF
Memory Address 0xC0000000-0xFEAFFFFF
Memory Address 0xD0000000-0xD1FFFFFF
I/O Port 0x0000E000-0x0000E07F
IRQ Channel IRQ 16
I/O Port 0x000003B0-0x000003BB
I/O Port 0x000003C0-0x000003DF
Memory Address 0xA0000-0xBFFFF
Driver c:\windows\system32\driverstore\filerepository\nv_dispi.inf_amd64_2e44aad2706ac9ff\nvlddmkm.sys (23.21.13.8800, 16.14 MB (16,924,088 bytes), 2017-10-25 4:23 PM)
Code:
RtlWlanu Realtek Wireless LAN 8 Realtek Wireless LAN 8 Kernel Manual Running OK TRUE FALSE 4,096 3,280,896 0 2017-08-04 1:47:48 AM C:\Windows\system32\drivers\rtwlanu.sys 4,096
Quote