Inlägg

Det blir denna...
Blir det bra tro?
https://www.inet.se/kundvagn/visa/12394321

https://www.inet.se/kundvagn/bild/12394321

Dator 21k
Ska mest surfa, Photoshop och lagra bilder. Snabbhet är prio då den gamla är seg.

https://www.inet.se/kundvagn/bild/12391306

plus ett EVGA GeForce GTX 1060 6GB SC Gaming

Vad tror ni om denna?

https://www.inet.se/datorbygge/bild/b1070866/bildbehandling-budg...

https://www.inet.se/kundvagn/bild/12374882

@IKEA Billy Bokhylla:
Det är för mitt privata bruk, hobby.
Photoshop

@anon99339: 32" går bra också, men inte större.

Lägger den till minnet!

Tänkte bygga en ny dator för bildbehandling.

Budget:
15000kr

Önskemål:
Snabb lagring: Corsair Force MP510 960GB eller liknande.
Stöd för Thunderbolt 3 så jag kan koppla en Samsung X5 Extern Portabel SSD 1TB Thunderbolt 3

Krav:
Datorn ska klara av bildbehandling av foto.
Ny bildskärm behöver jag gärna 24", som fungerar bra med bildbehandling.
Windows 10

Övrigt:
Ingen speldator!

Tack på förhand!

@N!klas:
Jag har installerat om drivrutinerna till nyare.

@dabman:
https://ibb.co/WxSKvvy

Done!

@N!klas:
Men, men jag har ju ASUS
https://www.inet.se/produkt/5411271/asus-strix-r9-285-directcu-ii-oc-2gd5

Hade innan två Gigabyte GeForce GTX 460 1024MB OC i SLI

Fick lite inblick i Blue screen of death....
Varje rad nedan är en krasch de senaste 12 månaderna, nyast först.

The problem seems to be caused by the following file: dxgmms1.sys
SYSTEM_THREAD_EXCEPTION_NOT_HANDLED

The problem seems to be caused by the following file: ntoskrnl.exe
PAGE_FAULT_IN_NONPAGED_AREA

The problem seems to be caused by the following file: USBPORT.SYS
BUGCODE_USB_DRIVER

The problem seems to be caused by the following file: atikmdag.sys
SYSTEM_SERVICE_EXCEPTION

The problem seems to be caused by the following file: ntoskrnl.exe
SYSTEM_SERVICE_EXCEPTION

The problem seems to be caused by the following file: atikmdag.sys
PAGE_FAULT_IN_NONPAGED_AREA

The problem seems to be caused by the following file: atikmdag.sys
SYSTEM_THREAD_EXCEPTION_NOT_HANDLED

The problem seems to be caused by the following file: nvmf6264.sys
DRIVER_IRQL_NOT_LESS_OR_EQUAL

The problem seems to be caused by the following file: ntoskrnl.exe
SYSTEM_THREAD_EXCEPTION_NOT_HANDLED

The problem seems to be caused by the following file: atikmdag.sys
KMODE_EXCEPTION_NOT_HANDLED

The problem seems to be caused by the following file: ntoskrnl.exe
PFN_LIST_CORRUPT

The problem seems to be caused by the following file: ntoskrnl.exe
BAD_POOL_CALLER

The problem seems to be caused by the following file: ntoskrnl.exe
IRQL_NOT_LESS_OR_EQUAL

The problem seems to be caused by the following file: atikmdag.sys
IRQL_NOT_LESS_OR_EQUAL

The problem seems to be caused by the following file: dxgmms1.sys
BAD_POOL_CALLER

The problem seems to be caused by the following file: afd.sys
DRIVER_IRQL_NOT_LESS_OR_EQUAL

The problem seems to be caused by the following file: tcpip.sys
PAGE_FAULT_IN_NONPAGED_AREA

The problem seems to be caused by the following file: atikmdag.sys
DRIVER_IRQL_NOT_LESS_OR_EQUAL

The problem seems to be caused by the following file: atikmdag.sys
DRIVER_IRQL_NOT_LESS_OR_EQUAL

The problem seems to be caused by the following file: usbprint.sys
UNEXPECTED_KERNEL_MODE_TRAP

The problem seems to be caused by the following file: fltmgr.sys
IRQL_NOT_LESS_OR_EQUAL

The problem seems to be caused by the following file: ntoskrnl.exe
PAGE_FAULT_IN_NONPAGED_AREA

The problem seems to be caused by the following file: atikmdag.sys
DRIVER_IRQL_NOT_LESS_OR_EQUAL

The problem seems to be caused by the following file: atikmdag.sys
SYSTEM_THREAD_EXCEPTION_NOT_HANDLED

The problem seems to be caused by the following file: atikmdag.sys
DRIVER_IRQL_NOT_LESS_OR_EQUAL

The problem seems to be caused by the following file: hal.dll
DRIVER_OVERRAN_STACK_BUFFER

The problem seems to be caused by the following file: dxgmms1.sys
DRIVER_IRQL_NOT_LESS_OR_EQUAL

The problem seems to be caused by the following file: atikmpag.sys
KMODE_EXCEPTION_NOT_HANDLED

The problem seems to be caused by the following file: Wdf01000.sys
DRIVER_IRQL_NOT_LESS_OR_EQUAL

The problem seems to be caused by the following file: watchdog.sys

The problem seems to be caused by the following file: atikmdag.sys
SYSTEM_THREAD_EXCEPTION_NOT_HANDLED

The problem seems to be caused by the following file: ntoskrnl.exe
DRIVER_IRQL_NOT_LESS_OR_EQUAL

The problem seems to be caused by the following file: dxgmms1.sys
ATTEMPTED_EXECUTE_OF_NOEXECUTE_MEMORY

The problem seems to be caused by the following file: dxgmms1.sys
DRIVER_IRQL_NOT_LESS_OR_EQUAL

Blue screen prog:
https://ibb.co/k14gmN1

@N!klas:
Samma fel?
https://ibb.co/LrGkDSm

@N!klas:
Scannow hittade inga fel.

DISM:
https://ibb.co/0yGKNpc

2019-03-03 14:44:08, Info DISM PID=6840 Scratch directory set to 'C:\Users\MITTNAMN~1\AppData\Local\Temp\'. - CDISMManager::put_ScratchDir
2019-03-03 14:44:08, Info DISM PID=6840 Successfully loaded the ImageSession at "C:\Windows\System32\Dism" - CDISMManager::LoadImageSession
2019-03-03 14:44:08, Info DISM DISM Provider Store: PID=6840 Found and Initialized the DISM Logger. - CDISMProviderStore::Internal_InitializeLogger
2019-03-03 14:44:08, Info DISM DISM Provider Store: PID=6840 Failed to get and initialize the PE Provider. Continuing by assuming that it is not a WinPE image. - CDISMProviderStore::Final_OnConnect
2019-03-03 14:44:08, Info DISM DISM Provider Store: PID=6840 Finished initializing the Provider Map. - CDISMProviderStore::Final_OnConnect
2019-03-03 14:44:08, Info DISM DISM Provider Store: PID=6840 Getting Provider DISMLogger - CDISMProviderStore::GetProvider
2019-03-03 14:44:08, Info DISM DISM Provider Store: PID=6840 Provider has previously been initialized. Returning the existing instance. - CDISMProviderStore::Internal_GetProvider
2019-03-03 14:44:08, Info DISM DISM Provider Store: PID=6840 Getting Provider DISMLogger - CDISMProviderStore::GetProvider
2019-03-03 14:44:08, Info DISM DISM Provider Store: PID=6840 Provider has previously been initialized. Returning the existing instance. - CDISMProviderStore::Internal_GetProvider
2019-03-03 14:44:08, Info DISM DISM Manager: PID=6840 Successfully created the local image session and provider store. - CDISMManager::CreateLocalImageSession
2019-03-03 14:44:08, Info DISM DISM Provider Store: PID=6840 Getting Provider DISMLogger - CDISMProviderStore::GetProvider
2019-03-03 14:44:08, Info DISM DISM Provider Store: PID=6840 Provider has previously been initialized. Returning the existing instance. - CDISMProviderStore::Internal_GetProvider
2019-03-03 14:44:08, Info DISM DISM.EXE:
2019-03-03 14:44:08, Info DISM DISM.EXE: <----- Starting Dism.exe session ----->
2019-03-03 14:44:08, Info DISM DISM.EXE:
2019-03-03 14:44:08, Info DISM DISM.EXE: Host machine information: OS Version=6.1.7601, Running architecture=amd64, Number of processors=4
2019-03-03 14:44:08, Info DISM DISM.EXE: Executing command line: DISM /Online/Cleanup-Image/RestoreHealth
2019-03-03 14:44:08, Info DISM DISM Provider Store: PID=6840 Getting the collection of providers from a local provider store type. - CDISMProviderStore::GetProviderCollection
2019-03-03 14:44:08, Info DISM DISM Provider Store: PID=6840 Provider has not previously been encountered. Attempting to initialize the provider. - CDISMProviderStore::Internal_GetProvider
2019-03-03 14:44:08, Info DISM DISM Provider Store: PID=6840 Loading Provider from location C:\Windows\System32\Dism\WimProvider.dll - CDISMProviderStore::Internal_GetProvider
2019-03-03 14:44:08, Info DISM DISM Provider Store: PID=6840 Connecting to the provider located at C:\Windows\System32\Dism\WimProvider.dll. - CDISMProviderStore::Internal_LoadProvider
2019-03-03 14:44:08, Info DISM DISM Provider Store: PID=6840 Provider has not previously been encountered. Attempting to initialize the provider. - CDISMProviderStore::Internal_GetProvider
2019-03-03 14:44:08, Info DISM DISM Provider Store: PID=6840 Loading Provider from location C:\Windows\System32\Dism\FolderProvider.dll - CDISMProviderStore::Internal_GetProvider
2019-03-03 14:44:08, Info DISM DISM Provider Store: PID=6840 Connecting to the provider located at C:\Windows\System32\Dism\FolderProvider.dll. - CDISMProviderStore::Internal_LoadProvider
2019-03-03 14:44:08, Info DISM DISM Provider Store: PID=6840 Provider has not previously been encountered. Attempting to initialize the provider. - CDISMProviderStore::Internal_GetProvider
2019-03-03 14:44:08, Info DISM DISM Provider Store: PID=6840 Loading Provider from location C:\Windows\System32\Dism\CompatProvider.dll - CDISMProviderStore::Internal_GetProvider
2019-03-03 14:44:08, Info DISM DISM Provider Store: PID=6840 Connecting to the provider located at C:\Windows\System32\Dism\CompatProvider.dll. - CDISMProviderStore::Internal_LoadProvider
2019-03-03 14:44:08, Info DISM DISM.EXE: Got the collection of providers. Now enumerating them to build the command table.
2019-03-03 14:44:08, Info DISM DISM.EXE: Attempting to add the commands from provider: WimManager
2019-03-03 14:44:08, Info DISM DISM.EXE: Succesfully registered commands for the provider: WimManager.
2019-03-03 14:44:08, Info DISM DISM.EXE: Attempting to add the commands from provider: FolderManager
2019-03-03 14:44:08, Info DISM DISM.EXE: Attempting to add the commands from provider: DISM Log Provider
2019-03-03 14:44:08, Info DISM DISM.EXE: Attempting to add the commands from provider: Compatibility Manager
2019-03-03 14:44:08, Info DISM DISM.EXE: Succesfully registered commands for the provider: Compatibility Manager.
2019-03-03 14:44:08, Error DISM DISM.EXE: No providers were found that support the command(online/cleanup-image/restorehealth). HRESULT=0
2019-03-03 14:44:08, Info DISM DISM.EXE: Image session has been closed. Reboot required=no.
2019-03-03 14:44:08, Info DISM DISM.EXE:
2019-03-03 14:44:08, Info DISM DISM.EXE: <----- Ending Dism.exe session ----->
2019-03-03 14:44:08, Info DISM DISM.EXE:
2019-03-03 14:44:08, Info DISM DISM Image Session: PID=6840 Disconnecting the provider store - CDISMImageSession::Final_OnDisconnect
2019-03-03 14:44:08, Info DISM DISM Provider Store: PID=6840 Disconnecting Provider: WimManager - CDISMProviderStore::Internal_DisconnectProvider
2019-03-03 14:44:08, Info DISM DISM Provider Store: PID=6840 Disconnecting Provider: FolderManager - CDISMProviderStore::Internal_DisconnectProvider
2019-03-03 14:44:08, Info DISM DISM Provider Store: PID=6840 Found the OSServices. Waiting to finalize it until all other providers are unloaded. - CDISMProviderStore::Final_OnDisconnect
2019-03-03 14:44:08, Info DISM DISM Provider Store: PID=6840 Disconnecting Provider: Compatibility Manager - CDISMProviderStore::Internal_DisconnectProvider
2019-03-03 14:44:08, Info DISM DISM Provider Store: PID=6840 Releasing the local reference to DISMLogger. Stop logging. - CDISMProviderStore::Internal_DisconnectProvider

@N!klas:
"Datorn har startats om utan att ha stängts av ordentligt först. Det här felet kan orsakas om datorn har slutat svara, om den har crashat eller om strömförsörjningen oväntat bryts."

- System

- Provider

[ Name] Microsoft-Windows-Kernel-Power
[ Guid] {331C3B3A-2005-44C2-AC5E-77220C37D6B4}

EventID 41

Version 2

Level 1

Task 63

Opcode 0

Keywords 0x8000000000000002

- TimeCreated

[ SystemTime] 2019-03-02T20:06:37.098800000Z

EventRecordID 507370

Correlation

- Execution

[ ProcessID] 4
[ ThreadID] 8

Channel System

Computer Pentagon

- Security

[ UserID] S-1-5-18

- EventData

BugcheckCode 126
BugcheckParameter1 0xffffffffc0000005
BugcheckParameter2 0xfffff88004b90bff
BugcheckParameter3 0xfffff880033ff358
BugcheckParameter4 0xfffff880033febc0
SleepInProgress false
PowerButtonTimestamp 0

https://ibb.co/djjf5sZ

Nu krasade datorn igen och jag hittade lite om det i loggboken.

@TiasE:
Så nu har jag kört det och hade inga fel. Tog typ 60min

@SAFA:
Tack, då väntar jag tills jag känner att det behövs och då blir det en helt ny.

@N!klas:
Denna typ av kritisk fel verkar vara vanlig...
https://ibb.co/gvqMDr3
https://ibb.co/HqjcGqB

@N!klas:
Bild på log
Vad jag letar jag efter?