BSOD while running games

[toxygamer]

Doesn't matter which game, it does it for them all.
I'm always getting a different error, or it won't tell me what it is at all.
I don't know much about computers at all and I've been trying to figure out what's wrong with no luck. Maybe someone here can help me?
I ran the SF Diag Tool and compressed the folder, I'll attach that.

My OS is Windows 7 Home Premium 64-bit and it is a fresh install.
I got this computer about 2 weeks ago and it's been crashing since I got it.

 

[Tews]

Unfortunately there were no .dmp files.. navigate to c:/windows/minidump and zip up any files and add them as an attachment to your next post...

 

[toxygamer]

Here ya go

 

[ttran]

First of all, please update this driver, it's date from 2005 is guaranteed for causing BSODs

ASACPI   ASACPI.sys   Mon Mar 28 09:30:36 2005 (42476C4C)

Please visit this link: ASUSTeK Computer Inc.-Support- download_item_mkt
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 10th or 11th 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 (NOT 2005).

I suspect the graphic card as dxgmms1.sys was blamed in the DMP and the stop code 7E is graphic card potentially. Please download and install fresh copy of the driver
When upgrading your graphic driver you MUST remove all traces of the current driver. In order to do that we recommend using Guru3D - Driver Sweeper

When it is removed then download and install the fresh copy.

Memory corruption was mentioned in the DMP, with exception code c000005, Download a copy of Memtest86 and burn the ISO to a CD using Iso Recorder or another ISO burning program. Boot from the CD, and leave it running for at least 5 or 6 passes.

nvm62x64 nvm62x64.sys Sat Oct 18 04:01:06 2008 (48F8FD12)

Update it please, it belong to nVidia Ethernet Networking Driver (nForce chipset driver)

BUGCHECK SUMMARY:

BugCheck 50, {ffffffffffffff8d, 0, fffff80002bb007c, 0}


Could not read faulting driver name
Probably caused by : hardware ( nt!AlpcpCaptureHandleAttribute+34 )

Followup: MachineOwner
---------
PROCESS_NAME:  [COLOR=Red][B]PnkBstrB.exe[/B][/COLOR]
BugCheck 1000007E, {ffffffffc0000005, fffff88010b38d90, fffff88002e866a8, fffff88002e85f10}

Probably caused by : dxgmms1.sys ( dxgmms1!VIDMM_GLOBAL::ReferenceAllocationForPreparation+c4 )

Followup: MachineOwner
---------
BugCheck A, {2a, 2, 0, fffff800028c9410}

Probably caused by : memory_corruption ( nt!MiFindNodeOrParent+0 )

Followup: MachineOwner
---------
BugCheck 3B, {c0000005, fffff960001a2bdf, fffff8800a8cc0a0, 0}

Probably caused by : win32k.sys ( win32k!ENTRYOBJ::vSetup+16b )

Followup: MachineOwner
---------

What third party antivirus/firewall are you using? What is Punk Baster and can you run the game without using it????

Let us know if you need help

Tuan

 

[toxygamer]

Wow thanks for all of that!!! I have no idea what Punk Baster is tho... could it be a virus? I just have the windows firewall on my pc

 

[toxygamer]

I'm being told I need Akamai Download Manager to download ATK0110 driver... I can't find it anywhere?

 

[ttran]

If you haven't known what Antivirus to use, I would recommend to use Microsoft Security Essential, it is known for BSODs free.
http://www.microsoft.com/security_essentials
I'm used to be gamer so I've heard that Punk baster is a software that you accidentally installed when you installed your game. Go to Control Panel-->Program features and see it is there, then uninstall it.
Take step by step and try what I've suggested
It's possible that graphic card cause all of these, or memory cause that or may be just drivers and the Punk Baster...Will see

Regard,

Tuan

 

[toxygamer]

Thank you so much for all of your help! I really appreciate it! I am so lost when it comes to this stuff. I'll do everything you said and see what happens, hopefully it fixes my problem!

 

[ttran]

Akamai Download Manager , I think they just made some change to the way you can download the file. You will be asked
I attached the file in case you can't download it from the site

 

[toxygamer]

K did everything you said but the Memtest thing... Still trying to figure that one out. and still need to find the nvidia ethernet driver.

 

[ttran]

memtestx86, easy, instruction is here:
Memory Diagnostics
Just download the file and use Isorecorder, drag the things in, let it burn and you have the CD. Then put it in when you start your computer, let it run while you sleeping or going to work
For the nvidia Ethernet driver, try to find the Nforce chipset driver from here, if you can't find it, that's just fine, I haven't seen anyone sucessfully update it (don't know why might be there haven't been any updates for it)
[nvidia][/nvidia]

 

[toxygamer]

have memtest running now! I'll let it go while I sleep. Thanks for all of your help

 

[toxygamer]

Looks like there's nothing wrong with the memory.

 

[toxygamer]

Unfortunately it's still crashing. could it be caused by a power supply not being powerful enough?

 

[Tews]

Without your system specs, its impossible to tell... please upload any new .dmp files that you may have.

 

[toxygamer]

kk. here's the newest one.

 

[toxygamer]

just found this page EVGA | Products on my graphic card... it states "Minimum 400 Watt for SLI mode system.
(Minimum recommended power supply with +12 Volt current rating of 22 Amps.)" Mine is in SLI mode and only has a 300 watt power supply. Could that make it blue screen?

 

[ttran]

It's likely that your graphic card cause BSODs
Look at my first post in which I blamed the graphic card. Stop code 7E is potentially caused by graphic card. Usually the best option is to try different card on your system and see if it fix the problem. I'm not good with hardware therefore I don't know how to adjust the number that you just mentioned. See if you can borrow a graphic card from somewhere or get it from the shop that you can return it.

STOP 0x0000007E: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED http://www.carrona.org/bsodindx.html#top

Usual causes: Insufficient disk space, Device driver, Video card, BIOS, Breakpoint with no debugger attached, Hardware incompatibility, Faulty system service, Memory, 3rd party remote control,

The generic way to know what the issue is is to changing video adapter. Hopefully you already try the reinstall the driver.

If that's not possible for you, then please enable Driver Verifier, so that we will know for sure what is current issue, because the bugcheck this time does not give us a lot of result:

I'd suggest that you first backup your stuff 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.

BUGCCHECK SUMMARY:

Microsoft (R) Windows Debugger Version 6.12.0002.633 X86
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Users\TUANTR~1\AppData\Local\Temp\Rar$DI00.841\080410-17908-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*e:\symbols*http://msdl.microsoft.com/download/symbols
Executable search path is: 
Windows 7 Kernel Version 7600 MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 7600.16539.amd64fre.win7_gdr.100226-1909
Machine Name:
Kernel base = 0xfffff800`02818000 PsLoadedModuleList = 0xfffff800`02a55e50
Debug session time: Wed Aug  4 21:26:36.809 2010 (UTC + 7:00)
System Uptime: 0 days 0:20:16.323
Loading Kernel Symbols
...............................................................
................................................................
......................
Loading User Symbols
Loading unloaded module list
....
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck A, {5100000008, 2, 1, fffff80002893c5d}

Probably caused by : ntkrnlmp.exe ( nt!KiRetireDpcList+13d )

Followup: MachineOwner
---------