[SOLVED] MSI b250 Pro, over 6 months of BSOD

[Mouad_1]

Hello,

i bought the B250 PRO VDH with i7 7700K, installed windows 10, windows 7 and windows 11.
i always get BSOD after few minutes up to an hour, with or without installing the drivers.

i installed fresh copy of windows 10 and installed all the drivers on msi website and still gets the blue screen.

BLUE SCREEN CODE: "System thread exception not handled", "ntoskrln.exe+3bd100", "wof.sys+2c750".

i tried different PSU, different rams and tried everything from my other pc. i also stress tested the ram using memtest86, during the test 0 error come and the pc didnt reboot or shutdown at all.

the problem still exist, i even re updated the bios even tho it was updated, i really don't know what's wrong with my pc or what to do, should i install an older bios version? or does the onboard gpu have incompatibility issues with this motherboard? i have no external GPU, what drivers do i need?

MOBO: B250 PRO VDH
RAM: corsair cmk16gx4m2e3200c16
I7 7700K

Thank you

 

[Colif]

1. Open Windows File Explore
2. Navigate to C:\Windows\Minidump
3. Copy the mini-dump files out onto your Desktop
4. Do not use Winzip, use the built in facility in Windows
5. Select those files on your Desktop, right click them and choose 'Send to' - Compressed (zipped) folder
6. Upload the zip file to the Cloud (OneDrive, DropBox . . . etc.)
7. Then post a link here to the zip file, so we can take a look for you . . .

what drives do you have? Make/model?

WoF.sys - Windows Overlay Filter . Seems to be storage related
fileinfo.sys - Windows File Information Minifilter Driver

all the processes mentioned make me think its either a driver for storage or the drives themselves, to blame.
i don't see anything on here - https://www.msi.com/Motherboard/B250M-PRO-VDH/support#driver

 

[Mouad_1]

all the processes mentioned make me think its either a driver for storage or the drives themselves, to blame.
i don't see anything on here - https://www.msi.com/Motherboard/B250M-PRO-VDH/support#driver

Thanks for joining, here is the minidump: https://we.tl/t-bGM6lSmi6A
at first i was using HDD: seagate barracude Z2AFZA78 500GB, in the last months i've been using different drive, Samsung SSD model: MZ - 7PD128M 128GB

 

[Colif]

I wonder if Magician works on that ssd - https://semiconductor.samsung.com/consumer-storage/support/tools/

I don't think I do all 50 right now, it would take over an hour and probably break my program running 50 at once
10 took long enough, I think I picked the right end of the 6 months.

If I can't figure it out from those, i do more. But normally I wouldn't have so many to pick from

I wouldn't have waited 6 months.

Conversion of dumps

report - Click run as fiddle to see report

Spoiler

File: 091122-3984-01.dmp (Sep 11 2022 - 22:48:08)
BugCheck: [SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M (1000007E)]
Probably caused by: memory_corruption (Process: System)
Uptime: 0 Day(s), 0 Hour(s), 19 Min(s), and 31 Sec(s)

File: 091122-3281-01.dmp (Sep 11 2022 - 23:01:11)
BugCheck: [SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M (1000007E)]
Probably caused by: Wof.sys (Process: System)
Uptime: 0 Day(s), 0 Hour(s), 12 Min(s), and 43 Sec(s)

File: 091122-3140-01.dmp (Sep 11 2022 - 23:48:47)
BugCheck: [SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M (1000007E)]
Probably caused by: Wof.sys (Process: System)
Uptime: 0 Day(s), 0 Hour(s), 14 Min(s), and 34 Sec(s)

File: 091122-3093-01.dmp (Sep 12 2022 - 00:04:06)
BugCheck: [SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M (1000007E)]
Probably caused by: memory_corruption (Process: System)
Uptime: 0 Day(s), 0 Hour(s), 14 Min(s), and 58 Sec(s)

File: 091022-4687-01.dmp (Sep 11 2022 - 00:45:49)
BugCheck: [SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M (1000007E)]
Probably caused by: Wof.sys (Process: System)
Uptime: 0 Day(s), 0 Hour(s), 15 Min(s), and 09 Sec(s)

File: 082022-4359-01.dmp (Aug 21 2022 - 00:46:07)
BugCheck: [SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M (1000007E)]
Probably caused by: Wof.sys (Process: System)
Uptime: 0 Day(s), 1 Hour(s), 10 Min(s), and 15 Sec(s)

File: 082022-3765-01.dmp (Aug 20 2022 - 20:39:43)
BugCheck: [PAGE_FAULT_IN_NONPAGED_AREA (50)]
Probably caused by: memory_corruption (Process: System)
Uptime: 0 Day(s), 0 Hour(s), 10 Min(s), and 30 Sec(s)

File: 082022-3750-01.dmp (Aug 20 2022 - 21:11:59)
BugCheck: [SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M (1000007E)]
Probably caused by: Unknown_Image (Process: System)
Uptime: 0 Day(s), 0 Hour(s), 10 Min(s), and 30 Sec(s)

File: 082022-3734-01.dmp (Aug 20 2022 - 20:50:28)
BugCheck: [PAGE_FAULT_IN_NONPAGED_AREA (50)]
Probably caused by: Wof.sys (Process: System)
Uptime: 0 Day(s), 0 Hour(s), 10 Min(s), and 31 Sec(s)

File: 082022-3718-01.dmp (Aug 20 2022 - 20:28:56)
BugCheck: [PAGE_FAULT_IN_NONPAGED_AREA (50)]
Probably caused by: Wof.sys (Process: System)
Uptime: 0 Day(s), 0 Hour(s), 10 Min(s), and 31 Sec(s)

all 10 caused by WoF.sys, or blame it. Microsoft drivers don't cause bsod so its another driver. Probably a storage driver.
i could guess its this driver to blame

Jan 13 2017

iaStorA.sys

Intel SATA Storage Device RAID Controller

as many wof.sys errrors tie into it
i would run this and see if it offers anything new - https://www.intel.com.au/content/www/au/en/support/intel-driver-support-assistant.html

another choice is run https://docs.microsoft.com/en-us/sysinternals/downloads/autoruns as admin and use it stop iaStorA.sys loading with windows. Just unticking it stops it loading. can also use autoruns to uninstall drivers. Leave it there for now as it will only be loaded if a program needs it if unticked.

 

[Mouad_1]

Click run as fiddle to see report

thank you so much for all this effort i really appreciate it, im glad you finally managed to figure out what made me nervous all this time,
i tried downloading intel driver support software and it completed and asked me to reboot, after the reboot no pop up or any confirmation was shown.
then i opened the autorun64 from Microsoft and disabled the iaStorA.sys. i rebooted the pc and it no longer wants to boot

i will install a new windows since i dont have any data and it installs quickly, could you please tell me if there is a possibility to disable the .sys without this, or is it linked to the ssd i have directly? i have access to other hard drives and ssd's if this ssd is the issue.

i'm not sure if this is related or not, but i just found out that windows 8.1/10 support was disabled from bios.

 

[Colif]

Can you see if the bios has sata drive set as AHCI or RAID. You would want it as AHCI

at first i was using HDD: seagate barracude Z2AFZA78 500GB, in the last months i've been using different drive, Samsung SSD model: MZ - 7PD128M 128GB

Do you still have both in PC?
the driver i got you to stop is a raid driver. could be windows was set up as raid but that would be odd on one ssd

I wasn't expecting that reaction. Sorry about that.

 

[Mouad_1]

Can you see if the bios has sata drive set as AHCI or RAID. You would want it as AHCI

The bios is set to : SATA MODE AHCI.
im only pluging one drive.
when i was about to create the windows usb, i choosed to try linux ubuntu iso instead.
went with the installation process, erased all windows files and after ubuntu installation i opened a text document and went to sleep. surprisingly after 9 hours and for the first time the system did not restart at all!!! this is a second confirmation to what you said, its just that driver.

After a while i will be installing the windows 10 on another drive and try to fix the .sys issue

 

[Colif]

Linux can run on a potato though. Its less stressing on a PC compared to windows.

At least PC works

 

[Mouad_1]

Linux can run on a potato though. Its less stressing on a PC compared to windows.

At least PC works

exactly at least it works haha
thank you so much Colif
i will work with linux for now and find a solution later since im sure its software related finally ...