Home » Hero Opinion » News Today Saleb » Paparazi Art » Politik Update » Super Saleb Info » Tips And Tips » BSOD (during gaming) three times in the last week on a one month old system

BSOD (during gaming) three times in the last week on a one month old system

News Saleb-,Newspapers are usually issued daily or weekly. BSOD (during gaming) three times in the last week on a one month old system, Magazine News weekly, but they also had a magazine format. Newspapers with common interests usually publish news articles and articles about national and international news as well as local news. These include news events and personalities of the political, business and finance, crime, weather, and natural hazards; health and medicine, science, and computers and technology; Sports; and entertainment, community, food and cuisine, apparel and home fashion, and the arts.

A wide range of materials have been published in newspapers. In addition to news,BSOD (during gaming) three times in the last week on a one month old system ,information and opinions expressed above, including weather forecasts; Criticism and reviews Arts (including literature, film, television, theater, art, and architecture) and local services such as a restaurant; obituaries, notices of birth and graduation announcements; Entertainment features such as crossword puzzles, horoscopes, editorial cartoons, jokes, cartoons and comics; Advice column, food, and other columns; and a list of radio and television (program schedule). In the year 2017, newspapers can also provide information about new movies and TV shows available on streaming video services such as Netflix. The newspaper has been classified ad section in which people and businesses can buy a small ad to sell goods or services; In the year 2013, a large increase in internet sites to sell goods, such as Craigslist and eBay have caused ad sales are much less classified for newspapers.BSOD (during gaming) three times in the last week on a one month old system Since 1983, it has been known mainly because of its annual report and rankings that influence in college and grad school, lies in most fields and subjects. U.s. News World Report is and academic institution is the oldest and most famous in America, [5] and covering the areas of business, law, medicine, engineering, social sciences, education and public affairs, in addition to many other areas. Print Edition] has consistently included in the list of national bestsellers, coupled with online subscriptions. Additional rankings published by U.s. News World Report and includes hospitals,BSOD (during gaming) three times in the last week on a one month old system, medical and specialty cars.
BSOD (during gaming) three times in the last week on a one month old system-News of the United States was founded in 1933 by David Lawrence (1888-1973), which also started the World Report in 1946. The two magazines are covering national and international news separately, but Lawrence combines them into news reports of U.S. in World and 1948 [1] and Later sold the magazine to its employees. Historically, this magazine tends to be a bit more conservative than the two main competitors, Time and Newsweek, and focus more on the story of economic, health, and education. It's also distancing news, entertainment and sports celebrities. [2] an important milestone in the history of the beginning of the magazine is including the introduction of the "Washington Whispers" column in 1934 and the column "News You Can Use" in 1952. [3] [4] in 1958, the circulation of the weekly magazine passed one million and two million in 1973. (wikipedia) BSOD (during gaming) three times in the last week on a one month old system

The post is long because of two BSOD reports from the Windows Minidump (.dmp files) if anyone finds any meaning in them. Any help appreciated.

The BSODs are:

1) 19 Nov: MEMORY_MANAGEMENT - about 40 min. into playing Company of Heroes on Steam. After this one I ran the Windows Memory Diagnostic (lasted one hour) with no issues found.

2) 23 Nov: IRQL_NOT_LESS_OR_EQUAL - about 30 min. into playing TrackMania on Steam. WinDbg report below.

3) 24 Nov: MEMORY_MANAGEMENT - similar as above, less than an hour into playing TrackMania on Steam. WinDbg report below.

After the BSOD the computer restarts automatically.

I've also played other games in the meanwhile without issues, so the BSODs seem to happen randomly. For example, on monday I've played Mass Effect 3 for 2.5 hours (in 4K) while streaming 1080p to YouTube. Yesterday I also played TrackMania for about an hour after the BSOD and it was fine.

Basic specs: (built on 27 Oct 2017)

PSU: Corsair RM850

MBD: ASUS ROG Strix B350-F Gaming

CPU: AMD Ryzen 7 1700X Eight-Core Processor, 3400 Mhz

RAM: 32GB; 4x 8GB G.Skill TridentZ DDR4, 3200Mhz

GPU: Nvidia MSI GeForce GTX 1080 GAMING X 8G

Windows 10 64-bit on a Samsung 830 SSD (256 GB). Games installed on a 1TB WD Blue.

Water-cooled system. Temps on GPU & CPU don't exceed 50C at max. load. All the drivers are up to date.

The only remaining hardware from the previous build is the PSU and all the drives (ssd + wd + one samsung). Could a bad PSU be a problem?

23 Nov WinDbg Report

Microsoft (R) Windows Debugger Version 10.0.16299.15 AMD64 Copyright (c) Microsoft Corporation. All rights reserved.

Loading Dump File [C:\Users\Iggy\Dropbox\BSOD\112317-6812-01.dmp] Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: srv* Executable search path is: Windows 10 Kernel Version 16299 MP (16 procs) Free x64 Product: WinNt, suite: TerminalServer SingleUserTS Built by: 16299.15.amd64fre.rs3_release.170928-1534 Machine Name: Kernel base = 0xfffff801e407f000 PsLoadedModuleList = 0xfffff801e43e0fb0 Debug session time: Thu Nov 23 11:58:54.761 2017 (UTC + 1:00) System Uptime: 3 days 18:49:13.344 Loading Kernel Symbols ............................................................... ................................................................ ............................................. Loading User Symbols Loading unloaded module list ..................................................

  • *
  • Bugcheck Analysis *
  • * *******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck A, {e8, 2, 1, fffff801e40c1c8f}

Probably caused by : ntkrnlmp.exe ( nt!KeAcquireInStackQueuedSpinLock+2f )

Followup: MachineOwner

5: 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: 00000000000000e8, 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: fffff801e40c1c8f, address which referenced memory

Debugging Details:

DUMP_CLASS: 1

DUMP_QUALIFIER: 400

BUILD_VERSION_STRING: 10.0.16299.64 (WinBuild.160101.0800)

SYSTEM_MANUFACTURER: System manufacturer

SYSTEM_PRODUCT_NAME: System Product Name

SYSTEM_SKU: SKU

SYSTEM_VERSION: System Version

BIOS_VENDOR: American Megatrends Inc.

BIOS_VERSION: 0902

BIOS_DATE: 09/08/2017

BASEBOARD_MANUFACTURER: ASUSTeK COMPUTER INC.

BASEBOARD_PRODUCT: ROG STRIX B350-F GAMING

BASEBOARD_VERSION: Rev X.0x

DUMP_TYPE: 2

BUGCHECK_P1: e8

BUGCHECK_P2: 2

BUGCHECK_P3: 1

BUGCHECK_P4: fffff801e40c1c8f

WRITE_ADDRESS: fffff801e4477380: Unable to get MiVisibleState Unable to get NonPagedPoolStart Unable to get NonPagedPoolEnd Unable to get PagedPoolStart Unable to get PagedPoolEnd 00000000000000e8

CURRENT_IRQL: 2

FAULTING_IP: nt!KeAcquireInStackQueuedSpinLock+2f fffff801`e40c1c8f 488711 xchg rdx,qword ptr [rcx]

CPU_COUNT: 10

CPU_MHZ: d42

CPU_VENDOR: AuthenticAMD

CPU_FAMILY: 17

CPU_MODEL: 1

CPU_STEPPING: 1

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: WIN8_DRIVER_FAULT

BUGCHECK_STR: AV

PROCESS_NAME: WerFault.exe

ANALYSIS_SESSION_HOST: DESKTOP-9P6V97R

ANALYSIS_SESSION_TIME: 11-24-2017 10:34:18.0361

ANALYSIS_VERSION: 10.0.16299.15 amd64fre

TRAP_FRAME: ffffbd0da80211c0 -- (.trap 0xffffbd0da80211c0) NOTE: The trap frame does not contain all registers. Some register values may be zeroed or incorrect. rax=0000000000000002 rbx=0000000000000000 rcx=00000000000000e8 rdx=ffffbd0da80213a0 rsi=0000000000000000 rdi=0000000000000000 rip=fffff801e40c1c8f rsp=ffffbd0da8021350 rbp=0000000000000000 r8=ffffbd0da80213a0 r9=ffffdd0000000000 r10=0000000000000000 r11=ffffbd0da80213e8 r12=0000000000000000 r13=0000000000000000 r14=0000000000000000 r15=0000000000000000 iopl=0 nv up ei pl zr na po nc nt!KeAcquireInStackQueuedSpinLock+0x2f: fffff801e40c1c8f 488711 xchg rdx,qword ptr [rcx] ds:00000000000000e8=???????????????? Resetting default scope

LAST_CONTROL_TRANSFER: from fffff801e41ee9e9 to fffff801e41e30e0

STACK_TEXT:
ffffbd0da8021078 fffff801e41ee9e9 : 000000000000000a 00000000000000e8 0000000000000002 0000000000000001 : nt!KeBugCheckEx ffffbd0da8021080 fffff801e41ecd7d : 7fffffffffffffff 0000000000000000 3fffffffffffffff 0000000009849d20 : nt!KiBugCheckDispatch+0x69 ffffbd0da80211c0 fffff801e40c1c8f : 0000000000000000 0000000000000000 0000000000000000 ffffbd0da8021500 : nt!KiPageFault+0x23d ffffbd0da8021350 fffff801e4156a7d : ffff9249249247f8 ffff9249248fff08 ffff9249248fff08 ffff92491ffe17d0 : nt!KeAcquireInStackQueuedSpinLock+0x2f ffffbd0da8021380 fffff801e40faa76 : fffff801e4400e00 0000028947fa2150 ffffbd0da80214f0 0000000000000002 : nt!MiReleasePageFileInfo+0x71 ffffbd0da80213f0 fffff801e40f65e6 : 0000000000000000 ffff8205f73d9700 0000000000000000 ffff8205f46c5080 : nt!MiDeleteVirtualAddresses+0xff6 ffffbd0da80216e0 fffff801e456a842 : ffff8205f73d9700 ffff8205f2ca46a0 0000000000000000 ffff8205f73d9700 : nt!MiDeleteVad+0x3b6 ffffbd0da8021830 fffff801e456a497 : ffff8205f73d9700 ffff820500000000 ffff8205f2ca46a0 ffff8205f2ca46a0 : nt!MiUnmapVad+0x32 ffffbd0da8021860 fffff801e456a2de : ffffffff00000000 ffff8205f9bb5890 ffff8205f2ca46a0 ffff8205f73d9700 : nt!MiCleanVad+0x27 ffffbd0da8021890 fffff801e4529a99 : ffffffffffffffff ffff8205f46c5080 ffff8205f46c5378 fffff801e45a6f06 : nt!MmCleanProcessAddressSpace+0x12e ffffbd0da8021910 fffff801e45bbc17 : ffff8205f46c5080 ffffc20006be49d0 ffffbd0da8021b80 0000000000000000 : nt!PspRundownSingleProcess+0x129 ffffbd0da8021990 fffff801e45bcc87 : 0000000000000000 ffffbd0da8021b01 000000498a3be000 ffff8205f73d9700 : nt!PspExitThread+0x583 ffffbd0da8021a90 fffff801e41ee553 : ffff820500004dc8 ffff8205f73d9700 ffff8205f46c5080 0000023c8d671230 : nt!NtTerminateProcess+0xeb ffffbd0da8021b00 00007ff8631503c4 : 0000000000000000 0000000000000000 0000000000000000 0000000000000000 : nt!KiSystemServiceCopyEnd+0x13 000000498a47f798 0000000000000000 : 0000000000000000 0000000000000000 0000000000000000 0000000000000000 : 0x00007ff8`631503c4

THREAD_SHA1_HASH_MOD_FUNC: a5ec02a0e10b754ce21ce75478c2b1d478cbadf0

THREAD_SHA1_HASH_MOD_FUNC_OFFSET: d68b84369f7b23facf04c6b817ed4163b7c31f14

THREAD_SHA1_HASH_MOD: 7f608ac2fbce9034a3386b1d51652e4911d30234

FOLLOWUP_IP: nt!KeAcquireInStackQueuedSpinLock+2f fffff801`e40c1c8f 488711 xchg rdx,qword ptr [rcx]

FAULT_INSTR_CODE: 48118748

SYMBOL_STACK_INDEX: 3

SYMBOL_NAME: nt!KeAcquireInStackQueuedSpinLock+2f

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: nt

IMAGE_NAME: ntkrnlmp.exe

DEBUG_FLR_IMAGE_TIMESTAMP: 59efff9b

IMAGE_VERSION: 10.0.16299.64

STACK_COMMAND: .thread ; .cxr ; kb

BUCKET_ID_FUNC_OFFSET: 2f

FAILURE_BUCKET_ID: AV_nt!KeAcquireInStackQueuedSpinLock

BUCKET_ID: AV_nt!KeAcquireInStackQueuedSpinLock

PRIMARY_PROBLEM_CLASS: AV_nt!KeAcquireInStackQueuedSpinLock

TARGET_TIME: 2017-11-23T10:58:54.000Z

OSBUILD: 16299

OSSERVICEPACK: 64

SERVICEPACK_NUMBER: 0

OS_REVISION: 0

SUITE_MASK: 272

PRODUCT_TYPE: 1

OSPLATFORM_TYPE: x64

OSNAME: Windows 10

OSEDITION: Windows 10 WinNt TerminalServer SingleUserTS

OS_LOCALE:

USER_LCID: 0

OSBUILD_TIMESTAMP: 2017-10-25 05:06:03

BUILDDATESTAMP_STR: 160101.0800

BUILDLAB_STR: WinBuild

BUILDOSVER_STR: 10.0.16299.64

ANALYSIS_SESSION_ELAPSED_TIME: c06

ANALYSIS_SOURCE: KM

FAILURE_ID_HASH_STRING: km:av_nt!keacquireinstackqueuedspinlock

FAILURE_ID_HASH: {4e843e91-40f1-2a76-3dbc-bba199ce6b1e}

Followup: MachineOwner

24 Nov WinDbg Report

Microsoft (R) Windows Debugger Version 10.0.16299.15 AMD64 Copyright (c) Microsoft Corporation. All rights reserved.

Loading Dump File [C:\Windows\Minidump\112417-6828-01.dmp] Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: srv* Executable search path is: Windows 10 Kernel Version 16299 MP (16 procs) Free x64 Product: WinNt, suite: TerminalServer SingleUserTS Built by: 16299.15.amd64fre.rs3_release.170928-1534 Machine Name: Kernel base = 0xfffff802efc9d000 PsLoadedModuleList = 0xfffff802efffefb0 Debug session time: Fri Nov 24 10:27:55.298 2017 (UTC + 1:00) System Uptime: 0 days 22:28:17.977 Loading Kernel Symbols ............................................................... ................................................................ ............................................ Loading User Symbols Loading unloaded module list ..............

  • *
  • Bugcheck Analysis *
  • * *******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 1A, {41793, ffffa2803b234f98, 10, f}

Probably caused by : memory_corruption ( nt!MiDeleteVirtualAddresses+1223bf )

Followup: MachineOwner

4: kd> !analyze -v

  • *
  • Bugcheck Analysis *
  • * *******************************************************************************

MEMORY_MANAGEMENT (1a) # Any other values for parameter 1 must be individually examined. Arguments: Arg1: 0000000000041793, The subtype of the bugcheck. Arg2: ffffa2803b234f98 Arg3: 0000000000000010 Arg4: 000000000000000f

Debugging Details:

DUMP_CLASS: 1

DUMP_QUALIFIER: 400

BUILD_VERSION_STRING: 10.0.16299.64 (WinBuild.160101.0800)

SYSTEM_MANUFACTURER: System manufacturer

SYSTEM_PRODUCT_NAME: System Product Name

SYSTEM_SKU: SKU

SYSTEM_VERSION: System Version

BIOS_VENDOR: American Megatrends Inc.

BIOS_VERSION: 0902

BIOS_DATE: 09/08/2017

BASEBOARD_MANUFACTURER: ASUSTeK COMPUTER INC.

BASEBOARD_PRODUCT: ROG STRIX B350-F GAMING

BASEBOARD_VERSION: Rev X.0x

DUMP_TYPE: 2

BUGCHECK_P1: 41793

BUGCHECK_P2: ffffa2803b234f98

BUGCHECK_P3: 10

BUGCHECK_P4: f

BUGCHECK_STR: 0x1a_41793

CPU_COUNT: 10

CPU_MHZ: d42

CPU_VENDOR: AuthenticAMD

CPU_FAMILY: 17

CPU_MODEL: 1

CPU_STEPPING: 1

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: WIN8_DRIVER_FAULT

PROCESS_NAME: SearchFilterHost.exe

CURRENT_IRQL: 2

ANALYSIS_SESSION_HOST: DESKTOP-9P6V97R

ANALYSIS_SESSION_TIME: 11-24-2017 10:31:52.0169

ANALYSIS_VERSION: 10.0.16299.15 amd64fre

LAST_CONTROL_TRANSFER: from fffff802efe39e3f to fffff802efe010e0

STACK_TEXT:
fffffb8d8bd4d418 fffff802efe39e3f : 000000000000001a 0000000000041793 ffffa2803b234f98 0000000000000010 : nt!KeBugCheckEx fffffb8d8bd4d420 fffff802efd145e6 : 0000000000000000 ffffd102de252080 0000000000000000 ffffd102e16b15c0 : nt!MiDeleteVirtualAddresses+0x1223bf fffffb8d8bd4d710 fffff802f01884aa : ffffd102de252080 ffffd102dc63de10 ffffd102dc63de10 ffffd102de252080 : nt!MiDeleteVad+0x3b6 fffffb8d8bd4d860 fffff802f01882de : ffffffff00000000 ffffd102dea78980 ffffd102dc63de10 ffffd102de252080 : nt!MiCleanVad+0x3a fffffb8d8bd4d890 fffff802f0147a99 : ffffffffffffffff ffffd102e16b15c0 ffffd102e16b18b8 ffffd10200000000 : nt!MmCleanProcessAddressSpace+0x12e fffffb8d8bd4d910 fffff802f01d9c17 : ffffd102e16b15c0 ffffb705f3bae060 fffffb8d8bd4db80 0000000000000000 : nt!PspRundownSingleProcess+0x129 fffffb8d8bd4d990 fffff802f01dac87 : 0000000000000000 fffffb8d8bd4db01 00000076469e6000 ffffd102de252080 : nt!PspExitThread+0x583 fffffb8d8bd4da90 fffff802efe0c553 : ffffd102000024c8 ffffd102de252080 ffffd102e16b15c0 000001ec4bca1230 : nt!NtTerminateProcess+0xeb fffffb8d8bd4db00 00007ffbf3a503c4 : 0000000000000000 0000000000000000 0000000000000000 0000000000000000 : nt!KiSystemServiceCopyEnd+0x13 0000007646a7f898 0000000000000000 : 0000000000000000 0000000000000000 0000000000000000 0000000000000000 : 0x00007ffb`f3a503c4

THREAD_SHA1_HASH_MOD_FUNC: 66b70bb23aa87ecd3790f5db7fe42422debab9f7

THREAD_SHA1_HASH_MOD_FUNC_OFFSET: 7b073c075ac4eb81fe3eca601a7e1199ee799ca4

THREAD_SHA1_HASH_MOD: 9f457f347057f10e1df248e166a3e95e6570ecfe

FOLLOWUP_IP: nt!MiDeleteVirtualAddresses+1223bf fffff802`efe39e3f cc int 3

FAULT_INSTR_CODE: c48b4dcc

SYMBOL_STACK_INDEX: 1

SYMBOL_NAME: nt!MiDeleteVirtualAddresses+1223bf

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: nt

DEBUG_FLR_IMAGE_TIMESTAMP: 59efff9b

IMAGE_VERSION: 10.0.16299.64

STACK_COMMAND: .thread ; .cxr ; kb

IMAGE_NAME: memory_corruption

BUCKET_ID_FUNC_OFFSET: 1223bf

FAILURE_BUCKET_ID: 0x1a_41793_nt!MiDeleteVirtualAddresses

BUCKET_ID: 0x1a_41793_nt!MiDeleteVirtualAddresses

PRIMARY_PROBLEM_CLASS: 0x1a_41793_nt!MiDeleteVirtualAddresses

TARGET_TIME: 2017-11-24T09:27:55.000Z

OSBUILD: 16299

OSSERVICEPACK: 64

SERVICEPACK_NUMBER: 0

OS_REVISION: 0

SUITE_MASK: 272

PRODUCT_TYPE: 1

OSPLATFORM_TYPE: x64

OSNAME: Windows 10

OSEDITION: Windows 10 WinNt TerminalServer SingleUserTS

OS_LOCALE:

USER_LCID: 0

OSBUILD_TIMESTAMP: 2017-10-25 05:06:03

BUILDDATESTAMP_STR: 160101.0800

BUILDLAB_STR: WinBuild

BUILDOSVER_STR: 10.0.16299.64

ANALYSIS_SESSION_ELAPSED_TIME: 502

ANALYSIS_SOURCE: KM

FAILURE_ID_HASH_STRING: km:0x1a_41793_nt!mideletevirtualaddresses

FAILURE_ID_HASH: {0730eb34-d667-1bcc-76fe-94b17390a3ef}

Followup: MachineOwner

4: kd> !analyze -v

  • *
  • Bugcheck Analysis *
  • * *******************************************************************************

MEMORY_MANAGEMENT (1a) # Any other values for parameter 1 must be individually examined. Arguments: Arg1: 0000000000041793, The subtype of the bugcheck. Arg2: ffffa2803b234f98 Arg3: 0000000000000010 Arg4: 000000000000000f

Debugging Details:

DUMP_CLASS: 1

DUMP_QUALIFIER: 400

BUILD_VERSION_STRING: 10.0.16299.64 (WinBuild.160101.0800)

SYSTEM_MANUFACTURER: System manufacturer

SYSTEM_PRODUCT_NAME: System Product Name

SYSTEM_SKU: SKU

SYSTEM_VERSION: System Version

BIOS_VENDOR: American Megatrends Inc.

BIOS_VERSION: 0902

BIOS_DATE: 09/08/2017

BASEBOARD_MANUFACTURER: ASUSTeK COMPUTER INC.

BASEBOARD_PRODUCT: ROG STRIX B350-F GAMING

BASEBOARD_VERSION: Rev X.0x

DUMP_TYPE: 2

BUGCHECK_P1: 41793

BUGCHECK_P2: ffffa2803b234f98

BUGCHECK_P3: 10

BUGCHECK_P4: f

BUGCHECK_STR: 0x1a_41793

CPU_COUNT: 10

CPU_MHZ: d42

CPU_VENDOR: AuthenticAMD

CPU_FAMILY: 17

CPU_MODEL: 1

CPU_STEPPING: 1

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: WIN8_DRIVER_FAULT

PROCESS_NAME: SearchFilterHost.exe

CURRENT_IRQL: 2

ANALYSIS_SESSION_HOST: DESKTOP-9P6V97R

ANALYSIS_SESSION_TIME: 11-24-2017 10:31:53.0467

ANALYSIS_VERSION: 10.0.16299.15 amd64fre

LAST_CONTROL_TRANSFER: from fffff802efe39e3f to fffff802efe010e0

STACK_TEXT:
fffffb8d8bd4d418 fffff802efe39e3f : 000000000000001a 0000000000041793 ffffa2803b234f98 0000000000000010 : nt!KeBugCheckEx fffffb8d8bd4d420 fffff802efd145e6 : 0000000000000000 ffffd102de252080 0000000000000000 ffffd102e16b15c0 : nt!MiDeleteVirtualAddresses+0x1223bf fffffb8d8bd4d710 fffff802f01884aa : ffffd102de252080 ffffd102dc63de10 ffffd102dc63de10 ffffd102de252080 : nt!MiDeleteVad+0x3b6 fffffb8d8bd4d860 fffff802f01882de : ffffffff00000000 ffffd102dea78980 ffffd102dc63de10 ffffd102de252080 : nt!MiCleanVad+0x3a fffffb8d8bd4d890 fffff802f0147a99 : ffffffffffffffff ffffd102e16b15c0 ffffd102e16b18b8 ffffd10200000000 : nt!MmCleanProcessAddressSpace+0x12e fffffb8d8bd4d910 fffff802f01d9c17 : ffffd102e16b15c0 ffffb705f3bae060 fffffb8d8bd4db80 0000000000000000 : nt!PspRundownSingleProcess+0x129 fffffb8d8bd4d990 fffff802f01dac87 : 0000000000000000 fffffb8d8bd4db01 00000076469e6000 ffffd102de252080 : nt!PspExitThread+0x583 fffffb8d8bd4da90 fffff802efe0c553 : ffffd102000024c8 ffffd102de252080 ffffd102e16b15c0 000001ec4bca1230 : nt!NtTerminateProcess+0xeb fffffb8d8bd4db00 00007ffbf3a503c4 : 0000000000000000 0000000000000000 0000000000000000 0000000000000000 : nt!KiSystemServiceCopyEnd+0x13 0000007646a7f898 0000000000000000 : 0000000000000000 0000000000000000 0000000000000000 0000000000000000 : 0x00007ffb`f3a503c4

THREAD_SHA1_HASH_MOD_FUNC: 66b70bb23aa87ecd3790f5db7fe42422debab9f7

THREAD_SHA1_HASH_MOD_FUNC_OFFSET: 7b073c075ac4eb81fe3eca601a7e1199ee799ca4

THREAD_SHA1_HASH_MOD: 9f457f347057f10e1df248e166a3e95e6570ecfe

FOLLOWUP_IP: nt!MiDeleteVirtualAddresses+1223bf fffff802`efe39e3f cc int 3

FAULT_INSTR_CODE: c48b4dcc

SYMBOL_STACK_INDEX: 1

SYMBOL_NAME: nt!MiDeleteVirtualAddresses+1223bf

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: nt

DEBUG_FLR_IMAGE_TIMESTAMP: 59efff9b

IMAGE_VERSION: 10.0.16299.64

STACK_COMMAND: .thread ; .cxr ; kb

IMAGE_NAME: memory_corruption

BUCKET_ID_FUNC_OFFSET: 1223bf

FAILURE_BUCKET_ID: 0x1a_41793_nt!MiDeleteVirtualAddresses

BUCKET_ID: 0x1a_41793_nt!MiDeleteVirtualAddresses

PRIMARY_PROBLEM_CLASS: 0x1a_41793_nt!MiDeleteVirtualAddresses

TARGET_TIME: 2017-11-24T09:27:55.000Z

OSBUILD: 16299

OSSERVICEPACK: 64

SERVICEPACK_NUMBER: 0

OS_REVISION: 0

SUITE_MASK: 272

PRODUCT_TYPE: 1

OSPLATFORM_TYPE: x64

OSNAME: Windows 10

OSEDITION: Windows 10 WinNt TerminalServer SingleUserTS

OS_LOCALE:

USER_LCID: 0

OSBUILD_TIMESTAMP: 2017-10-25 05:06:03

BUILDDATESTAMP_STR: 160101.0800

BUILDLAB_STR: WinBuild

BUILDOSVER_STR: 10.0.16299.64

ANALYSIS_SESSION_ELAPSED_TIME: 501

ANALYSIS_SOURCE: KM

FAILURE_ID_HASH_STRING: km:0x1a_41793_nt!mideletevirtualaddresses

FAILURE_ID_HASH: {0730eb34-d667-1bcc-76fe-94b17390a3ef}

Followup: MachineOwner



Submitted November 24, 2017 at 05:01PM by AlienwareSLO http://ift.tt/2Bicqeq

Title :BSOD (during gaming) three times in the last week on a one month old system
Source :BSOD (during gaming) three times in the last week on a one month old system

News Info:


Share on Facebook
Share on Twitter
Share on Google+

Related : BSOD (during gaming) three times in the last week on a one month old system

0 komentar:

Post a Comment

Subscribe to: Post Comments (Atom)