Sære problemer med PC-en. Bluescreen og lignende.

[exhizor]

.

Endret 1. februar 2017 av exhizor

[Bandaloginzih]

Hei!

 

Har du prøvd å oppdatere drivere for hovedkort og skjermkort?

 

Sjekk også på hovedkortets produktside at du har siste BIOS versjon

[exhizor]

.

Endret 1. februar 2017 av exhizor

[Bandaloginzih]

Skjermkort-drivere er oppdatert. Før jeg formaterte prøvde jeg å legge inn drivere på nytt, men fortsatt de samme problemene. Hva mener du med drivere for hovedkort? Kan prøve å oppdatere BIOS.

 

Sitter forresten på et ASUS hovedkort: http://www.asus.com/...DE_LX/#download

 

Med "drivere for HK" mente jeg drivere for innebygde enheter som chipset etc.

Jeg ville begynt med BIOS for å se om dette løser noe, og deretter prøve chipset, usb osv osv.

[Bandaloginzih]

Ser forøvrig på BIOS updates for ditt HK at det er mange "improve system stability"

[exhizor]

.

Endret 1. februar 2017 av exhizor

[Bandaloginzih]

OK.

 

Kan du prøve å legge ved den siste DUMP feilmeldingen?

 

Dump fil kan du finne her: C:\Windows\Minidump\

[exhizor]

.

Dumpfil.rar

Endret 1. februar 2017 av exhizor

[Albatraum]

Jeg har ikke så mye peiling men i den dmp fila du postet var en 3b stop med hal.dll som årsak. (Hardware Abstraction Layer). Det er den som styrer kommunikasjon melllom operativsystem og hardware. Har du mulighet til å poste flere dump filer? 3B stop er forøvrig relatert til skjermkort, antivirus eller minne.

[exhizor]

.

Dumpfiler.rar

Endret 1. februar 2017 av exhizor

[Albatraum]

Du kan prøve å avinstallere speedfan. Det er kjent for å gi random bsod. Hvis ikke det funker prøv http://memtest.org/#downiso

[exhizor]

.

112212-26036-01.rar

Endret 1. februar 2017 av exhizor

[Albatraum]

Hvordan gikk memtest? Fant den noen feil?

 

Her er forøvrig en kopi av dump filene dine. Den siste fikk jeg ikke til å lese

 

Loading User Symbols

Loading unloaded module list

....

*******************************************************************************

* *

* Bugcheck Analysis *

* *

*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 3B, {c0000005, fffff80002f8315f, fffff880084bffd0, 0}

Probably caused by : memory_corruption ( nt!MiUnsecureVirtualMemory+15f )

Followup: MachineOwner

---------

3: kd> !analyze -v

*******************************************************************************

* *

* Bugcheck Analysis *

* *

*******************************************************************************

SYSTEM_SERVICE_EXCEPTION (3b)

An exception happened while executing a system service routine.

Arguments:

Arg1: 00000000c0000005, Exception code that caused the bugcheck

Arg2: fffff80002f8315f, Address of the instruction which caused the bugcheck

Arg3: fffff880084bffd0, Address of the context record for the exception that caused the bugcheck

Arg4: 0000000000000000, zero.

Debugging Details:

------------------

 

EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.

FAULTING_IP:

nt!MiUnsecureVirtualMemory+15f

fffff800`02f8315f 488b0f mov rcx,qword ptr [rdi]

CONTEXT: fffff880084bffd0 -- (.cxr 0xfffff880084bffd0)

rax=2200000000000000 rbx=fffffa80099edb60 rcx=2200000000000000

rdx=0000000000000000 rsi=fffffa8007ccc060 rdi=2200000000000000

rip=fffff80002f8315f rsp=fffff880084c09b0 rbp=0000000000000001

r8=0000000000000000 r9=0000000000000000 r10=0000000000002928

r11=fffff880084c09c0 r12=fffffa8007ccc278 r13=0000000000000200

r14=0000000000000000 r15=0000000000000000

iopl=0 nv up ei pl zr na po nc

cs=0010 ss=0018 ds=002b es=002b fs=0053 gs=002b efl=00010246

nt!MiUnsecureVirtualMemory+0x15f:

fffff800`02f8315f 488b0f mov rcx,qword ptr [rdi] ds:002b:22000000`00000000=????????????????

Resetting default scope

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: WIN7_DRIVER_FAULT

BUGCHECK_STR: 0x3B

PROCESS_NAME: Blizzard Launc

CURRENT_IRQL: 0

LAST_CONTROL_TRANSFER: from 0000000000000000 to fffff80002f8315f

STACK_TEXT:

fffff880`084c09b0 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!MiUnsecureVirtualMemory+0x15f

 

FOLLOWUP_IP:

nt!MiUnsecureVirtualMemory+15f

fffff800`02f8315f 488b0f mov rcx,qword ptr [rdi]

SYMBOL_STACK_INDEX: 0

SYMBOL_NAME: nt!MiUnsecureVirtualMemory+15f

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: nt

DEBUG_FLR_IMAGE_TIMESTAMP: 4ce7951a

STACK_COMMAND: .cxr 0xfffff880084bffd0 ; kb

IMAGE_NAME: memory_corruption

FAILURE_BUCKET_ID: X64_0x3B_nt!MiUnsecureVirtualMemory+15f

BUCKET_ID: X64_0x3B_nt!MiUnsecureVirtualMemory+15f

Followup: MachineOwner

---------

 

 

Loading User Symbols

Loading unloaded module list

.........

*******************************************************************************

* *

* Bugcheck Analysis *

* *

*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck A, {fffffa800c7f7010, 2, 1, fffff80002d532a6}

Probably caused by : memory_corruption ( nt!MiReleaseConfirmedPageFileSpace+86 )

Followup: MachineOwner

---------

3: kd> !analyze -v

*******************************************************************************

* *

* Bugcheck Analysis *

* *

*******************************************************************************

IRQL_NOT_LESS_OR_EQUAL (a)

An attempt was made to access a pageable (or completely invalid) address at an

interrupt request level (IRQL) that is too high. This is usually

caused by drivers using improper addresses.

If a kernel debugger is available get the stack backtrace.

Arguments:

Arg1: fffffa800c7f7010, memory referenced

Arg2: 0000000000000002, IRQL

Arg3: 0000000000000001, bitfield :

bit 0 : value 0 = read operation, 1 = write operation

bit 3 : value 0 = not an execute operation, 1 = execute operation (only on chips which support this level of status)

Arg4: fffff80002d532a6, address which referenced memory

Debugging Details:

------------------

 

WRITE_ADDRESS: GetPointerFromAddress: unable to read from fffff80002ed00e8

GetUlongFromAddress: unable to read from fffff80002ed0198

fffffa800c7f7010 Nonpaged pool

CURRENT_IRQL: 2

FAULTING_IP:

nt!MiReleaseConfirmedPageFileSpace+86

fffff800`02d532a6 480fb328 btr qword ptr [rax],rbp

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: WIN7_DRIVER_FAULT

BUGCHECK_STR: 0xA

PROCESS_NAME: svchost.exe

TRAP_FRAME: fffff8800ba3b080 -- (.trap 0xfffff8800ba3b080)

NOTE: The trap frame does not contain all registers.

Some register values may be zeroed or incorrect.

rax=fffffa80085f7010 rbx=0000000000000000 rcx=0000000000000000

rdx=0000000000000000 rsi=0000000000000000 rdi=0000000000000000

rip=fffff80002d532a6 rsp=fffff8800ba3b210 rbp=0000000021000000

r8=fffff8800ba3b240 r9=00000000ffffffff r10=ffffffffffffffff

r11=0000000000000011 r12=0000000000000000 r13=0000000000000000

r14=0000000000000000 r15=0000000000000000

iopl=0 nv up ei pl zr na po nc

nt!MiReleaseConfirmedPageFileSpace+0x86:

fffff800`02d532a6 480fb328 btr qword ptr [rax],rbp ds:fffffa80`085f7010=ffffffffffffffff

Resetting default scope

LAST_CONTROL_TRANSFER: from fffff80002c9ebe9 to fffff80002c9f640

STACK_TEXT:

fffff880`0ba3af38 fffff800`02c9ebe9 : 00000000`0000000a fffffa80`0c7f7010 00000000`00000002 00000000`00000001 : nt!KeBugCheckEx

fffff880`0ba3af40 fffff800`02c9d860 : 00000000`00000008 fffff880`0ba3b100 00000000`00000000 00000000`00000000 : nt!KiBugCheckDispatch+0x69

fffff880`0ba3b080 fffff800`02d532a6 : 00000000`00000000 00000000`00000000 fffffa80`084a49b0 00000000`00020019 : nt!KiPageFault+0x260

fffff880`0ba3b210 fffff800`02d1263c : 21000000`00000000 fffff680`00151000 fffff680`00151050 000fffff`00000005 : nt!MiReleaseConfirmedPageFileSpace+0x86

fffff880`0ba3b290 fffff800`02c8c852 : 00000000`00000001 00000000`0000e561 fffffa80`0901d060 fffffa80`0901d3f8 : nt! ?? ::FNODOBFM::`string'+0x3bcb6

fffff880`0ba3bb20 fffff800`02c9e8d3 : ffffffff`ffffffff 00000000`0146f1d8 00000000`0146f1d0 00000000`00004000 : nt!NtFreeVirtualMemory+0x382

fffff880`0ba3bc20 00000000`76d714fa : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13

00000000`0146f198 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x76d714fa

 

STACK_COMMAND: kb

FOLLOWUP_IP:

nt!MiReleaseConfirmedPageFileSpace+86

fffff800`02d532a6 480fb328 btr qword ptr [rax],rbp

SYMBOL_STACK_INDEX: 3

SYMBOL_NAME: nt!MiReleaseConfirmedPageFileSpace+86

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: nt

DEBUG_FLR_IMAGE_TIMESTAMP: 4ce7951a

IMAGE_NAME: memory_corruption

FAILURE_BUCKET_ID: X64_0xA_nt!MiReleaseConfirmedPageFileSpace+86

BUCKET_ID: X64_0xA_nt!MiReleaseConfirmedPageFileSpace+86

Followup: MachineOwner

---------

 

 

Loading User Symbols

Loading unloaded module list

......

*******************************************************************************

* *

* Bugcheck Analysis *

* *

*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 3B, {c0000005, fffff80002df4617, fffff8800925afb0, 0}

Probably caused by : ntkrnlmp.exe ( nt!ExAllocatePoolWithTag+537 )

Followup: MachineOwner

---------

2: kd> !analyze -v

*******************************************************************************

* *

* Bugcheck Analysis *

* *

*******************************************************************************

SYSTEM_SERVICE_EXCEPTION (3b)

An exception happened while executing a system service routine.

Arguments:

Arg1: 00000000c0000005, Exception code that caused the bugcheck

Arg2: fffff80002df4617, Address of the instruction which caused the bugcheck

Arg3: fffff8800925afb0, Address of the context record for the exception that caused the bugcheck

Arg4: 0000000000000000, zero.

Debugging Details:

------------------

 

EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.

FAULTING_IP:

nt!ExAllocatePoolWithTag+537

fffff800`02df4617 48895808 mov qword ptr [rax+8],rbx

CONTEXT: fffff8800925afb0 -- (.cxr 0xfffff8800925afb0)

rax=5efff900c4ce2260 rbx=fffff88008b4aba0 rcx=fffff900c4cb6260

rdx=0000000000000aa0 rsi=00000000000000ab rdi=0000000000000021

rip=fffff80002df4617 rsp=fffff8800925b990 rbp=0000000000001000

r8=0000000000000021 r9=fffff88008b4aba0 r10=fffff88008b49cc8

r11=fffff900c4d00560 r12=fffff88008b49cc0 r13=0000000000000000

r14=fffffa8007b85660 r15=000000006c777355

iopl=0 nv up ei pl zr na po nc

cs=0010 ss=0018 ds=002b es=002b fs=0053 gs=002b efl=00010246

nt!ExAllocatePoolWithTag+0x537:

fffff800`02df4617 48895808 mov qword ptr [rax+8],rbx ds:002b:5efff900`c4ce2268=????????????????

Resetting default scope

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: WIN7_DRIVER_FAULT

BUGCHECK_STR: 0x3B

PROCESS_NAME: taskmgr.exe

CURRENT_IRQL: 0

LAST_CONTROL_TRANSFER: from 0000000000000000 to fffff80002df4617

STACK_TEXT:

fffff880`0925b990 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!ExAllocatePoolWithTag+0x537

 

FOLLOWUP_IP:

nt!ExAllocatePoolWithTag+537

fffff800`02df4617 48895808 mov qword ptr [rax+8],rbx

SYMBOL_STACK_INDEX: 0

SYMBOL_NAME: nt!ExAllocatePoolWithTag+537

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: nt

IMAGE_NAME: ntkrnlmp.exe

DEBUG_FLR_IMAGE_TIMESTAMP: 4ce7951a

STACK_COMMAND: .cxr 0xfffff8800925afb0 ; kb

FAILURE_BUCKET_ID: X64_0x3B_nt!ExAllocatePoolWithTag+537

BUCKET_ID: X64_0x3B_nt!ExAllocatePoolWithTag+537

Followup: MachineOwner

---------

 

[Chavalito]

Jeg tviler på at det er RAM som forårsaker de BSOD'ene. Den ene av de dump filene nevner Virtual_memory som synder, den andre PageFile, og den tredje ntkrnlmp.exe. Alle disse tre kan skyldes feil på hard disken da WIndows bruker hard disk som Virtual Memory, og Pagefile ligger jo på hard disken.

 

Kjør chkdsk /f på C disken din. Du burde kanskje bruke /r også, men det kan noen ganger gjøre saken verre, så ikke gjør det denne gangen.