|22 May 2012||#1|
| || |
BSOD every few minutes after upgrading to win7x64
I Recently upgraded my system from windows 7 Professional (X86) to Windows 7 ultimate (X64).
My system is approximately 9months old
4x Athlon processor
4 gigs DDR3 kingston
1 terabyte Western digital
2 500 gigabyte seagate
2 Terabyte Western Digital External Attached
No internet connection or network connection (pc is in a remote part of South America)
I am honestly tired of this BSOD nonsense, I updated all my drivers and reloaded the system so many times during this past month that I lost count.
I exchanged My video Card,Swapped out My Memory and Hard-drives but still no luck, as a matter of fact I think the problem has become worse, I get the bsod while playing videos,music, or even just launching or switching programs as opposed to before when the system would just freez while playing a video in VLC and then i would have do a hard restart.
I have attached my dump files along with a html page saved from bluescreen viewer.
This is my last attempt with windows 7, before I download a linux flavour.
All drivers were updated before my last reload, all drivers signed but still got BSOD.
By the way you may notice i have no Updates, that's because i recently reloaded Again and its difficult to drag this system out of its current location. (if this issue is resolved then ill do the update).
Thanks in advance.
|My System Specs|
|22 May 2012||#2|
| || |
* I am a big fan of Nir Sofer's work, BUT BlueScreenView more often than not, doesn't point out the correct causes. Similarly Who crashed is even worse.
I prefer to use WinDbg (the Windows Debugging Tools) to read the memory dumps. It is the Gold standard for those of us that do this and often will give us the answer by itself.
* These crashes were caused by memory corruption/exception (Cx05) probably a driver.
Please run these two tests to verify your memory and find which driver is causing the problem.
* If you are overclocking anything reset to default before running these tests.
In other words STOP!!!
* If you have a Raid update its Driver.
*Download a copy of Memtest86 and burn the ISO to a CD using Iso Recorder or another ISO burning program. Memtest86+ - Advanced Memory Diagnostic Tool
*Boot from the CD, and leave it running for at least 5-7 passes.
Just remember, any time Memtest reports errors, it can be either bad RAM or a bad motherboard slot.
Test the sticks individually, and if you find a good one, test it in all slots.
Any errors are indicative of a memory problem.
If a known good stick fails in a motherboard slot it is probably the slot.
Using Driver Verifier is an iffy proposition.
Most times it'll crash and it'll tell you what the driver is.
But sometimes it'll crash and won't tell you the driver.
Other times it'll crash before you can log in to Windows.
If you can't get to Safe Mode, then you'll have to resort to offline editing of the registry to disable Driver Verifier.
I'd suggest that you first backup your stuff and then make sure you've got access to another computer so you can contact us if problems arise.
Then make a System Restore point (so you can restore the system using the Vista/Windows 7 Startup Repair feature).
In Windows 7 you can make a Startup Repair disk by going to Start....All Programs...Maintenance...Create a System Repair Disc - with Windows Vista you'll have to use your installation disk or the "Repair your computer" option at the top of the Safe Mode menu .
Then, here's the procedure:
- Go to Start and type in "verifier" (without the quotes) and press Enter
- Select "Create custom settings (for code developers)" and click "Next"
- Select "Select individual settings from a full list" and click "Next"
- Select everything EXCEPT FOR "Low Resource Simulation"IRP Logging and Force Pending I/O Requests. and click "Next"
NOTE: You can use Low Resource Simulation if you'd like.
From my limited experimentation it makes the BSOD's come faster.
- Select "Select driver names from a list" and click "Next"
Then select all drivers NOT provided by Microsoft and click "Next"
- Select "Finish" on the next page.
If you are using win 8 add these
- Concurrency Stress Test
- DDI compliance checking
Reboot the system and wait for it to crash to the Blue Screen.
Continue to use your system normally, and if you know what causes the crash, do that repeatedly.
The objective here is to get the system to crash because Driver Verifier is stressing the drivers out.
If it doesn't crash for you, then let it run for at least 36 hours of continuous operation.
Reboot into Windows (after the crash) and turn off Driver Verifier by going back in and selecting "Delete existing settings" on the first page, then locate and zip up the memory dump file and upload it with your next post.
If you can't get into Windows because it crashes too soon, try it in Safe Mode.
If you can't get into Safe Mode, try using System Restore from your installation DVD to set the system back to the previous restore point that you created.
Thanks to JCGriff2 & Usasma.
Driver Reference Table (DRT)
Using Driver Verifier (Windows Drivers)
|My System Specs|
|Similar help and support threads for2: BSOD every few minutes after upgrading to win7x64|
|Win7x64 0x01e BSOD (possible overclock cause)||BSOD Help and Support|
|BSOD: Memory Management, Win7x64||BSOD Help and Support|
|BSOD Win7x64||BSOD Help and Support|
|Fresh win7x64 BSOD||BSOD Help and Support|
|HELP! Win7x64 always BSOD in ACER 4540||BSOD Help and Support|
|BSOD, Win7x64 Ultimate, Intel i7 920||BSOD Help and Support|
|Crash w/ screeching sound + BSOD BCCode: 124 on Win7x64||BSOD Help and Support|
|Our Sites ||Site Links ||About Us ||Find Us |
Windows 7 Forums is an independent web site and has not been authorized, sponsored, or otherwise approved by Microsoft Corporation. "Windows 7" and related materials are trademarks of Microsoft Corp.
© Designer Media Ltd
All times are GMT -5. The time now is 11:16 PM.