Manufacturer's chipset? I'm not sure what you mean. I'm not using any expansion cards, everything is connected to my motherboard. I sincerely doubt my PCI-e DLINK wireless adapter is the culprit since the internet works perfectly. Aside from that, yeah, everything is connected directly to the motherboard. How could the problem be a driver when reinstalling all drivers after a clean install of windows 7 should fix that?
If you "reinstalled all drivers after a clean installl of windows 7" then that may be your problem.
As stated clearly Win7 is driver-complete in the installer and via optional Windows Updates, requiring no drivers to be provided except those missing in the Device Manager after install and several rounds of Updates.
Only if there are performance problems traced directly to drivers should any drivers be changed from what is given by installer or Updates, e.g. low video resolution with no driver update from Standard VGA display driver - or issues such as you are having.
Motherboards normally come with a CD of drivers (and possibly also crapware).Another program that can't handle the 125% Display setting (pic 1).
Last edited by lehnerus2000; 22 Jan 2012 at 20:17.
Pirate 43.
In your Post 1 you say
As Sbrideau suggested in Post 2Sporadic blue screens at least once or twice weekly. (PFN LIST CORRUPT and one or two others I can't remember)
Are you able to get the dump file and attach it when you post back? Since you are getting blue screens, this could help some guys here see if they are relevant.
If you are getting BSOD's 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
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:
To ensure minidumps are enabled:* 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.
* 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.
@gregrocker - you misunderstand. I meant that by reinstalling windows 7, the drivers are reinstalled, so it's likely not a driver issue.
@JMH - I was overclocking but I stopped when the problems began occurring. I will attach the minidumps as soon as I can.
I have attached the contents of my minidump folder.
OK done!
1. Asacpi.sys
The pre 2009 version of this driver is a known bsod cause.
Please visit this link: Asus tek computer inc. -support- drivers and download p7p55d le
ASUSTeK Computer Inc. -Support- Drivers and Download P7P55D LE
ASUSTeK Computer Inc. - Motherboards- ASUS P5K-VM
Scroll down to the utilities category, then scroll down to the "atk0110 driver for windowsxp/vista/windows 7 32&64-bit" (it's about the 12th item down).
Download and install it.
Go to c:\windows\system32\drivers to check and make sure that the asacpi.sys file is date stamped from 2009 or 2010 (notbefore).
2. Next please run the update readiness tool and then update to SP-1.
Ensure you install the correct 64 or 32 bit option for your system)
Download the System Update Readiness Tool (64bit)
Download the System Update Readiness Tool (32bit)
Learn how to install Windows 7 Service Pack 1 (SP1)
3. When both of the above steps have been done run these two tests to verify your memory and find which driver may still cause a problem.
If you are overclocking anything reset to default before running these tests.
In other words STOP!!!
A-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 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.
Any errors are indicative of a memory problem.
If a known good stick fails in a motherboard slot it is probably the slot.
B-Driver verifier
Driver Verifier - Enable and DisableUsing 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 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.
Further Reading
Using Driver Verifier to identify issues with Windows drivers for advanced users
Last edited by JMH; 24 Jan 2012 at 01:55.
Quote