Kan detta vara en anledning till BSOD, Win 8.1

Trädvy Permalänk
Medlem
Registrerad
Mar 2012

Kan detta vara en anledning till BSOD, Win 8.1

Tjena,

För ett tag sen började min burk att få massa BSOD:s i tid och otid.

Jag försökte felsöka burken genom att ladda hem programmet "Whocrashed" och kolla minnet med memtest osv osv.

Då slog det mig plötsligt att det kanske var mitt PSU som kanske ligger på gränsen till att vara för svagt. Så jag tog bort min OC på 4.4 och återställande min
propp till default inställningar(default volt osv) och då minskade mina blue screens. Från att krasha 3-5 ggr per dag så får jag nu bara en BSOD ungefär varannan dag.

Eftersom detta halvt löste problemet och jag visste sen innan att mitt EVGA 780 SC ACX kort och min i5 4670K skulle vara på gränsen för mitt nuvarande pwr supply så kommer här frågan:

Kan det hela lösa sig genom att köpa sig en starkare pwr supply?

Chassi: Fractal Design Define R5 Titan Moderkort: ASUS Strix Z270E Gaming Grafikkort: ASUS GeForce GTX 1080 STRIX Advanced Gaming CPU: Intel Core i7 7700K @ Stock Kylning: Noctua NH-D15 Minne: Crucial Ballistix Sport LT 16GB 2400MHz SSD1: Samsung 850 EVO 250GB SSD2: Samsung 850 EVO 500GB PSU: Corsair RMx Series RM750x 750Watt 80 PLUS Gold

Trädvy Permalänk
Medlem
Plats
Kalix
Registrerad
Jun 2004

Vad får du för fel kod vid bsod? Vissa koder säger vad du har för problem.
Att problemet fortsätter trots du kör oklockat är lite mer oroade och visst kan din PSU vara trasig men det kan vara andra saker som strular tex minne som kan få för lite volt defult osv eller bara ett trist HW fel.

| I7 6700K | Asus Z170 Pro | Corsair 16GB DDR4 3000Mhz | Gainward GTX 1080 GLH | Be Quiet Dark power Pro 10 850W | Dell S2716DG | Noctua NH-D15 | Corsair Carbide 600Q | | Sony Z2 tablet | En HTPC

Trädvy Permalänk
Medlem
Registrerad
Mar 2012

Jag kan posta lite fel loggar direkt från "Whocrashed" när jag kommer hem, är just nu på arbetsplatsen.

Chassi: Fractal Design Define R5 Titan Moderkort: ASUS Strix Z270E Gaming Grafikkort: ASUS GeForce GTX 1080 STRIX Advanced Gaming CPU: Intel Core i7 7700K @ Stock Kylning: Noctua NH-D15 Minne: Crucial Ballistix Sport LT 16GB 2400MHz SSD1: Samsung 850 EVO 250GB SSD2: Samsung 850 EVO 500GB PSU: Corsair RMx Series RM750x 750Watt 80 PLUS Gold

Trädvy Permalänk
Medlem
Registrerad
Mar 2012

Nedan hittar mina rapporter från Whocrashed:

On Sun 2014-01-19 15:33:05 GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\011914-15484-01.dmp
This was probably caused by the following module: win32k.sys (win32k+0x16916)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF960001D7916, 0xFFFFD000214FB060, 0x0)
Error: SYSTEM_SERVICE_EXCEPTION
file path: C:\WINDOWS\system32\win32k.sys
product: Operativsystemet Microsoft® Windows®
company: Microsoft Corporation
description: Win32-drivrutin för flera användare
Bug check description: This indicates that an exception happened while executing a routine that transitions from non-privileged code to privileged code.
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 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 Sat 2014-01-18 19:25:32 GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\011814-14015-01.dmp
This was probably caused by the following module: dxgmms1.sys (dxgmms1+0x2C2F9)
Bugcheck code: 0x1000007E (0xFFFFFFFFC0000005, 0xFFFFF8000143E2F9, 0xFFFFD00020A36498, 0xFFFFD00020A35CA0)
Error: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M
file path: C:\WINDOWS\system32\drivers\dxgmms1.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: DirectX Graphics MMS
Bug check description: This indicates that a system thread 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 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 Sat 2014-01-18 15:47:55 GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\011814-15515-01.dmp
This was probably caused by the following module: netio.sys (NETIO+0x7BC5)
Bugcheck code: 0x1E (0xFFFFFFFFC0000005, 0xFFFFF80000C07BC5, 0xFFFFD00021D58EE8, 0xFFFFD00021D586F0)
Error: KMODE_EXCEPTION_NOT_HANDLED
file path: C:\WINDOWS\system32\drivers\netio.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Network I/O Subsystem
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 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 Sat 2014-01-18 13:56:27 GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\011814-15203-01.dmp
This was probably caused by the following module: dxgmms1.sys (0xFFFFF8000085695F)
Bugcheck code: 0xD1 (0xFFFFE00082FB9A60, 0x2, 0x0, 0xFFFFF8000085695F)
Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
file path: C:\WINDOWS\system32\drivers\dxgmms1.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: DirectX Graphics MMS
Bug check description: This indicates that a kernel-mode driver attempted to access pageable memory at a process IRQL that was too high.
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 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 Sat 2014-01-18 13:12:17 GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\011814-15859-01.dmp
This was probably caused by the following module: srtsp64.sys (SRTSP64+0x22668)
Bugcheck code: 0x3B (0x80000003, 0xFFFFF80004F54668, 0xFFFFD000272796E0, 0x0)
Error: SYSTEM_SERVICE_EXCEPTION
file path: C:\WINDOWS\System32\Drivers\NISx64\1404000.028\SRTSP64.SYS
product: AutoProtect
company: Symantec Corporation
description: Symantec AutoProtect
Bug check description: This indicates that an exception happened while executing a routine that transitions from non-privileged code to privileged code.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
A third party driver was identified as the probable root cause of this system error. It is suggested you look for an update for the following driver: srtsp64.sys (Symantec AutoProtect, Symantec Corporation).
Google query: Symantec Corporation SYSTEM_SERVICE_EXCEPTION

On Sat 2014-01-18 11:34:42 GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\011814-16265-01.dmp
This was probably caused by the following module: netio.sys (NETIO+0x1298B)
Bugcheck code: 0xD1 (0x10, 0x2, 0x1, 0xFFFFF8000081298B)
Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
file path: C:\WINDOWS\system32\drivers\netio.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Network I/O Subsystem
Bug check description: This indicates that a kernel-mode driver attempted to access pageable memory at a process IRQL that was too high.
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 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 Sat 2014-01-18 03:31:12 GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\011814-14843-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x14DCA0)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF8016B2E6359, 0xFFFFD00026F4D6E0, 0x0)
Error: SYSTEM_SERVICE_EXCEPTION
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 an exception happened while executing a routine that transitions from non-privileged code to privileged code.
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 Thu 2014-01-16 23:32:39 GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\011714-15218-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x14DCA0)
Bugcheck code: 0xD1 (0xFFFFF80010CBCE00, 0x2, 0x8, 0xFFFFF80010CBCE00)
Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
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 driver attempted to access pageable memory at a process IRQL that was too high.
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 Thu 2014-01-16 20:19:29 GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\011614-14953-01.dmp
This was probably caused by the following module: e22w8x64.sys (e22w8x64+0x8549)
Bugcheck code: 0x1000007E (0xFFFFFFFFC0000005, 0xFFFFF800025D4549, 0xFFFFD00020F386E8, 0xFFFFD00020F37EF0)
Error: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M
file path: C:\WINDOWS\system32\drivers\e22w8x64.sys
product: Killer e2200 PCI-E Gigabit Ethernet Controller
company: Qualcomm Atheros, Inc.
description: Killer e2200 PCI-E Gigabit Ethernet Controller
Bug check description: This indicates that a system thread 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.
A third party driver was identified as the probable root cause of this system error. It is suggested you look for an update for the following driver: e22w8x64.sys (Killer e2200 PCI-E Gigabit Ethernet Controller, Qualcomm Atheros, Inc.).
Google query: Qualcomm Atheros, Inc. SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M

On Wed 2014-01-15 20:44:54 GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\011514-16750-01.dmp
This was probably caused by the following module: pacer.sys (pacer+0x2A53)
Bugcheck code: 0x1E (0xFFFFFFFFC0000005, 0xFFFFF80001605A53, 0xFFFFD00020FB6378, 0xFFFFD00020FB5B80)
Error: KMODE_EXCEPTION_NOT_HANDLED
file path: C:\WINDOWS\system32\drivers\pacer.sys
product: Operativsystemet Microsoft® Windows®
company: Microsoft Corporation
description: QoS Packet Scheduler
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 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.

Chassi: Fractal Design Define R5 Titan Moderkort: ASUS Strix Z270E Gaming Grafikkort: ASUS GeForce GTX 1080 STRIX Advanced Gaming CPU: Intel Core i7 7700K @ Stock Kylning: Noctua NH-D15 Minne: Crucial Ballistix Sport LT 16GB 2400MHz SSD1: Samsung 850 EVO 250GB SSD2: Samsung 850 EVO 500GB PSU: Corsair RMx Series RM750x 750Watt 80 PLUS Gold

Trädvy Permalänk
Medlem
Plats
127.0.0.1
Registrerad
Sep 2003

Hur gick det med memtest, hur länge körde du?

Krasharna verkar ganska random så ändra är det en driver som bökar eller så skulle jag tippa på minnesfel, exempelvis fel timings, spänning etc. Kan ju vara vadsomhelst som får datorn att räkna fel egentligen...

1: Intel i7-3930K | 32GB Corsair Dominator GT | Asus Rampage IV Extreme x79 | 2 x 1080 GameRock Premium 8GB | 2 x Samsung Pro 840 512GB | Corsair AX1200i | BenQ XL2411 24" / W1070 135" | Bose QC25 | Windows 10 Pro x64 | HTC Vive |
2: Intel Core i7-4700HQ | 32GB RAM | Intel HM87 Express | GTX 780M | 17" | Windows 10 x64 |

Trädvy Permalänk
Moderator
Plats
Omnipresent
Registrerad
Okt 2004

Har du senaste firmwaren på din OCZ SSD då dessa tyvärr inte det mest stabila på marknaden, snabba ja men inte stabila.

Gud är Död! - Nietzsche
Nietzsche är Död! - Gud

Trädvy Permalänk
Medlem
Registrerad
Mar 2012

Har inte uppdaterat firmwaren till SSDn så det är något jag kan testa senare.

Memtest körde jag igenom 2ggr men den hittade inget fel, eller menar du memtest86+ som man måste göra en iso för ?

Chassi: Fractal Design Define R5 Titan Moderkort: ASUS Strix Z270E Gaming Grafikkort: ASUS GeForce GTX 1080 STRIX Advanced Gaming CPU: Intel Core i7 7700K @ Stock Kylning: Noctua NH-D15 Minne: Crucial Ballistix Sport LT 16GB 2400MHz SSD1: Samsung 850 EVO 250GB SSD2: Samsung 850 EVO 500GB PSU: Corsair RMx Series RM750x 750Watt 80 PLUS Gold

Trädvy Permalänk
Moderator
Plats
Omnipresent
Registrerad
Okt 2004
Skrivet av LoMack:

Har inte uppdaterat firmwaren till SSDn så det är något jag kan testa senare.

Memtest körde jag igenom 2ggr men den hittade inget fel, eller menar du memtest86+ som man måste göra en iso för ?

Ja han menar memtest86+ då den andra inte på långa vägar är lika djupgående.

Gud är Död! - Nietzsche
Nietzsche är Död! - Gud