praegune kellaaeg 19.06.2025 04:10:53 |
|
Hinnavaatlus
:: Foorum
:: Uudised
:: Ärifoorumid
:: HV F1 ennustusvõistlus
:: Pangalink
:: Telekavad
:: HV toote otsing
|
|
| autor |
|
Kapsapixel
HV vaatleja
liitunud: 19.03.2010
|
12.09.2019 23:00:29
Arvuti jookseb mängimise ajal kokku. |
|
|
Niisiis, venna arvutiga on probleem. Mängimise ajal lampi viskab bluescreeni. Ma olen niipalju ise teadnud otsida, et minidumpist vaadata mis pange keerab. BlueScreenView süüdistab ntoskrnlit ja pci.sys. need kaks on ainsad ühised errorid kõikide crashide juures.
Tekst WinDbg analüüsist:
Microsoft (R) Windows Debugger Version 10.0.18362.1 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [C:\Users\loner\Desktop\091219-35537-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available
Symbol search path is: srv*
Executable search path is:
Windows 7 Kernel Version 7601 (Service Pack 1) MP (12 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7601.24499.amd64fre.win7sp1_ldr.190612-0600
Machine Name:
Kernel base = 0xfffff800`03010000 PsLoadedModuleList = 0xfffff800`03249c90
Debug session time: Thu Sep 12 20:56:16.786 2019 (UTC + 3:00)
System Uptime: 0 days 2:30:22.816
Loading Kernel Symbols
...............................................................
................................................................
....................................
Loading User Symbols
Loading unloaded module list
.........................
For analysis of this file, run !analyze -v
11: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
DRIVER_IRQL_NOT_LESS_OR_EQUAL (d1)
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 kernel debugger is available get stack backtrace.
Arguments:
Arg1: 0000000000000064, memory referenced
Arg2: 000000000000000b, IRQL
Arg3: 0000000000000001, value 0 = read operation, 1 = write operation
Arg4: fffff88000f14e9b, address which referenced memory
Debugging Details:
------------------
GetUlongPtrFromAddress: unable to read from fffff800032ad300
KEY_VALUES_STRING: 1
PROCESSES_ANALYSIS: 1
SERVICE_ANALYSIS: 1
STACKHASH_ANALYSIS: 1
TIMELINE_ANALYSIS: 1
DUMP_CLASS: 1
DUMP_QUALIFIER: 400
BUILD_VERSION_STRING: 7601.24499.amd64fre.win7sp1_ldr.190612-0600
SYSTEM_MANUFACTURER: MSI
SYSTEM_PRODUCT_NAME: MS-7A37
SYSTEM_SKU: To be filled by O.E.M.
SYSTEM_VERSION: 2.0
BIOS_VENDOR: American Megatrends Inc.
BIOS_VERSION: A.70
BIOS_DATE: 09/20/2017
BASEBOARD_MANUFACTURER: MSI
BASEBOARD_PRODUCT: B350M MORTAR ARCTIC (MS-7A37)
BASEBOARD_VERSION: 2.0
DUMP_TYPE: 2
BUGCHECK_P1: 64
BUGCHECK_P2: b
BUGCHECK_P3: 1
BUGCHECK_P4: fffff88000f14e9b
WRITE_ADDRESS: GetPointerFromAddress: unable to read from fffff800032ad100
Unable to get MmSystemRangeStart
GetUlongPtrFromAddress: unable to read from fffff800032ad2f0
GetUlongPtrFromAddress: unable to read from fffff800032ad4a8
GetPointerFromAddress: unable to read from fffff800032ad0d8
0000000000000064
CURRENT_IRQL: b
FAULTING_IP:
pci!memset+2b
fffff880`00f14e9b 488910 mov qword ptr [rax],rdx
CPU_COUNT: c
CPU_MHZ: c80
CPU_VENDOR: AuthenticAMD
CPU_FAMILY: 17
CPU_MODEL: 1
CPU_STEPPING: 1
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: WIN7_DRIVER_FAULT
BUGCHECK_STR: 0xD1
PROCESS_NAME: System
ANALYSIS_SESSION_HOST: ATLANTIS2
ANALYSIS_SESSION_TIME: 09-12-2019 22:01:00.0248
ANALYSIS_VERSION: 10.0.18362.1 amd64fre
TRAP_FRAME: fffff880035e2840 -- (.trap 0xfffff880035e2840)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=0000000000000064 rbx=0000000000000000 rcx=0000000000000004
rdx=0000000000000000 rsi=0000000000000000 rdi=0000000000000000
rip=fffff88000f14e9b rsp=fffff880035e29d8 rbp=0000000000000002
r8=0000000000000048 r9=0101010101010101 r10=0000000000000000
r11=fffff880035e2950 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0 nv up ei pl nz na po nc
pci!memset+0x2b:
fffff880`00f14e9b 488910 mov qword ptr [rax],rdx ds:00000000`00000064=????????????????
Resetting default scope
EXCEPTION_RECORD: fffff880035b1180 -- (.exr 0xfffff880035b1180)
Cannot read Exception record @ fffff880035b1180
LAST_CONTROL_TRANSFER: from fffff800030b20e9 to fffff800030a3ca0
STACK_TEXT:
fffff880`035e26f8 fffff800`030b20e9 : 00000000`0000000a 00000000`00000064 00000000`0000000b 00000000`00000001 : nt!KeBugCheckEx
fffff880`035e2700 fffff800`030afece : 00000000`00000001 00000000`00000064 fffff880`00000000 00000000`0000004c : nt!KiBugCheckDispatch+0x69
fffff880`035e2840 fffff880`00f14e9b : fffff880`00f11c44 00000000`00000001 00000000`00000023 fffffa80`076eeab0 : nt!KiPageFault+0x44e
fffff880`035e29d8 fffff880`00f11c44 : 00000000`00000001 00000000`00000023 fffffa80`076eeab0 fffff800`035f4be3 : pci!memset+0x2b
fffff880`035e29e0 fffff880`00f1172e : 00000000`00000000 fffff880`035e2b30 fffffa80`07706f00 fffff800`03090593 : pci!ExpressRootPortAerInterruptRoutine+0x1bc
fffff880`035e2a40 fffff800`030a4908 : fffff880`035b1180 fffff880`035e2b30 fffffa80`07706f00 fffffa80`06d2c001 : pci!ExpressRootPortInterruptRoutine+0x36
fffff880`035e2ab0 fffff800`030a7202 : fffff880`035b1180 fffff880`035c0340 00000000`00000001 fffff880`00000001 : nt!KiInterruptDispatch+0xb8
fffff880`035e2c40 00000000`00000000 : fffff880`035e3000 fffff880`035dd000 fffff880`035e2c00 00000000`00000000 : nt!KiIdleLoop+0x32
THREAD_SHA1_HASH_MOD_FUNC: e4e481574ca01c3a3242310d537361d2eb2a595f
THREAD_SHA1_HASH_MOD_FUNC_OFFSET: ef023d1dadf716f12ea4d21938427d96560d7b8d
THREAD_SHA1_HASH_MOD: 8c8b28fe1dd8af486d2ffdf8a7ce653399f4747b
FOLLOWUP_IP:
pci!memset+2b
fffff880`00f14e9b 488910 mov qword ptr [rax],rdx
FAULT_INSTR_CODE: 48108948
SYMBOL_STACK_INDEX: 3
SYMBOL_NAME: pci!memset+2b
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: pci
IMAGE_NAME: pci.sys
DEBUG_FLR_IMAGE_TIMESTAMP: 5cb92d78
IMAGE_VERSION: 6.1.7601.24441
STACK_COMMAND: .thread ; .cxr ; kb
FAILURE_BUCKET_ID: X64_0xD1_pci!memset+2b
BUCKET_ID: X64_0xD1_pci!memset+2b
PRIMARY_PROBLEM_CLASS: X64_0xD1_pci!memset+2b
TARGET_TIME: 2019-09-12T17:56:16.000Z
OSBUILD: 7601
OSSERVICEPACK: 1000
SERVICEPACK_NUMBER: 0
OS_REVISION: 0
SUITE_MASK: 272
PRODUCT_TYPE: 1
OSPLATFORM_TYPE: x64
OSNAME: Windows 7
OSEDITION: Windows 7 WinNt (Service Pack 1) TerminalServer SingleUserTS
OS_LOCALE:
USER_LCID: 0
OSBUILD_TIMESTAMP: 2019-06-12 17:36:12
BUILDDATESTAMP_STR: 190612-0600
BUILDLAB_STR: win7sp1_ldr
BUILDOSVER_STR: 6.1.7601.24499.amd64fre.win7sp1_ldr.190612-0600
ANALYSIS_SESSION_ELAPSED_TIME: 1b45
ANALYSIS_SOURCE: KM
FAILURE_ID_HASH_STRING: km:x64_0xd1_pci!memset+2b
FAILURE_ID_HASH: {3cf65bf5-0990-d8a1-712d-0743b8b79e7b}
Followup: MachineOwner
---------
|
juurde lisatud ka dump fail ise: https://drive.google.com/open?id=1A1Y40xLjSIdfAKYad2FOkBrc2HDGf2Aj
Videodriverid said uuendatud kahe crashi vahel. Muutus puudub. Siiski, miskit videokaardi driveriga toimub et ainult mängimise ajal crashib.
Ram on veel testimata. Kõvaketas on ok.
muud specsid:
 Spoiler
Operating System
Windows 7 Ultimate 64-bit SP1
CPU
AMD Ryzen 5 1600 36 °C
14nm Technology
RAM
8,00GB Dual-Channel Unknown @ 1199MHz (17-17-17-39)
Motherboard
MSI B350M MORTAR ARCTIC (MS-7A37) (AM4) 36 °C
Graphics
BenQ GC2870 (1920x1080@59Hz)
4096MB ATI Radeon RX 560 Series (Gigabyte) 38 °C
Storage
2794GB TOSHIBA DT01ACA300 ATA Device (SATA ) 36 °C
Optical Drives
HL-DT-ST DVDRAM GH24NSD1 ATA Device
Audio
Realtek High Definition Audio |
Ma ei tea mida selle infoga edasi hakata, ning ei tea miks pci.sys crash tekitab, kõikvõimas google ütleb et driveriprobleem, kuid driverid said enne siintoodud dumpi uuendatud.
_________________
Olen allveelaev mis lendab nagu kaamel red bulli laksu all. |
|
| Kommentaarid: 6 loe/lisa |
Kasutajad arvavad: |
   |
:: |
0 :: |
0 :: |
6 |
|
| tagasi üles |
|
 |
Karl P.
HV kasutaja
liitunud: 18.12.2010
|
|
12.09.2019 23:28:20
|
|
|
| Kuidas driverid uuendasid? Võid proovida enne uue driveri installimist vana ära kustutada Display Driver Uninstalleriga. Samuti võid vanemaid drivereid proovida.
|
|
| Kommentaarid: 28 loe/lisa |
Kasutajad arvavad: |
|
:: |
0 :: |
0 :: |
24 |
|
| tagasi üles |
|
|
Kapsapixel
HV vaatleja
liitunud: 19.03.2010
|
|
12.09.2019 23:54:41
|
|
|
Uuendasingi AMD driveri tööriistaga - vana maha ja uus peale. Erinevaid drivereid pole proovinud sest probleem oli algusest peale vanemate driveri versioonidega ka.
_________________
Olen allveelaev mis lendab nagu kaamel red bulli laksu all. |
|
| Kommentaarid: 6 loe/lisa |
Kasutajad arvavad: |
|
:: |
0 :: |
0 :: |
6 |
|
| tagasi üles |
|
|
Dirty Harry
HV Guru
liitunud: 05.09.2002
|
|
13.09.2019 11:51:24
|
|
|
| Temperatuurid on alati üks lihtne asi, mida jälgida. Võib seda teha nii tarkvaraliselt kui kiskuda kast lahti ja vaadata, äkki mõni ventilaator ei keeruta end. Või siis näpuga ettevaatlikult katsuda siit ja sealt peale crashi väljalülitatud arvutit.
|
|
| Kommentaarid: 181 loe/lisa |
Kasutajad arvavad: |
|
:: |
1 :: |
1 :: |
145 |
|
| tagasi üles |
|
|
|
| lisa lemmikuks |
|
 |
sa ei või postitada uusi teemasid siia foorumisse
sa ei või vastata selle foorumi teemadele
sa ei või muuta oma postitusi selles foorumis
sa ei või kustutada oma postitusi selles foorumis
sa ei või vastata küsitlustele selles foorumis
sa ei saa lisada manuseid selles foorumis
sa võid manuseid alla laadida selles foorumis
|
|
Hinnavaatlus ei vastuta foorumis tehtud postituste eest.
|
:: KKK
:: otsing 
:: statistika
:: kasutajate nimekiri
:: kasutajate grupid
:: registreeri
teata moderaatorile
