BSoD daily - running Vista

Khymera · Jun 19, 2013

I've been experiencing BSoD crashes daily for the last couple of months it seems. These only seem to happen when I'm playing a specific game on my PC, I have no problems when I'm not playing.

However, I'll take all the help I can get as I feel very out of my element in this area. I followed the instructions posted in another thread ..
https://www.sysnative.com/forums/bs...g-instructions-windows-8-7-windows-vista.html

The files created are attached to this thread, the performance report was too large so it is in .zip format as well.
Any help at all is greatly appreciated.

Patrick · Jun 19, 2013

Hi,

It appears that every single dump has a bugcheck of PAGE_FAULT_IN_NONPAGED_AREA (50). This essentially means that there was an attempt to access an invalid memory address because of a driver bug, hardware issue (usually memory), corrupt NTFS volume, or anti virus software triggering it. At this time, I have a feeling it's a simple driver issue, and I see you have !avast installed, and I have a hunch that may be the issue here, so let's see by enabling 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:
[url]http://support.microsoft.com/kb/244617[/URL]

Regards,

Patrick

Khymera · Jun 19, 2013

Thank you for replying. I did as suggested and ran the driver verifier. It did force a BSoD shortly after startup but I am unable to read the mini dump file that was created. I have the debug dialog for Vista but the program won't generate a report. Can I simply upload the one new file for analysis? The error this time, instead of the page default, listed a corrupt driver as the problem. How do I fix this?

Patrick · Jun 19, 2013

Hi,

Driver Verifier successfully flagged a driver and that driver is ATK64AMD.sys which is the ATK Hotkey ATK0101 ACPI UTILITY driver. Running a !sysinfo machineid it appears you have an Asus G50VT? If so, I would more than recommend visiting Asus' website and updating that utility, or getting it the heck off of your system. Yours is dated from 2006 and the latest according to Asus' website for Vista 64 bit is 2008, so definitely an update needed if you want to keep it!

G50Vt - Notebooks & Ultrabooks - ASUS

Visiting that link, you should appear at the Vista 64-bit screen and at a list of downloads for various things. Find utilities and click it and then find the:

ATK_Hotkey Utility
ATK_Hotkey Utility for Vista

and then download by clicking global and update it asap!

Regards,

Patrick

Khymera · Jun 19, 2013

Thank you so much, again. I'll try that and let you know how it goes.

Patrick · Jun 19, 2013

Hi,

My pleasure! Let me know how things work out : )

Regards,

Patrick

Search

Search

BSoD daily - running Vista

Khymera

New member

Attachments

Patrick

Sysnative Staff

Khymera

New member

Attachments

Patrick

Sysnative Staff

Khymera

New member

Patrick

Sysnative Staff