Pervasive BSOD

[ragnarok1900]

For the past month or so now i've been having a very bothersome Bsod. It all started about 2 months ago when I bought a New motherboard, the Msi P55-GD80. For about 2 weeks everything was smooth until i started to overclock my processor and my graphics cards. I was very delicate with this procedure, however i did run into many crashes, blue screens, only the norm that i thought nothing of... I was finally satisfied with quite a hefty overclock of 3.8ghz on an i5 750 on aftermarket air, however after couple hours my system bsod. This slowly got worse and worse until my comp would only last about 90 seconds after log in. I got fed up with it and returned to default settings, However the bsod remained just as pervasive. Having tested other motherboards on the same ram and graphics cards and knowing that I kept my Cpu at nominal temperatures and voltages, i deduced that my motherboard had gone bad. Instinctively i RMA'd my motherboard. From here i put in my Asus M4A79XTD Evo and my AMD Athlon II 630 and had no problems. Upon Installation of my newly RMA'd Motherboard, the problem instantly resurfaced. From here I did many tests, Mostly finding that the stop error code 0x000003b was the most common and that the commonly afflicted processes were svhost.exe and explorer.exe. After all the swapping of motherboards that i had to do on this computer in order to have a working computer for school, i accidentally broke a dimm slot clip. Because of this i RMA'd it a second time where i now received a brand new board. After installation of this board I still got Bsod's, only now with completely different stop error codes. Having been exhausted of this issue i have fallen back to this forum for help. I have attached the dump files that i have only collected in the newest Rma board. Prior to installation of the board I had formatted my hard drive and started fresh. I have also tried reinstalling win 7 fresh with the board in, It bsod during installation. I am only 15 and i am just stumped on what to do from here. Thanks for any help.

 

[merkat106]

does sound like hardware. unless i am wrong, it sounds like the problem is with one of your ram sticks. one could be bad. try them each one at a time. also, if possible, check the bios to see if all the ram shows up. you might also want to run a memory check.
Memtest86+ - Advanced Memory Diagnostic Tool
also, the problem might be with your graphics card. is it the same one you overclocked? try booted with your onboard graphics. if the problem goes away then, then its the card.

 

[ragnarok1900]

I have ran each individual stick for 5 passes on memstest86+, and 10 passes on all 4 together. No errors. I tried booting with only one graphics card, then trying the other. Bsod no matter which one. My motherboard has no on-board graphics so i have no way of testing that... I can almost guarantee that it isn't the graphics cards or the ram because i can run my computer stably by swapping to my amd motherboard and amd processor, however i keep the exact same ram and graphics cards (no sli but i have tried each one on this setup before).

 

[Tews]

Please return your Processor and GPU to their default values, then let us know if you are still having problems... In the mean time Ill take a look at your .dmp file...

 

[ragnarok1900]

I have had my processor and Gpu at default values since i had to rma the board the first time and I haven't touched them since, but i have still been getting Bsod's.

I have to go mow my lawn so hold on guys! thanks for the help guys btw.

 

[Tews]

With the exception of one specific driver, most of your .dmp files are pointing to core Windows 7 files, and it is doubtful that they are to blame...

The specific driver that is blamed is ssidrv.sys. This is a driver for SpySweeper (Antivirus & Anti Spyware Security Software for Home & Business | Webroot) Delete this program and replace it with another product
SuperAntiSpyware is used by a great many users and comes highly recommended...

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

Use !analyze -v to get detailed debugging information.

BugCheck F4, {3, fffffa8007ca7b30, fffffa8007ca7e10, fffff80002bcb240}

Probably caused by : Winlogon.exe

Followup: MachineOwner
---------

1: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: Winlogon

IMAGE_NAME:  Winlogon.exe

FAILURE_BUCKET_ID:  X64_0xF4_taskmgr.exe_IMAGE_Winlogon.exe

BUCKET_ID:  X64_0xF4_taskmgr.exe_IMAGE_Winlogon.exe

Followup: MachineOwner
---------

_________________________________________________________________________


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

Use !analyze -v to get detailed debugging information.

BugCheck 3B, {c0000005, fffff96000188e2b, fffff8800be5ec80, 0}

Probably caused by : win32k.sys ( win32k!GetStyleWindow+13 )

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

Use !analyze -v to get detailed debugging information.

BugCheck BE, {fffff96000056b5e, 737000003478e021, fffff88002583810, b}

Probably caused by : win32k.sys ( win32k!xxxInternalDoSyncPaint+99 )

Followup: MachineOwner
---------

0: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************


DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

BUGCHECK_STR:  0xBE

PROCESS_NAME:  explorer.exe

CURRENT_IRQL:  0


......
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************



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

Use !analyze -v to get detailed debugging information.

BugCheck 135, {ffffffffc0000005, fffff8800a6118d0, fffff88000e69334, fffff8a00028a9a0}

Unable to load image \SystemRoot\system32\DRIVERS\ssidrv.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for ssidrv.sys
*** ERROR: Module load completed but symbols could not be loaded for ssidrv.sys
Probably caused by : ssidrv.sys ( ssidrv+7f14 )

Followup: MachineOwner
---------

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

Use !analyze -v to get detailed debugging information.

BugCheck 124, {0, fffffa8003d69028, be000000, 800400}

Probably caused by : hardware

Followup: MachineOwner
---------
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 135, {ffffffffc0000005, fffff8800b6938d0, fffff88000e69334, fffff8a0002bb730}

Unable to load image \SystemRoot\system32\DRIVERS\ssidrv.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for ssidrv.sys
*** ERROR: Module load completed but symbols could not be loaded for ssidrv.sys
Probably caused by : ssidrv.sys ( ssidrv+7f14 )

Followup: MachineOwner
---------

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

Use !analyze -v to get detailed debugging information.

BugCheck 135, {ffffffffc0000005, fffff88009a7e8d0, fffff88000e73334, fffff8a00023c310}

Unable to load image \SystemRoot\system32\DRIVERS\ssidrv.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for ssidrv.sys
*** ERROR: Module load completed but symbols could not be loaded for ssidrv.sys
Probably caused by : ssidrv.sys ( ssidrv+7f14 )

Followup: MachineOwner
---------

You also have an outdated driver that should be updated...

fffff880`049fa000 fffff880`049fe980   Lycosa   Lycosa.sys   Fri Jan 18 03:51:42 2008 (4790689E) Please uninstall the software and drivers for your Razer Tarantula Keyboard

Once you have done this enable driver verifier ...here's the procedure:
- Go to Start and type in "verifier" (without the quotes) and press Enter
- Select "Create custom settings (for code developers)" and click "Next"
- Select "Select individual settings from a full list" and click "Next"
- Select everything EXCEPT FOR "Low Resource Simulation" and click "Next"
- Select "Select driver names from a list" and click "Next"
Then select all drivers NOT provided by Microsoft and click "Next"
- Select "Finish" on the next page.

Reboot the system and wait for it to crash to the Blue Screen. Continue to use your system normally, and if you know what causes the crash, do that repeatedly. The objective here is to get the system to crash because Driver Verifier is stressing the drivers out. If it doesn't crash for you, then let it run for at least 36 hours of continuous operation (an estimate on my part).

 

[ragnarok1900]

I have done everything you have instructed, here's what happened

-Uninstalled webroot
-Enabled Driver verifier with instructed settings
-Reboot
-Froze at windows logo on startup
-Reset
-Booted to os
-driver verifier was working, cpu constantly at 40%+
-messed around with itunes, Sony vegas 9, installed some new drivers for nivida
-Reboot
-Froze at windows logo again
-reset
-Blue screened at log in screen
-Reboot, Got to log in screen, logged in, instantly blue screen
-Reboot, froze at windows logo
-Rebooted into safe mode
-Copied over dump files

 

[Tews]

2 of the 3 minidumps are Verifier enabled minidumps and blame MBfilt64.sys
This driver seems to be associated with your Realtek HiDefinition Audio device -

I would suggest disabling Driver Verifier. Then download the latest Audio drivers for your device from the Realtek support website or from the support website of your PC manufacturer.
Once that's done, uninstall the current software from Control Panel...Programs...Uninstall a program
Then install the freshly downloaded drivers and use the system to see if it BSOD's again.

The other .dmp blames CI.dll which is a core file... Run sfc /scannow to repair this file...

Here's a summary of the memory dumps:

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

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: CI

IMAGE_NAME:  CI.dll

DEBUG_FLR_IMAGE_TIMESTAMP:  4a5be01d

FAILURE_BUCKET_ID:  X64_0xA_VRF_CI!A_SHAUpdate+60

BUCKET_ID:  X64_0xA_VRF_CI!A_SHAUpdate+60

Followup: MachineOwner
---------



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

Use !analyze -v to get detailed debugging information.

BugCheck A, {0, 2, 0, fffff80002e907b6}

Unable to load image \SystemRoot\system32\drivers\MBfilt64.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for MBfilt64.sys
*** ERROR: Module load completed but symbols could not be loaded for MBfilt64.sys
Probably caused by : MBfilt64.sys ( MBfilt64+1807 )

Followup: MachineOwner
---------

FOLLOWUP_IP: 
MBfilt64+1807
fffff880`05df1807 ??              ???

SYMBOL_STACK_INDEX:  4

SYMBOL_NAME:  MBfilt64+1807

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: MBfilt64

IMAGE_NAME:  MBfilt64.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  4a23abe0

FAILURE_BUCKET_ID:  X64_0xA_VRF_MBfilt64+1807

BUCKET_ID:  X64_0xA_VRF_MBfilt64+1807

Followup: MachineOwner
---------

 

[ragnarok1900]

I uninstalled the Realtek audio drivers and installed the newest from the website but the computer imediatly bsod after when i went to run sfc / scannow. It then bsod upon log in screen after restart from the first. Here are the dump files.

 

[Tews]

All three .dmp are still pointing to your Realtec drivers... Are you sure that you installed the drivers for windows 7 ????

Microsoft (R) Windows Debugger Version 6.12.0002.633 X86
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Windows\Minidump\070810-19078-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*c:\symbols*http://msdl.microsoft.com/download/symbols
Executable search path is: 
Windows 7 Kernel Version 7600 MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7600.16539.amd64fre.win7_gdr.100226-1909
Machine Name:
Kernel base = 0xfffff800`02e1c000 PsLoadedModuleList = 0xfffff800`03059e50
Debug session time: Thu Jul  8 04:04:14.471 2010 (UTC - 4:00)
System Uptime: 0 days 0:00:18.938
Loading Kernel Symbols
...............................................................
................................................................
........
Loading User Symbols
Loading unloaded module list
.....
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck A, {0, 2, 0, fffff80002e907b6}

Unable to load image \SystemRoot\system32\drivers\MBfilt64.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for MBfilt64.sys
*** ERROR: Module load completed but symbols could not be loaded for MBfilt64.sys
Probably caused by : MBfilt64.sys ( MBfilt64+1807 )

Followup: MachineOwner
---------

 

[ragnarok1900]

Yes I am positive that I downloaded and installed win 7 64bit drivers, however those may be the wrong dump files. Right now I am away from home but later today I will try to recreate some bsod's for the correct dump files.

 

[ragnarok1900]

Alright so I have some new Dump files for anyone whose interested to look at.

My bsod have become much more mild and seem to happen only right after the log in screen. Its actually down to somewhat of a science, My pc will boot once and freeze at the windows logo, forcing me to restart. After the restart it will finish loading os but bsod right when it gets to the log in screen. After one more reboot it will log in just fine and virtually no problems (except for one bsod caused by a old lycosa driver, which was replaced). I would really love to not have to reboot my pc 3 times before it will boot up to an os that really doesn't feel to stable still. I would greatly appreciate it if some one would look over my current dump files.
Thanks a ton.

 

[Davidxtux]

Run Prime95 at cpu default clocks and voltage and see if it kicks out any errors.

Prime95 (64bit) - 25.11 Download - EXTREME Overclocking

 

[ragnarok1900]

been running prime 95 for a little under an hour, no errors....



Here's some fresh mini dump files, i'm pretty much convinced that it isn't hardware but who knows....

 

[Davidxtux]

Are you running the most recent drivers for both your keyboard and mouse?

 

[ragnarok1900]

I actually just updated them when i noticed that my system would bsod if i lost connection with my mouse. After uninstalling and reinstalling the bsod's for the mouse and keyboard (which both happened to be a razer lycosa and a razer copperhead) only got worse and after finding that the keyboard actually caused a bsod off boot up made me just ditch the two devices. My rig is running much more stable with a GE keyboard and a IBM mouse, however i am already looking at the Microsoft sidewinder series. Although this seems to have eliminated my bsod's for the moment, I did still get one right at the log in screen, and my pc seems to freeze almost every other time during the loading phase of windows with the pulsating windows logo. Any dump files created in these bsod will be in the last post

 

[Davidxtux]

Run an elevated chkdsk by doing the following:

Go to start menu
In search type cmd
Right click and select run as administrator
Type chkdsk /r and hit enter

 

[ragnarok1900]

Alright i have enabled chkdsk to run next reboot but i have found an interesting pattern in my bsod's. Off of the first boot my comp will get a bsod right when it gets to the login screen. then it will reboot and freeze up at the windows loading screen. Finally on the 3rd reboot the system will boot to os that since the removal of the faulty keyboard and mouse has yet to bsod. The numerous dump files for this bsod can be found 4 posts back.

 

[ragnarok1900]

I ran Chkdsk last night but fell asleep before it finished and awoke to my computer at the log in screen. Don't know what I should have been looking for but it seemed to make it through error free.

Things are running much smoother now, my pc has yet to crash inside of the os, and i don't think its freezeing or bsod during startup any more.

 

[Davidxtux]

Awesome! Hopefully everything works out for you. Report back if you need help.. we'll be waiting here to assist you.