Erg vreemd dat die er niet bij staat maar het betreft een I5 2500k. Heb het tevens toegevoegd aan de start post.
EDIT1:
Hier de uitslag van WhoCrashed:
code:
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
| System Information (local)
--------------------------------------------------------------------------------
computer name: KANTOOR
windows version: Windows 8.1 , 6.2, build: 9200
windows dir: C:\WINDOWS
Hardware: ASUSTeK Computer INC., P8P67 PRO
CPU: GenuineIntel Intel(R) Core(TM) i5-2500K CPU @ 3.30GHz Intel586, level: 6
4 logical processors, active mask: 15
RAM: 4260499456 total
--------------------------------------------------------------------------------
Crash Dump Analysis
--------------------------------------------------------------------------------
Crash dump directory: C:\WINDOWS\Minidump
Crash dumps are enabled on your computer.
On Fri 21-11-2014 10:17:30 GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\112114-8515-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x14F1A0)
Bugcheck code: 0x1A (0x41792, 0xFFFFF68000015F58, 0x1000000000000000, 0x0)
Error: MEMORY_MANAGEMENT
file path: C:\WINDOWS\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that a severe memory management error occurred.
This might be a case of memory corruption. More often memory corruption happens because of software errors in buggy drivers, not because of faulty RAM modules.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.
On Fri 21-11-2014 10:17:30 GMT your computer crashed
crash dump file: C:\WINDOWS\memory.dmp
This was probably caused by the following module: ntkrnlmp.exe (nt!KeBugCheckEx+0x0)
Bugcheck code: 0x1A (0x41792, 0xFFFFF68000015F58, 0x1000000000000000, 0x0)
Error: MEMORY_MANAGEMENT
Bug check description: This indicates that a severe memory management error occurred.
This might be a case of memory corruption. More often memory corruption happens because of software errors in buggy drivers, not because of faulty RAM modules.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.
On Thu 20-11-2014 08:08:48 GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\112014-8734-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x14F1A0)
Bugcheck code: 0x1A (0x41792, 0xFFFFF6805E397558, 0x1000000000000000, 0x0)
Error: MEMORY_MANAGEMENT
file path: C:\WINDOWS\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that a severe memory management error occurred.
This might be a case of memory corruption. More often memory corruption happens because of software errors in buggy drivers, not because of faulty RAM modules.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.
On Mon 17-11-2014 14:06:22 GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\111714-8421-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x14F1A0)
Bugcheck code: 0x1A (0x41792, 0xFFFFF680003FEBD8, 0x1000000000000000, 0x0)
Error: MEMORY_MANAGEMENT
file path: C:\WINDOWS\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that a severe memory management error occurred.
This might be a case of memory corruption. More often memory corruption happens because of software errors in buggy drivers, not because of faulty RAM modules.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.
On Mon 17-11-2014 07:14:33 GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\111714-8203-01.dmp
This was probably caused by the following module: ntfs.sys (Ntfs+0xA9E9)
Bugcheck code: 0x24 (0xB500190637, 0xFFFFD0015705B028, 0xFFFFD0015705A830, 0xFFFFF80264D5783D)
Error: NTFS_FILE_SYSTEM
file path: C:\WINDOWS\system32\drivers\ntfs.sys
product: Besturingssysteem Microsoft® Windows®
company: Microsoft Corporation
description: NT-bestandssysteemstuurprogramma
Bug check description: This indicates a problem occurred in the NTFS file system.
The crash took place in a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system that cannot be identified at this time.
On Sun 16-11-2014 11:52:01 GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\111614-7109-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x153FA0)
Bugcheck code: 0x1E (0xFFFFFFFFC0000005, 0xFFFFF8008486AA13, 0x0, 0xFFFFFFFFFFFFFFFF)
Error: KMODE_EXCEPTION_NOT_HANDLED
file path: C:\WINDOWS\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that a kernel-mode program generated an exception which the error handler did not catch.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.
On Sat 15-11-2014 22:00:09 GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\111514-8531-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x153FA0)
Bugcheck code: 0x139 (0x3, 0xFFFFD00023C63430, 0xFFFFD00023C63388, 0x0)
Error: KERNEL_SECURITY_CHECK_FAILURE
file path: C:\WINDOWS\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: The kernel has detected the corruption of a critical data structure.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.
On Thu 13-11-2014 12:20:04 GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\111314-8843-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x153FA0)
Bugcheck code: 0x1A (0x41792, 0xFFFFF6802C5620D8, 0x1000000000000000, 0x0)
Error: MEMORY_MANAGEMENT
file path: C:\WINDOWS\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that a severe memory management error occurred.
This might be a case of memory corruption. More often memory corruption happens because of software errors in buggy drivers, not because of faulty RAM modules.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.
On Tue 11-11-2014 20:40:37 GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\111114-8906-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x153FA0)
Bugcheck code: 0xF7 (0xFFFFD000E7F9B1F9, 0x766C2CA285F, 0xFFFFF8993D35D7A0, 0x0)
Error: DRIVER_OVERRAN_STACK_BUFFER
file path: C:\WINDOWS\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that a driver has overrun a stack-based buffer.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.
On Mon 10-11-2014 13:48:36 GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\111014-7109-01.dmp
This was probably caused by the following module: win32k.sys (0xFFFFF9600017D38C)
Bugcheck code: 0x109 (0xA3A01F5A73BF84F7, 0xB3B72BE0C63F977E, 0xFFFFF9600017D38C, 0xC)
Error: CRITICAL_STRUCTURE_CORRUPTION
file path: C:\WINDOWS\system32\win32k.sys
product: Besturingssysteem Microsoft® Windows®
company: Microsoft Corporation
description: Multi-User Win32-stuurprogramma
Bug check description: This indicates that the kernel has detected critical kernel code or data corruption.
This might be a case of memory corruption. More often memory corruption happens because of software errors in buggy drivers, not because of faulty RAM modules.
The crash took place in a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system that cannot be identified at this time.
--------------------------------------------------------------------------------
Conclusion
--------------------------------------------------------------------------------
14 crash dumps have been found and analyzed. Only 10 are included in this report. No offending third party drivers have been found. Connsider using WhoCrashed Professional which offers more detailed analysis using symbol resolution. Also configuring your system to produce a full memory dump may help you.
Read the topic general suggestions for troubleshooting system crashes for more information.
Note that it's not always possible to state with certainty whether a reported driver is responsible for crashing your system or that the root cause is in another module. Nonetheless it's suggested you look for updates for the products that these drivers belong to and regularly visit Windows update or enable automatic updates for Windows. In case a piece of malfunctioning hardware is causing trouble, a search with Google on the bug check errors together with the model name and brand of your computer may help you investigate this further. |
Kom er zelf niet bepaald verder mee.
Mijn conclusie zou alsnog zijn.
Of de memory controller in de cpu? Iets kapot op het moederbord qua memory beheer. Of toch die voeding die onvoldoende sterk is.
Het zijn te veel mogelijkheden en met de cpu en het moederbord kan ik niets doen qua testing. Het geheugen zou ik eventueel nog in een andere machine kunnen testen. Al geeft 19h memtest zonder errors mij toch wel het gevoel dat het hem daar niet in zit.
Kan dit uberhaupt een voeding probleem zijn? Is er iemand die dat kan bevestigen? Deze voeding is namelijk al eens eerder te kort geweest in een systeem. Dat systeem was echter veel zwaarder waardoor ik dat ook aannemelijk achtte.
Misschien dat deze voeding dan wel nooit goed is geweest.
EDIT2:
Inmiddels nog maar 1 geheugenbankje er in (2gig). Heb er een andere videokaart in gedaan GTX570ti, deze gebruikt minder stroom om de voeding wat te ontlasten. Misschien krijg ik nu duidelijkheid. De voeding is 520watt maar op de zeikant zag ik net staan dat de 12v rail 'maar' 408 watt kan hebben. Natuurlijk draait niet alles 12V maar wel veel.
I5: 95 Watt TDP
GTX 275: 220 Watt
P8P67: Ongeveer 60 Watt?
Dan zit je toch al snel tegen die 400 watt aan te hikken.
Ergens hoop ik maar dat dit de oplossing is. Dan kan ik of een zuinigere kaart kopen voor dit systeem. Of een andere voeding.
[
Voor 104% gewijzigd door
Clifdon op 22-11-2014 17:31
]
Always look on the bright side of life.
/u/179781/tweaker%2520avatar.png?f=community){kind=avatar}
:strip_icc():strip_exif()/u/630897/crop5fbcdfeaa4e31.jpeg?f=community)
