BSOD - Happens about anytime, mostly in games.

[Zeeky]

Attacked RAR files with info in it:
Been having this issue for a long time, only seems to get worse.\
Happens mostly in games, at random but mostly when game starts.
Screen goes black when it starts, then Full screen of 1 solid color (blue, red, green ext)
I still hear sounds and talk on teamspeak for a bit till everything goes weird.

Drivers fully upgraded.
One of those 2 in 1 video cards.
ATI Mobility Radeaon DH 4670

- Windows 7 64bit Home Premium
- If it matters, got from acer as "upgrade" disc, tho use it to freshly install
- I re-install it every now and then
- Systems a few years old (3-5)
- Laptop

Need anymore info let me know

 

[writhziden]

[list=1]
[*]
Microsoft (R) Windows Debugger Version 6.11.0001.404 X86
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [F:\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
---------
[*]
Loading Dump File [F:\BSODDmpFiles\Zeeky\Windows_NT6_BSOD_jcgriff2\011312-40669-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`0301b000 PsLoadedModuleList = 0xfffff800`03260670
Debug session time: Fri Jan 13 03:56:05.279 2012 (GMT-7)
System Uptime: 4 days 8:34:17.302
Loading Kernel Symbols
...............................................................
................................................................
........................................
Loading User Symbols
Loading unloaded module list
.................
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 124, {0, fffffa8005dc3038, f2000040, 800}

Probably caused by : hardware

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

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

WHEA_UNCORRECTABLE_ERROR (124)
A fatal hardware error has occurred. Parameter 1 identifies the type of error
source that reported the error. Parameter 2 holds the address of the
WHEA_ERROR_RECORD structure that describes the error conditon.
Arguments:
Arg1: 0000000000000000, Machine Check Exception
Arg2: fffffa8005dc3038, Address of the WHEA_ERROR_RECORD structure.
Arg3: 00000000f2000040, High order 32-bits of the MCi_STATUS value.
Arg4: 0000000000000800, Low order 32-bits of the MCi_STATUS value.

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


BUGCHECK_STR:  0x124_GenuineIntel

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

PROCESS_NAME:  System

CURRENT_IRQL:  f

STACK_TEXT:  
fffff880`009f09d8 fffff800`03616a3b : 00000000`00000124 00000000`00000000 fffffa80`05dc3038 00000000`f2000040 : nt!KeBugCheckEx
fffff880`009f09e0 fffff800`031a8513 : 00000000`00000001 fffffa80`05cc44e0 00000000`00000000 fffffa80`05cc4530 : hal!HalBugCheckSystem+0x1e3
fffff880`009f0a20 fffff800`03616700 : 00000000`00000728 fffffa80`05cc44e0 fffff880`009f0db0 fffff880`009f0d00 : nt!WheaReportHwError+0x263
fffff880`009f0a80 fffff800`03616052 : fffffa80`05cc44e0 fffff880`009f0db0 fffffa80`05cc44e0 00000000`00000000 : hal!HalpMcaReportError+0x4c
fffff880`009f0bd0 fffff800`03615f0d : 00000000`00000002 00000000`00000001 fffff880`009f0e30 00000000`00000000 : hal!HalpMceHandler+0x9e
fffff880`009f0c10 fffff800`03609e88 : fffffa80`0636c7e8 fffff880`009e8180 00000000`00000000 00000000`00000000 : hal!HalpMceHandlerWithRendezvous+0x55
fffff880`009f0c40 fffff800`0309652c : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : hal!HalHandleMcheck+0x40
fffff880`009f0c70 fffff800`03096393 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxMcheckAbort+0x6c
fffff880`009f0db0 fffff800`0360eeea : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiMcheckAbort+0x153
fffff880`0331bc28 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : hal!HalpHpetQueryCount+0x1c


STACK_COMMAND:  kb

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: hardware

IMAGE_NAME:  hardware

DEBUG_FLR_IMAGE_TIMESTAMP:  0

FAILURE_BUCKET_ID:  X64_0x124_GenuineIntel_PROCESSOR_BUS

BUCKET_ID:  X64_0x124_GenuineIntel_PROCESSOR_BUS

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

[*]
Loading Dump File [F:\BSODDmpFiles\Zeeky\Windows_NT6_BSOD_jcgriff2\110511-35084-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`02e02000 PsLoadedModuleList = 0xfffff800`03047670
Debug session time: Sat Nov  5 14:12:57.932 2011 (GMT-7)
System Uptime: 0 days 6:31:42.555
Loading Kernel Symbols
...............................................................
................................................................
........................................
Loading User Symbols
Loading unloaded module list
..................................................
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck A, {0, 2, 0, fffff800033ed477}

Unable to load image \SystemRoot\system32\DRIVERS\NETw5s64.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for NETw5s64.sys
*** ERROR: Module load completed but symbols could not be loaded for NETw5s64.sys
Probably caused by : NETw5s64.sys ( NETw5s64+b76b )

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

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

IRQL_NOT_LESS_OR_EQUAL (a)
An attempt was made to access a pageable (or completely invalid) address at an
interrupt request level (IRQL) that is too high.  This is usually
caused by drivers using improper addresses.
If a kernel debugger is available get the stack backtrace.
Arguments:
Arg1: 0000000000000000, memory referenced
Arg2: 0000000000000002, IRQL
Arg3: 0000000000000000, bitfield :
	bit 0 : value 0 = read operation, 1 = write operation
	bit 3 : value 0 = not an execute operation, 1 = execute operation (only on chips which support this level of status)
Arg4: fffff800033ed477, address which referenced memory

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


READ_ADDRESS: GetPointerFromAddress: unable to read from fffff800030b1100
 0000000000000000 

CURRENT_IRQL:  2

FAULTING_IP: 
hal!HalpDmaNextContiguousPiece+103
fffff800`033ed477 448b08          mov     r9d,dword ptr [rax]

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

BUGCHECK_STR:  0xA

PROCESS_NAME:  BitTorrent.exe

TRAP_FRAME:  fffff880091f69b0 -- (.trap 0xfffff880091f69b0)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=0000000000000000 rbx=0000000000000000 rcx=0000000000000044
rdx=0000000000000044 rsi=0000000000000000 rdi=0000000000000000
rip=fffff800033ed477 rsp=fffff880091f6b48 rbp=0000000000000000
 r8=0000000000000028  r9=0000000000000000 r10=00000000000fffff
r11=fffffa80069a19b0 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei pl nz ac pe nc
hal!HalpDmaNextContiguousPiece+0x103:
fffff800`033ed477 448b08          mov     r9d,dword ptr [rax] ds:0001:00000000`00000000=????????
Resetting default scope

LAST_CONTROL_TRANSFER:  from fffff80002e7e1e9 to fffff80002e7ec40

STACK_TEXT:  
fffff880`091f6868 fffff800`02e7e1e9 : 00000000`0000000a 00000000`00000000 00000000`00000002 00000000`00000000 : nt!KeBugCheckEx
fffff880`091f6870 fffff800`02e7ce60 : fffffa80`0a1c47b0 fffff880`0682bc2e fffffa80`040bdac0 fffffa80`08590fd8 : nt!KiBugCheckDispatch+0x69
fffff880`091f69b0 fffff800`033ed477 : fffffa80`091533b0 fffffa80`0cd79fbc fffff800`033ed524 fffffa80`08590fd8 : nt!KiPageFault+0x260
fffff880`091f6b48 fffff800`033ed524 : fffffa80`08590fd8 fffffa80`069a19b0 fffffa80`069a17d0 00000000`00000000 : hal!HalpDmaNextContiguousPiece+0x103
fffff880`091f6b60 fffff800`033f04fb : fffffa80`08590fd8 fffffa80`069a19b0 fffffa80`091533b0 fffffa80`0b03ffd8 : hal!HalpDmaMapScatterTransfer+0x34
fffff880`091f6bb0 fffff800`033f0472 : fffffa80`08590fd8 fffffa80`08590fd0 00000000`00000028 00000000`00000000 : hal!HalpMapTransfer+0x7b
fffff880`091f6c40 fffff800`033ef94f : 00000000`00000000 fffff800`033ecfb9 00000000`00000000 00000000`00000003 : hal!IoMapTransfer+0x8e
fffff880`091f6c80 fffff800`033efafd : fffffa80`0637d050 fffffa80`069a19b0 00000000`00000001 fffffa80`000003b4 : hal!HalpAllocateAdapterCallback+0xc7
fffff880`091f6d20 fffff800`033f0156 : fffffa80`069a19b0 00000000`00000000 fffffa80`069a1900 00000000`00000003 : hal!IoFreeAdapterChannel+0x109
fffff880`091f6d50 fffff800`033ef71f : fffffa80`0b0ee9d0 00000000`00000050 fffffa80`069a19b0 fffffa80`0a875330 : hal!HalAllocateAdapterChannel+0x11a
fffff880`091f6d90 fffff880`018b6750 : fffffa80`08acc260 fffffa80`069a1620 fffffa80`000000a0 fffff880`06a78c40 : hal!HalBuildScatterGatherList+0x2f3
fffff880`091f6e00 fffff880`0683476b : fffffa80`0637d1a0 00000000`00000000 fffffa80`0aa6a5b0 fffff880`069d9aa0 : ndis!NdisMAllocateNetBufferSGList+0x110
fffff880`091f6ea0 fffffa80`0637d1a0 : 00000000`00000000 fffffa80`0aa6a5b0 fffff880`069d9aa0 00000000`00000000 : NETw5s64+0xb76b
fffff880`091f6ea8 00000000`00000000 : fffffa80`0aa6a5b0 fffff880`069d9aa0 00000000`00000000 00000050`00000100 : 0xfffffa80`0637d1a0


STACK_COMMAND:  kb

FOLLOWUP_IP: 
NETw5s64+b76b
fffff880`0683476b ??              ???

SYMBOL_STACK_INDEX:  c

SYMBOL_NAME:  NETw5s64+b76b

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: NETw5s64

IMAGE_NAME:  NETw5s64.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  4aafedb7

FAILURE_BUCKET_ID:  X64_0xA_NETw5s64+b76b

BUCKET_ID:  X64_0xA_NETw5s64+b76b

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


[/list]

1. Due to your graphics card driver. Other possible causes are Memory problems... Corrupted hard disk file system... Corrupted System Files... Lack of Windows updates... Drivers...
2. Hardware stop.
3. Due to your network adapter driver. Other possible causes are Memory problems... Corrupted hard disk file system... Corrupted System Files... Lack of Windows updates... Antivirus Software...

Thanks to Dave76 for help understanding possible causes.



We will start with the common problems first (see bold possible causes). Do the following steps and test after each to see if stability increases. Post back your results after each step, and if you get a blue screen crash, upload the files again and await further instructions after we are able to analyze the crash.

• If you are overclocking any hardware, please stop.
  
  
  
• Download and install the appropriate version of HWINFO: HWiNFO32 for 32-bit Windows 7 or HWiNFO64 for 64-bit Windows 7 to check hardware temperatures by running in sensor-only mode.
  
  
  
• Use FurMark: VGA Stress Test, Graphics Card and GPU Stability Test, Burn-in Test, OpenGL Benchmark and GPU Temperature | oZone3D.Net to test the graphics card GPU. Then use the |MG| Video Memory Stress Test 1.7.116 Download to test your graphics card memory.
  
  
  
• Run http://www.sevenforums.com/tutorials/100352-hardware-stress-test-prime95.html to determine any hardware problems. Run all three tests for a few hours each. If you get errors, stop the test and post back here.
  
  
  
• Run the boot version of Memtest86+ paying close attention to Parts 2 and 3 of the tutorial. Also, in case Memtest86+ misses anything and comes up with no errors, run the extended version of the Windows Memory Diagnostics Tool for at least five passes. These you may want to run overnight since they take a long time to complete (run them an hour before bed each of the next two nights and check before going to sleep that they are still running).
  
  
  
• Hardware http://www.sevenforums.com/crash-lockup-debug-how/35349-stop-0x124-what-means-what-try.html
  
  
  
• Update your BIOS, Chipset drivers, and wireless network adapter drivers via your laptop model's support site.

 

[Zeeky]

Was unable to do FurMark test, "Has Stopped Working And Has To Close" keeps happening regardless on how its run.
Did the MG Video Memory test and so far no issues there.

Did first test on Stress test and no issues so far, will do others today.

Still wana get the FurMark to work tho...

 

[writhziden]

Try uninstalling and re-installing FurMark; maybe it did not install properly the first time.

 

[Zeeky]

Done that, even re-downloaded and re-installed, same issues for what ever reason...

I'll go ahead and download an older version to see if that will at least work.

Edit: Older version worked. Gona do that testing in a bit!

 

[writhziden]

Alright, glad the older version worked. Monitor the temperatures and post back what they even out at. If they get at all above 95 C, post back for further instructions.

 

[Zeeky]

OK, got pretty hot, ran with lots of diff setting, still no blue screen or anything.

More info if this helps:
I still think its some how hardware related because:
It started at playing high end games like Battle Field BC2, tho it started in Elder Scrolls Of Oblivion, then over a time, other games start getting it, games like Alice madness returns, then over a long period of time, even Wow got it at a few area's... NOW even League of Legends! Which is one of the biggest issues ATM since League of Legends is my main game and blue screening out of that game screws it up pretty bad.

Also, possibly happening out of no where not even in game, like trying to watch a video, mainly seems to happen when right clicking something to bring up a "box" o.0

Also to add: Friend got same same laptop as me same day, both played Battle Field BC2, WOW, ext...
SAME thing happened to him.

ANYWAYS, appeared to pass the Video Card Stress, tho I'll try it again later on.

 

[Zeeky]

Need anymore information?

Edit: didn't edit last post, forgot sry >_<

Also just in case I didn't say.

Before the bluescreen happens:
Screen goes black - Then starts showing Solid full screen colors (Red, Blue, Green) 1 after another, then weird black/white patters and then repeats, then sooner or later, gives bluescreen (Not all the time)
Also sounds when this happen go crazy a few secs into the first black screen (Can still talk on teamspeak for instance) then after wards, can't.

 

[writhziden]

What do temperatures get to when playing games? You can enable logging in sensor-only mode of HWINFO. Have it save the CSV file where you will remember, then compress (zip) the CSV file after a crash and post on here.

 

[Zeeky]

What do temperatures get to when playing games? You can enable logging in sensor-only mode of HWINFO. Have it save the CSV file where you will remember, then compress (zip) the CSV file after a crash and post on here.

I am going out and saying I am 90% sure heat is nothing to do with it.
During the test, I got to 95, and also during games, I have a fan on my laptop to test, kept checking temp, never got over 60-65 THO I will go ahead and test this anyways.

THO I HOPE I DON'T BSOD this game, if I do, ill have the info.

 

[writhziden]

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

 

[Zeeky]

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.

 

[writhziden]

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

 

[Zeeky]

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..

 

[writhziden]

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

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?

 

[Zeeky]

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

 

[writhziden]

http://global-download.acer.com/GDF...ep3=Aspire 8935G&OS=721&LC=en&BC=Acer&SC=PA_6

Is that newer?

If you cannot find a driver newer than June 2009 (need one after July 13, 2009), then install the driver using the steps for http://www.sevenforums.com/tutorials/98073-drivers-install-vista-drivers-windows-7-a.html.

 

[Zeeky]

Seems to be the same.

Attached a DxDiag log.
Hope this helps.

 

[writhziden]

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 http://www.sevenforums.com/tutorials/98073-drivers-install-vista-drivers-windows-7-a.html

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 http://www.sevenforums.com/tutorials/98073-drivers-install-vista-drivers-windows-7-a.html

 

[Zeeky]

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)