New
#11
another 101 bugcheck with "unknown driver"
In dxdiag it's showing your gfx card is installed and functioning but I notice It's using an unsigned driver for your HD4800, maybe try the 9.12 thats signed and seems stable ?
It's a shame about your motherboard being unsupported and I have to be honest I am seeing a lot of ASUS boards having trouble in the Windows 7 environment
my preference for builds over the past 6 months have been Biostar boards , I haven't had any issues :)
have you made sure you have a backup of all your critical files ?
given there seems to be an issue with the AHCI driver maybe you can reset in the bios to use IDE controller instead , but this may well need a fresh install ?
Hi icky
thanks for all your info
i went to AMD and ASUS to look for the AHCI drive. but ASUS had only vista drivers and when i looked at AMD
the mother board chipset doesnt come up.
But i managed to find it on GAME.AMD.com
I would have thought they are both the same site...
anyways
It has been installed and that allowed me to install the newest drivers for the GPU aswell.
But a new problem has come up.
Im unable to open up the catalyst controll centre, so i tried reinstalling it and same again.
i click on the icon/or in programs, all i c is the arrow trying to load and thats it.
I would suggest that you ditch the Raxco PerfectDisk driver app for now. Windows 7 has an on-board defrag that Task Manager schedules. You can always re-install later if you wish.
You mentioned VirginMedia Security - it has a firewall. I would remove the product for now - 3rd party firewalls tend to block local NETBIOS ports in Vista & Windows 7 causing system services to crash... which can result in a BSOD.
I found AVG drivers in the dumps. Remove AVG as well. It could be corrupted or could have caused corruption in VirginMedia or vice-versa. They will go after each other as each may consider the boot and kernel drivers of the other to be rogue.
AVG Removal --> AVG Antivirus and Security Software - Tools download
Re-boot after EACH removal; reset Windows firewall.
Use Microsoft Security Essentials, free --> http://www.microsoft.com/Security_Essentials/
These 2 drivers also in dumps; not able to ID them as of yet -
Code:rp_pkt64.sys Thu Apr 05 14:51:01 2007 (46154515) rp_skt64.sys Wed Nov 26 15:15:20 2008 (492DAE58)
Was system originally XP x86 or Vista x86?
Driver Verifier may be able to help flush the "unknown driver" out --> Tech Support Forum - View Single Post - Windows Has Recovered From Unexpected Shutdown - Blue Screen of Death - BSOD
Regards. . .
jcgriff2
,
progress at least and it's not a huge problem you can't access the catalyst control center atm .........
thanks griff for your input here youv'e spotted a few things I hadn't seen , so jonny try and follow all the things griff has advised and also let me know if you still get any bluescreens ?
as something else to check can you tell me what timings and voltage shows for your RAM in the BIOS and what voltage fro the Northbridge chipset ?
Last edited by ickymay; 22 Feb 2010 at 04:56.
Hi Guys
this is wot i have done
uninstalled Virginmedia > reboot.
download AVG remover and AVG ID protection Remover.
AVG remover Run. Reboot. AVG ID protection Remover Run. Reboot
After Reboot Blue Screen(file here)
Then Installed Microsoft Security Essentials. Reboot
Driver Verifier, followed instructions, After Reboot nothing happened
done this twice and had the same result.
Whats meant to happen after reboot??
And if i remembered correctly the Hard disk had had XP and Vista 32bit in it. but it was fomatted before installing this...
Icky ill get back to u on the ram and voltage settings
Icky im not sure if this is what you needed but here it is anyways
Hardware Monitor
CPU Temp 44.c
MB 38.c
CPU Fan 1227RPM
V Care Voltage 1.232V
3.3V Voltage 3.312V
5V Voltage 5.053V
12V Voltage 11.491V
Config System Frequency/ Voltage
AI over-clocking AUTO
CPU NB HT Link Speed AUTO
Processor Voltage AUTO
Processor NB Voltage AUTO
CPU VDDA Voltage AUTO
CPU Tweak Enabled
PLL1 Spread Spectrum Disabled
PLL2 Spread Spectrum Disabled
The last dump - bugcheck = 0x101 = X64_CLOCK_WATCHDOG_TIMEOUT_4_PROC_ANALYSIS_INCONCLUSIVE = a CPU timed out.
The system was up for just 45 seconds. The driver verifier needs time to stress-test the drivers. If it finds one it doesn't like, it will flag it and cause BSOD.
This old AMD chipset driver showed up in the loaded driver listing - needs to be updated -
Did you run the Windows 7 Upgrade Advisor?Code:ahcix64s.sys Thu Dec 28 05:52:55 2006 (4593A207)
--> Windows 7 Upgrade Advisor
Regards. . .
jcgriff2
.