New
#1
windows 7 bsod help
Windows 7 Home Premium 64-bit
pc & os about 1-2 years old
any other info needed please let me know
new to this so any help would be appreciated
dump files attached
Windows 7 Home Premium 64-bit
pc & os about 1-2 years old
any other info needed please let me know
new to this so any help would be appreciated
dump files attached
Have you deliberately disabled your ATI HDMI Audio? If so, why? If not, please update your ATI drivers.
50 memory dumps since the new year
MSINFO32 shows STOP 0x116 errors back in Sep 2010, and then you've been getting STOP 0x124 errors since then.
Older versions of Catalyst Control Center have been known to cause BSOD's.
Older versions of the Razer DeathAdder drivers have been known to cause BSOD's.
I would start by following the steps in this post: STOP 0x116: VIDEO_TDR_ERROR troubleshooting
After that, please read this post (for the STOP 0x124 errors): Stop 0x124 - what it means and what to try
I'll post back once the memory dumps are finished running....
Your BIOS is from 2009 and isn't listed on the Gigabyte website (yours is F4b - Gigabyte lists a BETA F4j)
Did you update the BIOS previously? If so, where did you get the BIOS files from?
All 50 errors are STOP 0x124
This means that you (most likely) either have a hardware problem or a compatibility problem.
Since your DeathAdder drivers are from 2007 - I'd suspect that this is the primary cause of your issues.
Please uninstall the DeathAdder software/drivers and test to see if that fixes it.
If it does, then install the latest drivers available from the Razer website and verify that the BSOD's don't come back.
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.
- Windows Update exceptions may be noted below for Windows drivers:
Only listing one of the STOP 0x124's in the summary:Code:atikmpag.sys Tue Oct 26 22:14:23 2010 (4CC78AFF) SCDEmu.SYS Sun Nov 08 22:27:29 2009 (4AF78C21) avipbb.sys Mon Feb 22 05:08:50 2010 (4B8257B2) WmXlCore.sys Fri Sep 11 15:40:07 2009 (4AAAA797) atikmdag.sys Tue Oct 26 22:29:53 2010 (4CC78EA1) Rt64win7.sys Thu Jul 30 07:58:43 2009 (4A718AF3) GEARAspiWDM.sys Mon May 18 08:17:04 2009 (4A1151C0) mcdbus.sys Tue Feb 24 05:34:07 2009 (49A3CD1F) tap0901.sys Wed Nov 19 13:22:35 2008 (4924596B) WmBEnum.sys Fri Sep 11 15:40:09 2009 (4AAAA799) cmudax3.sys Mon Nov 30 22:31:07 2009 (4B148DFB) avgntflt.sys Thu Nov 11 10:59:48 2010 (4CDC12F4) dadder.sys Thu Aug 02 05:33:03 2007 (46B1A4CF) WmFilter.sys Fri Sep 11 15:40:09 2009 (4AAAA799) 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) WmVirHid.sys Fri Sep 11 15:40:05 2009 (4AAAA795)
http://www.carrona.org/dvrref.html#atikmpag.sys
http://www.carrona.org/dvrref.html#SCDEmu.SYS
http://www.carrona.org/dvrref.html#avipbb.sys
http://www.carrona.org/dvrref.html#WmXlCore.sys
http://www.carrona.org/dvrref.html#atikmdag.sys
http://www.carrona.org/dvrref.html#Rt64win7.sys
http://www.carrona.org/dvrref.html#GEARAspiWDM.sys
http://www.carrona.org/dvrref.html#mcdbus.sys
http://www.carrona.org/dvrref.html#tap0901.sys
http://www.carrona.org/dvrref.html#WmBEnum.sys
http://www.carrona.org/dvrref.html#cmudax3.sys
http://www.carrona.org/dvrref.html#avgntflt.sys
http://www.carrona.org/dvrref.html#dadder.sys
http://www.carrona.org/dvrref.html#WmFilter.sys
http://www.carrona.org/dvrref.html#acedrv11.sys
http://www.carrona.org/dvrref.html#cpuz132_x64.sys
http://www.carrona.org/dvrref.html#gdrv.sys
http://www.carrona.org/dvrref.html#WmVirHid.sys
BSOD BUGCHECK SUMMARY
Code:Built by: 7600.16617.amd64fre.win7_gdr.100618-1621 Debug session time: Sat Mar 5 07:19:41.750 2011 (UTC - 5:00) System Uptime: 0 days 0:05:23.327 Probably caused by : hardware BUGCHECK_STR: 0x124_AuthenticAMD DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT PROCESS_NAME: Crysis2Demo.ex FAILURE_BUCKET_ID: X64_0x124_AuthenticAMD_PROCESSOR_CACHE Bugcheck code 00000124 Arguments 00000000`00000000 fffffa80`04ef8028 00000000`b66cc000 00000000`00000135 BiosVersion = F4b BiosReleaseDate = 11/13/2009 SystemManufacturer = Gigabyte Technology Co., Ltd. SystemProductName = GA-MA790GPT-UD3H ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
ATI HDMI Audio...I did disable...had read somewhere it may be the cause of BSOD in Batman:Arkham Asylum but I can re-enable if you think I should. Thanks.
I uninstall DeathAdder drivers but in the Device manager it still showed as using dadder.sys.? Should I remove everything relating to dadder & razer in the registry?
But I put an old logitech std usb mouse on and rebooted and used it for a while and it bsod'd. So, do you think I should get the latest Gigabyte BIOS first ?
I believe when I first got the pc, I updated & it would have only been from the gigabyte website. After looking at their site just now, I'm pretty sure I used their @BIOS to upgrade it.
In meantime I'll run that furmark & prime95 stuff.
Reenable the ATI HDMI Audio - then update your drivers
As for the Death Adder, check to ensure that the dadder.sys driver is really and truly gone from your system (search for it). Most commonly they are in C:\Windows\System32\drivers When you find it, rename it from .sys to .BAK and then reboot. If the driver loads (with or without the DeathAdder device attached) it can still cause BSOD's. If it BSOD's without the DeathAdder device and without the dadder.sys driver - then we have to look elsewhere for the cause.
DO NOT mess with the BIOS yet!!! It's possible that you installed a beta BIOS - but it's not necessary to do anything at this early stage in our diagnostics.
Go ahead and run the tests and that'll help us figure out what to do.
Good luck!
Enabled the ati hdmi audio & updated driver.
Renamed dadder.sys to dadder.bak - while using logitech, dadder.sys does not come back but when I put my deathadder back in and reboot the dadder.sys reappears....tested using just logitech and no dadder.sys and received bsod in game.
Furmark ran for a while stayed pretty much at 79C the whole time, will have to run prime95 tonight.
dump attached