New
#21
Alternatively, what software do I need to read the dump files (and hopefully work out what driver's causing the issue...)? It'd be very handy for future reference :)
Alternatively, what software do I need to read the dump files (and hopefully work out what driver's causing the issue...)? It'd be very handy for future reference :)
The MS page on that is seen at How to read the small memory dump files that Windows creates for debugging
Note that page was prepared when 7 was listed as "Windows 7 Beta". The Windows 7 SDK(Software Development Pack) is the download. Be sure to check off the debugging tools item when going to install. Driver Developer Resources: Debugging Tools for Windows
Open the dump file
To open the dump file after the installation is complete, follow these steps:
- Click Start, click Run, type cmd, and then click OK.
- Change to the Debugging Tools for Windows folder. To do this, type the following at the command prompt, and then press ENTER: cd c:\program files\debugging tools for windows
- To load the dump file into a debugger, type one of the following commands, and then press ENTER: windbg -y SymbolPath -i ImagePath -z DumpFilePath
kd -y SymbolPath -i ImagePath -z DumpFilePath
Sorry to be as persistent as this mutha**^$^*г&*%$*&$&* cold-boot-bsoding machine but can anyone please have a look at the last dump files I uploaded? I can't make head or tail of them. In the interim have disabled all ATI graphics and sound drivers and disabled any drivers on bits I'm not using. Shall see if this POS does the same thing tomorrow.
Hello,
It appears that AVG is causing the problem. Please uninstall it, and then run this tool: http://download.avg.com/filedir/util...removerx64.exe
Replace it with MSE: http://www.microsoft.com/security_essentials
You can now turn off driver verifier: Driver Verifier - Enable and Disable
...Summary of the dumps:
Code:Built by: 7600.16617.amd64fre.win7_gdr.100618-1621 Debug session time: Mon Nov 29 15:03:56.518 2010 (UTC - 5:00) System Uptime: 0 days 0:00:47.548 *** WARNING: Unable to verify timestamp for AVGIDSDriver.sys *** ERROR: Module load completed but symbols could not be loaded for AVGIDSDriver.sys Probably caused by : AVGIDSDriver.sys ( AVGIDSDriver+167d9 ) BUGCHECK_STR: 0xc4_f6 DEFAULT_BUCKET_ID: VERIFIER_ENABLED_VISTA_MINIDUMP PROCESS_NAME: svchost.exe FAILURE_BUCKET_ID: X64_0xc4_f6_VRF_AVGIDSDriver+167d9 ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии`` Built by: 7600.16617.amd64fre.win7_gdr.100618-1621 Debug session time: Mon Nov 29 14:55:26.280 2010 (UTC - 5:00) System Uptime: 0 days 0:00:50.685 *** WARNING: Unable to verify timestamp for avgfwd6a.sys *** ERROR: Module load completed but symbols could not be loaded for avgfwd6a.sys Probably caused by : avgfwd6a.sys ( avgfwd6a+2b3d ) BUGCHECK_STR: 0xc4_40 DEFAULT_BUCKET_ID: VERIFIER_ENABLED_VISTA_MINIDUMP PROCESS_NAME: System FAILURE_BUCKET_ID: X64_0xc4_40_VRF_avgfwd6a+2b3d ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
Or simply clean it off fully and see a fresh install following a full system restart. It does sound a bit odd like the AVG installation was corrupted somehow. I've run AVG for several years on XP, Vista, and 7 without ever running into booting problems as a result of it being on.
You guys are LEGENDS :) I'll try this out later and see what happens! It was one of the first things I'd installed after installing Windows, so it's highly probable I should have done a couple of shutdown/restart processes!
Will keep you posted :)
If you had a bad install and clean it off well and retry running AVG again without any further problems you've found the main problem. If it persists with a full clean install then you will need to find another suitable protection.
Several other here at SF run AVG without having any. But whenever any program is found to be unsuitable dump it regardless of what it is. You could be seeing a clash of some type if it wasn't from a bad install or some problematic files where you would need a substitute. See how it goes just the same.
Well, tee hee, I uninstalled, rebooted, reinstated other drivers, and have now installed AVG2011 (my licence key for AVG9 was kaput, as installing newer version, so have installed the FREE version of AVG2011... Watch this space LOL!
Thanks again guys!
Sorry to hear about the license part but at least this seems to be solved for you there. You can thank Jonathan_King for going over the dump file for you and finding the cause.
You may want to contact the Grisoft support some time to let them know what happened to you however. You may still be able to get some credit.