New
#11
Yes I did, installed the latest version several days back
Yes I did, installed the latest version several days back
Lets enable driver verifier to rule out buggy drivers.
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/Windows 7 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 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.
Driver Verifier - Enable and Disable
Verifier puts extreme stress on the drivers, bad ones will cause BSOD. If we change all those drivers we hope for no more BSODs, If you get no BSODs, then its not a driver and we look to hardware. With verifier on your computer may be a little laggy, but actually..its just doing its work.
Information
Driver Verifier runs in the background, "testing" drivers for bugs. If it finds one, a Blue Screen of Death (BSOD) will result; the corresponding dump file will hopefully show the faulty driver.
Okay I've set it up and instantly I've had two Blue screens on boot, and also caused another immediately when launching a game(to purposely make it crash)
No drivers here. The initial suspicion we're dealing with hardware failure is definitely possible. Though before going that route, make sure all software installed with your motherboard are uninstalled, leaving only drivers behind, and make sure the motherboard drivers are up-to-date, including the BIOS. If that's all been done, then there really is no choice but to swap out the CPU or the motherboard, since either can cause this (though with your 0x101 bugchecks, I put more blame on the CPU).
Btw, as a little more added info, I did !errrec on the first 0x124 crash to notice a generic error occuring on the CPU L2 cache:
Mobo software or bad BIOS can still cause this, but this points more blame on the CPU than the motherboard if it is indeed a hardware problem.Code:1: kd> !errrec fffffa800c5b1028 =============================================================================== Common Platform Error Record @ fffffa800c5b1028 ------------------------------------------------------------------------------- Record Id : 01cd8d5e78c7a324 Severity : Fatal (1) Length : 928 Creator : Microsoft Notify Type : Machine Check Exception Timestamp : 9/8/2012 7:28:49 (UTC) Flags : 0x00000000 =============================================================================== Section 0 : Processor Generic ------------------------------------------------------------------------------- Descriptor @ fffffa800c5b10a8 Section @ fffffa800c5b1180 Offset : 344 Length : 192 Flags : 0x00000001 Primary Severity : Fatal Proc. Type : x86/x64 Instr. Set : x64 Error Type : Cache error Operation : Generic Flags : 0x00 Level : 2 CPU Version : 0x00000000000206a7 Processor ID : 0x0000000000000001 =============================================================================== Section 1 : x86/x64 Processor Specific ------------------------------------------------------------------------------- Descriptor @ fffffa800c5b10f0 Section @ fffffa800c5b1240 Offset : 536 Length : 128 Flags : 0x00000000 Severity : Fatal Local APIC Id : 0x0000000000000001 CPU Id : a7 06 02 00 00 08 10 01 - bf e3 9a 1f ff fb eb bf 00 00 00 00 00 00 00 00 - 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 - 00 00 00 00 00 00 00 00 Proc. Info 0 @ fffffa800c5b1240 =============================================================================== Section 2 : x86/x64 MCA ------------------------------------------------------------------------------- Descriptor @ fffffa800c5b1138 Section @ fffffa800c5b12c0 Offset : 664 Length : 264 Flags : 0x00000000 Severity : Fatal Error : GCACHEL2_ERR_ERR (Proc 1 Bank 5) Status : 0xbe2000000005110a Address : 0x000000011ea04dc0 Misc. : 0x000000d084020086
Thankyou for the quick responses, I will double check that everything is up to date. I've just put a brand new CPU in today so it shouldnt be the CPU, are there any tests to narrow it down to the motherboard?
Unfortunately, outside of swapping the mobo, or utilizing a PC bench (which is really just an open PC with reliable parts to quickly swap mobos in and out) there's nothing you can do with it. Same goes for the PSU if that's the cause of the problem.
Remember that motherboard software should be uninstalled, not updated. This includes any monitoring software, any "enhancement" software, etc. etc. Anything that came with the mobo must go, drivers excluded.
Okay I've removed any software relating to the motherboard and started the process to update the motherboard drivers (apologies I'm a bit of a newbie), is there a place to check the dates of the motherboards current drivers against the website? Should I just get all of them so they are all freshly installed?
ASUSTeK Computer Inc. -Support- Drivers and Download P8P67-M PRO
just some extra info....blue screens now aren't just limited to when the comp has a game launched, it just blue screened whilst using internet and did again on boot, it also completely froze earlier too
Yes, you should just do a full update of everything. Stay away from the SATA stuff except for the Marvell Controller Driver. Utilities should be avoided.
Did these new symptoms just happen after you uninstalled the mobo software? If so, this may be a case where one of them uninstalled incorrectly, which is typical since those things are bugged up the wazoo. Driver Sweeper is a free app that's designed to clean that stuff off entirely, so you may wanna give that a shot.
Otherwise, I sure do hope your new CPU isn't bad on arrival. That'd be pretty disappointing :< .
I did driver sweeper...computer took several attempts to boot and blue screened a lot. It's been a lot worse today than usual
Should I just do a fresh wipe and reinstall of windows so everything is just reset and if the problems are still there it's definitely hardware?