New
#11
amd overdrive isnt compatable with my cpu. what should I use.
I know my ram is fine, ran a memtest for 26 hours.
amd overdrive isnt compatable with my cpu. what should I use.
I know my ram is fine, ran a memtest for 26 hours.
I have a list of the tests at: Hardware Diagnostics Try each one.
You can also use the Ultimate Boot CD - which has numerous different tests built into the disk.
oh I see them now, one more thing, could bent pins have something to do with it. if it is the cpu. and my motherboard doesnt support downclocking, is there a way I can lower the fsb.
I don't know if downclocking will even help in your situation.
Run the stress tests and let's see what the results are.
Do you have bent/broken pins? If so, I'd suggest posting to AMD Tech Support to see what they have to say. Although I favor Intel, I must say that I've received the best tech support from AMD over the last few months.
Just got a new BSOD
DRIVER_VERIFIER_IOMANAGER_VIOLATION
Happend again, while watching a YouTube video. just uninstalled Magic Iso/disk
w00t!!! Driver Verifier to the rescue!!! (sound byte here: http://www.carrona.org/mightymo.wav )
Looks like it blames MagicISO SCSI Host Controller driver (mcdbus.sys)
Since you've uninstalled MagicISO, I'd suggest watching for another BSOD (leave Driver Verifier working)
You can also remove BS_I2cIo.sys (it's still there). If you've already uninstalled that BIOS flash utility, then please post back for instructions on how to safely remove the driver.
Further info on BSOD error messages available at: http://www.carrona.org/bsodindx.html
The following info is just FYI, I've already addressed the issues that I saw in the above paragraphs
3RD PARTY DRIVERS PRESENT IN THE DUMP FILES
http://www.carrona.org/drivers/driver.php?id=Rt64win7.sysCode:Rt64win7.sys Thu Feb 26 04:04:13 2009 (49A65B0D) amdxata.sys Fri Mar 19 12:18:18 2010 (4BA3A3CA) MpFilter.sys Wed Apr 06 16:07:29 2011 (4D9CC801) scmndisp.sys Fri May 27 06:30:22 2011 (4DDF7D3E) speedfan.sys Fri Mar 18 12:08:46 2011 (4D83838E) bcmwlhigh664.sys Tue Apr 19 03:13:08 2011 (4DAD3604) LHidFilt.Sys Fri Sep 02 02:23:09 2011 (4E60764D) LMouFilt.Sys Fri Sep 02 02:23:15 2011 (4E607653) mcdbus.sys Tue Feb 24 05:34:07 2009 (49A3CD1F) nvhda64v.sys Tue Jan 17 07:45:46 2012 (4F156D7A) BS_I2cIo.sys Mon Dec 11 02:48:39 2006 (457D0D57) RTKVHD64.sys Tue Mar 27 05:01:50 2012 (4F7181FE) dc3d.sys Wed May 18 04:07:24 2011 (4DD37E3C) NuidFltr.sys Fri Apr 08 18:58:16 2011 (4D9F9308) point64.sys Wed May 18 04:07:20 2011 (4DD37E38) cpuz135_x64.sys Wed Sep 21 04:23:41 2011 (4E799F0D) nvlddmkm.sys Tue Apr 03 09:01:59 2012 (4F7AF4C7) nvBridge.kmd Fri May 20 23:58:23 2011 (4DD7385F)
http://www.carrona.org/drivers/driver.php?id=amdxata.sys
http://www.carrona.org/drivers/driver.php?id=MpFilter.sys
http://www.carrona.org/drivers/driver.php?id=scmndisp.sys
http://www.carrona.org/drivers/driver.php?id=speedfan.sys
http://www.carrona.org/drivers/driver.php?id=bcmwlhigh664.sys
http://www.carrona.org/drivers/driver.php?id=LHidFilt.Sys
http://www.carrona.org/drivers/driver.php?id=LMouFilt.Sys
http://www.carrona.org/drivers/driver.php?id=mcdbus.sys
http://www.carrona.org/drivers/driver.php?id=nvhda64v.sys
http://www.carrona.org/drivers/driver.php?id=BS_I2cIo.sys
http://www.carrona.org/drivers/driver.php?id=RTKVHD64.sys
http://www.carrona.org/drivers/driver.php?id=dc3d.sys
http://www.carrona.org/drivers/driver.php?id=NuidFltr.sys
http://www.carrona.org/drivers/driver.php?id=point64.sys
http://www.carrona.org/drivers/driver.php?id=cpuz135_x64.sys
http://www.carrona.org/drivers/driver.php?id=nvlddmkm.sys
http://www.carrona.org/drivers/driver.php?id=nvBridge.kmd
BSOD BUGCHECK SUMMARY
Code:Loading Dump File [C:\Users\FUBAR\_jcgriff2_\dbug\__Kernel__\042412-19858-01.dmp] Built by: 7601.17790.amd64fre.win7sp1_gdr.120305-1505 Debug session time: Tue Apr 24 15:49:08.284 2012 (UTC - 4:00) System Uptime: 0 days 3:43:29.001 *** WARNING: Unable to verify timestamp for mcdbus.sys *** ERROR: Module load completed but symbols could not be loaded for mcdbus.sys Probably caused by : mcdbus.sys ( mcdbus+36320 ) BUGCHECK_STR: 0xc9_7 DEFAULT_BUCKET_ID: VERIFIER_ENABLED_VISTA_MINIDUMP PROCESS_NAME: System FAILURE_BUCKET_ID: X64_0xc9_7_VRF_mcdbus+36320 Bugcheck code 000000C9 Arguments 00000000`00000007 fffff880`02c62320 fffffa80`05de2790 00000000`00000000 BiosVersion = 6.00 PG BiosReleaseDate = 01/10/2008 จจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจ``
I dont know anything about driver versifier, didn't even know it was running. how do I remove the BS_I2cIo.sys
Go to Start and type in "verifier" (without the quotes)
At the top of the search box, right click on verifier.exe and select "Run as administrator"
When the program opens, click on the button for "Delete existing settings"
Then click on the "Finish" button in the lower right corner of the window
Then reboot the system to reset the Driver Verifier to "OFF"
****************************************************
To remove the BS_I2cIo.sys driver please:
1 - Ensure that you can boot into Startup Repair from your installation DVD. If you can't, post back and we'll make other arrangements.
2 - Create a System Restore point (in case you can't get into Windows, you'll use the Startup Repair disk to access System Restore and restore the computer)
3 - Use Autoruns (which you downloaded for the jcgriff2 reports. Search for instances of BS_I2cIo.sys and disable them by removing the checkmark in the far left column of that entry
4 - Go to C:\Windows\System32\drivers and rename BS_I2cIo.sys to BS_I2cIo.BAD
5 - Reboot and see if the driver stays renamed (by checking in C:\Windows\System32\drivers
If the system doesn't boot to Windows, boot with the Startup Repair/Installation disk and get into the Startup Repair menu. Select System Restore and restore the system to the System Restore point that you made previously
I cant play any games at all -_- 5 minutes then they either crash or I get BSOD.
PAGE_FAULT_IN_NONPAGED_AREA
I need to know what exactly is causing this, because I was able to do anything fine for about a month.
I think you might find something different in the perfmon report.