BSOD || machine check exception

[salman15]

Ik heb vorige maand een nieuwe pc gekocht en gister toen ik photoshop wou afsluiten bleef mijn pc hangen en kreeg ik plotseling een BSOD met de melding machine check exception. Na veel trail en error ben ik nu bij het punt dat als ik via de bios alleen 2 cpu cores aanzet de pc gewoon werkt, maar als ik er 3 doe de pc vast blijft hangen bij het opstarten en bij 4 ik weer de error krijg.

Het probleem is nog steeds niet vast te stellen vind ik, omdat er te veel factoren mee spelen.
...

CPU temp is 37
MB temp is 40

MB: msi z270 M3
Processor: I5 7600K
Ram:corsair ddr4 vengeance lpx 2x8gb 3000 c15
PS: 700ww
GC: GTX 1070 Jetstream (factory OC)
...

Ik heb geprobeerd

Met 1 geheugen alle slots te testen,

Alle componenten verwijderd,

Bios te updaten

Bios te resetten naar default settings

Volts op de cpu te verhogen en dan 1 core en daarna 2 cores te activeren (zelfde resultaten)

Windows herinstallatie

Ram getest en kreeg een goede resultaat.

alle hdds/ssds verwijderd (heb geen cd/dvd)

fast boost uit/aan gezet

Ik ben nu radeloos en weet niet wat ik moet doen

http://www.tomshardware.c...hine-check-exception.html

...

[Anoniem: 58485]

Doe eens een memtest als eerst. Het lijkt erop alsof photoshop iets weg wil schrijven op waarop het mislukt. Kapot geheugen of geheugen dat fouten genereert kan de boosdoener zijn. Een core meer of minder uitschakelen is de oplossing niet.

[Anoniem: 263284]

Welke voeding gebruik je? Merk,type?
Cpu socket gecontroleerd op verbogen pinnetjes?

[ Voor 40% gewijzigd door Anoniem: 263284 op 11-05-2017 05:31 ]

[salman15]

@Anoniem: 58485 bedankt voor je reactie de memtest86 blijft hangen op 50% bij test 6 (block move, 64-byte blocks)

[McFastFood]

Krijg je ook errors met Memtest of freezt Memtest gewoon?
Als ik het zo hoor lijkt het me eerder een CPU/mobo probleem.

[salman15]

@Anoniem: 263284 bedankt voor de reactie,

Mijn psu is de enermax maxpro 700w

[salman15]

@McFastFood ik heb het met 2 verschillende rams getest en stap 6 schijnt de enige stap te zijn met dit probleem

@McFastFood Top, ik zal het voortaan zo aanpakken. Wat ik bedoel met stap 6 is; De memtest heeft 13 stappen en bij stap 6 en alleen stap 6 blijft het hangen bij 0%. Dus het begint nog geen eens. Ik heb er voor gekozen om alle andere testen uit te voeren behalve stap 6 en dat ging vlekken loos, maar zodra ik stap 6 gezamenlijk of alleen uitvoer blijft het resultaat hetzelfde. Er gebeurt niks memtest loopt vast en af en toe een reboot.

[ Voor 66% gewijzigd door salman15 op 11-05-2017 16:01 ]

[McFastFood]

salman15 schreef op donderdag 11 mei 2017 @ 15:53:
@McFastFood ik heb het met 2 verschillende rams getest en stap 6 schijnt de enige stap te zijn met dit probleem

Ik snap je eerlijk gezegd niet helemaal.
Wat bedoel je met stap 6?
Daarnaast vroeg ik of je errors kreeg met Memtest of dat het beeld bij 50% gewoon 'vastliep'

Tip: Post meerdere reacties in 1 post en bijv. niet 4 posts kort achter elkaar dat is wat overzichtelijker. Daarom staat er ook 'Je hebt als laatste gereageerd in dit topic. Wil je wat toevoegen, wijzig dan bij voorkeur je laatste reactie.' Als je als laatste hebt gereageerd

[ Voor 14% gewijzigd door McFastFood op 11-05-2017 15:59 ]

[Anoniem: 58485]

salman15 schreef op donderdag 11 mei 2017 @ 11:14:
@Anoniem: 58485 bedankt voor je reactie de memtest86 blijft hangen op 50% bij test 6 (block move, 64-byte blocks)

Welke memtest, die in windows?

[salman15]

Anoniem: 58485 schreef op donderdag 11 mei 2017 @ 17:48:
[...]


Welke memtest, die in windows?

@Anoniem: 58485 Memtest86, via een bootable usb

[Anoniem: 58485]

salman15 schreef op donderdag 11 mei 2017 @ 19:39:
[...]


@Anoniem: 58485 Memtest86, via een bootable usb

Gebruik je SMT als je deze test uitvoert? SMT stopt bij mij ook halverwege terwijl het geheugen niet defect is. Als je een single-thread test doet zou die wel meerdere passes moeten maken.

Maar als ie verder geen errors geeft en ineens hangt op exact hetzelfde stuk dan kan je er denk ik vanuit gaan dat je geheugen verder goed zit. Heb je geen andere OC toegepast op je systeem? Zijn je drivers up to date? Wat staat er in je windows error logs? Wat staat er in de logs van je disks ofzo? Mischien heb je een harde schijf / SSD die mogelijk faalt.

[salman15]

@Anoniem: 58485
SMT? Sorry maar ik weet niet wat dat is.

Het gekke is dat ik nooit mijn pc heb geoverclocked en heb all mijn drivers geupdate. Ik heb het probleem op 2 SSD's 1 oud en 1 net een maand oud

Windows dump file van mijn meest recente versie van Windows ( ik heb windows op een nieuwe SSD geinstalleerd)


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


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

Symbol search path is: *** Invalid ***
****************************************************************************
* Symbol loading may be unreliable without a symbol search path. *
* Use .symfix to have the debugger choose a symbol path. *
* After setting your symbol path, use .reload to refresh symbol locations. *
****************************************************************************
Executable search path is:
*********************************************************************
* Symbols can not be loaded because symbol path is not initialized. *
* *
* The Symbol Path can be set by: *
* using the _NT_SYMBOL_PATH environment variable. *
* using the -y <symbol_path> argument when starting the debugger. *
* using .sympath and .sympath+ *
*********************************************************************
*** ERROR: Symbol file could not be found. Defaulted to export symbols for ntkrnlmp.exe -
Windows 8 Kernel Version 15063 MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 15063.0.amd64fre.rs2_release.170317-1834
Machine Name:
Kernel base = 0xfffff803`baa0d000 PsLoadedModuleList = 0xfffff803`bad595a0
Debug session time: Thu May 11 15:41:46.642 2017 (UTC + 2:00)
System Uptime: 0 days 0:00:23.290
*********************************************************************
* Symbols can not be loaded because symbol path is not initialized. *
* *
* The Symbol Path can be set by: *
* using the _NT_SYMBOL_PATH environment variable. *
* using the -y <symbol_path> argument when starting the debugger. *
* using .sympath and .sympath+ *
*********************************************************************
*** ERROR: Symbol file could not be found. Defaulted to export symbols for ntkrnlmp.exe -
Loading Kernel Symbols
...............................................................

Loading User Symbols

Loading unloaded module list
..

************* Symbol Loading Error Summary **************
Module name Error
ntkrnlmp The system cannot find the file specified

You can troubleshoot most symbol related issues by turning on symbol loading diagnostics (!sym noisy) and repeating the command that caused symbols to be loaded.
You should also verify that your symbol search path (.sympath) is correct.
*** ERROR: Symbol file could not be found. Defaulted to export symbols for hal.dll -
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 9C, {0, fffff803bd5ddba0, 0, 0}

*** ERROR: Symbol file could not be found. Defaulted to export symbols for PSHED.dll -
***** Kernel symbols are WRONG. Please fix symbols to do analysis.

*************************************************************************
*** ***
*** ***
*** Either you specified an unqualified symbol, or your debugger ***
*** doesn't have full symbol information. Unqualified symbol ***
*** resolution is turned off by default. Please either specify a ***
*** fully qualified symbol module!symbolname, or enable resolution ***
*** of unqualified symbols by typing ".symopt- 100". Note that ***
*** enabling unqualified symbol resolution with network symbol ***
*** server shares in the symbol path may cause the debugger to ***
*** appear to hang for long periods of time when an incorrect ***
*** symbol name is typed or the network symbol server is down. ***
*** ***
*** For some commands to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!_KPRCB ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** Either you specified an unqualified symbol, or your debugger ***
*** doesn't have full symbol information. Unqualified symbol ***
*** resolution is turned off by default. Please either specify a ***
*** fully qualified symbol module!symbolname, or enable resolution ***
*** of unqualified symbols by typing ".symopt- 100". Note that ***
*** enabling unqualified symbol resolution with network symbol ***
*** server shares in the symbol path may cause the debugger to ***
*** appear to hang for long periods of time when an incorrect ***
*** symbol name is typed or the network symbol server is down. ***
*** ***
*** For some commands to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!_KPRCB ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** Either you specified an unqualified symbol, or your debugger ***
*** doesn't have full symbol information. Unqualified symbol ***
*** resolution is turned off by default. Please either specify a ***
*** fully qualified symbol module!symbolname, or enable resolution ***
*** of unqualified symbols by typing ".symopt- 100". Note that ***
*** enabling unqualified symbol resolution with network symbol ***
*** server shares in the symbol path may cause the debugger to ***
*** appear to hang for long periods of time when an incorrect ***
*** symbol name is typed or the network symbol server is down. ***
*** ***
*** For some commands to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!_KPRCB ***
*** ***
*************************************************************************
Probably caused by : PSHED.dll ( PSHED!PshedInitialize+ff )

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

Dit is de dump file van mijn oude Windows (waar ik het voor de eerste keer kreeg)


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


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

Symbol search path is: *** Invalid ***
****************************************************************************
* Symbol loading may be unreliable without a symbol search path. *
* Use .symfix to have the debugger choose a symbol path. *
* After setting your symbol path, use .reload to refresh symbol locations. *
****************************************************************************
Executable search path is:
*********************************************************************
* Symbols can not be loaded because symbol path is not initialized. *
* *
* The Symbol Path can be set by: *
* using the _NT_SYMBOL_PATH environment variable. *
* using the -y <symbol_path> argument when starting the debugger. *
* using .sympath and .sympath+ *
*********************************************************************
*** ERROR: Symbol file could not be found. Defaulted to export symbols for ntkrnlmp.exe -
Windows 8 Kernel Version 14393 MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 14393.693.amd64fre.rs1_release.161220-1747
Machine Name:
Kernel base = 0xfffff800`8f610000 PsLoadedModuleList = 0xfffff800`8f915060
Debug session time: Sat Apr 29 19:23:40.668 2017 (UTC + 2:00)
System Uptime: 0 days 1:33:49.292
*********************************************************************
* Symbols can not be loaded because symbol path is not initialized. *
* *
* The Symbol Path can be set by: *
* using the _NT_SYMBOL_PATH environment variable. *
* using the -y <symbol_path> argument when starting the debugger. *
* using .sympath and .sympath+ *
*********************************************************************
*** ERROR: Symbol file could not be found. Defaulted to export symbols for ntkrnlmp.exe -
Loading Kernel Symbols
...............................................................
................................................................
......................................................
Loading User Symbols

Loading unloaded module list
............

************* Symbol Loading Error Summary **************
Module name Error
ntkrnlmp The system cannot find the file specified

You can troubleshoot most symbol related issues by turning on symbol loading diagnostics (!sym noisy) and repeating the command that caused symbols to be loaded.
You should also verify that your symbol search path (.sympath) is correct.
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck C2, {7, 484c764e, 4050013, ffffd18401404f40}

*** ERROR: Module load completed but symbols could not be loaded for nvlddmkm.sys
*** ERROR: Symbol file could not be found. Defaulted to export symbols for dxgkrnl.sys -
***** Kernel symbols are WRONG. Please fix symbols to do analysis.

*************************************************************************
*** ***
*** ***
*** Either you specified an unqualified symbol, or your debugger ***
*** doesn't have full symbol information. Unqualified symbol ***
*** resolution is turned off by default. Please either specify a ***
*** fully qualified symbol module!symbolname, or enable resolution ***
*** of unqualified symbols by typing ".symopt- 100". Note that ***
*** enabling unqualified symbol resolution with network symbol ***
*** server shares in the symbol path may cause the debugger to ***
*** appear to hang for long periods of time when an incorrect ***
*** symbol name is typed or the network symbol server is down. ***
*** ***
*** For some commands to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!PVOID ***
*** ***
*************************************************************************
unable to get nt!MmSpecialPoolStart
unable to get nt!MmSpecialPoolEnd
*************************************************************************
*** ***
*** ***
*** Either you specified an unqualified symbol, or your debugger ***
*** doesn't have full symbol information. Unqualified symbol ***
*** resolution is turned off by default. Please either specify a ***
*** fully qualified symbol module!symbolname, or enable resolution ***
*** of unqualified symbols by typing ".symopt- 100". Note that ***
*** enabling unqualified symbol resolution with network symbol ***
*** server shares in the symbol path may cause the debugger to ***
*** appear to hang for long periods of time when an incorrect ***
*** symbol name is typed or the network symbol server is down. ***
*** ***
*** For some commands to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!_POOL_HEADER ***
*** ***
*************************************************************************
unable to get nt!MmPagedPoolEnd
unable to get nt!MmNonPagedPoolStart
unable to get nt!MmSizeOfNonPagedPoolInBytes
*************************************************************************
*** ***
*** ***
*** Either you specified an unqualified symbol, or your debugger ***
*** doesn't have full symbol information. Unqualified symbol ***
*** resolution is turned off by default. Please either specify a ***
*** fully qualified symbol module!symbolname, or enable resolution ***
*** of unqualified symbols by typing ".symopt- 100". Note that ***
*** enabling unqualified symbol resolution with network symbol ***
*** server shares in the symbol path may cause the debugger to ***
*** appear to hang for long periods of time when an incorrect ***
*** symbol name is typed or the network symbol server is down. ***
*** ***
*** For some commands to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!_POOL_HEADER ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** Either you specified an unqualified symbol, or your debugger ***
*** doesn't have full symbol information. Unqualified symbol ***
*** resolution is turned off by default. Please either specify a ***
*** fully qualified symbol module!symbolname, or enable resolution ***
*** of unqualified symbols by typing ".symopt- 100". Note that ***
*** enabling unqualified symbol resolution with network symbol ***
*** server shares in the symbol path may cause the debugger to ***
*** appear to hang for long periods of time when an incorrect ***
*** symbol name is typed or the network symbol server is down. ***
*** ***
*** For some commands to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!_POOL_TRACKER_BIG_PAGES ***
*** ***
*************************************************************************
Cannot get _POOL_TRACKER_BIG_PAGES type size
*************************************************************************
*** ***
*** ***
*** Either you specified an unqualified symbol, or your debugger ***
*** doesn't have full symbol information. Unqualified symbol ***
*** resolution is turned off by default. Please either specify a ***
*** fully qualified symbol module!symbolname, or enable resolution ***
*** of unqualified symbols by typing ".symopt- 100". Note that ***
*** enabling unqualified symbol resolution with network symbol ***
*** server shares in the symbol path may cause the debugger to ***
*** appear to hang for long periods of time when an incorrect ***
*** symbol name is typed or the network symbol server is down. ***
*** ***
*** For some commands to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!_KPRCB ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** Either you specified an unqualified symbol, or your debugger ***
*** doesn't have full symbol information. Unqualified symbol ***
*** resolution is turned off by default. Please either specify a ***
*** fully qualified symbol module!symbolname, or enable resolution ***
*** of unqualified symbols by typing ".symopt- 100". Note that ***
*** enabling unqualified symbol resolution with network symbol ***
*** server shares in the symbol path may cause the debugger to ***
*** appear to hang for long periods of time when an incorrect ***
*** symbol name is typed or the network symbol server is down. ***
*** ***
*** For some commands to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!KPRCB ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** Either you specified an unqualified symbol, or your debugger ***
*** doesn't have full symbol information. Unqualified symbol ***
*** resolution is turned off by default. Please either specify a ***
*** fully qualified symbol module!symbolname, or enable resolution ***
*** of unqualified symbols by typing ".symopt- 100". Note that ***
*** enabling unqualified symbol resolution with network symbol ***
*** server shares in the symbol path may cause the debugger to ***
*** appear to hang for long periods of time when an incorrect ***
*** symbol name is typed or the network symbol server is down. ***
*** ***
*** For some commands to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!_KPRCB ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** Either you specified an unqualified symbol, or your debugger ***
*** doesn't have full symbol information. Unqualified symbol ***
*** resolution is turned off by default. Please either specify a ***
*** fully qualified symbol module!symbolname, or enable resolution ***
*** of unqualified symbols by typing ".symopt- 100". Note that ***
*** enabling unqualified symbol resolution with network symbol ***
*** server shares in the symbol path may cause the debugger to ***
*** appear to hang for long periods of time when an incorrect ***
*** symbol name is typed or the network symbol server is down. ***
*** ***
*** For some commands to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!KPRCB ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** Either you specified an unqualified symbol, or your debugger ***
*** doesn't have full symbol information. Unqualified symbol ***
*** resolution is turned off by default. Please either specify a ***
*** fully qualified symbol module!symbolname, or enable resolution ***
*** of unqualified symbols by typing ".symopt- 100". Note that ***
*** enabling unqualified symbol resolution with network symbol ***
*** server shares in the symbol path may cause the debugger to ***
*** appear to hang for long periods of time when an incorrect ***
*** symbol name is typed or the network symbol server is down. ***
*** ***
*** For some commands to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!_KPRCB ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** Either you specified an unqualified symbol, or your debugger ***
*** doesn't have full symbol information. Unqualified symbol ***
*** resolution is turned off by default. Please either specify a ***
*** fully qualified symbol module!symbolname, or enable resolution ***
*** of unqualified symbols by typing ".symopt- 100". Note that ***
*** enabling unqualified symbol resolution with network symbol ***
*** server shares in the symbol path may cause the debugger to ***
*** appear to hang for long periods of time when an incorrect ***
*** symbol name is typed or the network symbol server is down. ***
*** ***
*** For some commands to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!_KPRCB ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** Either you specified an unqualified symbol, or your debugger ***
*** doesn't have full symbol information. Unqualified symbol ***
*** resolution is turned off by default. Please either specify a ***
*** fully qualified symbol module!symbolname, or enable resolution ***
*** of unqualified symbols by typing ".symopt- 100". Note that ***
*** enabling unqualified symbol resolution with network symbol ***
*** server shares in the symbol path may cause the debugger to ***
*** appear to hang for long periods of time when an incorrect ***
*** symbol name is typed or the network symbol server is down. ***
*** ***
*** For some commands to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!_KPRCB ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** Either you specified an unqualified symbol, or your debugger ***
*** doesn't have full symbol information. Unqualified symbol ***
*** resolution is turned off by default. Please either specify a ***
*** fully qualified symbol module!symbolname, or enable resolution ***
*** of unqualified symbols by typing ".symopt- 100". Note that ***
*** enabling unqualified symbol resolution with network symbol ***
*** server shares in the symbol path may cause the debugger to ***
*** appear to hang for long periods of time when an incorrect ***
*** symbol name is typed or the network symbol server is down. ***
*** ***
*** For some commands to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!_KPRCB ***
*** ***
*************************************************************************
Probably caused by : nvlddmkm.sys ( nvlddmkm+83546 )

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

[Anoniem: 58485]

Probably caused by : nvlddmkm.sys ( nvlddmkm+83546 )

Je nvidia driver is de boosdoener.

https://www.drivereasy.co...ror-solved-on-windows-10/

[ Voor 34% gewijzigd door Anoniem: 58485 op 11-05-2017 21:11 ]

[McFastFood]

Dan zou ik niet Driver easy gebruken maar DDU.
Link : http://www.guru3d.com/fil...uninstaller-download.html

[Anoniem: 58485]

Nee, denk dat het bericht ook gemaakt is met een refferal link ofzo. Ze verwijzen naar een betaalpakket. Hoewel ik een driver updater kan waarderen (Zo'n prog vond de drivers die ik onmogelijk voor W7 kon vinden voor een oude laptop), het probleem ligt in ieder geval bij je Nvidia drivers.

[salman15]

@Anoniem: 58485 , maar ik heb Windows opnieuw geinstalleerd en mijn videokaart zit momenteel niet in mijn computer. Kan het probleem dan nogsteeds door mijn nvidea drivers komen?

De meest recente error komt dus door: "Probably caused by : PSHED.dll ( PSHED!PshedInitialize+ff )" als ik het goed begrijp

[ Voor 27% gewijzigd door salman15 op 11-05-2017 22:10 ]

[Anoniem: 263284]

Download eens even een linux live distributie (knoppix) en start die eens op. Als je een kernel panic krijgt weet je zeker dat het hardware gerelateerd is.
Een machine check exception is bijna altijd een hardware failure.

[ Voor 17% gewijzigd door Anoniem: 263284 op 12-05-2017 00:09 ]

[salman15]

@Anoniem: 263284 Klopt heb ik geprobeerd en kreeg toen idd een kernel panic met als oorzaak de cpu core

[rdejongjr]

Sinds skylake heb ik helaas een aardige stijging van rotte cpu's mogen vernemen.

Veelal is de geheugencontroler in orde en wil de antieke memtest nog prima maar (her)installaties van Windows en diverse software laten de boel al klappen. (machine check, Hal stopt, memory management errors)

Als het een retail is zou je hem ook nog bij intel zelf aan kunnen melden, met een beetje geluk via advanced warranty waarbij je eerst de vervanger thuis krijgt. Maar hoe dan ook is je winkel je eerste aanspreekpunt.

[McFastFood]

rdejongjr schreef op vrijdag 12 mei 2017 @ 01:51:
Sinds skylake heb ik helaas een aardige stijging van rotte cpu's mogen vernemen.

Veelal is de geheugencontroler in orde en wil de antieke memtest nog prima maar (her)installaties van Windows en diverse software laten de boel al klappen. (machine check, Hal stopt, memory management errors)

Als het een retail is zou je hem ook nog bij intel zelf aan kunnen melden, met een beetje geluk via advanced warranty waarbij je eerst de vervanger thuis krijgt. Maar hoe dan ook is je winkel je eerste aanspreekpunt.

Dit verhaal kan ik bevestigen ik heb het ook vaker gezien. Vaak is het de geheugencontroller inderdaad dat kwam in eerste instantie ook in me op. Maar aangezien het probleem zich voordeed in Photoshop, en het tijdens het weg schrijven van bestanden was kon het RAM de boosdoener ook zijn. Kwestie van garantie claimen bij de desbetreffende leverancier en ook de error codes vermelden.

[salman15]

@McFastFood @rdejongjr @Anoniem: 58485 @Anoniem: 263284 Ik heb vandaag de geheugen, moederbord en processor terug gestuurd, om te laten wisselen voor een nieuwe. Nu ben ik alleen bang dat ik over een maand weer met het zelfde probleem sta.

[rdejongjr]

Uitval bij cpu's is meer dan voorheen maar nog steeds erg weinig.
Zo lang je het ding verder niet de vernieling in klokt zal het wel mee vallen.

[salman15]

@rdejongjr Ik Oc liever niet, omdat mijn garantie dan verloopt

[McFastFood]

salman15 schreef op vrijdag 12 mei 2017 @ 15:54:
@rdejongjr Ik Oc liever niet, omdat mijn garantie dan verloopt

Misschien een beetje off topic maar waarom heb je dan een z270 bord en een k cpu als je liever niet gaat overklokken?

[Anoniem: 58485]

rdejongjr schreef op vrijdag 12 mei 2017 @ 01:51:
Sinds skylake heb ik helaas een aardige stijging van rotte cpu's mogen vernemen.

Veelal is de geheugencontroler in orde en wil de antieke memtest nog prima maar (her)installaties van Windows en diverse software laten de boel al klappen. (machine check, Hal stopt, memory management errors)

Als het een retail is zou je hem ook nog bij intel zelf aan kunnen melden, met een beetje geluk via advanced warranty waarbij je eerst de vervanger thuis krijgt. Maar hoe dan ook is je winkel je eerste aanspreekpunt.

Kan je dat verduidelijken met een bron en wat er exact met die CPU's aan de hand is?

[salman15]

@McFastFood pas, na mijn garantie heheh.