Jump to content
Microsoft Windows Bulletin Board

BSOD on win 8


Guest Razvan-PetruCristolovean

Recommended Posts

Guest Razvan-PetruCristolovean
Posted

Hello people,

 

I'm having problems with a Windows 8 system. It seems that whenever it enters in idle, the system restarts and gives me BSOD. This is my .dmp report:

 

Microsoft ® Windows Debugger Version 10.0.17763.1 AMD64

Copyright © Microsoft Corporation. All rights reserved.

 

 

Loading Dump File [C:\Users\Razvan Cristolovean\Desktop\MEMORY.DMP]

Kernel Bitmap Dump File: Kernel address space is available, User address space may not be available.

 

Symbol search path is: srv*

Executable search path is:

Windows 8 Kernel Version 9200 MP (4 procs) Free x64

Product: WinNt, suite: TerminalServer SingleUserTS

Built by: 9200.17617.amd64fre.win8_gdr.151230-0600

Machine Name:

Kernel base = 0xfffff803`3e003000 PsLoadedModuleList = 0xfffff803`3e2cfb20

Debug session time: Thu Oct 18 10:53:11.880 2018 (UTC + 3:00)

System Uptime: 0 days 2:01:36.813

Loading Kernel Symbols

...............................................................

................................................................

.....................

Loading User Symbols

 

Loading unloaded module list

.......

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

* *

* Bugcheck Analysis *

* *

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

 

Use !analyze -v to get detailed debugging information.

 

BugCheck 1E, {ffffffffc0000005, 0, 8, 0}

 

Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+14589 )

 

Followup: MachineOwner

---------

 

0: kd> !analyze -v

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

* *

* Bugcheck Analysis *

* *

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

 

KMODE_EXCEPTION_NOT_HANDLED (1e)

This is a very common bugcheck. Usually the exception address pinpoints

the driver/function that caused the problem. Always note this address

as well as the link date of the driver/image that contains this address.

Arguments:

Arg1: ffffffffc0000005, The exception code that was not handled

Arg2: 0000000000000000, The address that the exception occurred at

Arg3: 0000000000000008, Parameter 0 of the exception

Arg4: 0000000000000000, Parameter 1 of the exception

 

Debugging Details:

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

 

 

KEY_VALUES_STRING: 1

 

 

STACKHASH_ANALYSIS: 1

 

TIMELINE_ANALYSIS: 1

 

 

DUMP_CLASS: 1

 

DUMP_QUALIFIER: 401

 

BUILD_VERSION_STRING: 9200.17617.amd64fre.win8_gdr.151230-0600

 

SYSTEM_MANUFACTURER: Gigabyte Technology Co., Ltd.

 

SYSTEM_PRODUCT_NAME: To be filled by O.E.M.

 

SYSTEM_SKU: To be filled by O.E.M.

 

SYSTEM_VERSION: To be filled by O.E.M.

 

BIOS_VENDOR: American Megatrends Inc.

 

BIOS_VERSION: F2

 

BIOS_DATE: 09/01/2015

 

BASEBOARD_MANUFACTURER: Gigabyte Technology Co., Ltd.

 

BASEBOARD_PRODUCT: H110M-S2PV DDR3-CF

 

BASEBOARD_VERSION: x.x

 

DUMP_TYPE: 1

 

BUGCHECK_P1: ffffffffc0000005

 

BUGCHECK_P2: 0

 

BUGCHECK_P3: 8

 

BUGCHECK_P4: 0

 

CPU_COUNT: 4

 

CPU_MHZ: e70

 

CPU_VENDOR: GenuineIntel

 

CPU_FAMILY: 6

 

CPU_MODEL: 5e

 

CPU_STEPPING: 3

 

CPU_MICROCODE: 6,5e,3,0 (F,M,S,R) SIG: 39'00000000 (cache) 39'00000000 (init)

 

DEFAULT_BUCKET_ID: WIN8_DRIVER_FAULT

 

BUGCHECK_STR: 0x1E

 

PROCESS_NAME: System

 

CURRENT_IRQL: 0

 

ANALYSIS_SESSION_HOST: DESKTOP-IRNO21F

 

ANALYSIS_SESSION_TIME: 10-26-2018 00:04:45.0875

 

ANALYSIS_VERSION: 10.0.17763.1 amd64fre

 

TRAP_FRAME: fffff880180905d0 -- (.trap 0xfffff880180905d0)

NOTE: The trap frame does not contain all registers.

Some register values may be zeroed or incorrect.

rax=00000000c0000022 rbx=0000000000000000 rcx=fffffa8005563b11

rdx=0000000000000001 rsi=0000000000000000 rdi=0000000000000000

rip=0000000000000000 rsp=fffff88018090760 rbp=fffff880c0000010

r8=0000000000000000 r9=fffff8a000005760 r10=fffffa800463d930

r11=fffffa8005563b10 r12=0000000000000000 r13=0000000000000000

r14=0000000000000000 r15=0000000000000000

iopl=0 nv up ei ng nz na pe nc

00000000`00000000 ?? ???

Resetting default scope

 

IP_IN_FREE_BLOCK: 0

 

LAST_CONTROL_TRANSFER: from fffff8033e1dde49 to fffff8033e05d140

 

STACK_TEXT:

fffff880`1808fd28 fffff803`3e1dde49 : 00000000`0000001e ffffffff`c0000005 00000000`00000000 00000000`00000008 : nt!KeBugCheckEx

fffff880`1808fd30 fffff803`3e05c542 : fffffa80`05e19820 00000000`00000000 fffff880`18090568 00000000`00000000 : nt! ?? ::FNODOBFM::`string'+0x14589

fffff880`180903f0 fffff803`3e05acba : 00000000`00000008 00000000`00000000 00000000`00f80000 fffff880`180905d0 : nt!KiExceptionDispatch+0xc2

fffff880`180905d0 00000000`00000000 : 00000000`00000000 00000000`00000000 fffffa80`07782000 fffff8a0`01df4ab0 : nt!KiPageFault+0x23a

 

 

THREAD_SHA1_HASH_MOD_FUNC: 9041c912964ff700ac617b24c2c708d61106b1d9

 

THREAD_SHA1_HASH_MOD_FUNC_OFFSET: 1b224c49bf8eedade59bd133c697f2a52dba36bc

 

THREAD_SHA1_HASH_MOD: d084f7dfa548ce4e51810e4fd5914176ebc66791

 

FOLLOWUP_IP:

nt! ?? ::FNODOBFM::`string'+14589

fffff803`3e1dde49 cc int 3

 

FAULT_INSTR_CODE: 78868bcc

 

SYMBOL_STACK_INDEX: 1

 

SYMBOL_NAME: nt! ?? ::FNODOBFM::`string'+14589

 

FOLLOWUP_NAME: MachineOwner

 

MODULE_NAME: nt

 

IMAGE_NAME: ntkrnlmp.exe

 

DEBUG_FLR_IMAGE_TIMESTAMP: 5683e832

 

IMAGE_VERSION: 6.2.9200.17617

 

STACK_COMMAND: .thread ; .cxr ; kb

 

BUCKET_ID_FUNC_OFFSET: 14589

 

FAILURE_BUCKET_ID: 0x1E_nt!_??_::FNODOBFM::_string_

 

BUCKET_ID: 0x1E_nt!_??_::FNODOBFM::_string_

 

PRIMARY_PROBLEM_CLASS: 0x1E_nt!_??_::FNODOBFM::_string_

 

TARGET_TIME: 2018-10-18T07:53:11.000Z

 

OSBUILD: 9200

 

OSSERVICEPACK: 17617

 

SERVICEPACK_NUMBER: 0

 

OS_REVISION: 0

 

SUITE_MASK: 272

 

PRODUCT_TYPE: 1

 

OSPLATFORM_TYPE: x64

 

OSNAME: Windows 8

 

OSEDITION: Windows 8 WinNt TerminalServer SingleUserTS

 

OS_LOCALE:

 

USER_LCID: 0

 

OSBUILD_TIMESTAMP: 2015-12-30 16:20:34

 

BUILDDATESTAMP_STR: 151230-0600

 

BUILDLAB_STR: win8_gdr

 

BUILDOSVER_STR: 6.2.9200.17617.amd64fre.win8_gdr.151230-0600

 

ANALYSIS_SESSION_ELAPSED_TIME: 67d

 

ANALYSIS_SOURCE: KM

 

FAILURE_ID_HASH_STRING: km:0x1e_nt!_??_::fnodobfm::_string_

 

FAILURE_ID_HASH: {9e00434f-0111-761e-4d68-b3b5c8ec7243}

 

Followup: MachineOwner

---------

 

Do you think I can get some help? Because it really drives me crazy, being my work system.

 

Thank Tou!

 

Continue reading...

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

×
×
  • Create New...