Hi.
I have only had this PC a week or so but keep getting BSOD's.
Will send it back but have spent hours setting up with all my software so looking to see if it is something simple first.
Have run Memtest and Seatools, all OK.
Files uploaded as per instructions.
Can anyone help?
Many thanks.
I am afraid you uploaded the application instead of the data, please try this method.
We do need the DMP file as it contains the only record of the sequence of events leading up to the crash, what drivers were loaded, and what was responsible.
If you are overclocking STOP
We could also use some system information, which you can get easily by running msinfo32.
To do that go to start>run>type msinfo32>enter
When it is finished running go to file>save>name it and upload to us here.
You may be able to get the DMP files without crashing by booting into safe mode (F8) with networking.
To enable us to assist you with your computer's BSOD symptoms, upload the contents of your "\Windows\Minidump" folder.
The procedure:
* Copy the contents of \Windows\Minidump to another (temporary) location somewhere on your machine.
* Zip up the copy.
* Attach the ZIP archive to your post using the "paperclip" (file attachments) button.
*If the files are too large please upload them to a file sharing service like "Rapidshare" and put a link to them in your reply.
To ensure minidumps are enabled:
* Go to Start, in the Search Box type: sysdm.cpl, press Enter.
* Under the Advanced tab, click on the Startup and Recovery Settings... button.
* Ensure that Automatically restart is unchecked.
* Under the Write Debugging Information header select Small memory dump (256 kB) in the dropdown box (the 256kb varies).
* Ensure that the Small Dump Directory is listed as %systemroot%\Minidump.
* OK your way out.
* Reboot if changes have been made.
Russ
You have a few issues. Most of the crashes were related to a memory issue (probably a driver). In addition two of the crashes were directly related to AVG. I would remove and replace it with MSE (at least to test)
I note you have AVG.
AVG can be a contributing cause of BSOD'S .
Please remove and replace with Microsoft Security Essentials AT LEAST TO TEST
Download tools and utilities | AVG Worldwide
Microsoft Security Essentials - Free Antivirus for Windows
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 raid update its Driver.
Memtest.
RAM - Test with Memtest86+*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.
Driver verifier
Using Driver Verifier (Windows Drivers)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.
So, 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/Win7 Startup Repair feature).
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 "Special Pool", "Force Pending I/O Requests" and "Low Resource Simulation" and click "Next"
- 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.
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.
OK thanks.
I removed AVG and replaced it with MS Essentials.
That has certainly cut the crashes down.
Attached are 2 crashes from today that have occured since removing AVG.
I also ran memtest all night and it showed no errors.
I guess I now need to attempt this driver verifier.
Thanks for your help so far.
Those crashes point toward memory or drivers. Proceed with Verifier enabled and post crash reports after you have had a few crashes to help find patterns.
Only one of the latest crashes was driver Verified, and all pointed to memory issues, even the one with Verifier catching the crash.
Go ahead and disable Verifier: Start Menu -> All Programs -> Accessories -> Right click Command Prompt -> Run as administrator -> Type the following command and then Enter:verifier /reset-> Restart your computer.
I would recommend running your system with 8 GB of RAM installed at a time. Check all slots, and all four sticks, but run with 8 GB at a time to determine a good pair or modules. Do the following:
- Remove two 4 GB modules from the system.
- See if Windows crashes while you do your normal routine for as long (or better, twice as long) as it usually takes for you to get a crash.
- If you do:
- Put the pair of modules in two other slots and see if you still get Windows to crash.
- If Windows crashes in the other two slots, replace the pair of 8 GB with the other pair of 8 GB.
- If you do not get crashes with the two modules, those modules and slots are good. Test the other two slots.
- If both pairs work well, then it may just be that your settings are not configured properly for 16 GB of RAM. We can help you adjust them if you are comfortable doing so.
OK many thanks.
I will try that next.
Kind regards
Adrian.
Thanks for everybody's help.
After you advised that the issue was down to memory I asked the manufacturer to send me 4 new memory modules.
I replaced all 4 and for the last week it has been perfect.
Not a single crash or any issues at all.
Then last night after I thought everything was fine, I had a new crash. The PC just switched itself off.
I enlose the Mini Dump file that relates to this crash.
I am hoping it is just a one off glitch but would value your opinions as to what caused it based on the minidump.
Many thanks again.
Quote