Hi
I've had my new Windows 7 (Home Premium 64bit, OEM, registered and activated) PC since August, and, without fail, I get a BSOD just after the red ball stops moving on the Windows 7 startup screen.
I've not dared to try flashing the BIOS yet, but have (afaik) all the latest drivers for the motherboard and the graphics card.
I suspect it's the graphics card, as I've run memtest overnight over 4 passes with no issues, and, once the machine is up, it's stable. It'll also come out of sleep mode with no issues.
I've attached the dump file zip - any help gratefully appreciated before I break the machine any worse than I already have LOL.
Dom
I've had my new Windows 7 (Home Premium 64bit, OEM, registered and activated) PC since August, and, without fail, I get a BSOD just after the red ball stops moving on the Windows 7 startup screen.
I've not dared to try flashing the BIOS yet, but have (afaik) all the latest drivers for the motherboard and the graphics card.
I suspect it's the graphics card, as I've run memtest overnight over 4 passes with no issues, and, once the machine is up, it's stable. It'll also come out of sleep mode with no issues.
I've attached the dump file zip - any help gratefully appreciated before I break the machine any worse than I already have LOL.
Dom
�� Quote: Originally Posted by domfjbrown 
Hi
I've had my new Windows 7 (Home Premium 64bit, OEM, registered and activated) PC since August, and, without fail, I get a BSOD just after the red ball stops moving on the Windows 7 startup screen.
I've not dared to try flashing the BIOS yet, but have (afaik) all the latest drivers for the motherboard and the graphics card.
I suspect it's the graphics card, as I've run memtest overnight over 4 passes with no issues, and, once the machine is up, it's stable. It'll also come out of sleep mode with no issues.
I've attached the dump file zip - any help gratefully appreciated before I break the machine any worse than I already have LOL.
Dom
I've had my new Windows 7 (Home Premium 64bit, OEM, registered and activated) PC since August, and, without fail, I get a BSOD just after the red ball stops moving on the Windows 7 startup screen.
I've not dared to try flashing the BIOS yet, but have (afaik) all the latest drivers for the motherboard and the graphics card.
I suspect it's the graphics card, as I've run memtest overnight over 4 passes with no issues, and, once the machine is up, it's stable. It'll also come out of sleep mode with no issues.
I've attached the dump file zip - any help gratefully appreciated before I break the machine any worse than I already have LOL.
Dom
the modules are in Chinese so we have no idea what they are or do.
Code:
??????????????????????????????????????? fffff880`077ca000 0x0001e000 7/13/2009 18:23:50 0x4a5bc206 fffff880`077ac000 ????????????????????????????????????????? fffff880`03fd1000 0x00016000 7/13/2009 19:10:24 0x4a5bccf0 fffff880`03fbb000 ???????????????????????????????????????? fffff880`041a7000 0x000f4000 10/1/2009 20:00:14 0x4ac5509e fffff880`040b3000 ???????????????????????????????????????? fffff880`04fe8000 0x0001d000 7/13/2009 19:00:40 0x4a5bcaa8 fffff880`04fcb000 ????????????????????????????????????????? fffff880`04839000 0x0000c000 7/13/2009 19:10:00 0x4a5bccd8 fffff880`0482d000 ????????????????????????????????????????? fffff880`03fac000 0x00046000 7/6/2010 20:15:42 0x4c33d53e fffff880`03f66000 ??????????????????????????????????????? fffff880`07692600 0x0004e600 10/7/2009 03:27:59 0x4acc510f fffff880`07644000 ??????????????????????????????????? fffff880`03edf000 0x00043000 3/3/2010 23:32:25 0x4b8f37d9 fffff880`03e9c000 ????????????????????????????????????????????? fffff880`04ff8000 0x00010000 7/13/2009 19:00:33 0x4a5bcaa1 fffff880`04fe8000 ???????????????????????????????????????? fffff880`041ed000 0x00046000 7/13/2009 18:38:32 0x4a5bc578 fffff880`041a7000 ????????????????????�???????????????????? fffff880`03e9c000 0x0000f000 7/13/2009 18:19:50 0x4a5bc116 fffff880`03e8d000
The only thing I can think of is to run a system file check to verify and repair your system files.\
SFC /SCANNOW Command - System File Checker
Ken J
Hello domfjbrown Welcome to the Seven Forums!
One way to reveal the actual source of the problem causing the blue screens would be disabling the automatic restart upon System Failure option in order to note the actual error information displated on the crash. That will have a specific error code which can be looked up as well as a look at the Event Viewer logs for the company name usually that will point to the video card or other software/hardware.
The image attached shows where that is in the "Control Panel>System>Advanced Settings>Start & Recovery" screen. You simply uncheck the item pointed to and allow the system to freeze on the next BSOD long enough to view and jot down the information. That will can a real help in isolating the problem by first looking up the information for that particular error.
One way to reveal the actual source of the problem causing the blue screens would be disabling the automatic restart upon System Failure option in order to note the actual error information displated on the crash. That will have a specific error code which can be looked up as well as a look at the Event Viewer logs for the company name usually that will point to the video card or other software/hardware.
The image attached shows where that is in the "Control Panel>System>Advanced Settings>Start & Recovery" screen. You simply uncheck the item pointed to and allow the system to freeze on the next BSOD long enough to view and jot down the information. That will can a real help in isolating the problem by first looking up the information for that particular error.
�� Quote: Originally Posted by zigzag3143 �� Quote: Originally Posted by domfjbrown Hi
I've had my new Windows 7 (Home Premium 64bit, OEM, registered and activated) PC since August, and, without fail, I get a BSOD just after the red ball stops moving on the Windows 7 startup screen.
I've not dared to try flashing the BIOS yet, but have (afaik) all the latest drivers for the motherboard and the graphics card.
I suspect it's the graphics card, as I've run memtest overnight over 4 passes with no issues, and, once the machine is up, it's stable. It'll also come out of sleep mode with no issues.
I've attached the dump file zip - any help gratefully appreciated before I break the machine any worse than I already have LOL.
Dom
I've had my new Windows 7 (Home Premium 64bit, OEM, registered and activated) PC since August, and, without fail, I get a BSOD just after the red ball stops moving on the Windows 7 startup screen.
I've not dared to try flashing the BIOS yet, but have (afaik) all the latest drivers for the motherboard and the graphics card.
I suspect it's the graphics card, as I've run memtest overnight over 4 passes with no issues, and, once the machine is up, it's stable. It'll also come out of sleep mode with no issues.
I've attached the dump file zip - any help gratefully appreciated before I break the machine any worse than I already have LOL.
Dom
the modules are in Chinese so we have no idea what they are or do.
Code:
??????????????????????????????????????? fffff880`077ca000 0x0001e000 7/13/2009 18:23:50 0x4a5bc206 fffff880`077ac000 ????????????????????????????????????????? fffff880`03fd1000 0x00016000 7/13/2009 19:10:24 0x4a5bccf0 fffff880`03fbb000 ???????????????????????????????????????? fffff880`041a7000 0x000f4000 10/1/2009 20:00:14 0x4ac5509e fffff880`040b3000 ???????????????????????????????????????? fffff880`04fe8000 0x0001d000 7/13/2009 19:00:40 0x4a5bcaa8 fffff880`04fcb000 ????????????????????????????????????????? fffff880`04839000 0x0000c000 7/13/2009 19:10:00 0x4a5bccd8 fffff880`0482d000 ?????????????????????????????�??????????? fffff880`03fac000 0x00046000 7/6/2010 20:15:42 0x4c33d53e fffff880`03f66000 ??????????????????????????????????????? fffff880`07692600 0x0004e600 10/7/2009 03:27:59 0x4acc510f fffff880`07644000 ??????????????????????????????????? fffff880`03edf000 0x00043000 3/3/2010 23:32:25 0x4b8f37d9 fffff880`03e9c000 ????????????????????????????????????????????? fffff880`04ff8000 0x00010000 7/13/2009 19:00:33 0x4a5bcaa1 fffff880`04fe8000 ???????????????????????????????????????? fffff880`041ed000 0x00046000 7/13/2009 18:38:32 0x4a5bc578 fffff880`041a7000 ????????????????????�???????????????????? fffff880`03e9c000 0x0000f000 7/13/2009 18:19:50 0x4a5bc116 fffff880`03e8d000
SFC /SCANNOW Command - System File Checker
Ken J
**EDIT** Or Chinese. Ha. We both better brush up.
Thanks for this!
I did actually have the error codes written down using that method a while back, but haven't got them handy! I'll try it again and get back to you guys.
Why would there be modules in chinese on an OEM (genuine) Windows7 installation, or are these for some kind of peripheral driver? Also, how would I go about getting a copy of the Beta of Service Pack 1 - is it legit?
I'll try this tonight and get back to you (am in the UK so it'll be about 10 hours from now - assuming I don't end up in the pub!).
Dom
I did actually have the error codes written down using that method a while back, but haven't got them handy! I'll try it again and get back to you guys.
Why would there be modules in chinese on an OEM (genuine) Windows7 installation, or are these for some kind of peripheral driver? Also, how would I go about getting a copy of the Beta of Service Pack 1 - is it legit?
I'll try this tonight and get back to you (am in the UK so it'll be about 10 hours from now - assuming I don't end up in the pub!).
Dom
�� Quote: Originally Posted by domfjbrown Thanks for this!
I did actually have the error codes written down using that method a while back, but haven't got them handy! I'll try it again and get back to you guys.
Why would there be modules in chinese on an OEM (genuine) Windows7 installation, or are these for some kind of peripheral driver? Also, how would I go about getting a copy of the Beta of Service Pack 1 - is it legit?
I'll try this tonight and get back to you (am in the UK so it'll be about 10 hours from now - assuming I don't end up in the pub!).
Dom
I did actually have the error codes written down using that method a while back, but haven't got them handy! I'll try it again and get back to you guys.
Why would there be modules in chinese on an OEM (genuine) Windows7 installation, or are these for some kind of peripheral driver? Also, how would I go about getting a copy of the Beta of Service Pack 1 - is it legit?
I'll try this tonight and get back to you (am in the UK so it'll be about 10 hours from now - assuming I don't end up in the pub!).
Dom
No it isnt legit. Didnt come from MS. One place I have seen it I wouldnt trust to download anything
The best advice anyone can offer is removing any unknowns not from a genuine source. The actual MS page for the SP1 RC is seen at Windows Server 2008 R2 SP1 Beta
That will bring you to Download Windows 7 and Windows Server 2008 R2 Service Pack 1 (SP1) Release Candidate(RC)
Some additional information about the RC presently available is seen at Making the Experience Better Together with Windows 7
That will bring you to Download Windows 7 and Windows Server 2008 R2 Service Pack 1 (SP1) Release Candidate(RC)
Some additional information about the RC presently available is seen at Making the Experience Better Together with Windows 7
As I predicted, didn't go near my PC last night LOL...
All my software on this PC is definitely fully legit - even GTA San Andreas and IV
I'm still wondering if it could be something to do with the power supply (shouldn't be - it's overkill for what I'm running) or, here's the interesting thing - AVG version 9 (bought), as it seems to crash on an AVG module when booting in safe mode sometimes...
I'll definitely get the error codes for you guys later today though! Thanks again for your help.
That chinese stuff is still a mystery though...
All my software on this PC is definitely fully legit - even GTA San Andreas and IV
I'm still wondering if it could be something to do with the power supply (shouldn't be - it's overkill for what I'm running) or, here's the interesting thing - AVG version 9 (bought), as it seems to crash on an AVG module when booting in safe mode sometimes... I'll definitely get the error codes for you guys later today though! Thanks again for your help.
That chinese stuff is still a mystery though...
Did you inadvertently download any of the optional language packs through the MS update site? That would be one explaination for the other language being seen.
Is that an Antec TP 650w? You misspelled the name in your specs.
A failing supply wouldn't particularly generate any BSODs rulling that out.
With the usual causes being sofrware related you may want to look at which ATI Catalyst version you have on now as problems have been seen with the 10.5 and newer versions on some systems. You could elimate that as a cause by removing the present catalyst install and downloading a fresh maybe being a different number.
Is that an Antec TP 650w? You misspelled the name in your specs.
A failing supply wouldn't particularly generate any BSODs rulling that out.With the usual causes being sofrware related you may want to look at which ATI Catalyst version you have on now as problems have been seen with the 10.5 and newer versions on some systems. You could elimate that as a cause by removing the present catalyst install and downloading a fresh maybe being a different number.
He he - yep, it's an Antec; I obviously didn't select the whole line from my eBuyer parts order screen
Right - it BSOD'd 3 times in a row this morrning, so I power cycled it and F8'd it and got error codes something like the following (my eyesight's not that good, so lost count on the number of zeros in the numbers - helpfully, not!):
PFN list corrupt
0x0000004e, 0x0000000000000007, 0x00118763, and then a couple with just all zeros.
I'm now about to try the theory of installing an older ATI graphics driver. Will be back soon! Have a good weekend in the meantime guys, and thanks for the help - majorly appreciated
Right - it BSOD'd 3 times in a row this morrning, so I power cycled it and F8'd it and got error codes something like the following (my eyesight's not that good, so lost count on the number of zeros in the numbers - helpfully, not!):
PFN list corrupt
0x0000004e, 0x0000000000000007, 0x00118763, and then a couple with just all zeros.
I'm now about to try the theory of installing an older ATI graphics driver. Will be back soon! Have a good weekend in the meantime guys, and thanks for the help - majorly appreciated
Dom .. navigate to c:/windows/minidump and upload the latest .dmp files.. 
�� Quote: Originally Posted by domfjbrown He he - yep, it's an Antec; I obviously didn't select the whole line from my eBuyer parts order screen
Right - it BSOD'd 3 times in a row this morrning, so I power cycled it and F8'd it and got error codes something like the following (my eyesight's not that good, so lost count on the number of zeros in the numbers - helpfully, not!):
PFN list corrupt
0x0000004e, 0x0000000000000007, 0x00118763, and then a couple with just all zeros.
I'm now about to try the theory of installing an older ATI graphics driver. Will be back soon! Have a good weekend in the meantime guys, and thanks for the help - majorly appreciated
Right - it BSOD'd 3 times in a row this morrning, so I power cycled it and F8'd it and got error codes something like the following (my eyesight's not that good, so lost count on the number of zeros in the numbers - helpfully, not!):
PFN list corrupt
0x0000004e, 0x0000000000000007, 0x00118763, and then a couple with just all zeros.
I'm now about to try the theory of installing an older ATI graphics driver. Will be back soon! Have a good weekend in the meantime guys, and thanks for the help - majorly appreciated
Bugchecks Explained: PFN_LIST_CORRUPT
�� Quote: Originally Posted by Tews Dom .. navigate to c:/windows/minidump and upload the latest .dmp files..
Sorry - partially sighted and missed the upload button. Duuuur - been a long day at work!
My plan - flash BIOS, remove ATI driver (also using driverclean or whatsitcalled) and then power down, and try again tomorrow!
My plan - flash BIOS, remove ATI driver (also using driverclean or whatsitcalled) and then power down, and try again tomorrow!
Flashed up to F8 BIOS now - that was fairly easy
Oh yeah - meant to say on Catalyst 10.4 it was still cold booting - so I wonder what it's all about? Seriously thinking of buying a new graphics card as the one I have doesn't seem to be good enough for GTA IV anyway (though the reg key for that's not letting me reinstall a legit code now - grrrr!)
Why is everyone always in a rush to flash the bios? The old saying of "don't fix what isn't broke to start with" seems to pass right by. Did you review the indormation on the page posted earlier on the actual cause?
Quote:
How Should I Fix It?
How this is fixed varies depending on the reason of the bugcheck. Using Driver Verifier and the checked build of the O/S should allow you to pinpoint the driver that is either corrupting memory or mishandling MDLs. If the offending driver is not a driver that you have any control over, the only available option is disabling the driver until a fixed version is available.
How this is fixed varies depending on the reason of the bugcheck. Using Driver Verifier and the checked build of the O/S should allow you to pinpoint the driver that is either corrupting memory or mishandling MDLs. If the offending driver is not a driver that you have any control over, the only available option is disabling the driver until a fixed version is available.
Well, that might be so, but at least now I know it's NOT the BIOS but this POS graphics card (presumably). When I've got some time (ie a day!) to look at this Driver Verifier thing I'll get to the bottom of it.
I mean, if it IS the graphics driver (and now on Catalyst 11) then I give up - if they can't get a driver fixed this late in the game I'll buy a graphics card from someone who knows what they're doing
I mean, if it IS the graphics driver (and now on Catalyst 11) then I give up - if they can't get a driver fixed this late in the game I'll buy a graphics card from someone who knows what they're doing
I would revert back to one of the earlier catalysts at least until 12 or 13 is found to work. I run a 5xxx series card here as well but only ended up with some OpenGL issues with any past the Cat. 4.
First you will to boot up in safe mode first however to see the Cat. and drivers uninstalled. I've into a few buggy Catalyst versions in the past and simply had to wait for the next one or following to watch everything run like it should.
Don't think for a moment NVidia hasn't seen problems with their updates at times either. When the 8800s first came people were having some issues there as well. AMD/ATI is simply running into some issues with a few new things they decided to add in.
First you will to boot up in safe mode first however to see the Cat. and drivers uninstalled. I've into a few buggy Catalyst versions in the past and simply had to wait for the next one or following to watch everything run like it should.
Don't think for a moment NVidia hasn't seen problems with their updates at times either. When the 8800s first came people were having some issues there as well. AMD/ATI is simply running into some issues with a few new things they decided to add in.
This is what I have from the earlier steps mentioned in this thread (abridged!):
C:\Windows\system32>sfc /scannow
Beginning system scan. This process will take some time.
Beginning verification phase of system scan.
Verification 100% complete.
Windows Resource Protection did not find any integrity violations.
-----
From fcdetails:
2010-11-29 19:20:50, Info CSI 000003dd [SR] Repairing 0 components
2010-11-29 19:20:50, Info CSI 000003de [SR] Beginning Verify and Repair transaction
2010-11-29 19:20:50, Info CSI 000003e0 [SR] Repair complete
----
I've run Driver Verifier too (though can't seem to find the files it created though have a .dmp file from the right time - as it BSOD'd almost immediately on opening to the Windows desktop (so perhaps we're getting somewhere!). I've enclosed a zip file with this and the older .dmp files, and an XML file from the first BSOD incident.
Hopefully some amazing person here can make head or tail of said .zip file
C:\Windows\system32>sfc /scannow
Beginning system scan. This process will take some time.
Beginning verification phase of system scan.
Verification 100% complete.
Windows Resource Protection did not find any integrity violations.
-----
From fcdetails:
2010-11-29 19:20:50, Info CSI 000003dd [SR] Repairing 0 components
2010-11-29 19:20:50, Info CSI 000003de [SR] Beginning Verify and Repair transaction
2010-11-29 19:20:50, Info CSI 000003e0 [SR] Repair complete
----
I've run Driver Verifier too (though can't seem to find the files it created though have a .dmp file from the right time - as it BSOD'd almost immediately on opening to the Windows desktop (so perhaps we're getting somewhere!). I've enclosed a zip file with this and the older .dmp files, and an XML file from the first BSOD incident.
Hopefully some amazing person here can make head or tail of said .zip file
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
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
Quote:
Open the dump file
To open the dump file after the installation is complete, follow these steps:
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:
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
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
Let us know, I suspect that AVG removal will do good.
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.
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!
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.
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.
Well, I suspect the licence key didn't work because I installed the latest version of AVG (which isn't, err, version 9 which I was licenced for). Durrrr
Anyway, I'm hoping when I switch my PC on again when I get home, it'll boot nicely-nice We shall see (and thanks, Jonathan_King - I definitely owe you one
Anyway, I'm hoping when I switch my PC on again when I get home, it'll boot nicely-nice
We shall see (and thanks, Jonathan_King - I definitely owe you one With AVG 2011 it still BSODs...
Bloody POS. Uninstalling now, and won't be near this PC until Saturday. I still don't see how AVG can cause a cold boot crash - can it be something else AS WELL as AVG causing the crash with driver verifier?
Watch this space
Bloody POS. Uninstalling now, and won't be near this PC until Saturday. I still don't see how AVG can cause a cold boot crash - can it be something else AS WELL as AVG causing the crash with driver verifier?
Watch this space
That's something else for sure! As suspected the most AVG would cause would at the worst stall Windows when already having reached the desktop. With BSODs you want to uncheck the automatic restart in the advanced system settings if needed to jot down the actual error code.
You could be looking at a hardware issue resulting in software errors being tacked on as well or some device driver is loading sideways on you. But the actual error message on the blue screen is what you will want to pass along here since that will be pointing at the likely source of your problems.
You could be looking at a hardware issue resulting in software errors being tacked on as well or some device driver is loading sideways on you. But the actual error message on the blue screen is what you will want to pass along here since that will be pointing at the likely source of your problems.
The only other thing that I can see causing AVG to crash would be your old Realtek Ethernet drivers: Install these updated ones: Realtek
In my experience, cold boot BSODs are usually caused by RAM. Try running Memtest86, after your machine is cold.
RAM - Test with Memtest86+
Code:
Rt64win7.sys Thu Aug 20 12:05:06 2009 (4A8D7432)
In my experience, cold boot BSODs are usually caused by RAM. Try running Memtest86, after your machine is cold.
RAM - Test with Memtest86+
Agreed! Bad ram will cause a lengthy list of issues to begin with. A good run of memtest certainly won't hurt.
You may want to run a hard drive diagnostics tool as well to see any if problems like bad sectors are being seen with the drive. Meanwhile try to grab any further blue screen error information since that will be the largest clue pointing to hardware or software in most cases.
You may want to run a hard drive diagnostics tool as well to see any if problems like bad sectors are being seen with the drive. Meanwhile try to grab any further blue screen error information since that will be the largest clue pointing to hardware or software in most cases.
Thanks guys - that's food for thought! At work we have a free licence for Sophos, so am installing that tonight BEFORE going online again first...
I've run Memtest86 overnight from a cold boot with no errors, and have chkdsk'd the hard drive a couple of times, though will retry that later as well.
The Realtek ethernet drivers are supposedly the latest ones from Gigabyte for my board, but I'll also try installing those too. Will definitely be back soon with more info - thanks for this, guys
Mind you, will have a good look inside my case first - I kicked the computer HARD several times on Saturday (yes, the HDD was powered down). Made me feel a lot better, but made the case look rather scuffed
I've run Memtest86 overnight from a cold boot with no errors, and have chkdsk'd the hard drive a couple of times, though will retry that later as well.
The Realtek ethernet drivers are supposedly the latest ones from Gigabyte for my board, but I'll also try installing those too. Will definitely be back soon with more info - thanks for this, guys
Mind you, will have a good look inside my case first - I kicked the computer HARD several times on Saturday (yes, the HDD was powered down
). Made me feel a lot better, but made the case look rather scuffed Well, that was a new one; got this in SAFE MODE (with networking) before putting AVG9 back on and trying those new drivers:
irql_not_less_or_equal windows 7 0x0000000a 0x000005ab00007b370 0x00000000000000002 0x0000000000000001 0xfffff800020c6419
I think that those codes are correct... Anyhow, the computer's up for now, and I've got Memtest in my CD drive for trying from cold tomorrow morning.
Interestingly, this last BSOD didn't create a minidump file... D'oh.
At least I've not kicked the computer this time
irql_not_less_or_equal windows 7 0x0000000a 0x000005ab00007b370 0x00000000000000002 0x0000000000000001 0xfffff800020c6419
I think that those codes are correct... Anyhow, the computer's up for now, and I've got Memtest in my CD drive for trying from cold tomorrow morning.
Interestingly, this last BSOD didn't create a minidump file... D'oh.
At least I've not kicked the computer this time
The irql_not_less_or_equal part of that points to a kernel mode driver issue of some type. At least that part is software not a hardware fault. A look at the Event Viewer logs would be an idea to see what manufacturers names are seen there.
<wipes egg off face>
Ohmygod - this gets weirder and weirder (thanks by the way, Night Hawk - will try to suss that one out later)... Cold booted straight into Memtest86 this morning, and errors all over the shop - a whole wall of red! Have left it running while at work, but looks like it is mainly down to memory after all!
So - what's the likeliest cause (as it's fine after a power cycle)? Should I meddle with the memory voltages, buy some new RAM (not a happy option
) or send the Corsair RAM back and get it exchanged?...
Curiouser and curiouser...
Ohmygod - this gets weirder and weirder (thanks by the way, Night Hawk - will try to suss that one out later)... Cold booted straight into Memtest86 this morning, and errors all over the shop - a whole wall of red! Have left it running while at work, but looks like it is mainly down to memory after all!
So - what's the likeliest cause (as it's fine after a power cycle)? Should I meddle with the memory voltages, buy some new RAM (not a happy option
) or send the Corsair RAM back and get it exchanged?... Curiouser and curiouser...
I suggest you send the RAM back for an exchange.
Out of the 100+ cold-boot BSODs I have seen, perhaps a couple of them were solved by increasing the RAM voltage slightly. Not a great success rate, but perhaps worth a shot.
Out of the 100+ cold-boot BSODs I have seen, perhaps a couple of them were solved by increasing the RAM voltage slightly. Not a great success rate, but perhaps worth a shot.
I tend to lean towards the PSU with cold boot issues. Maybe trying a different PSU would be worth while.
It's a 650watt Bronze-rated PSU with not an awful lot barring the mobo and a single graphics card - I don't believe it's anything to do with the PSU when there's such a graphical demonstration of the RAM thing... I'm not wasting money on another PSU and more RAM after all the money I've already invested in this flipping thing GRRRR...
I mean, now, NONE of the DVD writers can write to blanks either - this is starting to really **** me off...
I mean, now, NONE of the DVD writers can write to blanks either - this is starting to really **** me off...
If your memory is faulty, it can cause all sorts of problems with your system. These problems may or may not be consistent. Another thing that I would do if your motherboard has on-board graphics is to remove your graphics card and use the on-board instead. This will ease the load on your PSU, which might be enough to solve the problems.
How much RAM do you have in your system, and how many sticks? Your tests seem to point to RAM being the culprit. What you need to do is to test each stick of RAM individually, preferably for 3 or more complete test runs in each memory slot. When you have found a stick/slot that yields no errors, try running your system with just that single stick in that slot and see if it still BSODs. If it doesn't, then you have probably found the problem.
How much RAM do you have in your system, and how many sticks? Your tests seem to point to RAM being the culprit. What you need to do is to test each stick of RAM individually, preferably for 3 or more complete test runs in each memory slot. When you have found a stick/slot that yields no errors, try running your system with just that single stick in that slot and see if it still BSODs. If it doesn't, then you have probably found the problem.
He has a pair of 2gb dimms listed in his specs where pulling one to test the other would be the thought. It's likely only one dimm is faulty which would cause a list of problems.
Another likely problem is knowing what the voltage is! Not raising the voltage when the board expects:
"4 x 1.5V DDR3 DIMM sockets supporting up to 16 GB of system memory (Note 1)" GIGABYTE - Motherboard - Socket 1156 - GA-P55-USB3 (rev. 2.0)
That board like the one here runs 1.5v memory not 1.9v like they typically have listed in their supported memory list(which is out to lunch thinking there). I ran into that with the new build when first going with OCZ Gold and ending up with the memory speed seen at 1066 rather then the 1600 it was supposed to be until swapping to the Mushkin 1.5v memory installed since.
Another likely problem is knowing what the voltage is! Not raising the voltage when the board expects:
"4 x 1.5V DDR3 DIMM sockets supporting up to 16 GB of system memory (Note 1)" GIGABYTE - Motherboard - Socket 1156 - GA-P55-USB3 (rev. 2.0)
That board like the one here runs 1.5v memory not 1.9v like they typically have listed in their supported memory list(which is out to lunch thinking there). I ran into that with the new build when first going with OCZ Gold and ending up with the memory speed seen at 1066 rather then the 1600 it was supposed to be until swapping to the Mushkin 1.5v memory installed since.
Ahhh - should I try ramping the volts up as high as possible (1.9) then? I could have sworn that memory was listed as compatible on Gigabyte's website...
Re the graphics - I got a mobo without as the onboard graphics is usually fairly weedy, but then again, for games, the card I got is too (upgrade soon if I can lick the memory issues...)
I still don't understand why none of my DVD/CD writers will write to blank discs now though (admittedly, I pulled all the power to the optical drives while troubleshooting last week; could Win7 have got its knickers in a noodle? They all READ discs fine, but when you put a blank in, they claim they can't write to that type of disc. I got one disc to burn in my SATA drive last night, but that was it...
Re the graphics - I got a mobo without as the onboard graphics is usually fairly weedy, but then again, for games, the card I got is too (upgrade soon if I can lick the memory issues...)
I still don't understand why none of my DVD/CD writers will write to blank discs now though (admittedly, I pulled all the power to the optical drives while troubleshooting last week; could Win7 have got its knickers in a noodle? They all READ discs fine, but when you put a blank in, they claim they can't write to that type of disc. I got one disc to burn in my SATA drive last night, but that was it...
A colleague has suggested I fiddle with the RAM voltage, and, if that solves it, burning and reinstalling the whole system. I'm leaning to this idea as well as all the data I have is also on an old HDD so I can just copy the data back again afterwards. Have ordered a cheapy USB-SATA dock to do just this Will have a fiddle with the voltages later and let you guys know
Will have a fiddle with the voltages later and let you guys know That board runs memory at 1.5-1.65v at the max. If your memory speed is listed slower then the 1333 default you should be seeing the memory was rated for a higher voltage while the board simply backclocks it down to run at the 1.5v.
This is why I say their supposed memory supported list is in need of some work there listing 1.9v memory while the boards only run the 1.5v at the native speeds! But that still doesn't account for the cold boot issues.
When having the 1.9v OCZ memory in the system still ran fine except for seeing the memory speed reduced to 1066. Unfortunately the memory was ordered prior to reading the user manual which specifies 1.5v dimms. The supported list shows memory that will still be usable but not adequate.
You mentioned initially having run memtest at the top of the thread and that was advised again suggesting a look at the main drive for either bad sectors or some factory partitioning errors. As far as having a usb enclosure for adding a drive to back things up on I use one here that accepts both ide and sata drives for retrieving things from old cases as well as temp external storage.
This is why I say their supposed memory supported list is in need of some work there listing 1.9v memory while the boards only run the 1.5v at the native speeds! But that still doesn't account for the cold boot issues.
When having the 1.9v OCZ memory in the system still ran fine except for seeing the memory speed reduced to 1066. Unfortunately the memory was ordered prior to reading the user manual which specifies 1.5v dimms. The supported list shows memory that will still be usable but not adequate.
You mentioned initially having run memtest at the top of the thread and that was advised again suggesting a look at the main drive for either bad sectors or some factory partitioning errors. As far as having a usb enclosure for adding a drive to back things up on I use one here that accepts both ide and sata drives for retrieving things from old cases as well as temp external storage.
"You mentioned initially having run memtest at the top of the thread and that was advised again suggesting a look at the main drive for either bad sectors or some factory partitioning errors. As far as having a usb enclosure for adding a drive to back things up on I use one here that accepts both ide and sata drives for retrieving things from old cases as well as temp external storage."
I've got a USB SATA docking thingy on order
The memory is DEFINITELY registering as 1333 - correct. Mysterious...
I ran memtest originally after going through all the cold boot issues... The last couple of days, I've run it from cold (errors all over the place), once all day while at work (still erroring when I got back). Both times, a power cycle got memtest to produce NO errors at all!!! So I'm certain it's memory/motherboard-related.
Incidentally, I WAS able to ramp up the voltages to 1.9v (but it was in the "red zone" in the listings, whatever that meant) and I still had a cold boot error as before last night. So I'm going to yank out the chips and try one after another to see what happens...
I've got a USB SATA docking thingy on order
The memory is DEFINITELY registering as 1333 - correct. Mysterious...
I ran memtest originally after going through all the cold boot issues... The last couple of days, I've run it from cold (errors all over the place), once all day while at work (still erroring when I got back). Both times, a power cycle got memtest to produce NO errors at all!!! So I'm certain it's memory/motherboard-related.
Incidentally, I WAS able to ramp up the voltages to 1.9v (but it was in the "red zone" in the listings, whatever that meant) and I still had a cold boot error as before last night. So I'm going to yank out the chips and try one after another to see what happens...
Very similar issues. If you Google (as I'm sure you have, sorry!) 'GA-P55-USB3 cold boot' there are LOADS of related problems (Ususally with OCZ memory).
It's really pi$$1n6 me off now. Tried to RMA the board and memory, but it passes Memtest with flying colours so they won't take it back. I'm in the process of moaning (sorry, raising a support request) with both OCZ and Gigabyte but not holding my breath.
At the moment, I just boot the system, go to BIOS, come back 5 mins later & hit the reset button and all boots OK. As you can imagine, this is not satisfatory for 'er indoors after us spending the best part of �600 on this upgrade.
You have my sympathy.
It's really pi$$1n6 me off now. Tried to RMA the board and memory, but it passes Memtest with flying colours so they won't take it back. I'm in the process of moaning (sorry, raising a support request) with both OCZ and Gigabyte but not holding my breath.
At the moment, I just boot the system, go to BIOS, come back 5 mins later & hit the reset button and all boots OK. As you can imagine, this is not satisfatory for 'er indoors after us spending the best part of �600 on this upgrade.
You have my sympathy.
As i was saying that board as well as the Gigabyte model here run any memory at 1.5v. It's no surprize seeing the higher voltage setting red flagged on the spot. You can't simply raise the voltages on their boards like you can or would on an Asus or other make.
Don't feel bad about swapping out the memory for a new set that runs at the 1.5v defaults. I got caught on that when going with a Gigabyte board for the recent build earlier this year. The other thing I would suggest is seeing what the bios is set for as far as Native ide or AHCI mode.
Here I have to run at the Native ide to see the best results. That applies to both Sata II and III drives having seen 7 installed on one of the Sata III at the start.
Don't feel bad about swapping out the memory for a new set that runs at the 1.5v defaults. I got caught on that when going with a Gigabyte board for the recent build earlier this year. The other thing I would suggest is seeing what the bios is set for as far as Native ide or AHCI mode.
Here I have to run at the Native ide to see the best results. That applies to both Sata II and III drives having seen 7 installed on one of the Sata III at the start.
I *think* I'm on the native IDE setting (certainly, no issues with HDD performance!)...
I swapped out the RAM and no dice, so it's defo an incompatibility (power cycled, and perfect again as usual!)... However, according to Gigabyte's compatibility list for the board I have, this should fit the bill (another �60 quid, but the amount of blood and sweat I've wasted is about 5x that!) Kingston KHX1600C9D3K2/4G HyperX / 4GB 1600MHz PC3-12800 DDR3 / Non-ECC CL9 DIMM Dual Channel Computer Memory - Computing at Play.com (UK)
Have to see if I get some chrimbo money...
If this works, I should be able to punt the Corsair RAM for a decent price, as it's definitely OK in itself.
BTW, is the 1.9/1.5v thing a red herring if you set the board to "Auto" for memory?
I swapped out the RAM and no dice, so it's defo an incompatibility (power cycled, and perfect again as usual!)... However, according to Gigabyte's compatibility list for the board I have, this should fit the bill (another �60 quid, but the amount of blood and sweat I've wasted is about 5x that!) Kingston KHX1600C9D3K2/4G HyperX / 4GB 1600MHz PC3-12800 DDR3 / Non-ECC CL9 DIMM Dual Channel Computer Memory - Computing at Play.com (UK)
Have to see if I get some chrimbo money...
If this works, I should be able to punt the Corsair RAM for a decent price, as it's definitely OK in itself.
BTW, is the 1.9/1.5v thing a red herring if you set the board to "Auto" for memory?
Soz for additional waffly post, but noticed a Playtrade seller has this for �43 (damaged packaging, but seems potentially kosher). Wonder if it'll still be there on Tuesday...
Well that's why I suggested a good look at the drive as well as the drive mode. Running a drive diagnostic along examing the board and supply even if found not to be regulating properly.
Besides a board issue of some type sudden dropoffs with supplies can be a cause for things. At startup that's where you typically see the largest pull on the supply especially during the post tests. And right as Windows starts loading device drivers.... the supply wimps out?
The other fright is finding out you have a bad cap on the board. You ruled out a bad dimm it seems.
Besides a board issue of some type sudden dropoffs with supplies can be a cause for things. At startup that's where you typically see the largest pull on the supply especially during the post tests. And right as Windows starts loading device drivers.... the supply wimps out?
The other fright is finding out you have a bad cap on the board. You ruled out a bad dimm it seems.
Thanks Night Hawk - I'm just hoping it's NOT the mobo or PSU (it easily comes out of sleep mode with no issues, and it does seem odd literally powercycling it immediately sorts it out...).
I've bitten the bullet and ordered that Kingston RAM (assuming they can fight through all the snow to get it to my house before New Year!!), as another person has this same combination confirmed as compatible (Is this compatible?) as well as on the relevant Gigabyte data sheet.
If I STILL have cold boot issues, I'll RMA the motherboard first, as the PSU seems really nice. I doubt I could get the machine to even power up with my old one (400 watt) so can't test that theory...
Watch this space...
I've bitten the bullet and ordered that Kingston RAM (assuming they can fight through all the snow to get it to my house before New Year!!), as another person has this same combination confirmed as compatible (Is this compatible?) as well as on the relevant Gigabyte data sheet.
If I STILL have cold boot issues, I'll RMA the motherboard first, as the PSU seems really nice. I doubt I could get the machine to even power up with my old one (400 watt) so can't test that theory...
Watch this space...
1.65v memory which is in the voltage range while the board will still tend the memory at 1.5v at the next lower speed. I ran Hyper X on the last build and that was good memory.
The board at the link supports DDR3 2200mhz memory where you wouldn't expect to see any problems with the Kingston on the one pointed to there. You would likely see the memory run at 1333 with the model you have however.
Memory listed as 1.5v is the preferred however for the Gigabyte boards while other makes like Asus, MSI, Abit wouldn't be as fussy? But the lower voltage serves to keep memory temps lower as well. Don't feel too bad if you do end up returning the board anyways. I just got done replacing board and supply on the last case rather then buying a used board from EBay since that will run Vista there.
The board at the link supports DDR3 2200mhz memory where you wouldn't expect to see any problems with the Kingston on the one pointed to there. You would likely see the memory run at 1333 with the model you have however.
Memory listed as 1.5v is the preferred however for the Gigabyte boards while other makes like Asus, MSI, Abit wouldn't be as fussy? But the lower voltage serves to keep memory temps lower as well. Don't feel too bad if you do end up returning the board anyways. I just got done replacing board and supply on the last case rather then buying a used board from EBay since that will run Vista there.
Well well well! After installing the first 2 2gb Kingston RAM chips and cold booting, it works perfectly. So I got another 4gb as well Ran Memtest86 from cold overnight and had 8 passes with 0 errors I got both sets of 4gig from the same seller on Play - �68 all-in for 8 gigs was pretty good for solving all my problems!
Now all I need is a SATA cable and I can then reinstall my entire system's software from scratch to sort out the registry. Thanks again for all the help, guys!
Ran Memtest86 from cold overnight and had 8 passes with 0 errors I got both sets of 4gig from the same seller on Play - �68 all-in for 8 gigs was pretty good for solving all my problems!Now all I need is a SATA cable and I can then reinstall my entire system's software from scratch to sort out the registry. Thanks again for all the help, guys!
Không có nhận xét nào:
Đăng nhận xét