Windows 10: BSOD SYSTEM_SERVICE_EXCEPTION (fileinfo.sys) troubleshooting

Good Morning/Afternoon,

First thank you for even reading this. Right to the problem, I recently had to replace my motherboard as it wouldn't even boot on correctly to BIOS. Everything went smoothly with few hiccups, I got it to turn on and go through the initial stuff just fine.

I formatted the HD and installed Windows 8.1 from the disk provided me by the company and upgraded to Windows 10. I did run Windows Memory Diagnostic on standard and it came back with no errros. I ran sfc /scannnow on admin and it keeps stopping at first saying that it couldn't fix the corrupt files found now it says it could not perform the requested operation.

I've formatted then installed different os's and there were just little different things here and there. I'm thinking my HD is kaput following the mobo but i'd just like to know for learning if it was drivers as some of the other threads say. Please help me troubleshoot this i'd like to know what's going on with it. Thank you for any insight!

Included is the minidump fresh after the latest BSOD and my computer details.

:)

 

BSOD's

There were three different BSODs.

There was a SYSTEM_SERVICE_EXCEPTION (3b) stop error that referenced the NETIO.SYS and the Drive Verifier may point to the Netwtw04.sys however the driver that may have actually caused the crash was the tmeevw.sys a Trend Micro driver.

The other two errors, PAGE_FAULT_IN_NONPAGED_AREA (50) and SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M (1000007e) referenced file system drivers such as the ntfs.sys and fileinfo.sys.

There were Trend Micro drivers "unloaded" during all the crashes and that may indicate an issue with Trend Micro.

You might contact Trend Micro to see if there is a known issue.

 

How to delete Hauppauge drivers? (hcw88aud.sys and such) (causing BSODs)

I found an extra fileinfo.sys in a WinSxS folder beginning with amd and according to file.net spare fileinfo.sys files could be malware but I'm on the fence about deleting it.

Also, I thought this was common with every bsod everyone has but right before and during the bsod the speakers buzz in a way that it constantly repeats whatever sound was playing when it bsod'ed.

 

A full log will be required. *Arrow Blue Screen of Death (BSOD) Posting Instructions

 

Excuse me for that, I went ahead and uploaded the right files. Thank you for letting me know.

 

Code: BugCheck 3B, {c0000005, fffff8007875f057, ffffd0005759dc50, 0} Probably caused by : fileinfo.sys ( fileinfo!FIStreamFillStreamInfo+17 ) Followup: MachineOwner ---------[/quote] Initially we see one driver is flagged, Realtek PCIe GBE Family Controller.
Code: ffffd000`57599040 fffff800`7ad10000Unable to load image \SystemRoot\System32\drivers\rt640x64.sys, Win32 error 0n2 *** WARNING: Unable to verify timestamp for rt640x64.sys *** ERROR: Module load completed but symbols could not be loaded for rt640x64.sys rt640x64[/quote] Code: Image name: rt640x64.sys Timestamp: Tue May 05 21:51:03 2015 (5548EDEF)[/quote] Can you please go to GIGABYTE - Motherboard - Socket AM3+ - GA-78LMT-USB3 (rev. 6.0)
and install this one? Attachment 75256See how it goes. Let us know.

 

Initially we see one driver is flagged, Realtek PCIe GBE Family Controller.
Code: ffffd000`57599040 fffff800`7ad10000Unable to load image \SystemRoot\System32\drivers\rt640x64.sys, Win32 error 0n2 *** WARNING: Unable to verify timestamp for rt640x64.sys *** ERROR: Module load completed but symbols could not be loaded for rt640x64.sys rt640x64[/quote] Code: Image name: rt640x64.sys Timestamp: Tue May 05 21:51:03 2015 (5548EDEF)[/quote] Can you please go to GIGABYTE - Motherboard - Socket AM3+ - GA-78LMT-USB3 (rev. 6.0)
and install this one? Attachment 75256See how it goes. Let us know.[/quote] I did go to the gigabyte site and download and tried to install any and all of the drivers I could. Some were reported incompatible such as the bios and others were supposedly installed correctly such as the lan and audio drivers at the time of that report. The ones that weren't able to said something like cannot launch into failure or incompatible with this system.

 

The driver shown in the screenshot is compatible for your system and you need to try it. *Smile

 

Sorry about the lateness in reply something really funny happened. My computer didn't load up to windows (BIOS was fine)
and after trying out different route's I finally was able to just have windows 8 installed.

So I did see my mistake at the first part rev. 6.0 duh... and unfortunately I couldn't try the fix you suggested. Let me try upgrading this Windows 8 to a 10 one more time and we'll go from there. Thank you again for looking at my problem!

 

OK ... no problem. *Smile