windows 7 bsod help

usasma · 07 Mar 2011

You must keep the dadder.sys file out of the system. Don't use the DeathAdder mouse until we've solved this.

Then, you've gotta update or remove each of the following programs:
OLDER DRIVERS PRESENT IN THE DUMP FILES
- Please update these drivers from the device manufacturer's website - or uninstall/remove them from your system. Reference links included below.
- DO NOT use Windows Update or the Update Drivers function of Device Manager.
- Please feel free to post back about any drivers that you are having difficulty locating.
- Windows Update exceptions may be noted below for Windows drivers:

Code:


SCDEmu.SYS      Sun Nov 08 22:27:29 2009 (4AF78C21)
avipbb.sys      Mon Feb 22 05:08:50 2010 (4B8257B2)
cmudax3.sys     Mon Nov 30 22:31:07 2009 (4B148DFB)
WmXlCore.sys    Fri Sep 11 15:40:07 2009 (4AAAA797)
tap0901.sys     Wed Nov 19 13:22:35 2008 (4924596B)
mcdbus.sys      Tue Feb 24 05:34:07 2009 (49A3CD1F)
WmBEnum.sys     Fri Sep 11 15:40:09 2009 (4AAAA799)
Rt64win7.sys    Thu Jul 30 07:58:43 2009 (4A718AF3)
GEARAspiWDM.sys Mon May 18 08:17:04 2009 (4A1151C0)
WmFilter.sys    Fri Sep 11 15:40:09 2009 (4AAAA799)
avgntflt.sys    Thu Nov 11 10:59:48 2010 (4CDC12F4)
acedrv11.sys    Mon Jan 19 13:32:09 2009 (4974C729)
cpuz132_x64.sys Thu Mar 26 19:17:23 2009 (49CC0D03)
gdrv.sys        Thu Mar 12 23:22:29 2009 (49B9D175)
atikmpag.sys    Tue Oct 26 22:14:23 2010 (4CC78AFF)
atikmdag.sys    Tue Oct 26 22:29:53 2010 (4CC78EA1)
VKbms.sys       Thu Sep 30 12:16:33 2010 (4CA4B7E1)
dadder.sys      Mon Apr 19 05:04:42 2010 (4BCC1CAA)
dadder.sys      Thu Aug 02 05:33:03 2007 (46B1A4CF)
WmVirHid.sys    Fri Sep 11 15:40:05 2009 (4AAAA795)

If that doesn't fix things, then you've got to try stripping the system down in order to remove all but the essential pieces - then swap out each of the essential pieces to ensure that each of those is good.

waynebattle · 08 Mar 2011

The dadder.sys is still just c:\windows\system32\drivers\dadder.bak so I am not sure where else I should look.
I did find the file here, C:\Windows\System32\DriverStore\FileRepository\dadder.inf_amd64_neutral_f23561330219d441\dadder.sys
Should I rename it too?
I haven't used the deathadder mouse since we started this so not sure where it would be coming from.
I'll try to start updating the other drivers when I get chance. Thanks.

usasma · 08 Mar 2011

Let's leave things as they are and see what happens.
Worst case, we'll run Driver Verifier to see what's up.

waynebattle · 10 Mar 2011

I've tried to update a lot of the drivers. Can you see which ones may still be outstanding? I'm sorry, I got yanked off this a couple times and didn't keep list like I should have. My fault. Attached latest dump. still no dadder.sys just dadder.bak.

usasma · 11 Mar 2011

+ means it's been updated
- means it hasn't been updated
blank means that the driver wasn't present in the new memory dump:

+SCDEmu.SYS ; Sun Nov 08 22:27:29 2009 (4AF78C21) SCDEmu Mon Apr 12 04:52:25 2010 (4BC2DF49)
-avipbb.sys ; Mon Feb 22 05:08:50 2010 (4B8257B2) avipbb Mon Feb 22 05:08:50 2010 (4B8257B2)
-cmudax3.sys ; Mon Nov 30 22:31:07 2009 (4B148DFB) cmudax3 Mon Nov 30 22:31:07 2009 (4B148DFB)
+WmXlCore.sys ; Fri Sep 11 15:40:07 2009 (4AAAA797) WmXlCore Tue Apr 27 16:09:26 2010 (4BD74476)
-tap0901.sys ; Wed Nov 19 13:22:35 2008 (4924596B) tap0901 Wed Nov 19 13:22:35 2008 (4924596B)
-mcdbus.sys ; Tue Feb 24 05:34:07 2009 (49A3CD1F) mcdbus Tue Feb 24 05:34:07 2009 (49A3CD1F)
+WmBEnum.sys ; Fri Sep 11 15:40:09 2009 (4AAAA799) WmBEnum Tue Apr 27 16:10:19 2010 (4BD744AB)
-Rt64win7.sys ; Thu Jul 30 07:58:43 2009 (4A718AF3) Rt64win7 Thu Jul 30 07:58:43 2009 (4A718AF3)
-GEARAspiWDM.sys Mon May 18 08:17:04 2009 (4A1151C0) GEARAspiWDM Mon May 18 08:17:04 2009 (4A1151C0)
+WmFilter.sys ; Fri Sep 11 15:40:09 2009 (4AAAA799) WmFilter Tue Apr 27 16:10:19 2010 (4BD744AB)
-avgntflt.sys ; Thu Nov 11 10:59:48 2010 (4CDC12F4) avgntflt Thu Nov 11 10:59:48 2010 (4CDC12F4)
-acedrv11.sys ; Mon Jan 19 13:32:09 2009 (4974C729) acedrv11 Mon Jan 19 13:32:09 2009 (4974C729)
cpuz132_x64.sys Thu Mar 26 19:17:23 2009 (49CC0D03) NOT IN LATEST MEMORY DUMP
-gdrv.sys ; Thu Mar 12 23:22:29 2009 (49B9D175) gdrv Thu Mar 12 23:22:29 2009 (49B9D175)
+atikmpag.sys ; Tue Oct 26 22:14:23 2010 (4CC78AFF) atikmpag Wed Jan 26 17:13:33 2011 (4D409C8D)
+atikmdag.sys ; Tue Oct 26 22:29:53 2010 (4CC78EA1) atikmdag Wed Jan 26 17:48:28 2011 (4D40A4BC)
VKbms.sys ; Thu Sep 30 12:16:33 2010 (4CA4B7E1) NOT IN LATEST MEMORY DUMP
dadder.sys ; Mon Apr 19 05:04:42 2010 (4BCC1CAA) NOT IN LATEST MEMORY DUMP
dadder.sys ; Thu Aug 02 05:33:03 2007 (46B1A4CF) NOT IN LATEST MEMORY DUMP
WmVirHid.sys ; Fri Sep 11 15:40:05 2009 (4AAAA795) NOT IN LATEST MEMORY DUMP

waynebattle · 12 Mar 2011

Having issues with 4 drivers:
cmdudax3.sys - needs password to try to get driver?
mcdbus.sys - I've downloaded and installed latest magiciso, so not sure how to update driver further
rt64win7.sys - went to website, not sure what to download
acedrv11.sys - couldnt find driver

usasma · 12 Mar 2011

- cmdudax3.sys - click on the Have Account link and make up a new account. They have a pop-up, so you'll have to allow it in your popup blocker in order to get the download (or you can get the latest driver from the Gigabyte website. Worst case is that we disable sound until we're done troubleshooting.
- uninstall MagicISO and leave it off until we're finished troubleshooting
- Realtek driver here: Realtek
- For the acedrv11.sys driver
1 - set a system restore point
2 - go to C:\Windows\system32\drivers and rename acedrv11.sys to acedrv11.BAK
3 - reboot and see if everything is OK
This is a copy protection driver, so renaming it may have unforseen consequences. If it does, then use System Restore to set the computer back to before you started messing with it.

waynebattle · 12 Mar 2011

I think I've got all the drivers updated now. Take a look latest dump? Still BSOD.

usasma · 13 Mar 2011

Please uninstall OpenVPN for the duration of our testing - one of the drivers is from 2008 and isn't update.

The STOP errors continue as STOP 0x124's. Since you've updated all of these drivers and the errors still occur, it is most likely a hardware issue (although compatibility and Windows issues are a less likely possibility).

You can check for compatibility of your software and hardware here: Windows 7 Compatibility: Software Programs & Hardware Devices: Find Updates, Drivers, & Downloads

To test for Windows issues, you can wipe the hard drive with DBAN or KillDisk (both are free) and then install a bare Windows installation and test for further BSOD's.

We can run Driver Verifier, but it's not real likely that it'll reveal anything. There are recent reports of STOP 0x124 errors being due to a game ( https://www.sevenforums.com/crashes-d...ml#post1288538 ), so it may be worthwhile giving it a try. Please use these settings:

Using Driver Verifier is an iffy proposition. Most times it'll crash and it'll tell you what the driver is. But sometimes it'll crash and won't tell you the driver. Other times it'll crash before you can log in to Windows. If you can't get to Safe Mode, then you'll have to resort to offline editing of the registry to disable Driver Verifier.

So, I'd suggest that you first backup your stuff and then make sure you've got access to another computer so you can contact us if problems arise. Then make a System Restore point (so you can restore the system using the Vista/Win7 Startup Repair feature).

Then, 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"
NOTE: You can use Low Resource Simulation if you'd like. From my limited experimentation it makes the BSOD's come faster.
- 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).

Reboot into Windows (after the crash) and turn off Driver Verifier by going back in and selecting "Delete existing settings" on the first page, then locate and zip up the memory dump file and upload it with your next post.

If you can't get into Windows because it crashes too soon, try it in Safe Mode.
If you can't get into Safe Mode, try using System Restore from your installation DVD to set the system back to the previous restore point that you created.

If that doesn't work, post back and we'll have to see about fixing the registry entry off-line:

Code:

Delete these registry keys (works in XP, Vista, Win7):
        HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Session Manager\Memory Management\VerifyDrivers
        HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Session Manager\Memory Management\VerifyDriverLevel

More info on this at this link: Using Driver Verifier to identify issues with Windows drivers for advanced users

Finally, you can attempt to locate the faulty component by doing a hardware stripdown: Hardware Troubleshooting Via System Stripdown

waynebattle · 17 Mar 2011

I think I got it working...strange thing happened but I downloaded & installed the F4J bios and when I rebooted the system, when windows came up it said it was installing device driver for Realtek audio(which I had installed those drivers many reboots ago). I tried the game causing me most problem and no bsod. So the last several days no BSOD. So I appreciate your help getting all the latest drivers updated. I've learned a lot. I'm crossing my fingers. Thanks again.