BSOD - Happens about anytime, mostly in games.

[writhziden]

Run http://www.sevenforums.com/tutorials/1538-sfc-scannow-command-system-file-checker.html and post back the message it gives at the end.

 

[Zeeky]

Windows Resource Protection could not preform the requested operation.

stops around 29% and makes computer all screwy slow o.0

if its not one thing its another...

 

[writhziden]

Have you used any automated optimization programs, especially programs that do registry cleaning?

 

[Zeeky]

Have you used any automated optimization programs, especially programs that do registry cleaning?

I did a registry clean before, tho been long since I did one...
Still have the back up it deleted, if that helps?

 

[writhziden]

Probably too late to use the backup at this point.

Many of us on the forums actually do not recommend automated optimization tools for Windows 7. Windows 7 does a much better job of handling its own optimization than its predecessors did. We especially do not recommend registry cleaning as an "optimization" step because automated registry cleaning causes more harm to the registry than it actually repairs.

In the future, if you need help optimizing Windows 7, please post a thread in Performance & Maintenance - Windows 7 Forums or follow the tutorial enclosed in that forum to http://www.sevenforums.com/tutorial...ws-7-a.html?filter[2]=Performance Maintenance.


As for the system corruption that you are experiencing, it is probably prudent at this point to http://www.sevenforums.com/tutorials/3413-repair-install.html Windows 7.

 

[Zeeky]

OK.
Did all that windows repair n crap....
Then trying to install the ati driver as Vista compatibility didn't work out, as it would always hang at one point
So, just gone and don't it normally.

 

[writhziden]

That should work out. Let us know how stability is after the repair install.

 

[Zeeky]

i knew re-installing drivers wouldn't work.
BSOD again, not even in a game, just right clicking something on task bar....

 

[writhziden]

Please upload the latest crash report by following the http://www.sevenforums.com/crashes-debugging/96879-blue-screen-death-bsod-posting-instructions.html.

 

[Zeeky]

Please upload the latest crash report by following the http://www.sevenforums.com/crashes-debugging/96879-blue-screen-death-bsod-posting-instructions.html.

gona have to wait till i blue screen next cuz i got stuck in color changing loop.

ill see next time if it will give my blue screen

 

[Zeeky]

OK Sorry for the wait, haven't been doing much on laptop.

Got a BSOD again with a report this game.
Seems to be similar to the all the others tho.

 

[writhziden]

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


Loading Dump File [E:\BSODDmpFiles\Zeeky\Windows_NT6_BSOD_jcgriff2\021112-42728-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 7600 MP (2 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 7600.16841.amd64fre.win7_gdr.110622-1503
Machine Name:
Kernel base = 0xfffff800`03412000 PsLoadedModuleList = 0xfffff800`0364fe70
Debug session time: Sat Feb 11 13:39:32.281 2012 (GMT-7)
System Uptime: 3 days 1:06:28.951
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, fffff880043f90a9, fffff880071dbf38, fffff880071db7a0}

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: fffff880043f90a9, The address that the exception occurred at
Arg3: fffff880071dbf38, Exception Record Address
Arg4: fffff880071db7a0, Context Record Address

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


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

FAULTING_IP: 
atipmdag+3740a9
fffff880`043f90a9 41f7f0          div     eax,r8d

EXCEPTION_RECORD:  fffff880071dbf38 -- (.exr 0xfffff880071dbf38)
ExceptionAddress: fffff880043f90a9 (atipmdag+0x00000000003740a9)
   ExceptionCode: c0000094 (Integer divide-by-zero)
  ExceptionFlags: 00000000
NumberParameters: 0

CONTEXT:  fffff880071db7a0 -- (.cxr 0xfffff880071db7a0)
rax=0000000000000000 rbx=fffff880071dc1c0 rcx=0000000000000000
rdx=0000000000000000 rsi=fffffa800769b400 rdi=fffff88004085000
rip=fffff880043f90a9 rsp=fffff880071dc170 rbp=0000000000000026
 r8=0000000000000000  r9=000000000000fc2d r10=fffff880071dc1c0
r11=fffff880045eeb80 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`043f90a9 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 fffffa80065fe78e to fffff880043f90a9

STACK_TEXT:  
fffff880`071dc170 fffffa80`065fe78e : 00000000`00000002 fffff880`04490658 fffff880`038a2000 fffff880`071dc250 : atipmdag+0x3740a9
fffff880`071dc178 00000000`00000002 : fffff880`04490658 fffff880`038a2000 fffff880`071dc250 fffff880`043f81d1 : 0xfffffa80`065fe78e
fffff880`071dc180 fffff880`04490658 : fffff880`038a2000 fffff880`071dc250 fffff880`043f81d1 00000000`00000027 : 0x2
fffff880`071dc188 fffff880`038a2000 : fffff880`071dc250 fffff880`043f81d1 00000000`00000027 fffff880`bebe0031 : atipmdag+0x40b658
fffff880`071dc190 fffff880`071dc250 : fffff880`043f81d1 00000000`00000027 fffff880`bebe0031 fffffa80`05e4a000 : 0xfffff880`038a2000
fffff880`071dc198 fffff880`043f81d1 : 00000000`00000027 fffff880`bebe0031 fffffa80`05e4a000 fffffa80`06dbd858 : 0xfffff880`071dc250
fffff880`071dc1a0 00000000`00000027 : fffff880`bebe0031 fffffa80`05e4a000 fffffa80`06dbd858 fffff880`071dc250 : atipmdag+0x3731d1
fffff880`071dc1a8 fffff880`bebe0031 : fffffa80`05e4a000 fffffa80`06dbd858 fffff880`071dc250 fffffa80`0769b400 : 0x27
fffff880`071dc1b0 fffffa80`05e4a000 : fffffa80`06dbd858 fffff880`071dc250 fffffa80`0769b400 00000000`00000000 : 0xfffff880`bebe0031
fffff880`071dc1b8 fffffa80`06dbd858 : fffff880`071dc250 fffffa80`0769b400 00000000`00000000 0000fc0d`00000000 : 0xfffffa80`05e4a000
fffff880`071dc1c0 fffff880`071dc250 : fffffa80`0769b400 00000000`00000000 0000fc0d`00000000 00000000`00000000 : 0xfffffa80`06dbd858
fffff880`071dc1c8 fffffa80`0769b400 : 00000000`00000000 0000fc0d`00000000 00000000`00000000 fc2d0000`043bf3f6 : 0xfffff880`071dc250
fffff880`071dc1d0 00000000`00000000 : 0000fc0d`00000000 00000000`00000000 fc2d0000`043bf3f6 fa80065f`f3d40081 : 0xfffffa80`0769b400


FOLLOWUP_IP: 
atipmdag+3740a9
fffff880`043f90a9 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 0xfffff880071db7a0 ; kb

FAILURE_BUCKET_ID:  X64_0x7E_atipmdag+3740a9

BUCKET_ID:  X64_0x7E_atipmdag+3740a9

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

Alright, I am fairly certain at this point you either have a bad/outdated graphics card or bad memory. Rarely do I see memory go bad in a laptop unless the memory has been replaced or added at one time or another. I am leaning toward your graphics card not being properly supported for Windows 7. Contact the laptop manufacturer and/or AMD and see if they are aware of any problems with your graphics card with Windows 7. It could be the graphics card is failing, as well, if it is known by both companies to work with Windows 7.

 

[Zeeky]

alight, i was pretty sure that was the case..

I'll attempt to contact acer/AMD about it (if i can find out how to contact them)

Thanks for all you're help tho