Windows 10: Random BSOD - First BSOD after windows format

I got a bsod 4 days after a fresh windows installation. For many months I have been trying to figure out a kernel41 error with no bugcheck that would intermittently restart either idle or under stress, more so could take a month to restart or do it twice a day --- Background.

Fastforward to my fresh install. My PC no longer Kernel 41's like that and I finally got a dump file. I was hoping some experienced minds could shed some insight on what it could point to. Below is the entire bsod.

-----

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


Loading Dump File [C:\Windows\MEMORY.DMP]
Kernel Bitmap Dump File: Kernel address space is available, User address space may not be available.


************* Path validation summary **************
Response Time (ms) Location
Deferred SRV*C:\Windows\symbol_cache*Symbol information
Symbol search path is: SRV*C:\Windows\symbol_cache*Symbol information
Executable search path is:
Windows 10 Kernel Version 16299 MP (8 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 16299.15.amd64fre.rs3_release.170928-1534
Machine Name:
Kernel base = 0xfffff803`d521a000 PsLoadedModuleList = 0xfffff803`d5581110
Debug session time: Fri Mar 9 13:58:40.040 2018 (UTC - 5:00)
System Uptime: 2 days 18:19:37.750
Loading Kernel Symbols
...............................................................
................................................................
................................................................
.............
Loading User Symbols
PEB is paged out (Peb.Ldr = 00000000`00327018). Type ".hh dbgerr001" for details
Loading unloaded module list
............
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 50, {fffff80300000000, 10, fffff80300000000, 2}

Probably caused by : memory_corruption ( nt!MiSystemFault+142feb )

Followup: MachineOwner
---------

4: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

PAGE_FAULT_IN_NONPAGED_AREA (50)
Invalid system memory was referenced. This cannot be protected by try-except.
Typically the address is just plain bad or it is pointing at freed memory.
Arguments:
Arg1: fffff80300000000, memory referenced.
Arg2: 0000000000000010, value 0 = read operation, 1 = write operation.
Arg3: fffff80300000000, If non-zero, the instruction address which referenced the bad memory
address.
Arg4: 0000000000000002, (reserved)

Debugging Details:
------------------


DUMP_CLASS: 1

DUMP_QUALIFIER: 401

BUILD_VERSION_STRING: 16299.15.amd64fre.rs3_release.170928-1534

SYSTEM_MANUFACTURER: MSI

SYSTEM_PRODUCT_NAME: MS-7A59

SYSTEM_SKU: Default string

SYSTEM_VERSION: 1.0

BIOS_VENDOR: American Megatrends Inc.

BIOS_VERSION: 1.90

BIOS_DATE: 01/30/2018

BASEBOARD_MANUFACTURER: MSI

BASEBOARD_PRODUCT: Z270 SLI PLUS (MS-7A59)

BASEBOARD_VERSION: 1.0

DUMP_TYPE: 1

BUGCHECK_P1: fffff80300000000

BUGCHECK_P2: 10

BUGCHECK_P3: fffff80300000000

BUGCHECK_P4: 2

READ_ADDRESS: fffff80300000000

FAULTING_IP:
+0
fffff803`00000000 ?? ???

MM_INTERNAL_CODE: 2

CPU_COUNT: 8

CPU_MHZ: 1068

CPU_VENDOR: GenuineIntel

CPU_FAMILY: 6

CPU_MODEL: 9e

CPU_STEPPING: 9

CPU_MICROCODE: 6,9e,9,0 (F,M,S,R) SIG: 70'00000000 (cache) 70'00000000 (init)

DEFAULT_BUCKET_ID: WIN8_DRIVER_FAULT

BUGCHECK_STR: AV

PROCESS_NAME: MSIAfterburner.exe

CURRENT_IRQL: 0

ANALYSIS_SESSION_HOST: DESKTOP-LIEMFR6

ANALYSIS_SESSION_TIME: 03-10-2018 03:50:01.0731

ANALYSIS_VERSION: 10.0.16299.91 amd64fre

TRAP_FRAME: ffffaa0c642ce6e0 -- (.trap 0xffffaa0c642ce6e0)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=0000000000000000 rbx=0000000000000000 rcx=0000000000000011
rdx=ffffd982701f9880 rsi=0000000000000000 rdi=0000000000000000
rip=fffff80300000000 rsp=ffffaa0c642ce870 rbp=ffffd982701f9860
r8=ffffaa0c642ce878 r9=7fffd9823a28f2e8 r10=7ffffffffffffffc
r11=ffffaa0c642ce8e0 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0 nv up ei ng nz na po nc
fffff803`00000000 ?? ???
Resetting default scope

LAST_CONTROL_TRANSFER: from fffff803d53c55db to fffff803d538f430

FAILED_INSTRUCTION_ADDRESS:
+0
fffff803`00000000 ?? ???

STACK_TEXT:
ffffaa0c`642ce468 fffff803`d53c55db : 00000000`00000050 fffff803`00000000 00000000`00000010 ffffaa0c`642ce6e0 : nt!KeBugCheckEx
ffffaa0c`642ce470 fffff803`d5283fad : 00000000`00000010 fffff803`00000000 ffffaa0c`642ce6e0 ffffaa0c`642ce610 : nt!MiSystemFault+0x142feb
ffffaa0c`642ce510 fffff803`d539e54e : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!MmAccessFault+0x23d
ffffaa0c`642ce6e0 fffff803`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiPageFault+0x40e
ffffaa0c`642ce870 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0xfffff803`00000000


THREAD_SHA1_HASH_MOD_FUNC: 35852f70c1fb96d682b5bd0e931cc10c7b9fe1fe

THREAD_SHA1_HASH_MOD_FUNC_OFFSET: 8ad769b8d9deb49e62404f38e2d95fc17d23cc75

THREAD_SHA1_HASH_MOD: d084f7dfa548ce4e51810e4fd5914176ebc66791

FOLLOWUP_IP:
nt!MiSystemFault+142feb
fffff803`d53c55db cc int 3

FAULT_INSTR_CODE: 8a8d4dcc

SYMBOL_STACK_INDEX: 1

SYMBOL_NAME: nt!MiSystemFault+142feb

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: nt

DEBUG_FLR_IMAGE_TIMESTAMP: 5a8e0c50

STACK_COMMAND: .thread ; .cxr ; kb

IMAGE_NAME: memory_corruption

BUCKET_ID_FUNC_OFFSET: 142feb

FAILURE_BUCKET_ID: AV_INVALID_BAD_IP_nt!MiSystemFault

BUCKET_ID: AV_INVALID_BAD_IP_nt!MiSystemFault

PRIMARY_PROBLEM_CLASS: AV_INVALID_BAD_IP_nt!MiSystemFault

TARGET_TIME: 2018-03-09T18:58:40.000Z

OSBUILD: 16299

OSSERVICEPACK: 0

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: 2018-02-21 19:18:24

BUILDDATESTAMP_STR: 170928-1534

BUILDLAB_STR: rs3_release

BUILDOSVER_STR: 10.0.16299.15.amd64fre.rs3_release.170928-1534

ANALYSIS_SESSION_ELAPSED_TIME: a40

ANALYSIS_SOURCE: KM

FAILURE_ID_HASH_STRING: km:av_invalid_bad_ip_nt!misystemfault

FAILURE_ID_HASH: {48ad9531-e3f8-1044-fc5f-d917677674c7}

Followup: MachineOwner


I have attached the .zip file as requested per the rules.

I would appreciate any and all help with this. I am in no way familiar with BSOD reading.

If I left out anything please let me know so I can update. Thank you in advance.

:)

 

help with BSOD KMODE_EXCEPTION_NOT_HANDLED intelppm.sys+2140

Hello, after i upgraded from windows 7 to windows 10, i am getting those random BSOD screens. First i thought it was my usb wifi adapter, cause it was supported only for win 7 up, but after upgrade i am still getting those BSOD errors. Can anyone help me
where is the problem ? There are dump files, just bother with the last one from 7.8.2015 - that is the new after USB wifi adapter changed.

Free File Hosting - Online Storage; Upload Mp3, Videos, Music. Backup Files

 

Not able to install Windows 10 after a BSOD stop code

I have ran into one of the craziest error with Windows 10. Long story, short. After a random BSOD with random stop code error and infinite Loop sessions, I was not able to resolve my issue with all the provide information I found online. So I decide to wipe
my drive clean and do a clean install of windows 10. Even after with the drive formatted, I still got the BSOD and stop code errors....****? How is that possible? Went out and got a new drive, same issue. Reformatted my USB flash with Windows 10 media creation
tool, same issue. Used a new flash drive, same issue. Anyone have any suggestions? Virus.? Hardware.?Bios.? Any help will do.

thanks

 

Hi necronikka ,

Welcome to Ten Forums BSOD forum.

Please update the specs in the "My Computer" section:
System Specs - Fill in at Ten Forums:
System Specs - Fill in at Ten Forums Windows 10 Tutorials
In the left corner below in your post you find 'My System Specs'.
After clicking it you can find a link a little below that says 'Update your System Spec', click on this link to get to the page where you can fill in your system specs.
System Info - See Your System Specs - Windows 7 Help Forums


Include PSU. cooler, case, peripherals and anything attached to the computer by wired or wireless (mouse, keyboard, headset, printer, xbox, USB wireless network card, etc.)



1) Open administrative command prompt and copy and paste:
2) sfc /scannow
3) dism /online /cleanup-image /restorehealth
4) chkdsk /scan
5) When these have completed > right click on the top bar or title bar of the administrative command prompt box > left click on edit then select all > right click on the top bar again > left click on edit then copy > paste into the thread
6) uninstall the Nvidia GPU driver using DDU (display driver uninstaller)
7) re-install the Nvidia GPU driver from the Nvidia website
8) make sure that you check the clean install box and if available install the physx driver.
Display Driver Uninstaller Download version 17.0.8.2
Display Driver Uninstaller: How to use - Windows 7 Help Forums
NVIDIA
Download Display Driver Uninstaller - MajorGeeks
9) For any BSOD run the beta log collector and post a new zip into the thread:
log collector v2-beta08.zip
(extract > open)

Code: 3/9/2018 6:59 PM Windows Error Reporting Fault bucket , type 0 Event Name: BlueScreen Response: Not available Cab Id: 0 Problem signature: P1: 50 P2: fffff80300000000 P3: 10 P4: fffff80300000000 P5: 2 P6: 10_0_16299 P7: 0_0 P8: 256_1 P9: P10: Attached files: \\?\C:\WINDOWS\Minidump\030918-6953-01.dmp \\?\C:\WINDOWS\TEMP\WER-10406-0.sysdata.xml \\?\C:\WINDOWS\MEMORY.DMP \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER31AE.tmp.WERInternalMetadata.xml \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER31BE.tmp.csv \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER31CF.tmp.txt These files may be available here: C:\ProgramData\Microsoft\Windows\WER\ReportArchive\Kernel_50_2c68a76b501640ffe352c94ce67f3e4bc27ab132_00000000_cab_176c322b Analysis symbol: Rechecking for solution: 0 Report Id: b4f3beaa-baba-492e-b057-9c5e9c4e1214 Report Status: 2049 Hashed bucket:3/9/2018 6:59 PM Windows Error Reporting Fault bucket , type 0 Event Name: BlueScreen Response: Not available Cab Id: 0 Problem signature: P1: 50 P2: fffff80300000000 P3: 10 P4: fffff80300000000 P5: 2 P6: 10_0_16299 P7: 0_0 P8: 256_1 P9: P10: Attached files: \\?\C:\WINDOWS\Minidump\030918-6953-01.dmp \\?\C:\WINDOWS\TEMP\WER-10406-0.sysdata.xml \\?\C:\WINDOWS\MEMORY.DMP \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER31AE.tmp.WERInternalMetadata.xml \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER31BE.tmp.csv \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER31CF.tmp.txt These files may be available here: C:\ProgramData\Microsoft\Windows\WER\ReportQueue\Kernel_50_2c68a76b501640ffe352c94ce67f3e4bc27ab132_00000000_032831ce Analysis symbol: Rechecking for solution: 0 Report Id: b4f3beaa-baba-492e-b057-9c5e9c4e1214 Report Status: 4 Hashed bucket:[/quote]

 

Hi,

please remove those tools. They are known for causing bluescreens:

MSI Afterburner
NZXT CAM

Since "MSIAfterburner.exe" was the main process at bsod, please revert all program settings (also any OC settings) in MSI Afterburner back to stock.

Read carefully before proceeding.



Warning If you're overclocking your system, revert back to stock clocks now.

Code: 0x00000050: PAGE_FAULT_IN_NONPAGED_AREA (2018-03-09 19:58:40) [Windows 10] CAUSED BY: memory_corruption nvlddmkm.sys [2018-02-23] * nVidia Video drivers * => Download Drivers | NVIDIA PROCESS: MSIAfterburner.exe[/quote]

 

[/quote] I redid my system specs per your instruction. I have already done DDU in the past as well with no luck. I have not done all of the other things yet, but when I was about to hop back onto my PC when I woke up, I got another Kernel 51, this time with no BSOD at all again. Just restarted itself back to the welcome screen.

 

Code: 0x00000050: PAGE_FAULT_IN_NONPAGED_AREA (2018-03-09 19:58:40) [Windows 10] CAUSED BY: memory_corruption nvlddmkm.sys [2018-02-23] * nVidia Video drivers * => Download Drivers | NVIDIA PROCESS: MSIAfterburner.exe[/quote] That was the first bluescreen I ever got, I did notice that process was one of the issues. I did get another Kernel 41 today that didn't generate a blue screen though. As far as overclocking, my cpu has the turbo boost I can disable but my GPU overclocks itself based on temperature and all that, through research I found I can't turn that off.

 

1) Please run the beta log collector and post a zip into the thread:
log collector v2-beta08.zip
(extract > open)

2) In the left lower corner search type: system or system control > open system control panel > on the left pane click advanced system settings
a) > on the advanced tab under startup and recovery > click settings > post an image of the startup and recovery into the thread.
b) > on the advanced tab under performance > click on settings > under performance options > click on the advanced tab > under virtual memory > click on change > post an image of the virtual memory tab into the thread
3) If the computer has Ccleaner > click windows tab > scroll down to system and advanced > post an image into the thread
4) When available please update the progress with each of the steps in post #2
5) For any BSOD please run the beta log collector and post an new zip into the thread

 

Apologies, I could not figure out how to edit my steps under post #2, so I'm quoting a reply again :/ .

Here are all the attached images you requested, this is a fresh install of windows since 4 days ago so I do not have CCcleaner.

Also I did go ahead and disable to default turbo mode for the CPU in the BIOS, I didn't want to overclock anything in the first place. I only use afterburner to control the fans to keep my GPU temp under 65 when under stress, even without it this issue occurs though. The gpu clocks itself higher based on temps with something called "GPU BOOST", which there is no way to turn off, but I do not think that's relevent.

I have attached all files you requested.









DESKTOP-LIEMFR6 (2018-03-10 18 51).zip New log file

Thank you so much for assisting me, I have been dealing with this for months and there has never been an issue before I could not isolate.

 

1) For startup and recovery system failure:
a) un-check automatically restart

When automatic restart is checked you may not know if you had a BSOD unless there were opened applications that are no longer open or if you search the logs.

When automatic restart is unchecked you will see the BSOD windows.
On the BSOD windows there will be a bugcheck and there may be a misbehaving driver displayed in the form *.sys
If you see the misbehaving driver > record it and post it into the thread
Always make sure that if you see a BSOD window live that you allow it to complete the 100% so that it creates a BSOD mini or memory dump file.

 

I have unchecked that option per your instruction.

The issue is very intermittent, as the restart kernel 41 I had today could happen tomorrow or a week from now.

I believe the initial BSOD that started this thread is unrelated since afterburner was the culprit and I haven't had a BSOD in 10 months.

When you say bugcheck, are you referring to the event viewer? TLDR the *.sys is a foreign language to me as to where I would locate that info.

You are the best, this is the first time a forum has offered to assist, if you isolate this issue for me in the end, I would be more than happy to donate you cash via paypal or some sort.

--

On a side note in april of last year I got a BSOD, and someone looked at it and it pointed to my GPU, albeit the person who looked has no experience so I cannot verify that as accurate. I work in IT and the DDU side of things I have already done per a co-workers instruction, he is just very busy with kids and the like so troubleshooting with him is spotty.

 

When there is a BSOD they are given a number and a name for classification.
PAGE_FAULT_IN_NONPAGED_AREA (50)
This BSOD had the number 50 and the name: PAGE_FAULT_IN_NONPAGED_AREA
So when you see the BSOD window it may have a different name.
Drivers typically end with .sys
So for some BSOD you may only see the bugcheck name and for other BSOD you may see both.

Once you uninstall the Nvidia GPU using DDU and reinstall a new driver this should fix the BSOD.
Sometimes there are problems with the underlying hardware.
Other times there is another driver that caused the crash and another driver was a bystander.
At this time the first step is to replace the GPU driver and then observer the computer for stability.

 

I see, before I used DDU to remove and reinstall but did not perform the extra steps you provided. I will do so in the coming hour.

 

I also performs the CMD commands (errors were found before installations but none here) but here are the results

Microsoft Windows [Version 10.0.16299.251](c) 2017 Microsoft Corporation. All rights reserved.

- currently entering safe mode for DDU, will post back shortly
--------------------------------

C:\WINDOWS\system32>sfc /scannowBeginning system scan. This process will take some time.Beginning verification phase of system scan.Verification 100% complete.Windows Resource Protection did not find any integrity violations.C:\WINDOWS\system32>dism / online /cleanup-image /restorehealthError: 87DISM doesn't recognize the command-line option "".For more information, refer to the help by running DISM.exe /?.The DISM log file can be found at C:\WINDOWS\Logs\DISM\dism.logC:\WINDOWS\system32>dism /online /cleanup-image /restorehealthDeployment Image Servicing and Management toolVersion: 10.0.16299.15Image Version: 10.0.16299.251[==========================100.0%==========================] The restore operation completed successfully.The operation completed successfully.C:\WINDOWS\system32>chkdsk /scanThe type of the file system is NTFS.Stage 1: Examining basic file system structure ... 348672 file records processed.File verification completed. 6191 large file records processed. 0 bad file records processed.Stage 2: Examining file name linkage ... 357 reparse records processed. 444472 index entries processed.Index verification completed. 0 unindexed files scanned. 0 unindexed files recovered to lost and found. 357 reparse records processed.Stage 3: Examining security descriptors ...Security descriptor verification completed. 47901 data files processed.CHKDSK is verifying Usn Journal... 40822928 USN bytes processed.Usn Journal verification completed.Windows has scanned the file system and found no problems.No further action is required. 487805951 KB total disk space. 105374568 KB in 203205 files. 138196 KB in 47902 indexes. 0 KB in bad sectors. 472947 KB in use by the system. 65536 KB occupied by the log file. 381820240 KB available on disk. 4096 bytes in each allocation unit. 121951487 total allocation units on disk. 95455060 allocation units available on disk.C:\WINDOWS\system32>


---- Edit : Upon removal of drivers in safe mode using DDU, I installed directly from website instead of geforce software. The physx box was already checked and i checked the clean install box as well.

 

Spamming I know, just for purposes of being new to this forum and making sure you catch everything. At this point I have uninstalled and reinstalled the GPU drivers directly from the website instead of through their nvidia software and unchecked the auto restart box from before so something will be generated in the future. I am pretty positive this will happen again soon but at this point software related I suppose it is a waiting game.