gasolin
#0
Bsod, i5 6600k asus z170 pro gaming 2x8gb 2133mhz kingston hyper x fury, 500gb, samsung 840 evo 250gb samsung evo 850 til spil, palit gtx 1060 6gb, windows 10 64 bit
Skal jeg virkelig til at geninstallere windows?
On Sat 07-01-2017 22:11:32 your computer crashed
crash dump file: C:\WINDOWS\Minidump\010717-4765-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x14A6F0)
Bugcheck code: 0xD1 (0x0, 0xFF, 0x3C, 0x0)
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 Sat 07-01-2017 22:11:32 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: 0xD1 (0x0, 0xFF, 0x3C, 0x0)
Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
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.
Skal jeg virkelig til at geninstallere windows?
On Sat 07-01-2017 22:11:32 your computer crashed
crash dump file: C:\WINDOWS\Minidump\010717-4765-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x14A6F0)
Bugcheck code: 0xD1 (0x0, 0xFF, 0x3C, 0x0)
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 Sat 07-01-2017 22:11:32 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: 0xD1 (0x0, 0xFF, 0x3C, 0x0)
Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
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.
#1
Basic hardware test foerst
sfc /scannow
reinstaller chipst lydkort og gfxkort driver
sfc /scannow
reinstaller chipst lydkort og gfxkort driver
#2
Har prøvet sf/scannow der var ingen fejl
Prøvede også mdsched.exe der skulle vise en log efter jeg er logget på, men det har jeg ikke set
bruger ikke lyddriveren så den har har jeg slettet
Prøvede også mdsched.exe der skulle vise en log efter jeg er logget på, men det har jeg ikke set
bruger ikke lyddriveren så den har har jeg slettet
#3
har du seneste firmware på dine SSD'er?
#4
har du seneste firmware på dine SSD'er?
Ja skulle være nyeste driver til de 2 forskellige ssder også selv om de er forskellige
EXTODB6Q 840 EVO
EMT02B6Q 850 EVO
#5
#2
den skulle gerne komme op med en besked lige naar du logger ind efter genstart.
den skulle gerne komme op med en besked lige naar du logger ind efter genstart.
#6
Så er det rammene det er galt med.
Tjek om de får den rigtige spænding osv i bios.
Tjek om de får den rigtige spænding osv i bios.
#7
Rammene skulle for 1.20 volt (kan ikke lige se det uden at gå i biosen) det hele køre på auto og med mit bundkort for de ikke for lidt volt, da jeg havde corsair vengeance 3000mhz fik de på aut ca 1.510 volt
#8
Aktiver XMP, der skulle være en til standard clock på kortet.
#9
Har prøvet xmp, det gør ikke nogen forskel
#10
#7 + #9
du har stadigvaek ikke koert basis hw test ?
du har stadigvaek ikke koert basis hw test ?
#11
Har kørt sfc/scannow, prime 95, ibt og mdsched.exe (ram test)
#12
har købt ny nøgle på kinguin
Det går bare ikke mere,jeg kommer ikke uden om det
Det går bare ikke mere,jeg kommer ikke uden om det
#13
Hej gasolin,
Fik du løst dine udfordringer og hvis ja, hvordan?
Mvh.
Fik du løst dine udfordringer og hvis ja, hvordan?
Mvh.
#14
det vare b.la min virtuel hukommelse/sidefil i system,avancerede systeminstilling,avanceret,ydeevne,avanceret der blev ændret og mit grafikkort driver der blev slettet og geninstalleret
havde kontakt med live supporten mindst 4 gange
Min pc køre 7-9-13 stabilt
havde kontakt med live supporten mindst 4 gange
Min pc køre 7-9-13 stabilt
#15
glemte lige at skrive at jeg også flyttede mit grafik en pci e ned