BSOD - Happens about anytime, mostly in games.

When is the last time you blew the dust out of the system?

To remove dust, follow the following general procedure. If you have a desktop bought from Dell, HP, Sony, Lenovo, etc. make sure removing the desktop casing will not void your warranty first. Call the company if you are still under warranty and ask if it is okay to remove the casing and blow dust out. The procedure described is fine for laptops; just make sure no stickers are on panels saying if you remove the panel it will void the warranty.

1. Shut down and turn off your computer.
2. Unplug all power supplies to the computer (AC Power then battery for laptops, AC power for desktops)
3. Hold down the power button for 30 seconds to close the circuit and ensure all power drains from components.
4. Remove the casing for a desktop, or remove any screwed on panels and disc drives for laptops.
5. Blow out the dust inside by using a can of compressed air or a low pressure compressor. You will want to put the computer on a desk or table so you can maintain the can in an upright position if using a can of air. Blow into all crevices on the motherboard, heat sinks, cards, modules, etc. for a desktop. Blow into vents, opened panels, disc drive areas, USB ports, and the keyboard if it is a laptop. You may also want to blow inside the disc drive by replacing the drive to the laptop, starting the computer, opening the drive, and then turning off the computer and removing all power as described above including the 30 second power button step. For a desktop, you may also want to blow inside the disc drive by starting the computer, opening the drive, and then turning off the computer and removing all power as described above including the 30 second power button step.
6. Replace casing for the desktop. Replace panels and disc drive (if you have not already done so) for the laptop.
7. Plug power supplies in. AC adapter for the desktop. Battery and then AC Adapter for the laptop.
8. Start the computer and see if performance is better.

I also note ManyCam on your system. This is a known cause of blue screen crashes in Windows 7. Please uninstall and replace with SplitCam Free webcam software for video stream splitting and adding cool video effects to your webcam video

Edit: Blue Screen, Temps are normal....
So temp not causing it....

also i don't have manycam on ever and still had issues before I got it, only got it not to long ago to take pic of ma kittys to give away...

THO i'll uninstall it anyways, never use it.

Can you upload the new crash report? Hopefully it will reveal something useful. :)

OK, open the case at the bottom.
DUSTLESS!
Checked if ram and everything else didn't look ****ed, all looks great.

So 100% sure, heat has no issue with this now..

On attachments are the last 3 BSOD i got, i think 1 of them is the one I already posts.
Goes from oldest to newest.

Normally blue screen won't come up and just stays in the Color changing cycle.

Sucks having to use the 2nd vid card to play games, can hardly play League of Legends, at least no blue screening tho...

Really hope this can be resolved!

>_<

Won't be for another 2 months till I get my new computer..

The latest .dmp file I have, your graphics card driver is very old. I really need the .dmp files so I can check drivers.

Code:

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


Loading Dump File [F:\Kingston\BSODDmpFiles\Zeeky\Windows_NT6_BSOD_jcgriff2\013112-29889-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*C:\SymCache*http://msdl.microsoft.com/download/symbols
Executable search path is: 
Windows 7 Kernel Version 7601 (Service Pack 1) MP (2 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506
Machine Name:
Kernel base = 0xfffff800`03061000 PsLoadedModuleList = 0xfffff800`032a6670
Debug session time: Mon Jan 30 21:59:00.117 2012 (GMT-7)
System Uptime: 0 days 0:08:26.601
Loading Kernel Symbols
...............................................................
................................................................
........................................
Loading User Symbols
Loading unloaded module list
....
Unable to load image \SystemRoot\system32\DRIVERS\atipmdag.sys, Win32 error 0n2
*** ERROR: Module load completed but symbols could not be loaded for atipmdag.sys
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 1000007E, {ffffffffc0000094, fffff88004dfa0a9, fffff880085dbf38, fffff880085db790}

Probably caused by : atipmdag.sys ( atipmdag+3740a9 )

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

1: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M (1000007e)
This is a very common bugcheck.  Usually the exception address pinpoints
the driver/function that caused the problem.  Always note this address
as well as the link date of the driver/image that contains this address.
Some common problems are exception code 0x80000003.  This means a hard
coded breakpoint or assertion was hit, but this system was booted
/NODEBUG.  This is not supposed to happen as developers should never have
hardcoded breakpoints in retail code, but ...
If this happens, make sure a debugger gets connected, and the
system is booted /DEBUG.  This will let us see why this breakpoint is
happening.
Arguments:
Arg1: ffffffffc0000094, The exception code that was not handled
Arg2: fffff88004dfa0a9, The address that the exception occurred at
Arg3: fffff880085dbf38, Exception Record Address
Arg4: fffff880085db790, Context Record Address

Debugging Details:
------------------


EXCEPTION_CODE: (NTSTATUS) 0xc0000094 - {EXCEPTION}  Integer division by zero.

FAULTING_IP: 
atipmdag+3740a9
fffff880`04dfa0a9 41f7f0          div     eax,r8d

EXCEPTION_RECORD:  fffff880085dbf38 -- (.exr 0xfffff880085dbf38)
ExceptionAddress: fffff88004dfa0a9 (atipmdag+0x00000000003740a9)
   ExceptionCode: c0000094 (Integer divide-by-zero)
  ExceptionFlags: 00000000
NumberParameters: 0

CONTEXT:  fffff880085db790 -- (.cxr 0xfffff880085db790)
rax=0000000000000000 rbx=fffff880085dc1c0 rcx=0000000000000000
rdx=0000000000000000 rsi=fffffa8007394400 rdi=fffff88004a86000
rip=fffff88004dfa0a9 rsp=fffff880085dc170 rbp=0000000000000026
 r8=0000000000000000  r9=000000000000fc2d r10=fffff880085dc1c0
r11=fffff88004fefb80 r12=0000000000000000 r13=00000000ffffffff
r14=00000000000009dd r15=00000000000009de
iopl=0         nv up ei pl zr na po nc
cs=0010  ss=0018  ds=002b  es=002b  fs=0053  gs=002b             efl=00010246
atipmdag+0x3740a9:
fffff880`04dfa0a9 41f7f0          div     eax,r8d
Resetting default scope

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

BUGCHECK_STR:  0x7E

PROCESS_NAME:  System

CURRENT_IRQL:  0

ERROR_CODE: (NTSTATUS) 0xc0000094 - {EXCEPTION}  Integer division by zero.

LAST_CONTROL_TRANSFER:  from fffffa80073be78e to fffff88004dfa0a9

STACK_TEXT:  
fffff880`085dc170 fffffa80`073be78e : 00000000`00000002 fffff880`04e91658 fffff880`0389e000 fffff880`085dc250 : atipmdag+0x3740a9
fffff880`085dc178 00000000`00000002 : fffff880`04e91658 fffff880`0389e000 fffff880`085dc250 fffff880`04df91d1 : 0xfffffa80`073be78e
fffff880`085dc180 fffff880`04e91658 : fffff880`0389e000 fffff880`085dc250 fffff880`04df91d1 00000000`00000027 : 0x2
fffff880`085dc188 fffff880`0389e000 : fffff880`085dc250 fffff880`04df91d1 00000000`00000027 fffff880`bebe0031 : atipmdag+0x40b658
fffff880`085dc190 fffff880`085dc250 : fffff880`04df91d1 00000000`00000027 fffff880`bebe0031 fffffa80`03c58000 : 0xfffff880`0389e000
fffff880`085dc198 fffff880`04df91d1 : 00000000`00000027 fffff880`bebe0031 fffffa80`03c58000 fffffa80`073acd48 : 0xfffff880`085dc250
fffff880`085dc1a0 00000000`00000027 : fffff880`bebe0031 fffffa80`03c58000 fffffa80`073acd48 fffff880`085dc250 : atipmdag+0x3731d1
fffff880`085dc1a8 fffff880`bebe0031 : fffffa80`03c58000 fffffa80`073acd48 fffff880`085dc250 fffffa80`07394400 : 0x27
fffff880`085dc1b0 fffffa80`03c58000 : fffffa80`073acd48 fffff880`085dc250 fffffa80`07394400 00000000`00000000 : 0xfffff880`bebe0031
fffff880`085dc1b8 fffffa80`073acd48 : fffff880`085dc250 fffffa80`07394400 00000000`00000000 0000fc0d`00000000 : 0xfffffa80`03c58000
fffff880`085dc1c0 fffff880`085dc250 : fffffa80`07394400 00000000`00000000 0000fc0d`00000000 00000000`00000000 : 0xfffffa80`073acd48
fffff880`085dc1c8 fffffa80`07394400 : 00000000`00000000 0000fc0d`00000000 00000000`00000000 fc2d0000`04dc03f6 : 0xfffff880`085dc250
fffff880`085dc1d0 00000000`00000000 : 0000fc0d`00000000 00000000`00000000 fc2d0000`04dc03f6 fa80073b`f3d40081 : 0xfffffa80`07394400


FOLLOWUP_IP: 
atipmdag+3740a9
fffff880`04dfa0a9 41f7f0          div     eax,r8d

SYMBOL_STACK_INDEX:  0

SYMBOL_NAME:  atipmdag+3740a9

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: atipmdag

IMAGE_NAME:  atipmdag.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  4a4a90cd

STACK_COMMAND:  .cxr 0xfffff880085db790 ; kb

FAILURE_BUCKET_ID:  X64_0x7E_atipmdag+3740a9

BUCKET_ID:  X64_0x7E_atipmdag+3740a9

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

1: kd> lmvm atipmdag
start             end                 module name
fffff880`04a86000 fffff880`050ab000   atipmdag   (no symbols)           
    Loaded symbol image file: atipmdag.sys
    Image path: \SystemRoot\system32\DRIVERS\atipmdag.sys
    Image name: atipmdag.sys
    Timestamp:        Tue Jun 30 16:25:17 2009 (4A4A90CD)
    CheckSum:         005DE6B5
    ImageSize:        00625000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4

Jun, 2009 is pre-Windows 7. Make sure your graphics card driver is the newest available. Also, what is the make and model of your laptop? Acer? Model?

Is newest driver, none after 2009, sad as it is...
Acer

because it being one of those shit 2 in 1 video cards, no normal driver works.
from what I can see, no way around that.

AT least on the acer laptop site....

Laptop: Aspire 8935g

Seems to be the same.

Attached a DxDiag log.
Hope this helps.

Alright, uninstall the driver, and then re-intall using the Vista method linked in my previous post. When you uninstall and re-install, use the following method.

1. Download the latest drivers for your display card(s)
2. Click Start Menu
3. Right Click My Computer/Computer
4. Click Manage
5. Click Device Manager from the list on the left
6. Expand Display adapters
7. Do the following for each adapter (in case you have multiple display cards in the list)
   
   • Right click the adapter
   • Click Uninstall (do not click OK in the dialog box that pops up after hitting Uninstall)
   • Put a tick in Delete driver software for this device (if this option is available, otherwise just hit OK) and hit OK
8. Restart your computer after uninstalling drivers for all display cards
9. Install the latest driver for the display cards once Windows starts using the methods outlined in Drivers - Install Vista Drivers on Windows 7

Alternatively:

1. Login as an adminstrative user
2. Download the latest drivers for your display card(s)
3. Click Start Menu
4. Click Control Panel
5. Click Hardware and Sound
6. Click Device Manager (the last link under Devices and Printers)
7. Expand Display adapters
8. Do the following for each adapter (in case you have multiple display cards in the list)
   
   • Right click the adapter
   • Click Uninstall (do not click OK in the dialog box that pops up after hitting Uninstall)
   • Put a tick in Delete driver software for this device (if this option is available, otherwise just hit OK) and hit OK
9. Restart your computer after uninstalling drivers for all display cards
10. Install the latest driver for the display cards once Windows starts using the methods outlined in Drivers - Install Vista Drivers on Windows 7

OK, installing driver after fresh uninstall, got an error that I never seen before...

RunDLL
There was a problem starting C:\Windows\system32\pnpui.dll

The Specified module could not be found.

The dll it self is there tho, so not missing.

SO for now stuck on "Crappy" video card until I can get pass this error or get another driver (Or just use the driver disc)