New
#11
You can go ahead and turn off verifier, as described in the instructions.
Upload the new dumps, and we'll take a look.
You can go ahead and turn off verifier, as described in the instructions.
Upload the new dumps, and we'll take a look.
turns out you can't just choose to reset verifier, you have to do this step (which i was unaware of for the better part of 3 hours)
"If you get a STOP screen (bsod) you will have to reboot to safe mode and run verifier again and have it "delete existing settings""
So I don't know if the original problem is better yet but at least I'm no longer constantly crashing upon boot.
Here's the new .dmp's
Please remove ZoneAlarm completely from your system, they appear to be the cause. I saw Jonathan suggest you this before but I haven't seen you remove it yet.
ZoneAlarm uninstaller - removal tool available - Windows Help Forum
Remove CounterSp, Sunbelt TDI Inspection System as well, it appear to be the cause
As Deep Freeze appear to be the cause, I would suggest to remove it as well. If you need a alternative AV program, try MSE as Jonathan suggested.
Run system file check please:Code:BugCheck C9, {c, 87463374, 9852cf48, 0} Probably caused by : netbt.sys ( netbt!SubmitTdiRequest+5e ) Followup: MachineOwner --------- BugCheck C2, {9b, 0, 2000, 8503ea0d} Unable to load image \SystemRoot\system32\DRIVERS\vsdatant.sys, Win32 error 0n2 *** WARNING: Unable to verify timestamp for vsdatant.sys *** ERROR: Module load completed but symbols could not be loaded for vsdatant.sys Probably caused by : vsdatant.sys ( vsdatant+2e9e6 ) Followup: MachineOwner --------- BugCheck C9, {c, 921704fc, 96488f48, 0} Probably caused by : afd.sys ( afd!AfdIssueDeviceControl+e7 ) Followup: MachineOwner --------- BugCheck C9, {c, 87463374, 9c2c8f48, 0} Probably caused by : netbt.sys ( netbt!SubmitTdiRequest+5e ) Followup: MachineOwner --------- BugCheck 1000008E, {c0000005, 82c1fbaa, 92158498, 0} *** WARNING: Unable to verify timestamp for sbtis.sys *** ERROR: Module load completed but symbols could not be loaded for sbtis.sys Probably caused by : sbtis.sys ( sbtis+ae1d ) Followup: MachineOwner --------- BugCheck 1000008E, {c0000046, 82c938f8, 8235b5ec, 0} *** WARNING: Unable to verify timestamp for DeepFrz.sys *** ERROR: Module load completed but symbols could not be loaded for DeepFrz.sys *** WARNING: Unable to verify timestamp for VMkbd.sys *** ERROR: Module load completed but symbols could not be loaded for VMkbd.sys Probably caused by : DeepFrz.sys ( DeepFrz+18775 ) Followup: MachineOwner ---------
SFC /SCANNOW Command - System File Checker
Let us know if you need help
Tuan
I removed deepfreeze, zonealarm, and vmware. I am currently not experiencing the bsod when I change video output from the laptop in question (the original issue was that I use a switch to go between a laptop and a desktop using one monitor, keyboard, and mouse. When the video feed changed the laptop bluescreened.)
This I believe is a solid indicator that one of those three applications was the culprit to the issues I was having. I will reinstall them one by one to test how windows handles it and I will report back on what I find. I appreciate everyones help with this as it was becoming quite the bother. Thanks!
I suggest keeping ZoneAlarm off, just because it is famous for causing so many problems. Keep MSE installed, and use that instead.
I can say first hand that MSE gives better performance anyway.
Made the steps, began reinstalling things one by one. Zone Alarm was reinstalled for a couple days, no crashes. Reinstalled Deep Freeze, BAM crash. I feel safe in saying Deep Freeze is the culprit behind the original BSOD when video output is interrupted. I uninstalled it and I still have a windows alert warning me about issues with deepfrz.sys and the only suggested solution is to email faronics with your key and they might give you an update. I'm on a trial version so we'll see how much sympathy they have. If anyone has any suggestions for fixing a .sys issue I'd love to hear them. Thanks guys.
Actually I thought that when I suggested you to remove it too, especially when I couldn't even find an article showing what it is and how to remove it. But yes, now you know the cause.Reinstalled Deep Freeze, BAM crash
Finger crossed that no more BSODs :)
It's a really cool program that locks your systems data so that no matter what changes are made when you reboot it goes back to how it was frozen. Universities all over use it. It was my luck that it crashed my system. Ran flawlessly on XP though. Good program, crappy compatibility issue.
Oh ok, I just realize what the program is. yes, I install that for my parents computer in case my brothers at home install crappy stuff. yes, I think it is perfect choice for window xp, but for vista and especially window 7, I'm not sure if it gonna run ok