Windows 10 Help Needed for BSOD Issues - Dump Files Uploaded

[PabloBS]

Hi,
I'm with a BSOD problem too. Could you help me? I've uploaded the dump files.
Thanks

 

[Neemobeer]

Looks like a hard fault was reached, which basically means data was trying to be accessed that was not present in memory. This is normal behavior, it appears the BSOD occurred because the requested data was not loaded into memory due to an I/O error. The dump is indicating the hard drive was at fault.

• I would first go to the computer manufacturer site and verify you have the non-generic hard drive driver installed.
• If the issue continues, I would run a drive fitness test to see if there are any problems with your drive. Seagate SeaTools work pretty well or the disk manufacturer will generally have a tool for their brand.
• If the disk passes and you have the latest driver, you may want to try temporarily disabling your AV and see if that resolves the issue
• Optionally I would also run a memory test with memtest86

 

[BIGBEARJEDI]

Hi,
I'm with a BSOD problem too. Could you help me? I've uploaded the dump files.
Thanks

>>>Did you remember to run the W10 COMPATABILLITY TEST prior to upgrading to W10? If not, you should backup all your data to external media before attempting further repairs. Instructions for running the W10 COMPATABILLITY TEST are here:
Get Windows 10 app - Check Compatibility Report for Windows 10
If you bought your computer with factory pre-loaded W10 then it's a different series of steps to fix it, but you need to do the backup thing first before getting instructions from us to proceed further. I'm adamant about telling people this, so please forgive me.

Good luck,
<<<BIGBEARJEDI>>>

 

[kemical]

*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 154, {ffffe001a3e4c000, ffffd00021d46080, 0, 0}

Probably caused by : ntkrnlmp.exe ( nt!SMKM_STORE<SM_TRAITS>::SmStUnhandledExceptionFilter+22 )

Followup: MachineOwner

Hi,
all the dump files sent were the same as the above and it means the the store component caught an unexpected exception. The dump file cannot read the exception record past a certain point and could be down to driver corruption.

I see your running McAfee:
mfeaack.sys Sat Mar 05 01:00:03 2016: McAfee Arbitrary Access Control Driver. This is known on occasion to cause the odd issue and we ask the you remove it for the duration of troubleshooting.
Just use the on board Defender as this is super stable.

bcmwl63a.sys Wed Sep 12 22:30:03 2012: Broadcom 802.11 Network Adapter wireless driver. Please update using the driver from your systems support page:
Link Removed

gbftin64.sys Thu May 05 21:45:23 2016: GAS Tecnologia, have you checked this driver for compatibility with Windows 10? Uninstall to test.

Please ensure you update your chipset driver: Link Removed

iaStorA.sys Wed Feb 05 16:07:11 2014: Intel RST (Rapid Storage Technology) driver please update using your support page:
Link Removed

RTDVHD64.sys Tue Jun 30 08:59:48 2015: Realtek HD audio please update:
Link Removed

Please run these scans:
File scans
Right click on the Start menu icon and from the revealed list choose 'admin command prompt'. Type:
sfc /scannow
press enter and await results

In the same command prompt and after the above scan has finished type:
dism /online /cleanup-image /restorehealth
Press enter and await results (longer this time).

If the first scan found files it could not repair but the second scan is successful, run the first scan again using the same command prompt box and this time it should repair the files found.

If after making the above changes the bsod continues then try running the driver verifier. The Driver verifier will stress each driver in turn and if any are suspect they'll bsod and hopefully the culprits name will be written on the dump file.

First however you'll need to create a recovery disk/USB, sometimes the verifier can cause a bsod start up loop. Using the recovery disk/USB to boot from you can enter safe mode and turn the verifier off. Hopefully the culprit will be caught on the dump file:
Recovery
Link Removed

Driver Verifier guide:
How do I fix a Blue Screen in Windows using Driver Verifier?

Please post any new dump files.

 

[PabloBS]

Looks like a hard fault was reached, which basically means data was trying to be accessed that was not present in memory. This is normal behavior, it appears the BSOD occurred because the requested data was not loaded into memory due to an I/O error. The dump is indicating the hard drive was at fault.

• I would first go to the computer manufacturer site and verify you have the non-generic hard drive driver installed.
• If the issue continues, I would run a drive fitness test to see if there are any problems with your drive. Seagate SeaTools work pretty well or the disk manufacturer will generally have a tool for their brand.
• If the disk passes and you have the latest driver, you may want to try temporarily disabling your AV and see if that resolves the issue
• Optionally I would also run a memory test with memtest86

Here is my HD map by HD Tune

 

[PabloBS]

Here is my HD map by HD Tune

View attachment 32975

HD Tune Pro: WDC WD10EARS-00Y5B1 Error Scan

Scanned data : 978 gB
Damaged Blocks : 2.7 %
Elapsed Time : 3:32:46
1 Error at 41523 MB (LBA 85039488)
2 Error at 41545 MB (LBA 85085312)
3 Error at 57693 MB (LBA 118156736)
4 Error at 58978 MB (LBA 120787296)
5 Error at 66671 MB (LBA 136542816)
6 Error at 70483 MB (LBA 144349376)
7 Error at 70517 MB (LBA 144420544)
8 Error at 71732 MB (LBA 146908640)
9 Error at 73017 MB (LBA 149539072)
10 Error at 93743 MB (LBA 191987008)
11 Error at 94303 MB (LBA 193133600)
12 Error at 94356 MB (LBA 193242144)
13 Error at 94904 MB (LBA 194364032)
14 Error at 94931 MB (LBA 194419712)
15 Error at 94947 MB (LBA 194452608)
16 Error at 94960 MB (LBA 194479104)
17 Error at 95026 MB (LBA 194614272)
18 Error at 95536 MB (LBA 195658720)
19 Error at 95561 MB (LBA 195709920)
20 Error at 97431 MB (LBA 199538784)
21 Error at 105698 MB (LBA 216471488)
22 Error at 113309 MB (LBA 232058464)
23 Error at 137475 MB (LBA 281549952)
24 Error at 154527 MB (LBA 316471680)
25 Error at 154527 MB (LBA 316471808)
26 Error at 154530 MB (LBA 316478080)
27 Error at 154542 MB (LBA 316502400)
28 Error at 154542 MB (LBA 316502528)
29 Error at 154542 MB (LBA 316502656)
30 Error at 154543 MB (LBA 316504832)
31 Error at 154543 MB (LBA 316504960)
32 Error at 154547 MB (LBA 316513792)
33 Error at 154550 MB (LBA 316520320)
34 Error at 154551 MB (LBA 316520448)
35 Error at 154553 MB (LBA 316524544)
36 Error at 154554 MB (LBA 316526976)
37 Error at 154555 MB (LBA 316529280)
38 Error at 154558 MB (LBA 316535808)
39 Error at 154568 MB (LBA 316555776)
40 Error at 154572 MB (LBA 316564224)
41 Error at 154576 MB (LBA 316573568)
42 Error at 154578 MB (LBA 316575744)
43 Error at 154601 MB (LBA 316624512)
44 Error at 154608 MB (LBA 316637440)
45 Error at 154608 MB (LBA 316637568)
46 Error at 154619 MB (LBA 316659712)
47 Error at 154619 MB (LBA 316659840)
48 Error at 155109 MB (LBA 317664736)
49 Error at 155110 MB (LBA 317667168)
50 Error at 155117 MB (LBA 317680352)
51 Error at 155117 MB (LBA 317680608)
52 Error at 155139 MB (LBA 317726688)
53 Error at 155173 MB (LBA 317795680)
54 Error at 155182 MB (LBA 317813216)
55 Error at 155201 MB (LBA 317853280)
56 Error at 155201 MB (LBA 317853408)
57 Error at 179831 MB (LBA 368294112)
58 Error at 179836 MB (LBA 368304736)
59 Error at 181081 MB (LBA 370854272)
60 Error at 181081 MB (LBA 370854400)
61 Error at 182959 MB (LBA 374701952)
62 Error at 200205 MB (LBA 410019936)
63 Error at 200242 MB (LBA 410096608)
64 Error at 206944 MB (LBA 423822656)
65 Error at 216232 MB (LBA 442843328)
66 Error at 216232 MB (LBA 442844864)
67 Error at 276704 MB (LBA 566690176)

 

[BIGBEARJEDI]

Looks like your hard drive has failed and must be replaced!! We suggest you go to wd.com and download the free DLG DIAGNOSTIC specifically for WD hard drives and confirm. It's always best to use the manufacturer tool if available and in this case it is. HDTUNE is not a primary drive diagnostic. Make sure to run both short and long tests on your drive. If DLG returns errors on either test you have confirmed that your hard drive has failed and must be replaced!

<<<BIGBEARJEDI>>>