Seemingly random BSODs, when accessing win explorer, chrome, games,etc

shuttyt · 29 Jul 2012

I first had blue screens when doing even menial tasks, not when stressing hardware. I ran memcheck on my two ram sticks for days in all ports, always came out clean with no errors. Checked hard drives, all came out clean with no bad sectors.

I ran driver verifier and found that i had a multimedia driver, motuaw.sys, which was corrupt, so i updated and had no bsods. Then a few days ago, bsods started coming back and more frequently, as the time stamps may show.

I havent ran verifier since updating my motuAW driver, and when i did previously, it would crash on startup.

Pulling my hair out, please help.

shuttyt · 30 Jul 2012

also, if it helps, bluescreenview keeps pointing to ntoskrnl.exe as a consistent culprit. I know this may not indicate much, as bluescreenview does that, I heard.

FredeGail · 30 Jul 2012

Hello shuttyt and welcome to Sevenforums.

A .nfo file is needed.

To get this: Start Menu -> Type msinfo32 into the Search programs and files box -> When it opens, go to File, Save -> Save as msinfo32.nfo and save in a place you will remember -> Let it finish the process of gathering and saving the system info -> Right click the .nfo file, click send to compressed (zipped) folder -> Upload the .zip file here.

BSOD Analyse

It's funny you mentioned the motuAW.sys driver. I've rolled my eyes on a batch utility, that produced all your 3rd party drivers. motuAW.sys, as I've never heard of - came up.

Concerns

Code:

MotuAW.sys Thu Apr 26 22:41:05 2012 (4F99B2E1)

MotuAW.sys is not very known. As far as I'm concerned it's not digitally signed by Microsoft. If you're running this device with a driver you've installed yourself, try to uninstall the current driver, and let Windows 7 choose the solution.

Code:

GEARAspiWDM.sys Mon May 18 14:17:04 2009 (4A1151C0)
SynUSB64.sys Fri Jun 26 15:30:11 2009 (4A44CD63)
intelppm.sys Tue Jul 14 01:19:25 2009 (4A5BC0FD)
amdxata.sys Fri Mar 19 17:18:18 2010 (4BA3A3CA)
netr28ux.sys Wed Jun 8 04:40:42 2011 (4DEEE12A)
HECIx64.sys Thu Nov 10 01:52:25 2011 (4EBB2049)
Rt64win7.sys Fri Feb 3 14:00:02 2012 (4F2BDA52)
iusb3hub.sys Mon Feb 27 11:56:50 2012 (4F4B6172)
iusb3xhc.sys Mon Feb 27 11:56:53 2012 (4F4B6175)
iusb3hcs.sys Mon Feb 27 11:58:49 2012 (4F4B61E9)
MpFilter.sys Fri Mar 9 12:05:26 2012 (4F59E3F6)
nvhda64v.sys Wed Apr 18 19:07:54 2012 (4F8EF4EA)
MotuAW.sys Thu Apr 26 22:41:05 2012 (4F99B2E1)
MAWWAVE.sys Thu Apr 26 22:41:12 2012 (4F99B2E8)
nvlddmkm.sys Tue May 15 09:35:36 2012 (4FB20748)
SCDEmu.SYS Thu May 31 03:33:23 2012 (4FC6CA63)
GEARAspiWDM.sys
SynUSB64.sys
intelppm.sys
amdxata.sys
netr28ux.sys
HECIx64.sys
Rt64win7.sys
iusb3hub.sys
iusb3xhc.sys
iusb3hcs.sys
MpFilter.sys
nvhda64v.sys
MotuAW.sys <--- Not available on the Driver Reference Table
MAWWAVE.sys <--- Not available on the Driver Reference Table
nvlddmkm.sys
SCDEmu.SYS

Best Regards,
Frederik.

shuttyt · 30 Jul 2012

heres the msinfo.

For the motu drivers, it's a driver set for a bit of hardware that i have for audio editing.

MOTU.com - PCI-424 Compatibility

i had problems with them before and had to reload the drivers, but since then, i havent had blue screens with association to this driver. I had quite a few dmps pick this one up, but through collaboration with a few other people, we found it and updated it.

Windows will not find a suitable driver for this bit of hardware.

FredeGail · 30 Jul 2012

So just to clarify, you had it updated just now?

Best Regards,
Frederik.

shuttyt · 30 Jul 2012

i updated about a couple of weeks ago. I completely wiped it from my system and did a clean reinstall, and that was when i disabled driver verifier. If you notice the time stamps, that was the 15th of july, and everything since then just started happening.

FredeGail · 30 Jul 2012

Yes I see. What happens if you uninstall it from the Device Manager, and just leave it uninstalled. Eventhough Windows couldn't find the driver, does it work properly?

Best Regards,
Frederik

(Sent from Tapatalk)

shuttyt · 31 Jul 2012

I just tried it to no avail. Windows will not allow this device to function without its drivers.

I also just ran into a slight problem with reinstalling the drivers. When attempting to reinstall, I found that there was no box to select for my desired drivers. (The installer is a multi driver installer, so there was a choice between a PCI unit, USB/Firewire, and microbook) It seems that PCI drivers are registered somewhere as having been installed, and so I cannot perform an install of it again. Should I have to clean this up in my registry to actually continue? Or would you say that I should try to contact the manufacturer?

Also, if you don't mind me asking (since i am curious), what is the danger behind drivers that aren't digitally signed?

FredeGail · 31 Jul 2012

shuttyt said:

Should I have to clean this up in my registry to actually continue?

Registry cleaners can ruin your whole system, so I wouldn't start doing it. It's obviously the Motu driver that's the problem. I'd maybe suggest you to do a Clean Install Windows 7
, and then just go for all the Windows 7 drivers has for your hardware, for the time being.

Or would you say that I should try to contact the manufacturer?

I would yes, their driver ain't working as they should.

Also, if you don't mind me asking (since i am curious), what is the danger behind drivers that aren't digitally signed?

Microsoft can't find re-installations for them, they attend not to work properly with the OS itself. And most importantly, Microsoft haven't tested them!

I hope this helps,

Frederik.

shuttyt · 01 Aug 2012

So I decided to try to just do a complete new install on a different drive, and boot from there, but during the win 7 installation, i got a BSOD. keep in mind that this is still in the boot-from-CD stage.

As far as im concerned, this can only really point to hardware. Am i correct in doing so? And if i were to assume anything, I can only say that it would be the mobo.