THANKS SO VERY MUCH ZIGZAG AND JMH AND ALL WHO HELPED!!! i uninstalled avast, installed essentials, restarted, ran fsx and no problem up to now! i'll keep fsx running for about 3-4hours and if theres still no prob ill mark the thread as solved! again, thanks alot! ill never support avast again, i really worried that it could be motherboard or cpu! thanks so much!!!!
no luck. after the previous reply i started fsx and my computer hanged. i then restarted and started fsx again, then got a restart like always... ill upload the minidump again but i dont think it was logged because of the time stamp but i dont now how the minidump works so ill upload it anyway.
what do you all think is the cause that now a minidump flie is logged, and the next is just a restart with no minidump log? i ran fsx again, and again just a restart with no new time stamp on the log file...
Ok we seem to be getting nowhere fast.
You have a couple of choices. First a clean install of windows. That would be the fastest (though not necessarily the easiest) way to get working again. You will need either the win 7 dvd or a working factory restore partition
Second to keep doing diagnostics without DMP files. If you want to do this please run these two tests.
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)
Thanks zigzag, I've done most of it already. I don't overclock at all, I don't believe in overclocking laptops, don't think it has enough cooling.
its a fresh install of windows, and yes I've got a windows 7 dvd, but everytime I reinstall it needs to update and my internet cap is beginning to run low now.
I've done a verifier way in the beginning, but ill do it again for incase.
And I've tested my ram, its a week old now, and also tested the slots, but then again ill make sure.
Will be back with the results shortly. Thanks.
JMH, what's your and zigzag's relation if I may ask? I noticed the picture at the bottom of both of your posts (the picture with your names in it). If I may ask?
Yes you may indeed ask. :)
Our signatures indicate that we are partners.
Thought its something in that line :)
Quote