|13 May 2012||#1|
| || |
Multiple BSoD strings - Unable to pinpoint
I had read through the guide on how to post, so please don't be angry with the lack of following the guide. The downloaded Windows_NT6_BSOD file won't run on my computer under any compatibility settings either with or without Admin rights. So I've done the best I can to get you all the information needed. I also included a screen shot of the loading error for that .exe.
System Manufacturer/Model Number: Custom
OS: Windows 7 Home Premium x64 (SP1)
CPU: Intel Core i5-2500K (3.30 GHz)
Motherboard: ASUSTeK P8Z68-V LE (LGA 1155)
Memory: G.Skill Sniper 4GB x2 (240-Pin DDR3 SDRAM 1866)
Graphics Card(s): 1024 NVIDIA GeForce GTX 550 Ti (MSI)
Sound Card: Built-in
Monitor(s) Displays: Samsung 21" LED
Screen Resolution: 1920x1080 (32bit - 60Hz)
OCZ Onyx Series 32GB SATA II MLC (SSD)
Western Digital Caviar Green WD20EARX 2TB
Optical Drive: Optiarc DVD RW AD-7280S
PSU: COOLER MASTER eXtreme Power Plus RS500-PCARD3-US 500W ATX12V v2.3 Power Supply
Case: COOLER MASTER Elite 311
ZALMAN CNPS9500 AT 2 Ball CPU Cooling Fan/Heatsink
COOLER MASTER 120mm 4 Blue LED Case (x2)
Keyboard: Logitech K120 Wired
Mouse: Logitech M505 Wireless
Internet Speed: Up to 15 MB/s (Time Warner Cable)
Anti-Virus: Avast! free.
Common programs ran: Google Chrome, iTunes 64-bit, Photoshop CS5, Multiple games, Programming software
I have tried to narrow this down for a while now. I feel that my PSU and SSD are issues, both are too small for the job. The SSD caused issues when first installing windows, but the HDD won't accept a Windows 7 install under any circumstances.
I have tried to check the RAM to be sure that it was not an issue, and came out with no errors during my testing.
MY SSD is only Windows 7, everything else is run off of the 2TB HDD. I modified registry files to default to the HDD for installing software.
Have been contemplating a switch to a Crucial M4 64GB or 128GB SSD, and a Corsair TX750 PSU. If those are necessary upgrades, I'll order today.
If you need any other information I may be missing, I'll be glad to get it to you.
Any and all help is appreciated. Thanks
|My System Specs|
|13 May 2012||#2|
| || |
These crashes were caused by memory corruption/exception (Cx05) probably a driver. I see you have run some memory test but we need you to run memtest for the 6-8 passes needed to stress the memory.
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" 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|
|13 May 2012||#3|
| || |
After three 100% passes on 1 of my 4GB G.Skill sticks, I swapped out for the other, and have come across 17920 errors near the end of Test #4 is even complete. Moved the stick to each of the slots, and it fails the same way on each. The other stick passes on each.
That would bring it down to being a bad stick, while the slots are all good, correct? In that case, do I still need to run the driver verify?
EDIT: System won't run with only 1 stick. Claims missing BootMgr. Running Windows Memory Diagnostics tool went around into a reboot, BSOD crash before the 4 corner colors even move, BSOD in/out so fast I can't see it. Chkdsk found nothing, and SFC /SCANNOW won't run because it claims a system repair is pending.
|My System Specs|
|Similar help and support threads for2: Multiple BSoD strings - Unable to pinpoint|
|BSOD Unable to pinpoint cause||BSOD Help and Support|
|BSOD errors with different strings caused by ntoskrnl.exe and ndis.sys||BSOD Help and Support|
|BSOD at random times with Bug Check Strings||BSOD Help and Support|
|BSOD can't pinpoint what is triggering it||BSOD Help and Support|
|BSOD problems when doing nothing/browsing, reports KERNEL/NTFS strings||BSOD Help and Support|
|BSOD on Win 7 startup- trying to pinpoint cause||BSOD Help and Support|
|BSOD problems...can't pinpoint...help!?||BSOD Help and Support|