add arrow-down arrow-left arrow-right arrow-up authorcheckmark clipboard combo comment delete discord dots drag-handle dropdown-arrow errorfacebook history inbox instagram issuelink lock markup-bbcode markup-html markup-pcpp markup-cyclingbuilder markup-plain-text markup-reddit menu pin radio-button save search settings share star-empty star-full star-half switch successtag twitch twitter user warningwattage weight youtube

Please Help me; BSOD

mrvino
  • 20 months ago

This is my dump file:

Crash Dump Analysis provided by OSR Open Systems Resources, Inc. (http://www.osr.com) Online Crash Dump Analysis Service See http://www.osronline.com for more information Windows 8 Kernel Version 17134 MP (4 procs) Free x64 Product: WinNt, suite: TerminalServer SingleUserTS Personal Built by: 17134.1.amd64fre.rs4_release.180410-1804 Machine Name: Kernel base = 0xfffff80125296000 PsLoadedModuleList = 0xfffff801256532f0 Debug session time: Sat Jun 16 14:45:02.638 2018 (UTC - 4:00) System Uptime: 0 days 0:00:03.356


  • *
  • Bugcheck Analysis *
  • *

BAD_SYSTEM_CONFIG_INFO (74) Can indicate that the SYSTEM hive loaded by the osloader/NTLDR was corrupt. This is unlikely, since the osloader will check a hive to make sure it isn't corrupt after loading it. It can also indicate that some critical registry keys and values are not present. (i.e. somebody used regedt32 to delete something that they shouldn't have) Booting from LastKnownGood may fix the problem, but if someone is persistent enough in mucking with the registry they will need to reinstall or use the Emergency Repair Disk. Arguments: Arg1: 0000000000000002, (reserved) Arg2: fffff98bce362970, (reserved) Arg3: 0000000000000002, (reserved) Arg4: ffffffffc000012d, usually the NT status code.

Debugging Details:

TRIAGER: Could not open triage file : e:\dump_analysis\program\triage\modclass.ini, error 2

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: WIN8_DRIVER_FAULT

BUGCHECK_STR: 0x74

PROCESS_NAME: Registry

CURRENT_IRQL: 0

LAST_CONTROL_TRANSFER: from fffff80125988808 to fffff8012542d680

STACK_TEXT:
fffff98bce362878 fffff80125988808 : 0000000000000074 0000000000000002 fffff98bce362970 0000000000000002 : nt!KeBugCheckEx fffff98bce362880 fffff80125377ae7 : ffffde8c69fdb080 ffffde8c69fdb080 fffff801258cf130 0000000000000002 : nt!CmpLoadHiveThread+0xb96d8 fffff98bce362b10 fffff80125435bc6 : ffffce81619ef180 ffffde8c69fdb080 fffff80125377aa0 0000000000000246 : nt!PspSystemThreadStartup+0x47 fffff98bce362b60 0000000000000000 : fffff98bce363000 fffff98bce35c000 0000000000000000 0000000000000000 : nt!KiStartSystemThread+0x16

STACK_COMMAND: kb

FOLLOWUP_IP: nt!CmpLoadHiveThread+b96d8 fffff801`25988808 cc int 3

SYMBOL_STACK_INDEX: 1

SYMBOL_NAME: nt!CmpLoadHiveThread+b96d8

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: nt

IMAGE_NAME: ntkrnlmp.exe

DEBUG_FLR_IMAGE_TIMESTAMP: 5b015ac2

FAILURE_BUCKET_ID: X64_0x74_nt!CmpLoadHiveThread+b96d8

BUCKET_ID: X64_0x74_nt!CmpLoadHiveThread+b96d8

Followup: MachineOwner

Furthermore this is what is located in my Mini dump folder: 061618-306984-01.dmp

Also, When I run trouble shooter for drivers it says that:

KabyLake PCI Express Root Port #10 - A2B1 needs updating but the Intel driver and stability says there is no further updating When I run Fallout 4 it crashes now and from time to time I notice a small screen flickering when my computer is going A Wall.

Any help would be greatly appreciated

I updated my amd r9 fury graphics card drivers and intel says everything is fine. Only when I reboot the BSOD pops up and I can still use my computer normally.

Things Im noticing: My GPu clock is flucuating alot while the temp stays relatively low. CPU temp also stays pretty good. even while gaming.

My computer is very dusty on the inside and I will be cleaning it out soon with dust spray hopefully that works!

Oh and this is my new dump file with second crash which was most recent after driver updates:

Crash Dump Analysis provided by OSR Open Systems Resources, Inc. (http://www.osr.com) Online Crash Dump Analysis Service See http://www.osronline.com for more information Windows 8 Kernel Version 17134 MP (4 procs) Free x64 Product: WinNt, suite: TerminalServer SingleUserTS Personal Machine Name: Kernel base = 0xfffff80126401000 PsLoadedModuleList = 0xfffff801267bb1f0 Debug session time: Sat Jun 16 16:16:23.978 2018 (UTC - 4:00) System Uptime: 0 days 0:00:07.697


  • *
  • Bugcheck Analysis *
  • *

WINLOGON_FATAL_ERROR (c000021a) The Winlogon process terminated unexpectedly. Arguments: Arg1: ffff9b0768cd9d10, String that identifies the problem. Arg2: ffffffffc000009a, Error Code. Arg3: ffff9b0768868660 Arg4: 0000000000000000

Debugging Details:

----- ETW minidump data unavailable-----TRIAGER: Could not open triage file : e:\dump_analysis\program\triage\modclass.ini, error 2

ERROR_CODE: (NTSTATUS) 0xc000021a - {Fatal System Error} The %hs system process terminated unexpectedly with a status of 0x%08x (0x%08x 0x%08x). The system has been shut down.

EXCEPTION_CODE: (NTSTATUS) 0xc000021a - {Fatal System Error} The %hs system process terminated unexpectedly with a status of 0x%08x (0x%08x 0x%08x). The system has been shut down.

EXCEPTION_PARAMETER1: ffff9b0768cd9d10

EXCEPTION_PARAMETER2: ffffffffc000009a

EXCEPTION_PARAMETER3: ffff9b0768868660

EXCEPTION_PARAMETER4: 0

ADDITIONAL_DEBUG_TEXT: Verification of a KnownDLL failed.

BUGCHECK_STR: 0xc000021a_c000009a

DEFAULT_BUCKET_ID: WIN8_DRIVER_FAULT

PROCESS_NAME: smss.exe

CURRENT_IRQL: 0

BAD_PAGES_DETECTED: 15281

LAST_CONTROL_TRANSFER: from fffff801268948b4 to fffff80126599330

STACK_TEXT:
ffffd4883db8a4a8 fffff801268948b4 : 000000000000004c 00000000c000021a ffffd4883df1a2f0 ffffc308383b0230 : nt!KeBugCheckEx ffffd4883db8a4b0 fffff8012688c556 : ffffd4883db8a5d0 ffffd4883db8a570 ffffffff8000052c ffffd4883db8a5d0 : nt!PopGracefulShutdown+0x294 ffffd4883db8a4f0 fffff8012688511c : 0000000000000301 fffff80100000006 0000000000000004 000000000002001f : nt!PopTransitionSystemPowerStateEx+0xc386 ffffd4883db8a5b0 fffff801265a9943 : fffff801267dc000 fffff80126473c21 0000000000000010 0000000000000082 : nt!NtSetSystemPowerState+0x4c ffffd4883db8a780 fffff8012659cd50 : fffff80126ad8c4d 0000000000000000 00000000c0000004 ffffc3083401a6c0 : nt!KiSystemServiceCopyEnd+0x13 ffffd4883db8a918 fffff80126ad8c4d : 0000000000000000 00000000c0000004 ffffc3083401a6c0 ffffc3083401a680 : nt!KiServiceLinkage ffffd4883db8a920 fffff801269f43f9 : 0000000000000000 ffffc30833a97360 ffffc3083401a580 0000000000000000 : nt!PopIssueActionRequest+0xe473d ffffd4883db8a9e0 fffff801264fb30b : 0000000000000001 0000000000000002 ffffc30833a97300 0000000000000000 : nt!PopPolicyWorkerAction+0x69 ffffd4883db8aa50 fffff80126443315 : ffffc3083401a580 fffff801264fb290 ffffc30833a97360 fffff801267dd8a0 : nt!PopPolicyWorkerThread+0x7b ffffd4883db8aa80 fffff801264e5cb7 : ffffc3083401a580 0000000000000080 ffffc30833aeb440 ffffc3083401a580 : nt!ExpWorkerThread+0xf5 ffffd4883db8ab10 fffff801265a07d6 : ffffac017d3ef180 ffffc3083401a580 fffff801264e5c70 01d3ebf100740078 : nt!PspSystemThreadStartup+0x47 ffffd4883db8ab60 0000000000000000 : ffffd4883db8b000 ffffd4883db84000 0000000000000000 0000000000000000 : nt!KiStartSystemThread+0x16

STACK_COMMAND: kb

SYMBOL_NAME: PAGE_NOT_ZERO

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: Unknown_Module

IMAGE_NAME: Unknown_Image

DEBUG_FLR_IMAGE_TIMESTAMP: 0

BUCKET_ID: PAGE_NOT_ZERO

Followup: MachineOwner

*** Memory manager detected 86657 instance(s) of page corruption, target is likely to have memory corruption.

Comments

  • 20 months ago
  • 2 points

Whoa, that is a lot of information.

This looks like a software issue, with all of that debugging info. It could be corrupt RAM files, bad drivers, or even a virus. A hardware issue is not very likely. Boot into Safe mode and delete all of the drivers and programs, then re-install only the bare-bone ones. If the BSOD happens again, Slot in your Windows installation DVD/USB flash drive, and restore your system to a point before your system was crashing. This should solve the problem. If not, Reinstall Windows. If all of this doesn't fix the problem, a hardware issue is very likely; the RAM or motherboard should be the culprit.

[comment deleted by staff]

Sort

add arrow-down arrow-left arrow-right arrow-up authorcheckmark clipboard combo comment delete discord dots drag-handle dropdown-arrow errorfacebook history inbox instagram issuelink lock markup-bbcode markup-html markup-pcpp markup-cyclingbuilder markup-plain-text markup-reddit menu pin radio-button save search settings share star-empty star-full star-half switch successtag twitch twitter user warningwattage weight youtube