KERNEL SECURITY CHECK FAILURE BSOD By Unknown Driver

michaelmuliadi · 09 Dec 2017

This will be my 2nd thread after the last resolved one.

It has been several days of peace without bsod until it happened again just now.

I ran driver verifier like I was told and still waiting for the bsod to come

Unlike last time, there isn't any bsod taking place in boot screen, so no IOMANAGER VIOLATION this time

If anyone can help looking for any trace of the culprit please let me know :)

For now I'll attach the newest log, thanks...

zbook · 09 Dec 2017

Please update the system specs in the "My Computer" section:

How To Fill Out Your System Specs
System Specs - Fill in at Ten Forums:
System Specs - Fill in at Ten Forums Site Use Tutorials
In the left corner below in your post you find 'My System Specs'.
After clicking it you can find a link a little below that says 'Update your System Spec', click on this link to get to the page where you can fill in your system specs.
System Info - See Your System Specs - Windows 7 Help Forums

The computer had KMS uninstalled,
There is mismatched RAM.
The logs have entries indicating problems with the drive.
The logs displayed WHEA errors.

Bug Check 0x139 KERNEL_SECURITY_CHECK_FAILURE

Plan:
1) check for malware
2) check operating system integrity
2) check drive with chkdsk and HD Tune
3) check RAM / DIMM / MB

For all tests please post images into the thread.
In case there are any problems posting images please post one drive or drop box share links.

1) Run: ESET: Free Virus Scan | Online Virus Scan from ESET ESET
2) Run: SUERANTISPYWARE: SUPERAntiSpyware | Remove Malware | Remove Spyware - AntiMalware, AntiSpyware, AntiAdware!
3) Run: AdwCleaner: Malwarebytes | AdwCleaner
4) Run: KASPERSKY Tdss killer: https://usa.kaspersky.com/downloads/tdsskiller
5) Run: MALWAREBYTES: Malwarebytes | Free Cyber Security & Anti-Malware Software

6) Open administrative command prompt and type or copy and paste:
7) sfc /scannow
8) dism /online /cleanup-image /restorehealth
9) 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
10) chkdsk /x /f /r
This may take many hours so plan to run overnight.
Use the information in this link to find the report in the event viewer and post the results into the thread.
11) Read Chkdsk Log in Event Viewer in Windows 10 Performance Maintenance Tutorials

12) Run HDTune: http://www.hdtune.com/
to check the health,
scan for errors, no quick scan but full scan
run a benchmark.
It may take some time, but please take the time you need to perform it properly.
When above is done please make screenshots of the following
the health,
the error scan,
the benchmark incl. following
transfer rate,
access time,
burst rate,
cpu usage.
Take Screenshot in Windows 10 General Tips Tutorials

13) 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
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 8 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

14) Open device manager > click on view > show hidden devices > expand all rows > look for any row with a yellow triangle and a black exclamation mark > post an image into the thread

15) In device manager > update all chipset and network drivers:
Updating a driver: Updating a driver. - Microsoft Community

Code:

04/12/2017 09:54    Windows Error Reporting    Fault bucket , type 0
Event Name: BlueScreen
Response: Not available
Cab Id: 0

Problem signature:
P1: 1000007e
P2: ffffffffc0000005
P3: fffff8001064b75d
P4: fffffe8db418f6d8
P5: fffffe8db418ef20
P6: 10_0_16299
P7: 0_0
P8: 768_1
P9: 
P10: 

Attached files:
\\?\C:\WINDOWS\Minidump\120417-28296-01.dmp
\\?\C:\WINDOWS\TEMP\WER-264968-0.sysdata.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER71D1.tmp.WERInternalMetadata.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER7202.tmp.csv
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER7222.tmp.txt

These files may be available here:
C:\ProgramData\Microsoft\Windows\WER\ReportArchive\Kernel_1000007e_f9732f6daafc1812e3b79ce4943f664797fef558_00000000_cab_1cbdadcd

Analysis symbol: 
Rechecking for solution: 0
Report ID: 6eba5667-8302-4cd3-8b09-3ada6789ed45
Report Status: 2049
Hashed bucket:04/12/2017 04:51    Windows Error Reporting    Fault bucket , type 0
Event Name: BlueScreen
Response: Not available
Cab Id: 0

Problem signature:
P1: 1000007e
P2: ffffffffc0000005
P3: fffff8001064b75d
P4: fffffe8db418f6d8
P5: fffffe8db418ef20
P6: 10_0_16299
P7: 0_0
P8: 768_1
P9: 
P10: 

Attached files:
\\?\C:\WINDOWS\Minidump\120417-28296-01.dmp
\\?\C:\WINDOWS\TEMP\WER-264968-0.sysdata.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER71D1.tmp.WERInternalMetadata.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER7202.tmp.csv
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER7222.tmp.txt

These files may be available here:
C:\ProgramData\Microsoft\Windows\WER\ReportQueue\Kernel_1000007e_f9732f6daafc1812e3b79ce4943f664797fef558_00000000_0320722f

Analysis symbol: 
Rechecking for solution: 0
Report ID: 6eba5667-8302-4cd3-8b09-3ada6789ed45
Report Status: 4
Hashed bucket:
06/12/2017 23:49    Windows Error Reporting    Fault bucket , type 0
Event Name: BlueScreen
Response: Not available
Cab Id: 0

Problem signature:
P1: 133
P2: 1
P3: 1e00
P4: fffff801a3890370
P5: 0
P6: 10_0_16299
P7: 0_0
P8: 768_1
P9: 
P10: 

Attached files:
\\?\C:\WINDOWS\Minidump\120617-45093-01.dmp
\\?\C:\WINDOWS\TEMP\WER-254375-0.sysdata.xml
\\?\C:\WINDOWS\MEMORY.DMP
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER582E.tmp.WERInternalMetadata.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER58EA.tmp.csv
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER58FA.tmp.txt

These files may be available here:
C:\ProgramData\Microsoft\Windows\WER\ReportArchive\Kernel_133_44fe2f648a92892adaa8b58727a4a4776aaf06_00000000_cab_1b14a4ec

Analysis symbol: 
Rechecking for solution: 0
Report ID: 17af89b4-ec33-4ce6-bbaa-f7df544cd13c
Report Status: 2049
Hashed bucket:
06/12/2017 14:30    Windows Error Reporting    Fault bucket , type 0
Event Name: BlueScreen
Response: Not available
Cab Id: 0

Problem signature:
P1: 133
P2: 1
P3: 1e00
P4: fffff801a3890370
P5: 0
P6: 10_0_16299
P7: 0_0
P8: 768_1
P9: 
P10: 

Attached files:
\\?\C:\WINDOWS\Minidump\120617-45093-01.dmp
\\?\C:\WINDOWS\TEMP\WER-254375-0.sysdata.xml
\\?\C:\WINDOWS\MEMORY.DMP
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER582E.tmp.WERInternalMetadata.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER58EA.tmp.csv
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER58FA.tmp.txt

These files may be available here:
C:\ProgramData\Microsoft\Windows\WER\ReportQueue\Kernel_133_44fe2f648a92892adaa8b58727a4a4776aaf06_00000000_03185909

Analysis symbol: 
Rechecking for solution: 0
Report ID: 17af89b4-ec33-4ce6-bbaa-f7df544cd13c
Report Status: 4
Hashed bucket:
09/12/2017 11:03    Windows Error Reporting    Fault bucket , type 0
Event Name: BlueScreen
Response: Not available
Cab Id: 0

Problem signature:
P1: 139
P2: 3
P3: ffffe1860460f6a0
P4: ffffe1860460f5f8
P5: 0
P6: 10_0_16299
P7: 0_0
P8: 768_1
P9: 
P10: 

Attached files:
\\?\C:\WINDOWS\Minidump\120917-28765-01.dmp
\\?\C:\WINDOWS\TEMP\WER-285078-0.sysdata.xml
\\?\C:\WINDOWS\MEMORY.DMP
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERE442.tmp.WERInternalMetadata.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERE5E8.tmp.csv
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERE617.tmp.txt

These files may be available here:
C:\ProgramData\Microsoft\Windows\WER\ReportQueue\Kernel_139_f8c01ac1cbcd0a770715111af8a7315a516ad1_00000000_0318e684

Analysis symbol: 
Rechecking for solution: 0
Report ID: 35b84126-1c1f-4f06-ac8d-397ecde8ecb5
Report Status: 4
Hashed bucket:
22/11/2017 16:08    Windows Error Reporting    Fault bucket , type 0
Event Name: BlueScreen
Response: Not available
Cab Id: 0

Problem signature:
P1: a
P2: 0
P3: ff
P4: 0
P5: fffff802daeec09a
P6: 10_0_16299
P7: 0_0
P8: 768_1
P9: 
P10: 

Attached files:
\\?\C:\WINDOWS\Minidump\112217-35718-01.dmp
\\?\C:\WINDOWS\TEMP\WER-185140-0.sysdata.xml
\\?\C:\WINDOWS\MEMORY.DMP
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERDB1F.tmp.WERInternalMetadata.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERDBAB.tmp.csv
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERDBDB.tmp.txt

These files may be available here:
C:\ProgramData\Microsoft\Windows\WER\ReportArchive\Kernel_a_f7f6ed4c25e6494861ff4990d617fa6e5b31589e_00000000_cab_06f7e6b4

Analysis symbol: 
Rechecking for solution: 0
Report ID: 2c29dc36-7dba-403f-9459-13333d567ae3
Report Status: 2049
Hashed bucket:
22/11/2017 16:04    Windows Error Reporting    Fault bucket , type 0
Event Name: BlueScreen
Response: Not available
Cab Id: 0

Problem signature:
P1: a
P2: 0
P3: ff
P4: 0
P5: fffff802daeec09a
P6: 10_0_16299
P7: 0_0
P8: 768_1
P9: 
P10: 

Attached files:
\\?\C:\WINDOWS\Minidump\112217-35718-01.dmp
\\?\C:\WINDOWS\TEMP\WER-185140-0.sysdata.xml
\\?\C:\WINDOWS\MEMORY.DMP
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERDB1F.tmp.WERInternalMetadata.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERDBAB.tmp.csv
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERDBDB.tmp.txt

These files may be available here:
C:\ProgramData\Microsoft\Windows\WER\ReportQueue\Kernel_a_f7f6ed4c25e6494861ff4990d617fa6e5b31589e_00000000_0313dbda

Analysis symbol: 
Rechecking for solution: 0
Report ID: 2c29dc36-7dba-403f-9459-13333d567ae3
Report Status: 4
Hashed bucket:
01/12/2017 10:02    Windows Error Reporting    Fault bucket , type 0
Event Name: BlueScreen
Response: Not available
Cab Id: 0

Problem signature:
P1: a
P2: 18
P3: 2
P4: 1
P5: fffff800ef959410
P6: 10_0_16299
P7: 0_0
P8: 768_1
P9: 
P10: 

Attached files:
\\?\C:\WINDOWS\Minidump\120117-28875-01.dmp
\\?\C:\WINDOWS\TEMP\WER-272437-0.sysdata.xml
\\?\C:\WINDOWS\MEMORY.DMP
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER9120.tmp.WERInternalMetadata.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER918E.tmp.csv
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER919E.tmp.txt

These files may be available here:
C:\ProgramData\Microsoft\Windows\WER\ReportArchive\Kernel_a_c2ee9bcca3c2927881bd8a51299d75c8736eb3_00000000_cab_198e0a05

Analysis symbol: 
Rechecking for solution: 0
Report ID: b4d36137-8b40-4d98-a540-4ae57c525807
Report Status: 2049
Hashed bucket:
01/12/2017 10:00    Windows Error Reporting    Fault bucket , type 0
Event Name: BlueScreen
Response: Not available
Cab Id: 0

Problem signature:
P1: a
P2: 18
P3: 2
P4: 1
P5: fffff800ef959410
P6: 10_0_16299
P7: 0_0
P8: 768_1
P9: 
P10: 

Attached files:
\\?\C:\WINDOWS\Minidump\120117-28875-01.dmp
\\?\C:\WINDOWS\TEMP\WER-272437-0.sysdata.xml
\\?\C:\WINDOWS\MEMORY.DMP
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER9120.tmp.WERInternalMetadata.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER918E.tmp.csv
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER919E.tmp.txt

These files may be available here:
C:\ProgramData\Microsoft\Windows\WER\ReportQueue\Kernel_a_c2ee9bcca3c2927881bd8a51299d75c8736eb3_00000000_031c91bd

Analysis symbol: 
Rechecking for solution: 0
Report ID: b4d36137-8b40-4d98-a540-4ae57c525807
Report Status: 4
Hashed bucket:
28/11/2017 16:17    Windows Error Reporting    Fault bucket , type 0
Event Name: BlueScreen
Response: Not available
Cab Id: 0

Problem signature:
P1: a
P2: ffffb50fbfe0631c
P3: ff
P4: 0
P5: fffff8006f85bf86
P6: 10_0_16299
P7: 0_0
P8: 768_1
P9: 
P10: 

Attached files:
\\?\C:\WINDOWS\Minidump\112817-28156-01.dmp
\\?\C:\WINDOWS\TEMP\WER-152171-0.sysdata.xml
\\?\C:\WINDOWS\MEMORY.DMP
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERD816.tmp.WERInternalMetadata.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERD839.tmp.csv
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERD84A.tmp.txt

These files may be available here:
C:\ProgramData\Microsoft\Windows\WER\ReportArchive\Kernel_a_c8a8288a13524922f4ad8d234cc6f635584861c_00000000_cab_1d0c09dc

Analysis symbol: 
Rechecking for solution: 0
Report ID: 50dda862-cde2-4925-95de-852241e37dd4
Report Status: 2049
Hashed bucket:
28/11/2017 16:11    Windows Error Reporting    Fault bucket , type 0
Event Name: BlueScreen
Response: Not available
Cab Id: 0

Problem signature:
P1: a
P2: ffffb50fbfe0631c
P3: ff
P4: 0
P5: fffff8006f85bf86
P6: 10_0_16299
P7: 0_0
P8: 768_1
P9: 
P10: 

Attached files:
\\?\C:\WINDOWS\Minidump\112817-28156-01.dmp
\\?\C:\WINDOWS\TEMP\WER-152171-0.sysdata.xml
\\?\C:\WINDOWS\MEMORY.DMP
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERD816.tmp.WERInternalMetadata.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERD839.tmp.csv
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERD84A.tmp.txt

These files may be available here:
C:\ProgramData\Microsoft\Windows\WER\ReportQueue\Kernel_a_c8a8288a13524922f4ad8d234cc6f635584861c_00000000_0326d855

Analysis symbol: 
Rechecking for solution: 0
Report ID: 50dda862-cde2-4925-95de-852241e37dd4
Report Status: 4
Hashed bucket:
27/11/2017 11:44    Windows Error Reporting    Fault bucket , type 0
Event Name: BlueScreen
Response: Not available
Cab Id: 0

Problem signature:
P1: a
P2: ffffc78a0f430069
P3: 2
P4: 0
P5: fffff8015bae4537
P6: 10_0_16299
P7: 0_0
P8: 768_1
P9: 
P10: 

Attached files:
\\?\C:\WINDOWS\Minidump\112717-29031-01.dmp
\\?\C:\WINDOWS\TEMP\WER-205875-0.sysdata.xml
\\?\C:\WINDOWS\MEMORY.DMP
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER94BF.tmp.WERInternalMetadata.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER94EE.tmp.csv
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER94FF.tmp.txt

These files may be available here:
C:\ProgramData\Microsoft\Windows\WER\ReportArchive\Kernel_a_ea391922fbb816f276797c5227eb4839965c2c67_00000000_cab_0e3e85c9

Analysis symbol: 
Rechecking for solution: 0
Report ID: e767147b-ff57-49fc-807b-93e9261b14b4
Report Status: 2049
Hashed bucket:
27/11/2017 07:53    Windows Error Reporting    Fault bucket , type 0
Event Name: BlueScreen
Response: Not available
Cab Id: 0

Problem signature:
P1: a
P2: ffffc78a0f430069
P3: 2
P4: 0
P5: fffff8015bae4537
P6: 10_0_16299
P7: 0_0
P8: 768_1
P9: 
P10: 

Attached files:
\\?\C:\WINDOWS\Minidump\112717-29031-01.dmp
\\?\C:\WINDOWS\TEMP\WER-205875-0.sysdata.xml
\\?\C:\WINDOWS\MEMORY.DMP
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER94BF.tmp.WERInternalMetadata.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER94EE.tmp.csv
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER94FF.tmp.txt

These files may be available here:
C:\ProgramData\Microsoft\Windows\WER\ReportQueue\Kernel_a_ea391922fbb816f276797c5227eb4839965c2c67_00000000_031b94fe

Analysis symbol: 
Rechecking for solution: 0
Report ID: e767147b-ff57-49fc-807b-93e9261b14b4
Report Status: 4
Hashed bucket:
01/12/2017 13:06    Windows Error Reporting    Fault bucket , type 0
Event Name: BlueScreen
Response: Not available
Cab Id: 0

Problem signature:
P1: c9
P2: 21f
P3: fffff8093d6ab174
P4: ffffb908475acc70
P5: 0
P6: 10_0_16299
P7: 0_0
P8: 768_1
P9: 
P10: 

Attached files:
\\?\C:\WINDOWS\Minidump\120117-26328-01.dmp
\\?\C:\WINDOWS\TEMP\WER-316562-0.sysdata.xml
\\?\C:\WINDOWS\MEMORY.DMP
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER1BCC.tmp.WERInternalMetadata.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER1C1B.tmp.csv
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER1C2B.tmp.txt

These files may be available here:
C:\ProgramData\Microsoft\Windows\WER\ReportArchive\Kernel_c9_c124931fe721902fbdfb676a9f86f0c5557777fe_00000000_cab_16087997

Analysis symbol: 
Rechecking for solution: 0
Report ID: e541bbf0-2f41-4f50-af89-465bf1231854
Report Status: 2049
Hashed bucket:
01/12/2017 11:13    Windows Error Reporting    Fault bucket , type 0
Event Name: BlueScreen
Response: Not available
Cab Id: 0

Problem signature:
P1: c9
P2: 21f
P3: fffff8093d6ab174
P4: ffffb908475acc70
P5: 0
P6: 10_0_16299
P7: 0_0
P8: 768_1
P9: 
P10: 

Attached files:
\\?\C:\WINDOWS\Minidump\120117-26328-01.dmp
\\?\C:\WINDOWS\TEMP\WER-316562-0.sysdata.xml
\\?\C:\WINDOWS\MEMORY.DMP
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER1BCC.tmp.WERInternalMetadata.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER1C1B.tmp.csv
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER1C2B.tmp.txt

These files may be available here:
C:\ProgramData\Microsoft\Windows\WER\ReportQueue\Kernel_c9_c124931fe721902fbdfb676a9f86f0c5557777fe_00000000_031d1ce6

Analysis symbol: 
Rechecking for solution: 0
Report ID: e541bbf0-2f41-4f50-af89-465bf1231854
Report Status: 4
Hashed bucket:

Code:

The system failed to flush data to the transaction log. Corruption may occur in VolumeId: G:, DeviceName: \Device\HarddiskVolume9.
(A device which does not exist was specified.)

Code:

Event[5369]: Log Name: System
Source: Disk
Date: 2017-12-06T18:07:13.278
Event ID: 51
Task: N/A
Level: Warning
Opcode: N/A
Keyword: Classic
User: N/A
User Name: N/A
Computer: MICHAEL
Description: 
An error was detected on device \Device\Harddisk1\DR3 during a paging operation.


Event[5370]:
Log Name: System
Source: Disk
Date: 2017-12-06T18:07:13.278
Event ID: 51
Task: N/A
Level: Warning
Opcode: N/A
Keyword: Classic
User: N/A
User Name: N/A
Computer: MICHAEL
Description: 
An error was detected on device \Device\Harddisk1\DR3 during a paging operation.

Code:


Event[5366]:
  Log Name: System
  Source: Disk
  Date: 2017-12-06T18:06:52.397
  Event ID: 11
  Task: N/A
  Level: Error
  Opcode: N/A
  Keyword: Classic
  User: N/A
  User Name: N/A
  Computer: MICHAEL
  Description: 
The driver detected a controller error on \Device\Harddisk1\DR3.

Code:

Event[567]:
  Log Name: System
  Source: Microsoft-Windows-WHEA-Logger
  Date: 2017-11-13T00:27:02.659
  Event ID: 17
  Task: N/A
  Level: Warning
  Opcode: Info
  Keyword: N/A
  User: S-1-5-19
  User Name: NT AUTHORITY\LOCAL SERVICE
  Computer: MICHAEL
  Description: 
A corrected hardware error has occurred.


Component: PCI Express Root Port
Error Source: Advanced Error Reporting (PCI Express)


Bus:Device:Function: 0x0:0x1C:0x5
Vendor ID:Device ID: 0x8086:0x9D15
Class Code: 0x30400


The details view of this entry contains further information.

Code:

Event[5877]:  Log Name: System
  Source: Microsoft-Windows-WHEA-Logger
  Date: 2017-12-07T14:34:25.942
  Event ID: 17
  Task: N/A
  Level: Warning
  Opcode: Info
  Keyword: N/A
  User: S-1-5-19
  User Name: NT AUTHORITY\LOCAL SERVICE
  Computer: MICHAEL
  Description: 
A corrected hardware error has occurred.


Component: PCI Express Root Port
Error Source: Advanced Error Reporting (PCI Express)


Bus:Device:Function: 0x0:0x1C:0x5
Vendor ID:Device ID: 0x8086:0x9D15
Class Code: 0x30400


The details view of this entry contains further information.

DonCeCo · 09 Dec 2017

1. Ensure your temperatures are within standard and nothing's overheating. You can use a program such as Speccy if you'd like to monitor temps - http://www.piriform.com/speccy

2. Clear your CMOS (or load optimized BIOS defaults) to ensure there's no improper BIOS setting - http://pcsupport.about.com/od/fixtheproblem/tp/clearcmos.htm

3. Ensure your BIOS is up to date.

4. The only software conflict that can usually cause *9C or *124 bugchecks are OS to BIOS utilities from manufacturer's like Asus' AI Suite, AI Charger software, etc. If you have something like this software-wise, remove it ASAP (which I see you do have Asus software installed).

5. If all of the above fail, the only left to do is replace your processor as it is faulty

michaelmuliadi · 10 Dec 2017

Whoa, this sounds like a lot of trouble...

Thanks for all the guideline, zbook. I'll try following the steps above

I'll inform regarding the result ASAP.

Also thanks for the insight, Don. I'll look into my BIOS setings and ASUS related software

michaelmuliadi · 12 Dec 2017

So far I've got IOMANAGER VIOLATION BSOD again

I haven't done all the diagnostics since I've been using my laptop non stop, so I can only share what I can

Hopefully what I attach is enough to pinpoint the troublesome driver, thanks :)

DonCeCo · 12 Dec 2017

Like said @zbook
"13) 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
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 8 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