Win7 Pro 64Bit BSOD + App crashes

[paulf22]

I recently installed Win7 Pro 64Bit on my system, which now seems to have become completely unstable.

Apps that have run happily for months, or even years under WinXP Pro and then Win 7 Ultimate 32Bit, will now fail to start, and I've also experienced BSOD's after some of the app failures.

I initially thought this might have something to do with the security upgrades and patches I'd installed, but apparently not.

Last weekend I had a total BSOD, couldn't even get into Safe Mode, so I reset my SSD OS drive and did a completely clean install plus update of all drivers and security patches etc.

Because I thought this might have something to do with the updates, when KB2160841 and KB2416472 were released on Tuesday I didn't install them.

I can't remember the last time I saw a BSOD, either under WinXP, and certainly not under Win7 32Bit, which ran flawlessly for over a year.

Does anyone have any insight as to what might be happening?

Thanks
Paul

 

[yowanvista]

http://www.sevenforums.com/crashes-debugging/96879-blue-screen-death-bsod-posting-instructions.html

 

[paulf22]

Thanks for the reply yowanvista. I've included the BSOD zipped report with this mail, but I'm afraid I don't understand how to generate a report from perfmon. Can you tell me what information you're looking for, and how to get it?

My Win7 Pro 64Bit is an OEM disk; I built the system myself.
My SSD OS/Apps drive is an OCZ 60GB Vertex, which previously ran my Win7 Ultimate 32Bit system.

Thanks
Paul

 

[yowanvista]

Thanks for the reply yowanvista. I've included the BSOD zipped report with this mail, but I'm afraid I don't understand how to generate a report from perfmon. Can you tell me what information you're looking for, and how to get it?

Thanks
Paul

We need the .dmp files which are absent in your attachment. Did you run a system cleaner such as Ccleaner after the crashes?

 

[paulf22]

My current installation is a clean install from last week's crash, everything's up-to-date, security updates, including KB2160841 and KB2416472 that were released this week, hotfixes and drivers.

I didn't get a BSOD tonight, but one of my apps failed to start, and my IS suite turned itself off and had to be restarted after applying this weeks updates. I decided to uninstall my app with RevoUninstall, but I don't think that would have touched any Windows reporting files, would it?

As I mentioned, after running rock solid for a couple of years now, my system has become as flakey as hell after upgrading to Win7 64Bit.

I really am at a loss as to understand what's going on, and was going to simply reformat my drive and go back to Win7 32Bit - I have a lot of work I need to get done! - when I thought I'd ask a question on this board.

 

[yowanvista]

My current installation is a clean install from last week's crash, everything's up-to-date, security updates, including KB2160841 and KB2416472 that were released this week, hotfixes and drivers.

I didn't get a BSOD tonight, but one of my apps failed to start, and my IS suite turned itself off and had to be restarted after applying this weeks updates. I decided to uninstall my app with RevoUninstall, but I don't think that would have touched any Windows reporting files, would it?

As I mentioned, after running rock solid for a couple of years now, my system has become as flakey as hell after upgrading to Win7 64Bit.

I really am at a loss as to understand what's going on, and was going to simply reformat my drive and go back to Win7 32Bit - I have a lot of work I need to get done! - when I thought I'd ask a question on this board.

Your installation may be damaged, run SFC
http://www.sevenforums.com/tutorials/1538-sfc-scannow-command-system-file-checker.html

Don't go back to 32-bit, you'll only be able to use about 3.25GB of your RAM if you do so

 

[paulf22]

Hi yowanvista... I've just run sfc /scannow for the 3rd time, and I'm seeing 100's of "cannot repair..." entries like this...

2011-02-19 01:15:39, Info CSI 00000743 [SR] Cannot repair member file [l:36{18}]"Amd64\brio14aa.bcm" of prnbr009.inf, Version = 6.1.7600.16385, pA = PROCESSOR_ARCHITECTURE_AMD64 (9), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type = [l:24{12}]"driverUpdate", TypeName neutral, PublicKey neutral in the store, file is missing

Is there any way of fixing this other than a complete re-install?

Thanks
Paul

P.S. The reason I upgraded to 64Bit was to access more RAM, so I really don't want to go back to 32Bit at all!

 

[yowanvista]

Hi yowanvista... I've just run sfc /scannow for the 3rd time, and I'm seeing 100's of "cannot repair..." entries like this...

2011-02-19 01:15:39, Info CSI 00000743 [SR] Cannot repair member file [l:36{18}]"Amd64\brio14aa.bcm" of prnbr009.inf, Version = 6.1.7600.16385, pA = PROCESSOR_ARCHITECTURE_AMD64 (9), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type = [l:24{12}]"driverUpdate", TypeName neutral, PublicKey neutral in the store, file is missing

Is there any way of fixing this other than a complete re-install?

Thanks
Paul

P.S. The reason I upgraded to 64Bit was to access more RAM, so I really don't want to go back to 32Bit at all!

This confirms that your system is corrupt, do a http://www.sevenforums.com/tutorials/3413-repair-install.html

 

[paulf22]

Looks like I'm out of luck; I built this system myself, and both of my Win7 disks are OEM's.

According to http://www.sevenforums.com/tutorials/3413-repair-install.html the repair/install can only be done from a Retail copy of the OS, not an OEM.

I did create a Recovery Disc, but that's not helping; it looks like my only option is a clean install.

The larger question is WHY is this happening? This is the fourth straight week in a row I have had issues so bad I have had to re-install my Win7 Pro 64Bit.

I initially thought the problems were being caused by the security updates, or even a specific app I'm using... what could be causing Win7 to become corrupted like this?

Thanks
Paul

 

[paulf22]

Just a thought, the sample above of the SFC report talks about 64Bit AMD Processor Architecture, but I'm running an Intel E8400 - I need to upgrade to a Quad! - so why would those "missing" files be an issue?