BSOD:s again..

[Nippe]

I can report this post for possible operator assistance if you'd like...

That would be awesome

mdsched and memtest both ran perfectly with no errors detected..

 

[CarlTR6]

baarod, yowan is correct; the dump blames MpFilter.sys.

Probably caused by : Probably caused by : MpFilter.sys

Now as to whether or not that MpFilter.sys is the real cause is another story. The OP has an obsolete driver loaded on his system. I suggest he update the driver or uninstall the hardware.

skfiltv.sys Thu Aug 14 02:48:33 2008 - probably Pilote USB audio (WDM); Creative wireless headset; Hs-1200 Digital Wireless Headset. Creative Worldwide Support

 

[baarod]

baarod, yowan is correct; the dump blames MpFilter.sys.

Probably caused by : Probably caused by : MpFilter.sys

Now as to whether or not that MpFilter.sys is the real cause is another story. The OP has an obsolete driver loaded on his system. I suggest he update the driver or uninstall the hardware.

skfiltv.sys Thu Aug 14 02:48:33 2008 - probably Pilote USB audio (WDM); Creative wireless headset; Hs-1200 Digital Wireless Headset. Creative Worldwide Support

Read up in the dump. It cannot load the symbols for the file. As such it has NOTHING to go on to blame it. In fact, it's less than a shot in the dark.

 

[yowanvista]

baarod, yowan is correct; the dump blames MpFilter.sys.

Probably caused by : Probably caused by : MpFilter.sys

Now as to whether or not that MpFilter.sys is the real cause is another story. The OP has an obsolete driver loaded on his system. I suggest he update the driver or uninstall the hardware.

skfiltv.sys Thu Aug 14 02:48:33 2008 - probably Pilote USB audio (WDM); Creative wireless headset; Hs-1200 Digital Wireless Headset. Creative Worldwide Support

Read up in the dump. It cannot load the symbols for the file. As such it has NOTHING to go on to blame it. In fact, it's less than a shot in the dark.

This means MpFilter.sys was involved in the crash

 

[baarod]

baarod, yowan is correct; the dump blames MpFilter.sys.Now as to whether or not that MpFilter.sys is the real cause is another story. The OP has an obsolete driver loaded on his system. I suggest he update the driver or uninstall the hardware.

Read up in the dump. It cannot load the symbols for the file. As such it has NOTHING to go on to blame it. In fact, it's less than a shot in the dark.

This means MpFilter.sys was involved in the crash

Without the symbols loaded how can it tell?

I'm going to suggest that you follow How to disable Windows Defender in Windows 7 – Simple Help to turn off Defender as well just to prove this point. If the issue goes away, hey, I'm wrong. It's happened once or twice before Just have to make sure that OP followed directions and completely uninstalled MSSE as well. The goal here is to prevent loading of that filesystem filter driver so the debugger doesn't get lost in the filter chain as it traces through it. Since the RAM tests were reported clean I'm suspecting another filesystem filter like a virtual CD or the like.

 

[Nippe]

If MpFilter.sys causes crash (should be removed when I uninstall MSE?), why does comouter still bluescreen on first boot..

Now as to whether or not that MpFilter.sys is the real cause is another story. The OP has an obsolete driver loaded on his system. I suggest he update the driver or uninstall the hardware. Quote:
skfiltv.sys Thu Aug 14 02:48:33 2008 - probably Pilote USB audio (WDM); Creative wireless headset; Hs-1200 Digital Wireless Headset. Creative Worldwide Support

Thats driver for HS-1200 wireless..? I'm using HS-1000 USB headset, should I remove that then? And how? Creative got some update tool that cannot find any newer version to my drivers.

 

[yowanvista]

If MpFilter.sys causes crash (should be removed when I uninstall MSE?), why does comouter still bluescreen on first boot..

Now as to whether or not that MpFilter.sys is the real cause is another story. The OP has an obsolete driver loaded on his system. I suggest he update the driver or uninstall the hardware. Quote:
skfiltv.sys Thu Aug 14 02:48:33 2008 - probably Pilote USB audio (WDM); Creative wireless headset; Hs-1200 Digital Wireless Headset. Creative Worldwide Support

Thats driver for HS-1200 wireless..? I'm using HS-1000 USB headset, should I remove that then? And how? Creative got some update tool that cannot find any newer version to my drivers.

Uninstall the driver then download the latest from the manufacturer's website

 

[Nippe]

Uninstalled all Creative programs but the driver (skfiltv.sys) is still on my PC, how am I supposed to remove it? And do I even have to reinstall driver after removing?

Places where skfiltv.sys is:

C:\Windows\System32\DriverStore\FileRepository\xfiskv.inf_amd64_neutral_1ce8ee75da7e8191\WinVista\amd64
C:\Windows\System32\DriverStore\FileRepository\xfiskv.inf_amd64_neutral_a25d73415b2fe706\WinVista\amd64
C:\Windows\System32\drivers

 

[yowanvista]

Uninstalled all Creative programs but the driver (skfiltv.sys) is still on my PC, how am I supposed to remove it? And do I even have to reinstall driver after removing?

Places where skfiltv.sys is:

C:\Windows\System32\DriverStore\FileRepository\xfiskv.inf_amd64_neutral_1ce8ee75da7e8191\WinVista\amd64
C:\Windows\System32\DriverStore\FileRepository\xfiskv.inf_amd64_neutral_a25d73415b2fe706\WinVista\amd64
C:\Windows\System32\drivers

Delete the leftover driver or just rename it .old

 

[Nippe]

Should I just leave those drivers in C:\Windows\System32\DriverStore\FileRepository where they are or try to delete them somehow? Because they need permission from system to be deleted.

 

[CarlTR6]

You can leave the ones in the FileRepository. Just rename the one in System32\Drivers. If there is no updated driver later than 2008, the hardware is obsolete and not designed for Win 7.

 

[Nippe]

In Creative webpage (Creative Worldwide Support > Fatal1ty USB Gaming Headset HS-1000) they say

This download is a driver providing Microsoft® Windows® 7, Windows Vista® and Windows XP support for certain Creative gaming headsets.

So I think that driver should support Windows 7.. Should I try removing it and see if computer don't bluescreen tomorrow? And how can "bluescreen every first startup of the day" be caused by headset driver?

 

[CarlTR6]

While a 2008 driver could be OK with Win 7, it is definitely not a Win 7 driver. Win 7 was not even released in 2008. The "magic" date for third party Win 7 drivers is July 13, 2009, or later. I suggest you rename this driver from .sys to .old and reboot. The driver won't load; but your device will not work. See how your system does without this driver. You can always rename it back to .sys.

 

[baarod]

And how can "bluescreen every first startup of the day" be caused by headset driver?

It's not. Folks were trying to get you to believe that MpFilter.sys causes your crash but now have changed direction and are blaming headphones. Please follow my instructions here: http://www.sevenforums.com/crashes-debugging/129207-bsod-s-again.html#post1115438, uninstalling Microsoft Security Essentials and then disabling Windows Defender to find the filter driver in the filesystem filter chain that is causing your crash.

 

[CarlTR6]

And how can "bluescreen every first startup of the day" be caused by headset driver?

It's not. Folks were trying to get you to believe that MpFilter.sys causes your crash but now have changed direction and are blaming headphones. Please follow my instructions here: http://www.sevenforums.com/crashes-debugging/129207-bsod-s-again.html#post1115438, uninstalling Microsoft Security Essentials and then disabling Windows Defender to find the filter driver in the filesystem filter chain that is causing your crash.

Mike, I am trying to eliminate all possible causes as a means of troubleshooting by process of elimination. For the record, I never stated MpFilter.sys was the cause of the crash. I did state that the dump blamed MpFilter.sys and then clearly stated that something else could be conflicting. A 2008 driver is definitely a potential cause of conflict. I am well aware that just because a dump blames a particular driver, that driver may not be the cause.

 

[yowanvista]

Folks were trying to get you to believe that MpFilter.sys causes your crash

MpFilter.sys was involved in the crash but its impossible to determine if it was that driver the cause, MSE rarely cause BSODs

 

[baarod]

And how can "bluescreen every first startup of the day" be caused by headset driver?

It's not. Folks were trying to get you to believe that MpFilter.sys causes your crash but now have changed direction and are blaming headphones. Please follow my instructions here: http://www.sevenforums.com/crashes-debugging/129207-bsod-s-again.html#post1115438, uninstalling Microsoft Security Essentials and then disabling Windows Defender to find the filter driver in the filesystem filter chain that is causing your crash.

Mike, I am trying to eliminate all possible causes as a means of troubleshooting by process of elimination. For the record, I never stated MpFilter.sys was the cause of the crash. I did state that the dump blamed MpFilter.sys and then clearly stated that something else could be conflicting. A 2008 driver is definitely a potential cause of conflict. I am well aware that just because a dump blames a particular driver, that driver may not be the cause.

Fair enough. I'm just hoping to get past the symbol block in the dump that's hiding the root cause. I'm betting on another filesystem filter.

 

[baarod]

Folks were trying to get you to believe that MpFilter.sys causes your crash

MpFilter.sys was involved in the crash but its impossible to determine if it was that driver the cause, MSE rarely cause BSODs

What's worrying me is that the timestamp on MpFilter.sys cannot be verified. That makes me suspect possible tampering. Since MpFilter.sys is part of both MSE and built into 7 by way of Defender, maybe SFC would be a good exercise?

 

[CarlTR6]

I think SFC is a good idea; it certainly cannot hurt anything. I always look to see what the dump analysis blames; but I do not rely on that unless it is something, that experience has taught me, causes conflicts. I agree that filters are a good potential cause of crashes. I also agree with uninstalling Defender and MSE and reinstalling MSE. A fresh install of MSE may cure the problem - unless something else was interfering.

Nippe, run SFC /SCANNOW from a command prompt - right click on Command Prompt and select Run as administrator. At the prompt, type "sfc /scannow" (without the quotes).

 

[Nippe]

Wow.. Ran SFC /scannow and it found corrupted files but was unable to fix them, uploading report cause it looks pretty bad :/

Oh, and noticed it ain't "first boot of the day".. If I leave computer without power for about 2 or more hours it crashes after next startup.