BSOD issue repeating offense

Mar 4, 2018
12
0
10
0
Hi all, my computer has been suffering from BSOD randomly, idle, gaming, web brousing it happens whenever. Please help as i am lost.
 

friedlander.m.s

Upstanding
Feb 16, 2018
76
0
210
27
It's almost always a new device that you installed or a new driver which is incompatible with hardware/software.
Remove any new drivers which were installed and try an older version of the driver.
 
Mar 4, 2018
12
0
10
0
I found iTunes was corrupt and after destroying the program I am hoping that this solves the issue. Thank you for your advice.
 
photos are not useful. you need to provide the actual memory dump file
from c:\windows\minidump directory.


otherwise, you would remove any overclocking software for the CPU and GPU, update the GPU driver from the GPU vendors website. UPdate the motherboard BIOS and motherboard drivers from the motherboard vendors website. (motherboard audio driver can crash GPU drivers)

since one of the error codes was 0xc0000005 you should run memtest86.exe on its own boot image to confirm your bios memory timings and that the memory works as expected.

if this is a older machine, you should blow out the dust from the CPU,gpu and PSU and make sure the fans are all working as expected.
 
Mar 4, 2018
12
0
10
0
Johnbl,

I have removed any and all overcolcking by reseting the bios settings to default prior to this last crash. All drivers and bios versions have been verified to the latest version.
I have run multiple mem tests but unsure what you mean by on its own boot image, like when the computer first posts run the test?

The machine is just about 4yrs old and has been maintained.

How should i upload/view these .dmp files?

Thank you for your help,

Zez
 

PyroMSI

Prominent
May 8, 2017
12
0
510
0
I had the same issue, I tried everything I could, and finally it turned out to be a defective CPU.

I found out when I read the DMP file, and used the !errrec command.

Learn here how to read your DMP file:
https://docs.microsoft.com/en-us/windows-hardware/drivers/debugger/opening-a-crash-dump-file-using-windbg

I dont rlly remember but you have to get the BSOD error string, it looks a bit like this: fffffa80064132c0

learn here how to use commands like !whea and !errrec
https://docs.microsoft.com/en-us/windows-hardware/drivers/debugger/-errrec

This way you could find out what is causing the bsod's.
If you cant figure things out, I suggest that you upload the DMP file somewhere and
post a link to it here.
 
you would copy the files from c:\windows\minidump directory to a cloud server like Microsoft onedrive or google docs. Share the files for public access and post a link.

kernel memory dumps will be stored in c:\windows\memory.dmp file




 
Mar 4, 2018
12
0
10
0
Microsoft (R) Windows Debugger Version 6.11.0001.404 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Windows\MEMORY.DMP]
Kernel Summary Dump File: Only kernel address space is available

Symbol search path is: srv*c:\symbols*http://msdl.microsoft.com/download/symbols
Executable search path is:
Windows 7 Kernel Version 7601 (Service Pack 1) MP (6 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7601.24093.amd64fre.win7sp1_ldr_escrow.180327-2230
Machine Name:
Kernel base = 0xfffff800`03a58000 PsLoadedModuleList = 0xfffff800`03c97c90
Debug session time: Sat Apr 7 00:59:15.285 2018 (GMT-5)
System Uptime: 1 days 18:55:32.033
Loading Kernel Symbols
...............................................................
................................................................
........................................
Loading User Symbols
PEB is paged out (Peb.Ldr = 000007ff`fffdf018). Type ".hh dbgerr001" for details
Loading unloaded module list
..............
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck BE, {fffff8a0012c0fa0, 800000040e803121, fffff8800af53830, b}

PEB is paged out (Peb.Ldr = 000007ff`fffdf018). Type ".hh dbgerr001" for details
PEB is paged out (Peb.Ldr = 000007ff`fffdf018). Type ".hh dbgerr001" for details
Probably caused by : ntkrnlmp.exe ( nt!KiPageFault+44a )

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

this is what the memory dump is reading, does this correlate to a bad stick of memory? I am compiling the dump files in the minidump. will attach shortly
 
you would need to provide the memory dump binary files so that they can be read using a windows debugger.

ie copy the files from c:\windows\minidump directory to a cloud server, share them for public access and post a link.

some bugchecks might require that you turn on verifier functions and provide a kernel memory dump.




 
Mar 4, 2018
12
0
10
0
Microsoft (R) Windows Debugger Version 6.11.0001.404 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.


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

Symbol search path is: srv*https://msdl.microsoft.com/download/symbols
Executable search path is:
Windows 7 Kernel Version 7601 (Service Pack 1) MP (6 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7601.24093.amd64fre.win7sp1_ldr_escrow.180327-2230
Machine Name:
Kernel base = 0xfffff800`03a14000 PsLoadedModuleList = 0xfffff800`03c53c90
Debug session time: Mon Apr 9 01:56:38.317 2018 (GMT-5)
System Uptime: 1 days 4:28:59.117
Loading Kernel Symbols
...............................................................
................................................................
............................................
Loading User Symbols
Loading unloaded module list
..................
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck D1, {2aaaae1d1, 2, 0, fffff880111322c0}

Unable to load image \SystemRoot\system32\DRIVERS\nvlddmkm.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for nvlddmkm.sys
*** ERROR: Module load completed but symbols could not be loaded for nvlddmkm.sys
Probably caused by : nvlddmkm.sys ( nvlddmkm+1202c0 )

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


Another one happened today, I would gladly provide the files but ever time i try and upload them somewhere it doesn't allow it. I will look into it further
 
Mar 4, 2018
12
0
10
0
Figured it out, the PSU was starting to fail. A detailed and lengthy process caused the ram to fail over time during the random generation portion. I upped the amount of voltage the psu was to supply the ram and the issue ceased. New psu installed and all is well
 

ASK THE COMMUNITY

TRENDING THREADS