Temps still seem w/in range. Fans look ok/clean? Like I said, mine started out intermittent and got exponentially worse. If you have another i3/5/7 you could try swapping it out, otherwise you will have to wait until it gets worse or you can duplicate the crash on demand. Regardless you sound like you are having my identical problem. Check out my last thread for details.
Sharon,
Will take a look at latest .dmp files later.
If you only run one and only one program at a time, no matter what that program is, does the problem still surface.
I don't think it matters. For example at least 2 of yesterday's crashes were while I was away from the pc and I think all programs barring windows 7 were closed.
Sunday and Monday the pc was on permanently while running driver verified. And it didn't crash at one stage I opened at least 5 programs.
Yesterday we had to turn the pc off and unplug and when turned back on again we started gettig the bsods while verified was running
Sharon,
I think you will find this thread interesting since you asacpi.sys file is from 2005.
https://www.sevenforums.com/crashes-d...ease-help.html
Last edited by karlsnooks; 24 Aug 2011 at 01:07. Reason: spelling
I have now updated the asacpi.sys file. Now we just have to wait and see.
I spoke too soon. Its crashed again. Ive attached the file
thanks for the suggestions
Wacomm driver now upto date
so again we play the waiting game
33 of 50 crashes directly point to memory corruption the rest indirectly.
Memory corruption probably caused by a driver. please run these two tests
1-Memtest.
*Download a copy of Memtest86 and burn the ISO to a CD using Iso Recorder or another ISO burning program.
*Boot from the CD, and leave it running for at least 5 or 6 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.
RAM - Test with Memtest86+
2-Driver verifier
Driver Verifier - Enable and DisableI'd suggest that you first backup your data 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"
- 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 (an estimate on my part).
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.
Quote