Solved Persistent cold boot issues

[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

 

[zigzag3143]

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

Dom you have several modules that are unknown. I suspect you upgrade to win 7 SP1 beta.

the modules are in Chinese so we have no idea what they are or do.

ﻺ췘췘闷⨑䀸Ꚕ땅ⱅ囪勊᭠媑ටᐝ얭䵩垵碂碃��釥스㝘❮죑쓝⾖⚗ﰘꫣ蛒葮멒멕        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                
僣࠰䘎ً昷Џ荕쥙Ὕ⪬dz噁そ倊췶싦⢱鈭䜭ꃍꤣ﵄勼턘턜᳹籱⚩ﮰ糣ͯ돐䊮㾜ȣ䚿惕᜕敵荕纲灆        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.\

http://www.sevenforums.com/tutorials/1538-sfc-scannow-command-system-file-checker.html?ltr=S


Ken J

 

[Night Hawk]

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.

 

[Lemur]

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

Dom you have several modules that are unknown. I suspect you upgrade to win 7 SP1 beta.

the modules are in Chinese so we have no idea what they are or do.

ﻺ췘췘闷⨑䀸Ꚕ땅ⱅ囪勊᭠媑ටᐝ얭䵩垵碂碃��釥스㝘❮죑쓝⾖⚗ﰘꫣ蛒葮멒멕        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                
僣࠰䘎ً昷Џ荕쥙Ὕ⪬dz噁そ倊췶싦⢱鈭䜭ꃍꤣ﵄勼턘턜᳹籱⚩ﮰ糣ͯ돐䊮㾜ȣ䚿惕᜕敵荕纲灆        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.\

http://www.sevenforums.com/tutorials/1538-sfc-scannow-command-system-file-checker.html?ltr=S


Ken J

LOL. Korean. Better brush up, Ken.

**EDIT** Or Chinese. Ha. We both better brush up.

 

[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

 

[zigzag3143]

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

Dom did you by chance upgrade to the RC SP1?? when released it was in chinese


No it isnt legit. Didnt come from MS. One place I have seen it I wouldnt trust to download anything

 

[Night Hawk]

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

 

[domfjbrown]

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...

 

[Night Hawk]

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.

 

[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

 

[Tews]

Dom .. navigate to c:/windows/minidump and upload the latest .dmp files..

 

[Night Hawk]

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

It's definitely a driver issue! You may want to review the information for that particular error and proceed from there.

Bugchecks Explained: PFN_LIST_CORRUPT

 

[domfjbrown]

Dom .. navigate to c:/windows/minidump and upload the latest .dmp files..

Right - back on my PC finally again - these are the last ones I got (though been on the machine a few times since then, but with no changes to config).

 

[domfjbrown]

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!

 

[domfjbrown]

Flashed up to F8 BIOS now - that was fairly easy

 

[domfjbrown]

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!)

 

[Night Hawk]

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?

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.

 

[domfjbrown]

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

 

[Night Hawk]

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.

 

[domfjbrown]

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