Hello and welcome to TSF!

We have various different bugchecks here... much mention of memory corruption. How long did you run Memtest86+ for? No less than 7-8 passes is recommended.

Taking a look at your drivers, you have a few things that need attention:

Lachesis.sys - Fri Aug 17 03:48:44 2007 (Razer Lachesis Mouse driver). Update if available here. To my knowledge, the latest Lachesis driver should be 2010. Razer is known for their drivers causing BSOD's.. and when we enable DV, we'll see if Razer's drivers are causing any issues.

Lycosa.sys - Fri Jan 18 03:51:42 2008 (Razer Lycosa Keyboard driver). Same as above.

I noticed AiChargerPlus.sys is in your drivers list, this is the Asus Charger Driver. It has been guilty in the past of causing BSOD's, and in fact, I'd recommend temporarily at least for now in regards to troubleshooting recommend uninstalling any Asus motherboard related utilities.

Also, your BIOS version is 1101 - the latest is 3402, so I would definitely recommend updating the BIOS:

P8Z68-V PRO BIOS 3402
1.Improve Improve system stability.
2.Enhance compatibility with some USB devices.
3.Support new CPUs. Please refer to our website at: ASUSTeK Computer Inc. -Support- CPU Support

Update here: ASUS - Motherboards- ASUS P8Z68-V PRO

If after doing these things, you're still crashing, let's enable Driver Verifier -

Driver Verifier:

What is Driver Verifier?

Driver Verifier is included in Windows 7, Windows Server 2008 R2, Windows Vista, Windows Server 2008, Windows 2000, Windows XP, and Windows Server 2003 to promote stability and reliability; you can use this tool to troubleshoot driver issues. Windows kernel-mode components can cause system corruption or system failures as a result of an improperly written driver, such as an earlier version of a Windows Driver Model (WDM) driver.

Essentially, if there's a 3rd party driver believed to be at issue, enabling Driver Verifier will help flush out the rogue driver by flagging it and causing your system to BSOD.

Before enabling Driver Verifier, it is recommended to create a System Restore Point:

Vista - START | type rstrui - create a restore point

Windows 7 - START | type create | select "Create a Restore Point"

How to enable Driver Verifier:

Start > type "verifier" without the quotes > Select the following options -

1. Select - "Create custom settings (for code developers)"

2. Select - "Select individual settings from a full list"

3. Check the following boxes -

- Special Pool

- Pool Tracking

- Force IRQL Checking

- Deadlock Detection

- Security Checks (Windows 7)

- Concurrentcy Stress Test (Windows 8)

- DDI compliance checking (Windows 8)

- Miscellaneous Checks

4. Select - "Select driver names from a list"

5. Click on the "Provider" tab. This will sort all of the drivers by the provider.

6. Check EVERY box that is NOT provided by Microsoft / Microsoft Corporation.

7. Click on Finish.

8. Restart.

Important information regarding Driver Verifier:

- If Driver Verifier finds a violation, the system will BSOD.

- After enabling Driver Verifier and restarting the system, depending on the culprit, if for
example the driver is on start-up, you may not be able to get back into normal Windows
because Driver Verifier will flag it, and as stated above, that will cause / force a BSOD.

If this happens, do not panic, do the following:

- Boot into Safe Mode by repeatedly tapping the F8 key during boot-up.

- Once in Safe Mode - Start > type "system restore" without the quotes.

- Choose the restore point you created earlier.

If you did not set up a restore point, do not worry, you can still disable Driver Verifier to get
back into normal Windows:

- Start > Search > type "cmd" without the quotes.

- To turn off Driver Verifier, type in cmd "verifier /reset" without the quotes.

- Restart and boot into normal Windows.

How long should I keep Driver Verifier enabled for?

It varies, many experts and analysts have different recommendations. Personally, I recommend
keeping it enabled for at least 36-48 hours. If you don't BSOD by then, disable Driver Verifier.

My system BSOD'd, where can I find the crash dumps?

They will be located in C:\Windows\Minidump

Any other questions can most likely be answered by this article:

Using Driver Verifier to identify issues with Windows drivers for advanced users

Regards,

Patrick

 

I let memtest run for 10 passes each time. I actually had problems when I ran it at first so I went and replaced all of my ram with a new set. Then let it run again without issue.

I'll get all of those issues fixed and hopefully post back here in a few days saying that I haven't had any issues...

 

Sounds good

Regards,

Patrick

 

well... it has crashed while i have been away so i'll load up Driver Verifier.

 

Hi,

Keep me updated after you enable verifier.

Regards,

Patrick

 

i have turned it on but it isn't blue screening, it is just locking up.

Edit:
It lets me put in the password to log in then immediately crashes.

 

edit for the above:
It lets me put in the password to log in then immediately freezes

 

Definitely a driver issue here then. But the fact that it's locking up, that is frustrating...

I'm assuming because it's locking up, new dumps aren't being written? Or are they.

If you disable verifier via safe mode, or just boot into safe mode, and check c:\windows\minidump, you can check.

Regards,

Patrick

 

No dumps, but I've been taking things off the startup list one at a time from safemode seeing if one fixes it... and I think I've found it... I took the Lycosa keyboard out of the startup and it boots just fine now. So I've uninstalled both the mouse and keyboard from my system. I'll let driver verifier run now that the system starts and hope that that fixes my issues, and if it does I can now justify a G19 to myself and the wife!!!

 

Hopefully next time I reply It'll be a "I haven't had any issues in a week now!"

Thanks for everything so far though

 

My pleasure, I was going to recommend exactly what you did next, so great work!!

Regards,

Patrick

 

It locked up again, with no BDOD and no dump files. I let it sit for an hour hoping that it would BSOD and dump but no such luck. It seems like with driver verifier on it is not giving me BSOD's but instead just hard locking. Any ideas?

 

That could be signs of a driver being an issue, but since it's not generating dumps and just locking up, it'll be rather hard to decipher what the culprit is. Since it's locking up, we'll need to troubleshoot.

You mentioned this happen suddenly and out of the blue, what were the most recent changes you made to the system if you can remember at the time of when the crashes started happening? Did you add any hardware, any software installed, any startup services added, etc.

Locking up could also be signs of memory, how long did you run Memtest86+ for?

Regards,

Patrick

 

I'm starting to think that its one of my hard drives. My games are crashing without BSOD's and the one that tells me what went wrong is telling me that it couldn't find certain files. So I think I may try a new HD.... Does that sound reasonable?

I ran memtest86+ for 10 passes. Should I run it again?

 

It's a possibility, yes of course.

You could flat out purchase a new one, or RMA your current. But HDD diagnostics would be a good idea too: Hard Drive Diagnostic Procedure

Regards,

Patrick