os windows 7 x64
retail version upgrade from xp to win 7
AMD Phenon 2 x4 3.2mhz
4gb of ram
500gb hdd 2 x partions
mother board 4 months old cpu 4 months old
2gb ram 4 months old **2gb ram 3 years old ** thinks this maybe problem
AMD redeaon 6700
if you need any other info please ask
find a health report attached and Windows_NT6_BSOD_jcgriff2 attached
These crashes were caused by memory corruption probably your Symantec. I would remove it to test FIRST. If you continue to crash run these.
Symantec is a frequent cause of BSOD's. I would remove and replace it with Microsoft Security Essentials AT LEAST TO TEST
http://us.norton.com/support/kb/web_...080710133834EN
Microsoft Security Essentials - Free Antivirus for Windows
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.
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 to identify issues with Windows drivers for advanced usersUsing 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/Win7 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.
Sysnative Forums
Driver Reference Table
Driver Verifier
Using Driver Verifier (Windows Drivers)
hi and thank you for your reply ok so i ran memtest86
1st test 1st ram stopped after 100000+ errors
2nd test 1st ram in 2nd slot stopped 100000+ errors
3rd test 2nd ram complete 1 error
4th test 2nd ram in 2nd slot complete 1 error =
failing address
0007c033fec 1984.1mb
good
00000800
bad
00000000
err-bits
00000800
count
1
cpu
3
this mean nothing to me other than mobo slots are ok but ram with over 100000+ errors within 5 mins of test starting is the problem
what i dont understand is this is a new ram stick only by a few weeks but the other ram came as a package with mobo and the one that seem to be broke :) came from a different shop
could it be a compatibilty issue ??? with mobo ??
RAM can fail anytime. If you r 1st ram was tested individually and threw errors in slot one and two it is the ram.
Compatibility would only come into play if 1st ram was tested together with 2nd ram.
Ram needs to be purchased in one package at one time or it may not be compatible.
yes it had errors in both slots :) this is what you get when u buy cheap ram
*starts to save for 2 x 4gb vegence ram
thanks for your time
is the other ram ok with just one error ?? i think it is as since the post pc has ran fine apart from only having 2gb ram lol
Quote