Windows 7 Massive BDSO 0x000000007e Problems

[Computergandalf2014]

Hi!

I have tryed everything now, i cant get rid of this problem since i installet windows 7 on my new samsung SSD.
My last system was windows xp on the same Hardware (exept the samsung ssd) an i never had so massive problems with BSOD.

The BSOD only happens , if i start up my pc after it was powerd off for a longer time. If i do so, the BSOD comes just bevore the Windows login comes.


i made it to let the pc create a minidump file and i debugget it.


Please can anyon halp me with reading this file:


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


Loading Dump File [C:\Windows\MEMORY.DMP]
Kernel Summary Dump File: Only kernel address space is available

Symbol search path is: srv*c:\symbols* Link Removed _NT_SYMBOL_PATH = symsrv*symsrv.dll*f:\localsymbols*http://msdl.microsoft.com/download/symbols
Executable search path is:
Windows 7 Kernel Version 7601 (Service Pack 1) MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 7601.18247.amd64fre.win7sp1_gdr.130828-1532
Machine Name:
Kernel base = 0xfffff800`02a5b000 PsLoadedModuleList = 0xfffff800`02c9e6d0
Debug session time: Sat Feb 1 11:58:12.062 2014 (UTC + 1:00)
System Uptime: 0 days 0:00:28.359
Loading Kernel Symbols
...............................................................
.................
Loading User Symbols

*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 7E, {ffffffffc0000005, fffff80002af6150, fffff880031b4f38, fffff880031b4790}

*** ERROR: Module load completed but symbols could not be loaded for atikmpag.sys
Probably caused by : atikmpag.sys ( atikmpag+2bf03 )

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

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

SYSTEM_THREAD_EXCEPTION_NOT_HANDLED (7e)
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.
Arguments:
Arg1: ffffffffc0000005, The exception code that was not handled
Arg2: fffff80002af6150, The address that the exception occurred at
Arg3: fffff880031b4f38, Exception Record Address
Arg4: fffff880031b4790, Context Record Address

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


EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - Die Anweisung in 0x%08lx verweist auf Speicher 0x%08lx. Der Vorgang %s konnte nicht im Speicher durchgef hrt werden.

FAULTING_IP:
nt!MiReplenishPageSlist+c0
fffff800`02af6150 f00fba6b1000 lock bts dword ptr [rbx+10h],0

EXCEPTION_RECORD: fffff880031b4f38 -- (.exr 0xfffff880031b4f38)
ExceptionAddress: fffff80002af6150 (nt!MiReplenishPageSlist+0x00000000000000c0)
ExceptionCode: c0000005 (Access violation)
ExceptionFlags: 00000000
NumberParameters: 2
Parameter[0]: 0000000000000000
Parameter[1]: ffffffffffffffff
Attempt to read from address ffffffffffffffff

CONTEXT: fffff880031b4790 -- (.cxr 0xfffff880031b4790)
rax=fffffa8005b96080 rbx=fffef28112c21800 rcx=0000058000000000
rdx=0000000000000047 rsi=0000000000000002 rdi=0000000000000005
rip=fffff80002af6150 rsp=fffff880031b5170 rbp=fffffa8005b99080
r8=fffff80002d0b500 r9=fffffa8006900000 r10=fffffa8006900de0
r11=fffff80002c4be80 r12=fffff80002d0b500 r13=2aaaaaaaaaaaaaab
r14=fdffffffffffffff r15=0000058000000000
iopl=0 nv up ei pl nz na pe nc
cs=0010 ss=0018 ds=002b es=002b fs=0053 gs=002b efl=00010202
nt!MiReplenishPageSlist+0xc0:
fffff800`02af6150 f00fba6b1000 lock bts dword ptr [rbx+10h],0 ds:002b:fffef281`12c21810=????????
Resetting default scope

DEFAULT_BUCKET_ID: WIN7_DRIVER_FAULT

PROCESS_NAME: System

CURRENT_IRQL: 2

ERROR_CODE: (NTSTATUS) 0xc0000005 - Die Anweisung in 0x%08lx verweist auf Speicher 0x%08lx. Der Vorgang %s konnte nicht im Speicher durchgef hrt werden.

EXCEPTION_PARAMETER1: 0000000000000000

EXCEPTION_PARAMETER2: ffffffffffffffff

READ_ADDRESS: ffffffffffffffff

FOLLOWUP_IP:
atikmpag+2bf03
fffff880`0182bf03 33d2 xor edx,edx

BUGCHECK_STR: 0x7E

LOCK_ADDRESS: fffff80002cd4be0 -- (!locks fffff80002cd4be0)

Resource @ nt!PiEngineLock (0xfffff80002cd4be0) Exclusively owned
Threads: fffffa8006a48040-01<*>
1 total locks, 1 locks currently held

PNP_TRIAGE:
Lock address : 0xfffff80002cd4be0
Thread Count : 1
Thread address: 0xfffffa8006a48040
Thread wait : 0x717

LAST_CONTROL_TRANSFER: from fffff80002e412b4 to fffff80002ad0bc0

STACK_TEXT:
fffff880`031b5170 fffff800`02af490f : fffffa80`06900dc0 00000000`00000058 fffffa80`05ba8080 00000000`00000058 : nt!MiReplenishPageSlist+0xc0
fffff880`031b51e0 fffff800`02a904c0 : fa80071b`db6004c0 00000000`00000000 00000000`000000b0 00000000`00000000 : nt!MiRemoveAnyPage+0x24f
fffff880`031b5300 fffff800`02e96f6f : fffffa80`077f4010 fffffa80`00000000 fffffa80`06a48040 fffff8a0`005f2400 : nt!MiPfPutPagesInTransition+0x7c7
fffff880`031b5470 fffff800`02eac093 : fffff8a0`005f2400 00000000`00000000 fffffa80`077f4010 fffff880`031b5878 : nt!MiPrefetchControlArea+0x6f
fffff880`031b54c0 fffff800`02eac40c : ffffffff`80000074 fffffa80`08000000 00000000`00140000 ffffffff`8000006c : nt!MmCheckSystemImage+0xe3
fffff880`031b55f0 fffff800`02eac627 : ffffffff`80000074 fffff800`00000001 00000000`00000000 00000000`00000000 : nt!MiCreateSectionForDriver+0xcc
fffff880`031b56a0 fffff800`02eb820d : 00000000`00000000 00000000`00000000 fffffa80`06a48040 00000000`00000000 : nt!MiObtainSectionForDriver+0xd7
fffff880`031b5700 fffff800`02ebaead : fffff880`031b5878 00000000`00000000 00000000`00000000 00000000`00000000 : nt!MmLoadSystemImage+0x23d
fffff880`031b5820 fffff800`02ebb865 : fffff800`024040c4 00000000`00000000 fffff880`0183583c fffffa80`06a48040 : nt!IopLoadDriver+0x44d
fffff880`031b5af0 fffff800`02f4f70b : 00000000`00000000 ffffffff`800000fc 00000000`00000000 fffff8a0`005e0a70 : nt!IopLoadUnloadDriver+0x55
fffff880`031b5b30 fffff800`02acfe53 : fffffa80`06a48040 00000000`0000000a fffff880`031b5bf0 fffff880`031b5bf0 : nt!NtLoadDriver+0x189
fffff880`031b5be0 fffff800`02acc410 : fffff880`0182bf03 00000000`000000fc fffffa80`06a39040 fffff8a0`00001a50 : nt!KiSystemServiceCopyEnd+0x13
fffff880`031b5d78 fffff880`0182bf03 : 00000000`000000fc fffffa80`06a39040 fffff8a0`00001a50 00000000`000000fc : nt!KiServiceLinkage
fffff880`031b5d80 fffff880`0182c085 : fffffa80`077d7e70 fffff880`031b5ee0 fffff800`02c4be80 fffffa80`077e0000 : atikmpag+0x2bf03
fffff880`031b5de0 fffff880`018594e4 : fffffa80`077d7e70 fffffa80`077e0000 fffffa80`077e0000 ffffffff`800000fc : atikmpag+0x2c085
fffff880`031b5fb0 fffff800`02ebb467 : fffffa80`077d7e70 00000000`0000000d 00000000`00000000 00000000`000007ff : atikmpag+0x594e4
fffff880`031b6280 fffff800`02f4f190 : 00000000`00000001 00000000`00000000 fffff880`031b6828 ffffffff`80000108 : nt!IopLoadDriver+0xa07
fffff880`031b6550 fffff800`02d8b76e : 00000000`00000001 00000000`00000000 fffff8a0`005c97d0 00000000`00000000 : nt!PipCallDriverAddDeviceQueryRoutine+0x390
fffff880`031b6650 fffff800`02d8b47e : ffffffff`80000118 00000000`00000000 fffff880`031b6860 fffff880`031b6828 : nt!RtlpCallQueryRegistryRoutine+0x106
fffff880`031b66d0 fffff800`02ebe73c : fffffa80`06a0f6e0 00000000`00000000 00000000`c0000034 fffff880`031b6828 : nt!RtlQueryRegistryValues+0x17e
fffff880`031b67a0 fffff800`02ebfed2 : fffffa80`06a00310 fffffa80`06a0f6e0 00000000`00000002 fffff8a0`0000004c : nt!PipCallDriverAddDevice+0x45c
fffff880`031b6950 fffff800`02ec036c : fffff800`02cd2500 00000000`00000000 00000000`00000000 00000000`00000000 : nt!PipProcessDevNodeTree+0x2b2
fffff880`031b6bc0 fffff800`02bd3802 : 00000001`00000003 00000000`00000000 00000000`32706e50 00000000`00000084 : nt!PiProcessStartSystemDevices+0x7c
fffff880`031b6c10 fffff800`02ada261 : fffff800`02bd3500 fffff800`02dc7101 fffffa80`06a48000 00000000`00000000 : nt!PnpDeviceActionWorker+0x302
fffff880`031b6cb0 fffff800`02d6d2ea : 00000000`00000000 fffffa80`06a48040 00000000`00000080 fffffa80`06a39040 : nt!ExpWorkerThread+0x111
fffff880`031b6d40 fffff800`02ac18e6 : fffff880`02f64180 fffffa80`06a48040 fffff880`02f6efc0 00000000`00000000 : nt!PspSystemThreadStartup+0x5a
fffff880`031b6d80 00000000`00000000 : fffff880`031b7000 fffff880`031b1000 fffff880`031b3d80 00000000`00000000 : nt!KxStartSystemThread+0x16


SYMBOL_STACK_INDEX: d

SYMBOL_NAME: atikmpag+2bf03

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: atikmpag

IMAGE_NAME: atikmpag.sys

DEBUG_FLR_IMAGE_TIMESTAMP: 517f30ef

STACK_COMMAND: .cxr 0xfffff880031b4790 ; kb

FAILURE_BUCKET_ID: X64_0x7E_atikmpag+2bf03

BUCKET_ID: X64_0x7E_atikmpag+2bf03

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

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

SYSTEM_THREAD_EXCEPTION_NOT_HANDLED (7e)
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.
Arguments:
Arg1: ffffffffc0000005, The exception code that was not handled
Arg2: fffff80002af6150, The address that the exception occurred at
Arg3: fffff880031b4f38, Exception Record Address
Arg4: fffff880031b4790, Context Record Address

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


EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - Die Anweisung in 0x%08lx verweist auf Speicher 0x%08lx. Der Vorgang %s konnte nicht im Speicher durchgef hrt werden.

FAULTING_IP:
nt!MiReplenishPageSlist+c0
fffff800`02af6150 f00fba6b1000 lock bts dword ptr [rbx+10h],0

EXCEPTION_RECORD: fffff880031b4f38 -- (.exr 0xfffff880031b4f38)
ExceptionAddress: fffff80002af6150 (nt!MiReplenishPageSlist+0x00000000000000c0)
ExceptionCode: c0000005 (Access violation)
ExceptionFlags: 00000000
NumberParameters: 2
Parameter[0]: 0000000000000000
Parameter[1]: ffffffffffffffff
Attempt to read from address ffffffffffffffff

CONTEXT: fffff880031b4790 -- (.cxr 0xfffff880031b4790)
rax=fffffa8005b96080 rbx=fffef28112c21800 rcx=0000058000000000
rdx=0000000000000047 rsi=0000000000000002 rdi=0000000000000005
rip=fffff80002af6150 rsp=fffff880031b5170 rbp=fffffa8005b99080
r8=fffff80002d0b500 r9=fffffa8006900000 r10=fffffa8006900de0
r11=fffff80002c4be80 r12=fffff80002d0b500 r13=2aaaaaaaaaaaaaab
r14=fdffffffffffffff r15=0000058000000000
iopl=0 nv up ei pl nz na pe nc
cs=0010 ss=0018 ds=002b es=002b fs=0053 gs=002b efl=00010202
nt!MiReplenishPageSlist+0xc0:
fffff800`02af6150 f00fba6b1000 lock bts dword ptr [rbx+10h],0 ds:002b:fffef281`12c21810=????????
Resetting default scope

DEFAULT_BUCKET_ID: WIN7_DRIVER_FAULT

PROCESS_NAME: System

CURRENT_IRQL: 2

ERROR_CODE: (NTSTATUS) 0xc0000005 - Die Anweisung in 0x%08lx verweist auf Speicher 0x%08lx. Der Vorgang %s konnte nicht im Speicher durchgef hrt werden.

EXCEPTION_PARAMETER1: 0000000000000000

EXCEPTION_PARAMETER2: ffffffffffffffff

READ_ADDRESS: ffffffffffffffff

FOLLOWUP_IP:
atikmpag+2bf03
fffff880`0182bf03 33d2 xor edx,edx

BUGCHECK_STR: 0x7E

LOCK_ADDRESS: fffff80002cd4be0 -- (!locks fffff80002cd4be0)

Resource @ nt!PiEngineLock (0xfffff80002cd4be0) Exclusively owned
Threads: fffffa8006a48040-01<*>
1 total locks, 1 locks currently held

PNP_TRIAGE:
Lock address : 0xfffff80002cd4be0
Thread Count : 1
Thread address: 0xfffffa8006a48040
Thread wait : 0x717

LAST_CONTROL_TRANSFER: from fffff80002e412b4 to fffff80002ad0bc0

STACK_TEXT:
fffff880`031b5170 fffff800`02af490f : fffffa80`06900dc0 00000000`00000058 fffffa80`05ba8080 00000000`00000058 : nt!MiReplenishPageSlist+0xc0
fffff880`031b51e0 fffff800`02a904c0 : fa80071b`db6004c0 00000000`00000000 00000000`000000b0 00000000`00000000 : nt!MiRemoveAnyPage+0x24f
fffff880`031b5300 fffff800`02e96f6f : fffffa80`077f4010 fffffa80`00000000 fffffa80`06a48040 fffff8a0`005f2400 : nt!MiPfPutPagesInTransition+0x7c7
fffff880`031b5470 fffff800`02eac093 : fffff8a0`005f2400 00000000`00000000 fffffa80`077f4010 fffff880`031b5878 : nt!MiPrefetchControlArea+0x6f
fffff880`031b54c0 fffff800`02eac40c : ffffffff`80000074 fffffa80`08000000 00000000`00140000 ffffffff`8000006c : nt!MmCheckSystemImage+0xe3
fffff880`031b55f0 fffff800`02eac627 : ffffffff`80000074 fffff800`00000001 00000000`00000000 00000000`00000000 : nt!MiCreateSectionForDriver+0xcc
fffff880`031b56a0 fffff800`02eb820d : 00000000`00000000 00000000`00000000 fffffa80`06a48040 00000000`00000000 : nt!MiObtainSectionForDriver+0xd7
fffff880`031b5700 fffff800`02ebaead : fffff880`031b5878 00000000`00000000 00000000`00000000 00000000`00000000 : nt!MmLoadSystemImage+0x23d
fffff880`031b5820 fffff800`02ebb865 : fffff800`024040c4 00000000`00000000 fffff880`0183583c fffffa80`06a48040 : nt!IopLoadDriver+0x44d
fffff880`031b5af0 fffff800`02f4f70b : 00000000`00000000 ffffffff`800000fc 00000000`00000000 fffff8a0`005e0a70 : nt!IopLoadUnloadDriver+0x55
fffff880`031b5b30 fffff800`02acfe53 : fffffa80`06a48040 00000000`0000000a fffff880`031b5bf0 fffff880`031b5bf0 : nt!NtLoadDriver+0x189
fffff880`031b5be0 fffff800`02acc410 : fffff880`0182bf03 00000000`000000fc fffffa80`06a39040 fffff8a0`00001a50 : nt!KiSystemServiceCopyEnd+0x13
fffff880`031b5d78 fffff880`0182bf03 : 00000000`000000fc fffffa80`06a39040 fffff8a0`00001a50 00000000`000000fc : nt!KiServiceLinkage
fffff880`031b5d80 fffff880`0182c085 : fffffa80`077d7e70 fffff880`031b5ee0 fffff800`02c4be80 fffffa80`077e0000 : atikmpag+0x2bf03
fffff880`031b5de0 fffff880`018594e4 : fffffa80`077d7e70 fffffa80`077e0000 fffffa80`077e0000 ffffffff`800000fc : atikmpag+0x2c085
fffff880`031b5fb0 fffff800`02ebb467 : fffffa80`077d7e70 00000000`0000000d 00000000`00000000 00000000`000007ff : atikmpag+0x594e4
fffff880`031b6280 fffff800`02f4f190 : 00000000`00000001 00000000`00000000 fffff880`031b6828 ffffffff`80000108 : nt!IopLoadDriver+0xa07
fffff880`031b6550 fffff800`02d8b76e : 00000000`00000001 00000000`00000000 fffff8a0`005c97d0 00000000`00000000 : nt!PipCallDriverAddDeviceQueryRoutine+0x390
fffff880`031b6650 fffff800`02d8b47e : ffffffff`80000118 00000000`00000000 fffff880`031b6860 fffff880`031b6828 : nt!RtlpCallQueryRegistryRoutine+0x106
fffff880`031b66d0 fffff800`02ebe73c : fffffa80`06a0f6e0 00000000`00000000 00000000`c0000034 fffff880`031b6828 : nt!RtlQueryRegistryValues+0x17e
fffff880`031b67a0 fffff800`02ebfed2 : fffffa80`06a00310 fffffa80`06a0f6e0 00000000`00000002 fffff8a0`0000004c : nt!PipCallDriverAddDevice+0x45c
fffff880`031b6950 fffff800`02ec036c : fffff800`02cd2500 00000000`00000000 00000000`00000000 00000000`00000000 : nt!PipProcessDevNodeTree+0x2b2
fffff880`031b6bc0 fffff800`02bd3802 : 00000001`00000003 00000000`00000000 00000000`32706e50 00000000`00000084 : nt!PiProcessStartSystemDevices+0x7c
fffff880`031b6c10 fffff800`02ada261 : fffff800`02bd3500 fffff800`02dc7101 fffffa80`06a48000 00000000`00000000 : nt!PnpDeviceActionWorker+0x302
fffff880`031b6cb0 fffff800`02d6d2ea : 00000000`00000000 fffffa80`06a48040 00000000`00000080 fffffa80`06a39040 : nt!ExpWorkerThread+0x111
fffff880`031b6d40 fffff800`02ac18e6 : fffff880`02f64180 fffffa80`06a48040 fffff880`02f6efc0 00000000`00000000 : nt!PspSystemThreadStartup+0x5a
fffff880`031b6d80 00000000`00000000 : fffff880`031b7000 fffff880`031b1000 fffff880`031b3d80 00000000`00000000 : nt!KxStartSystemThread+0x16


SYMBOL_STACK_INDEX: d

SYMBOL_NAME: atikmpag+2bf03

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: atikmpag

IMAGE_NAME: atikmpag.sys

DEBUG_FLR_IMAGE_TIMESTAMP: 517f30ef

STACK_COMMAND: .cxr 0xfffff880031b4790 ; kb

FAILURE_BUCKET_ID: X64_0x7E_atikmpag+2bf03

BUCKET_ID: X64_0x7E_atikmpag+2bf03

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

Do i have to throu my Graphiccard out of the window and drive over it?

But why does it work with windows XP?
I dont really think its a Graphiccard hardware issue but i dont have a2nd one to test it. (not now)

 

[Computergandalf2014]

I´m sorry. This is my PC:

Komponente Details Teilbewertung Gesamtbewertung
Prozessor AMD Phenom(tm) II X4 945 Processor 7,3
7,3
Ergibt sich aus der niedrigsten Teilbewertung
Arbeitsspeicher (RAM) 8,00 GB 7,5
Grafik ATI Radeon HD 4800 Series 7,6
Grafik (Spiele) 4862 MB insgesamt verfügbarer Grafikspeicher 7,6
Primäre Festplatte 139GB frei (233GB gesamt) 7,7
Windows 7 Home Premium

System
Hersteller Gigabyte Technology Co., Ltd.
Modell GA-MA790XT-UD4P
Gesamter Systemspeicher 8,00 GB RAM
Systemtyp 64 Bit-Betriebssystem
Anzahl der Prozessorkerne 4
Speicher
Gesamtgröße der Festplatte(n) 531 GB
Datenträgerpartition (C 139 GB frei (233 GB gesamt)
Datenträgerpartition (D 33 GB frei (298 GB gesamt)
Medienlaufwerk (E CD/DVD
Medienlaufwerk (F CD/DVD
Grafik
Grafikkartentyp ATI Radeon HD 4800 Series
Insgesamt verfügbarer Grafikspeicher 4862 MB
Dedizierter Grafikspeicher 1024 MB
Dedizierter Systemarbeitsspeicher 0 MB
Gemeinsam genutzter Systemspeicher 3838 MB
Grafikkarten-Treiberversion 8.970.100.1100
Auflösung des primären Monitors 1440x900
DirectX-Version DirectX 10
Netzwerk
Netzwerkadapter Realtek RTL8168C(P)/8111C(P)-Familie-PCI-E-Gigabit-Ethernet-NIC (NDIS 6.20)

 

[kemical]

Hi,
I moved your thread to the correct section (probably why i missed it).

I really need to see your actual dmp files in order to debug. Please read the thread found here and post the results:
Link Removed