BSOD on WIN 10 (flash, yowindow screen saver, chrome, ff)

U

uki

Member
Joined
Jun 5, 2016
Posts
10
Hello guys. I really need your help... It seems I can NOT figure it out myself.

Here are my specs:


· OS - Windows 10 PRO
· x64
· ISO file from MS
· ~5 months old OS


· i5 6600
· 8 GB RAM (2 sticks)
· Crucial MX100 256 GB
· Gigabyte GTX 760 OC
· ASUS H170 PRO GAMING (newest BIOS 1807)
· Power Supply - BeQuiet Pure Power L8 600W


I get random BSOD WHEA_UNCORRECTABLE_ERROR (124).
Sometimes using Chrome, Firefox. Especially when installed YoWindow screen saver (based on flash player I assume).


What I did:


- run memtest - full scan for ~7 h - 0 errors,
- run benchmarks for GPU and CPU - highest temp CPU - 68
- highest temp GPU - 81,
- Swap RAM sticks; insterted one each time - still BSOD,
- run HD Tune for SSD check


I've noticed that everytime I start YoWindow I got BSOD in about 1s - 2min (system idle, just YoWindow started)






DMP files in attachment. I cannot perform "perfmon /report" - gives me error.


Can You guys help in diagnose?


Thank You!


uki
 
I recommend you start by updating the following drivers since they pre-date Windows 10:

LHidFilt.Sys Wed Apr 22 18:05:22 2009 (49EFB0C2)
Logitech SetPoint HID Filter Driver Logitech Support + Downloads
http://www.carrona.org/drivers/driver.php?id=LHidFilt.Sys

LMouFilt.Sys Wed Apr 22 18:05:26 2009 (49EFB0C6)
Logitech SetPoint HID Filter Driver Logitech Support + Downloads
http://www.carrona.org/drivers/driver.php?id=LMouFilt.Sys

dcdbas64.sys Thu Jun 11 11:44:04 2009 (4A314264)
Dell System Management Device Driver Drivers & Downloads | Dell US
http://www.carrona.org/drivers/driver.php?id=dcdbas64.sys

AsIO.sys Wed Aug 22 03:54:47 2012 (5034AC67)
Asus PCProbe Utility http://support.asus.com/download/download.aspx
http://www.carrona.org/drivers/driver.php?id=AsIO.sys

semav6msr64.sys Fri Jan 24 12:22:40 2014 (52E2BD80)
SEMA Software Driver Download () - http://sema-soft.com/en/start.php
http://www.carrona.org/drivers/driver.php?id=semav6msr64.sys

netr28ux.sys Thu Jun 5 20:14:29 2014 (53912405)
Ralink RT2870 series USB802.11n Wireless Adapter Driver (you may have a different manufacturer) http://www.mediatek.com/en/downloads/
http://www.carrona.org/drivers/driver.php?id=netr28ux.sys

HWiNFO64A.SYS Sun Nov 23 09:24:07 2014 (54720A27)
HWiNFO32 Kernel Driver http://www.hwinfo.com/download32.html
http://www.carrona.org/drivers/driver.php?id=HWiNFO64A.SYS
 
None of the .dmps provided were new. I still note some of your drivers predate Windows 10 from your SysList file:
  • LHidFilt.Sys - Logitech SetPoint HID Filter Driver
  • LMouFilt.Sys - Logitech SetPoint HID Filter Driver
  • dcdbas64.sys - Dell System Management Device Driver
  • I would recommend removing all ASUS software utilities; ASUS AI Charger, ASUS PC Probe, etc. Those utilities can conflict with your hardware power configuration and cause hardware related crashes.


If the above does not work - The main hardware showing up in your stack trace is your file system which probably points to your SSD or memory.
  • Is your SSD Firmware up to date?
  • You said you ran memtest for 7 hours. What memtest did you run? The built in Windows version or Memtest86+?
 
Memtest86+ full scan - 0 errors. NONE.

SSD up to date with firmware MU02 for MX100.

I will try that in the evening.

Besides SSD gives me error in booting Win10 : "BOOTMGR is missing" form time to time. As a workaround I enter the BIOS and turn off CSM, restart, BIOS - turn back ON CSM. And BOOTMGR is OK.
Maybe this is an indication what's wrong with the system...

MX100 SMART:

[TABLE="class: table table-bordered table-striped table-condensed table-hover help, width: 100%"]
[TR]
[TH="class: text-right, align: right"]ID[/TH]
[TH]Description[/TH]
[TH="class: text-right, align: right"]Current Value[/TH]
[TH]Units[/TH]
[/TR]
[TR]
[TD="class: text-right, bgcolor: #F9F9F9, align: right"]1[/TD]
[TD="bgcolor: #F9F9F9"]Raw Read Error Rate[/TD]
[TD="class: text-right, bgcolor: #F9F9F9, align: right"]11[/TD]
[TD="bgcolor: #F9F9F9"]Errors/Page[/TD]
[/TR]
[TR]
[TD="class: text-right, align: right"]5[/TD]
[TD]Retired NAND Blocks[/TD]
[TD="class: text-right, align: right"]1[/TD]
[TD]NAND Blocks[/TD]
[/TR]
[TR]
[TD="class: text-right, bgcolor: #F9F9F9, align: right"]9[/TD]
[TD="bgcolor: #F9F9F9"]Power On Hours Count[/TD]
[TD="class: text-right, bgcolor: #F9F9F9, align: right"]6398[/TD]
[TD="bgcolor: #F9F9F9"]Hours[/TD]
[/TR]
[TR]
[TD="class: text-right, align: right"]12[/TD]
[TD]Power Cycle Count[/TD]
[TD="class: text-right, align: right"]1919[/TD]
[TD]Cycles[/TD]
[/TR]
[TR]
[TD="class: text-right, bgcolor: #F9F9F9, align: right"]171[/TD]
[TD="bgcolor: #F9F9F9"]Program Fail Count[/TD]
[TD="class: text-right, bgcolor: #F9F9F9, align: right"]0[/TD]
[TD="bgcolor: #F9F9F9"]NAND Page Program Failures[/TD]
[/TR]
[TR]
[TD="class: text-right, align: right"]172[/TD]
[TD]Erase Fail Count[/TD]
[TD="class: text-right, align: right"]0[/TD]
[TD]NAND Block Erase Failures[/TD]
[/TR]
[TR]
[TD="class: text-right, bgcolor: #F9F9F9, align: right"]173[/TD]
[TD="bgcolor: #F9F9F9"]Average Block-Erase Count[/TD]
[TD="class: text-right, bgcolor: #F9F9F9, align: right"]115[/TD]
[TD="bgcolor: #F9F9F9"]Erases[/TD]
[/TR]
[TR]
[TD="class: text-right, align: right"]174[/TD]
[TD]Unexpected Power Loss Count[/TD]
[TD="class: text-right, align: right"]148[/TD]
[TD]Unexpected Power Loss events[/TD]
[/TR]
[TR]
[TD="class: text-right, bgcolor: #F9F9F9, align: right"]180[/TD]
[TD="bgcolor: #F9F9F9"]Unused reserved block count[/TD]
[TD="class: text-right, bgcolor: #F9F9F9, align: right"]2158[/TD]
[TD="bgcolor: #F9F9F9"]Blocks[/TD]
[/TR]
[TR]
[TD="class: text-right, align: right"]183[/TD]
[TD]SATA Interface Downshift[/TD]
[TD="class: text-right, align: right"]0[/TD]
[TD]Downshifts[/TD]
[/TR]
[TR]
[TD="class: text-right, bgcolor: #F9F9F9, align: right"]184[/TD]
[TD="bgcolor: #F9F9F9"]Error Correction Count[/TD]
[TD="class: text-right, bgcolor: #F9F9F9, align: right"]0[/TD]
[TD="bgcolor: #F9F9F9"]Correction Events[/TD]
[/TR]
[TR]
[TD="class: text-right, align: right"]187[/TD]
[TD]Reported Uncorrectable Errors[/TD]
[TD="class: text-right, align: right"]0[/TD]
[TD]ECC Correction Failures[/TD]
[/TR]
[TR]
[TD="class: text-right, bgcolor: #F9F9F9, align: right"]194[/TD]
[TD="bgcolor: #F9F9F9"]Enclosure Temperature[/TD]
[TD="class: text-right, bgcolor: #F9F9F9, align: right"]24[/TD]
[TD="bgcolor: #F9F9F9"]Current Temperature (C)[/TD]
[/TR]
[TR]
[TD="colspan: 2"][/TD]
[TD="class: text-right, align: right"]48[/TD]
[TD]Highest Lifetime Temperature (C)[/TD]
[/TR]
[TR]
[TD="class: text-right, bgcolor: #F9F9F9, align: right"]196[/TD]
[TD="bgcolor: #F9F9F9"]Reallocation Event Count[/TD]
[TD="class: text-right, bgcolor: #F9F9F9, align: right"]1[/TD]
[TD="bgcolor: #F9F9F9"]Events[/TD]
[/TR]
[TR]
[TD="class: text-right, align: right"]197[/TD]
[TD]Current Pending Sector Count[/TD]
[TD="class: text-right, align: right"]0[/TD]
[TD]512 Byte Sectors[/TD]
[/TR]
[TR]
[TD="class: text-right, bgcolor: #F9F9F9, align: right"]198[/TD]
[TD="bgcolor: #F9F9F9"]SMART Off-line Scan Uncorrectable Errors[/TD]
[TD="class: text-right, bgcolor: #F9F9F9, align: right"]0[/TD]
[TD="bgcolor: #F9F9F9"]Errors[/TD]
[/TR]
[TR]
[TD="class: text-right, align: right"]199[/TD]
[TD]Ultra-DMA CRC Error Count[/TD]
[TD="class: text-right, align: right"]5[/TD]
[TD]Errors[/TD]
[/TR]
[TR]
[TD="class: text-right, bgcolor: #F9F9F9, align: right"]202[/TD]
[TD="bgcolor: #F9F9F9"]Percentage Lifetime Used[/TD]
[TD="class: text-right, bgcolor: #F9F9F9, align: right"]3[/TD]
[TD="bgcolor: #F9F9F9"]% Lifetime Used[/TD]
[/TR]
[TR]
[TD="class: text-right, align: right"]206[/TD]
[TD]Write Error Rate[/TD]
[TD="class: text-right, align: right"]0[/TD]
[TD]Program Fails/MB[/TD]
[/TR]
[TR]
[TD="class: text-right, bgcolor: #F9F9F9, align: right"]210[/TD]
[TD="bgcolor: #F9F9F9"]RAIN Successful Recovery Page Count[/TD]
[TD="class: text-right, bgcolor: #F9F9F9, align: right"]3[/TD]
[TD="bgcolor: #F9F9F9"]TUs successfully recovered by RAIN[/TD]
[/TR]
[TR]
[TD="class: text-right, align: right"]246[/TD]
[TD]Cumulative Host Write Sector Count[/TD]
[TD="class: text-right, align: right"]16399892608[/TD]
[TD]512 Byte Sectors[/TD]
[/TR]
[TR]
[TD="class: text-right, bgcolor: #F9F9F9, align: right"]247[/TD]
[TD="bgcolor: #F9F9F9"]Host Program Page Count[/TD]
[TD="class: text-right, bgcolor: #F9F9F9, align: right"]520744042[/TD]
[TD="bgcolor: #F9F9F9"]NAND Page[/TD]
[/TR]
[TR]
[TD="class: text-right, align: right"]248[/TD]
[TD]FTL Program Page Count[/TD]
[TD="class: text-right, align: right"]1399587393[/TD]
[TD]NAND Page[/TD]
[/TR]
[/TABLE]

I've noticed that "Ultra-DMA CRC Error Count" just raised by 1 point since I last checked (at the time I replaced SATA cable aswell).

Thank You.

 
uki said:
I've noticed that "[FONT=&]Ultra-DMA CRC Error Count" just raised by 1 point since I last checked (at the time I replaced SATA cable aswell).

Thank You.

[/FONT]
Click to expand...

Keep an eye on that number. If it continues to increase even after replacing your SATA cable, that may indicate a problem with your motherboard's SATA controller.
 
Crashes still point to the SSD or memory. Based on your earlier findings, I would suspect the motherboard SATA controller. Do you have other SATA devices besides the SSD plugged into the motherboard?
 
Have you tried disconnecting the 2TB drive and plugging the SSD into the same SATA port the 2TB drive is currently plugged into?
 
No, I didn't try that. But I reinstalled WIN10. Installing drivers right now. Until now - 0 errors (YoWindow installed and running).
Could it be a software issue then? Just asking, because BSOD 124 seems to be strictly hardware failure. Before formatting hal.dll also started crashing anlong with ntoskrnl.exe.

I'm going to send MOBO anyways because I suspect that error "BOOTMGR is missing" is caused by this board.

I'll post back the results later.
 
uki said:
No, I didn't try that. But I reinstalled WIN10. Installing drivers right now. Until now - 0 errors (YoWindow installed and running).
Could it be a software issue then? Just asking, because BSOD 124 seems to be strictly hardware failure. Before formatting hal.dll also started crashing anlong with ntoskrnl.exe.

I'm going to send MOBO anyways because I suspect that error "BOOTMGR is missing" is caused by this board.

I'll post back the results later.
Click to expand...

As I said before, it could be related to the drivers you had that pre-dated Windows 10. That was why I started from that angle. It's always best to rule out software before hardware when possible.
 
Quick update: BSOD hal.dll+35f1f. I'm done. I'm going to disassemble CPU and MOBO and RMA.


Thank You Very Much for Your help writhziden. Much appreciated! :)

PS Of course I'll post the results later (with hopefully new mobo or CPU).
 
I'll look forward to your next post, and hopefully you will tell us the RMA resolved all issues.
 
Hello again! :)

RMA result:

MOBO - all fine!

CPU - BROKEN!

Wow, 1 in a million, I'm lucky, I guess... :)
 

Has Sysnative Forums helped you? Please consider donating to help us support the site!

Back
Top