Solved Bsod

[windowsuser111]

hi, i got a bsod and it rebooted normally
win 7 x64 home premium oem
inspiron 580, bought it in november

logs (recorded as instructed in the sticky post) attached

 

[windowsuser111]

whoops, forgot to do the performance monitor check, here's the html file

 

[windowsuser111]

bump

 

[Tews]

Your .dmp file is blaming acedrv09.sys (Part of ProtectDISC Software) This is from February 2007, and may not be compatible with Windows 7. Download the latest version from their website, or uninstall the software. ProtectDISC Software

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

Use !analyze -v to get detailed debugging information.

BugCheck 50, {fffff8a009829000, 0, fffff88000fdfc02, 0}

Unable to load image \??\C:\Windows\system32\drivers\acedrv09.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for acedrv09.sys
*** ERROR: Module load completed but symbols could not be loaded for acedrv09.sys
Unable to load image \SystemRoot\system32\DRIVERS\MpFilter.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for MpFilter.sys
*** ERROR: Module load completed but symbols could not be loaded for MpFilter.sys

Could not read faulting driver name
Probably caused by : acedrv09.sys ( acedrv09+4c02 )

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

start             end                 module name
fffff880`00fdb000 fffff880`00fff000   acedrv09 [COLOR="Red"]acedrv09.sys Fri Feb 09 08:51:36 2007[/COLOR] (45CC7C68)

 

[windowsuser111]

thanks
is there any way for me to tell which program the drm software is attached to?

edit:ah, judging from another thread on this forum, it appears to be magix music maker which i had recently installed
thanks again for the help

 

[Tews]

Hope that it solves your problem..

 

[windowsuser111]

i neglected to uninstall magix music maker 12

it happened again once, i was awa for a while and logged in to find the screen looking weird because the ati drivers were gone (and i couldnt reinstall because the inf folder wasn't there either) so i rebooted and used startup repair and system restore to fix everything
when it happened the third time, startup repair "couldn't fix it automatically", so i can't even log in anymore

 

[Tews]

Don't panic ... see if you can login into safe mode ... if you can do a system restore to your last known configuration that allowed you to boot normally...

 

[windowsuser111]

safe mode doesn't seem to work (you go into safe mode by holding f8 as it's starting right?), it just makes this odd noise as i'm holding the key down and keeps starting up and proceeds to the startup repair/start normally selection menu

btw in the system repair details it said something like "unspecified changes to configuration could have caused the problem"
the closest thing i can remember doing is this - http://forums.gamesforwindows.com/t/8958.aspx - to fix a game error

edit: i've started system restore by going into "advanced recovery options", i'll post about how it goes

 

[windowsuser111]

it didn't work, it briefly bluescreens and boots into the system rpair menu again (like always), i'll try again with an earlier restore point

edit: ok, the earlier point worked, now time to uninstall the magix crap

too bad i also lost some good stuff from giveaway of the day...

 

[Tews]

Just remember ..... Backups are your friend!

 

[windowsuser111]

it happened again while i was doing virus scans (malwarebytes had found spyware.passwords.xgen in an executable that came in a .rar i downloaded, luckily i scanned and removed it without opening it)

this time i was able to start up normally

i thought acedrv09.sys would be gone after i uninstalled the software it came with, but evidently i'm wrong

 

[windowsuser111]

i've deleted acedrv09.sys and acedrv09.dll from the system32/drivers and /sysWOW64 folders respectively into the recycle bin, let's see if this fixes it

 

[windowsuser111]

could you remove the "fixed" tag for now, thanks

ok, it bluescreened and failed to start again when i started up after shutting down a minute or so earlier
prior to this (hours before i shut down) , my windows color somehow changed to another color, and everything started loading slowly for a while, i don't know if this is related

i used system restore from the recovery options menu, to the second-latest restore point (the latest was set at a windows update and didn't work), and when i logged in i found that my wallpaper was zoomed in.

"acedrv09.dll" and "acedrv09.sys" are back from the recycle bin

i'm attaching the new outputs from the BSOD Dump & System File Collection app and Perfmon.

while the file collection app was running, a window came up saying "refreshing system information"

edit: i also can't synchronize with time.nist.gov, don't know if it's related
edit:nvm, time sync had an error when i tried to update manually but now it's fine

i've copied (for backup) acedrv09.dll and acedrv09.sys into a folder in \My Documents, and put the originals into the recycle bin (don't like to perma-delete)

 

[Tews]

Sorry, no .dmp files were included in your attachment...

 

[windowsuser111]

in the Windows/Minidump folder, there's only one .dmp from a week ago
let me try and run the utility again
btw, i just used the protectdisc driver uninstaller

edit:here are the new dump and perfmon files, attached

 

[Tews]

Sorry, no new .dmp files .. turn on driver verifier again, upload the new .dmp files...

 

[windowsuser111]

what's the driver verifier?
i got something like "the user profile service failed to start" when trying to log in on my admin account, it worked after switching to another account and back

edit:trying driver verifier now
edit:i turned it on with the instructions in this post and nothing happenend while rebooting, should i try it again?

 

[Tews]

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).

Let it run as suggested...

 

[windowsuser111]

i have some questions about the verifier

-could it potentially cause a crash that i wouldn't be able to get out of?

-how much stress can i put on the pc while running it? (can i play games, work in photoshop?)

-will process lasso affect anything at all?

thanks, sorry for taking so long to respond