Tech Support banner

Status
Not open for further replies.
1 - 19 of 19 Posts

·
Registered
Joined
·
12 Posts
Discussion Starter · #1 ·
· OS - Vista/ Windows 7 ? Windows 7
· x86 (32-bit) or x64 ? 32-bit
· What was original installed OS on system? Windows 7
· Is the OS an OEM version. OEM
· Age of system 4-5 yrs
· Age of OS installation - have you re-installed the OS? Just recently reinstalled 4 days ago

· CPU AMD Athalon(tm) 64 x2 dual core processsor 6400+ 3.22 ghz
· Video Card Geforce 560ti 448 cores
· MotherBoard ASUS m2n-sli
· Power Supply - brand & wattage

·I built this computer.

BSOD mostly occurs when watching any form of video or trying to play any FPS game.
 

Attachments

·
TSF Team, Emeritus
Joined
·
4,349 Posts
Re: Random BSOD

Hi,

Update to Service Pack 1 ASAP: Learn how to install Windows 7 Service Pack 1 (SP1)

Various different bugchecks here:

Before moving forward with troubleshooting, try the following first:

Code:
ASACPI    91ffa000    91ffb420    Thu Aug 12 22:52:52 2004 (411c2d04)    00004aa7        ASACPI.sys
DATED FROM 2004

^^ Asus ATK0110 ACPI Utility (a known BSOD maker in Win7 and Win8). Also a part of many Asus utilities. Either update this driver ASAP or remove any and all Asus utilities.

Code:
nvm62x32    91416000    9146ac80    Fri Oct 17 17:00:39 2008 (48f8fcf7)    000610af        nvm62x32.sys
Dated from 2008, see if update is available - Drivers - Download NVIDIA Drivers
^^
nVidia Ethernet Networking Driver (nForce chipset driver)

If the above does not help, move on to the following~

PAGE_FAULT_IN_NONPAGED_AREA (50)

This indicates that invalid system memory has been referenced.


Usual causes are a bug in a device driver, hardware related memory issues, corrupt NTFS volume, anti-virus software.
For this, run a chkdsk:

start>search bar>type cmd right click and select run as admin

Elevated CMD should now be opened, type the following:

chkdsk x: /r

x implies your drive letter, so if your hard drive in question is letter c, it would be:

chkdsk c: /r

Restart system and let chkdsk run.
MEMORY_MANAGEMENT (1a)

A severe memory management error occurred.
Usually hardware memory related. I cannot get any info from this dump as the first parameter is of the following: 00041287


0x41287 Internal memory management structures are corrupted. To further investigate the cause, a kernel memory dump file is needed.
Due to MEMORY MANAGEMENT though, run Memtest:



Memtest86+:



Download Memtest86+ here:
http://www.memtest.org/



Which should I download?



You can either download the pre-compiled ISO that you would burn to a CD and then boot from the CD, or you can download the auto-installer for the USB key. What this will do is format your USB drive, make it a bootable device, and then install the necessary files. Both do the same job, it's just up to you which you choose, or which you have available (whether it's CD or USB).



How Memtest works:



Memtest86 writes a series of test patterns to most memory addresses, reads back the data written, and compares it for errors.



The default pass does 9 different tests, varying in access patterns and test data. A tenth test, bit fade, is selectable from the menu. It writes all memory with zeroes, then sleeps for 90 minutes before checking to see if bits have changed (perhaps because of refresh problems). This is repeated with all ones for a total time of 3 hours per pass.



Many chipsets can report RAM speeds and timings via SPD (Serial Presence Detect) or EPP (Enhanced Performance Profiles), and some even support changing the expected memory speed. If the expected memory speed is overclocked, Memtest86 can test that memory performance is error-free with these faster settings.



Some hardware is able to report the "PAT status" (PAT: enabled or PAT: disabled). This is a reference to Intel Performance acceleration technology; there may be BIOS settings which affect this aspect of memory timing.



This information, if available to the program, can be displayed via a menu option.



Any other questions, they can most likely be answered by reading this great guide here:



http://forum.canardpc.com/threads/28864-FAQ-please-read-before-posting
Regards,
Patrick


 

·
Registered
Joined
·
12 Posts
Discussion Starter · #5 ·
Re: Random BSOD

Mini Update
I have a lot more BSODs occuring and more frequent than I did before I installed the SP1
 

·
TSF Team, Emeritus
Joined
·
4,349 Posts
Re: Random BSOD

Thanks for the update, that's interesting.

Well, in any case, try and get the rest of the diagnostic steps taken care of. Let me know if you actually cannot because of how frequent the BSOD's are.

Take care of ASCAPI.sys right away next.

Regards,

Patrick
 

·
Registered
Joined
·
12 Posts
Discussion Starter · #7 ·
Re: Random BSOD

Fortunately, I found an extra 650gb harddrive, and I reinstalled onto it, so far no BSOD's, the BSODs became to frequent for me to try to work on the computer so I just trashed it haha, Ill keep you posted but I believe it was harddrive failure.
 

·
TSF Team, Emeritus
Joined
·
4,349 Posts
Re: Random BSOD

Yeah, that's what I imagined was probably the case. It's why I recommended a chkdsk, etc. Just to be sure.

Anyway, keep me updated on the system's behavior since the new drive.

Regards,

Patrick
 

·
Registered
Joined
·
12 Posts
Discussion Starter · #9 ·
Re: Random BSOD

After Instaling the new Drive, It seemed I had no errors, till the dreaded blue screen came back, Im not service pack 1 but that shouldnt be an issue I dont think. but heres a new .dmp file
 

Attachments

·
TSF Team, Emeritus
Joined
·
4,349 Posts
Re: Random BSOD

Hi,

You still need to update your nVidia network drivers:

Dated from 2008, see if update is available - Drivers - Download NVIDIA Drivers
^^
nVidia Ethernet Networking Driver (nForce chipset driver)

If after you do, you're still crashing, 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:
http://support.microsoft.com/kb/244617

Regards,

Patrick
 

·
Registered
Joined
·
12 Posts
Discussion Starter · #12 ·
Re: Random BSOD

Sorry for the late reply, I ran memtest86 and no issues so far Im gonna do a full night testing tonight on that though, and I have the driver verifier on as well which I haven't BSOD'd yet from. But Im still having issues with my games, anytime I go to play anything in 3d mode with any of the 3 Video Cards I own with the correct drivers installed even my computer bluescreens real quick, If I just idle or download something or play music I have no issues, but it seems as soon as I come to watching any form of video

Edit: Btw, I installed the NForce Drivers but my GTX 560 ti isn't supported by it and I think the NForce drivers are obsolete since 2010
 

·
TSF Team, Emeritus
Joined
·
4,349 Posts
Re: Random BSOD

Hi,

Let me know as soon as you crash and attach the DMP that came with it : )

Regards,

Patrick
 

·
Registered
Joined
·
12 Posts
Discussion Starter · #14 · (Edited)
Re: Random BSOD

Hi,

Let me know as soon as you crash and attach the DMP that came with it : )

Regards,

Patrick
I just crashed again, It seems its only when I play video. If I play a game it will crash 3 times to the desktop or twice and then the third time I attempt it will blue screen, I thought possibly it was the latest NVidia Drivers so I switched back to 314 and im going to attempt the 320.0 driver. but heres the most recent dmp I believe.

Edit: As well I have tried using a house fan blowing on the open case thinking it may be a probable overheating issue even though my readings are in the 39-50 c range for everything still no fix.
 

Attachments

·
TSF Team, Emeritus
Joined
·
4,349 Posts
Re: Random BSOD

Hi,

All of the attached dumps have been of the UNEXPECTED_KERNEL_MODE_TRAP (7f) bugcheck all containing amdk8 in the stack as well as throughout the DMP(s). Verifier is enabled in these dumps, but fails to flag or fault anything but amdk8.sys. This could signify a hardware error, and with amdk8.sys being the consistent fault, possibly a processor fault itself.

amdk8.sys = Processor Device Driver.

Try the different video card drivers as you mentioned.

Give Prime95 a try - Hardware - Stress Test With Prime95 - Windows 7 Help Forums

Run Blend and Small FFT's.

Regards,

Patrick
 

·
Registered
Joined
·
12 Posts
Discussion Starter · #16 ·
Re: Random BSOD

Hi,

All of the attached dumps have been of the UNEXPECTED_KERNEL_MODE_TRAP (7f) bugcheck all containing amdk8 in the stack as well as throughout the DMP(s). Verifier is enabled in these dumps, but fails to flag or fault anything but amdk8.sys. This could signify a hardware error, and with amdk8.sys being the consistent fault, possibly a processor fault itself.

amdk8.sys = Processor Device Driver.
Would you suggest buying a new processor? I have an extra AM2 but it wont even boot
 

·
TSF Team, Emeritus
Joined
·
4,349 Posts
Re: Random BSOD

No, not yet.

Run Prime95 as I instructed please and let me know how the system handles stress.

Regards,

Patrick
 

·
Registered
Joined
·
12 Posts
Discussion Starter · #18 ·
[SOLVED]Random BSOD

The stress test was okay, no errors. My BSODs are gone now, I did the stress testing fine and got a bluescreen so I went out and bought 2 1gb sticks of DDR2 and now Im fine. I've been playing games for 6+ hours now and Im quite content. Thanks for the awesome help! Love TSF!
 
1 - 19 of 19 Posts
Status
Not open for further replies.
Top