facing different BSODs in my new build pleas someone help

Toggle sidebar Toggle sidebar
G

gautamshrm554

Honorable
Feb 23, 2018
11
0
10,510
System Information (local)
--------------------------------------------------------------------------------

Computer name: DESKTOP-OL8V0RA
Windows version: Windows 10 , 10.0, build: 16299
Windows dir: C:\Windows
Hardware: H110M-S2, Gigabyte Technology Co., Ltd., H110M-S2-CF
CPU: GenuineIntel Intel(R) Pentium(R) CPU G4560 @ 3.50GHz Intel586, level: 6
4 logical processors, active mask: 15
RAM: 8547688448 bytes total

other than this am using 1tb toshiba hdd and 320gb wd blue hdd

and here is the full system specification:- http://speccy.piriform.com/results/HHTnR1Ur86ufrBZOBScEOkt


--------------------------------------------------------------------------------
Crash Dump Analysis
--------------------------------------------------------------------------------

Crash dumps are enabled on your computer.

Crash dump directories:
C:\Windows
C:\Windows\Minidump

On Fri 23-Feb-18 4:46:35 PM your computer crashed or a problem was reported
crash dump file: C:\Windows\Minidump\022318-23171-01.dmp
This was probably caused by the following module: nvlddmkm.sys (0xFFFFF8063AC9873B)
Bugcheck code: 0xD1 (0xFFFFCA8849F784C8, 0x2, 0x0, 0xFFFFF8063AC9873B)
Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
file path: C:\Windows\System32\DriverStore\FileRepository\nv_dispi.inf_amd64_7a39871618b19f06\nvlddmkm.sys
product: NVIDIA Windows Kernel Mode Driver, Version 390.77
company: NVIDIA Corporation
description: NVIDIA Windows Kernel Mode Driver, Version 390.77
Bug check description: This indicates that a kernel-mode driver attempted to access pageable memory at a process IRQL that was too high.
This bug check belongs to the crash dump test that you have performed with WhoCrashed or other software. It means that a crash dump file was properly written out.
A third party driver was identified as the probable root cause of this system error. It is suggested you look for an update for the following driver: nvlddmkm.sys (NVIDIA Windows Kernel Mode Driver, Version 390.77 , NVIDIA Corporation).
Google query: nvlddmkm.sys NVIDIA Corporation DRIVER_IRQL_NOT_LESS_OR_EQUAL



On Fri 23-Feb-18 4:46:35 PM your computer crashed or a problem was reported
crash dump file: C:\Windows\MEMORY.DMP
This was probably caused by the following module: nvlddmkm.sys (0xFFFFF8063AC9873B)
Bugcheck code: 0xD1 (0xFFFFCA8849F784C8, 0x2, 0x0, 0xFFFFF8063AC9873B)
Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
file path: C:\Windows\System32\DriverStore\FileRepository\nv_dispi.inf_amd64_7a39871618b19f06\nvlddmkm.sys
product: NVIDIA Windows Kernel Mode Driver, Version 390.77
company: NVIDIA Corporation
description: NVIDIA Windows Kernel Mode Driver, Version 390.77
Bug check description: This indicates that a kernel-mode driver attempted to access pageable memory at a process IRQL that was too high.
This bug check belongs to the crash dump test that you have performed with WhoCrashed or other software. It means that a crash dump file was properly written out.
A third party driver was identified as the probable root cause of this system error. It is suggested you look for an update for the following driver: nvlddmkm.sys (NVIDIA Windows Kernel Mode Driver, Version 390.77 , NVIDIA Corporation).
Google query: nvlddmkm.sys NVIDIA Corporation DRIVER_IRQL_NOT_LESS_OR_EQUAL



On Fri 23-Feb-18 3:23:20 AM your computer crashed or a problem was reported
crash dump file: C:\Windows\Minidump\022318-23843-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x175430)
Bugcheck code: 0x50 (0xFFFFDE4BC0A56E67, 0x0, 0xFFFFCE2E53E2BE25, 0x2)
Error: PAGE_FAULT_IN_NONPAGED_AREA
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that invalid system memory has been referenced.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.



On Thu 22-Feb-18 8:36:47 PM your computer crashed or a problem was reported
crash dump file: C:\Windows\Minidump\022218-24203-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x175430)
Bugcheck code: 0xF7 (0x178BD143B650, 0x9C45A7E1BB94, 0xFFFF63BA581E446B, 0x0)
Error: DRIVER_OVERRAN_STACK_BUFFER
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that a driver has overrun a stack-based buffer.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.



On Thu 22-Feb-18 6:04:46 PM your computer crashed or a problem was reported
crash dump file: C:\Windows\Minidump\022218-23312-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x175430)
Bugcheck code: 0x19 (0x20, 0xFFFF840044850DC0, 0xFFFF840044850E20, 0x2506001F)
Error: BAD_POOL_HEADER
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that a pool header is corrupt.
This might be a case of memory corruption. This may be because of a hardware issue such as faulty RAM, overheating (thermal issue) or because of a buggy driver. This problem might also be caused because of overheating (thermal issue).
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.



On Thu 22-Feb-18 5:46:27 PM your computer crashed or a problem was reported
crash dump file: C:\Windows\Minidump\022218-24500-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x175430)
Bugcheck code: 0x4E (0x99, 0x10B15E, 0x2, 0x600014FFFFFFF11)
Error: PFN_LIST_CORRUPT
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that the page frame number (PFN) list is corrupted.
This bug check belongs to the crash dump test that you have performed with WhoCrashed or other software. It means that a crash dump file was properly written out.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.
 
Solution
J
both files are from the same bugcheck
all it says is that the file system called a bugchmaeck because it could not read from a particular location.

At this point I would go into control panel and turn off virtual memory, reboot, make sure the hidden c:\pagefile.sys is deleted then turn on the virtual memory to have a new pagefile created. I might also run Microsoft rammap64.exe and go to the menu item empty and empty the working set (just run all of the empty menu items)

all on the assumption that you might have something hidden in your pagefile.sys or in your standby memory.

I would also google about how to make a kernel memory dump file and check the settings for your machine.
Ie make sure there is plenty of pagefile space...
Sort by date Sort by votes
reboot your machine, go to the NVidia website and do a full reinstall of the GPU and GPU sound drivers, reboot the machine again.

go to your motherboard vendors website and find the motherboard sound driver and install the current version

and see if you still get bugchecks.

guessing that you have two causes of the bugchecks
- old driver was copied from the Microsoft driverstore on the local machine did not match the other two drivers for the NVidia card.

- motherboard sound driver could cause a buffer overrun in the gpu sound support driver.

try the updates and delete the old memory dumps, provide new ones if you still get a problem.
the pool corruption and page file list corruption may or may not be related to the audio driver. It is hard to tell, it would not typically cause these errors so you might have another problem going on.
generally to find this type of corruption you would have to change the memory dump type to kernel, then run verifier.exe to check for corruption and have someone look at any produced memory dump.

I would try the other fix attempts first and see if you still bugcheck
 
Upvote -1 Downvote
with the h110 chipset make sure it has the bios update for the newest cpu code. if your power supply is no name or low end it can cuase gpu issue if the 12v rail is not stable...clean. download hardware info turn on logging and sensor see if the 12v rail is holding.
 
Upvote 0 Downvote


sorry for the down vote i clicked accidentally
well i happened to have two audio drivers installed which i corrected but am still getting following BSODs:

On Sat 24-Feb-18 10:55:21 PM your computer crashed or a problem was reported
crash dump file: C:\Windows\Minidump\022418-23109-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x175430)
Bugcheck code: 0x1A (0x61941, 0x138AC80C190, 0xD, 0xFFFFA603C7B17B00)
Error: MEMORY_MANAGEMENT
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that a severe memory management error occurred.
This might be a case of memory corruption. This may be because of a hardware issue such as faulty RAM, overheating (thermal issue) or because of a buggy driver. This problem might also be caused because of overheating (thermal issue).
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.



On Sat 24-Feb-18 10:55:21 PM your computer crashed or a problem was reported
crash dump file: C:\Windows\MEMORY.DMP
This was probably caused by the following module: ntkrnlmp.exe (nt!RtlAvlInsertNodeEx+0x32A1)
Bugcheck code: 0x1A (0x61941, 0x138AC80C190, 0xD, 0xFFFFA603C7B17B00)
Error: MEMORY_MANAGEMENT
Bug check description: This indicates that a severe memory management error occurred.
This might be a case of memory corruption. This may be because of a hardware issue such as faulty RAM, overheating (thermal issue) or because of a buggy driver. This problem might also be caused because of overheating (thermal issue).
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.



On Sat 24-Feb-18 9:17:07 PM your computer crashed or a problem was reported
crash dump file: C:\Windows\Minidump\022418-25343-01.dmp
This was probably caused by the following module: nvlddmkm.sys (0xFFFFF801A828873B)
Bugcheck code: 0x50 (0xFFFF8D0DC6D01048, 0x0, 0xFFFFF801A828873B, 0x2)
Error: PAGE_FAULT_IN_NONPAGED_AREA
file path: C:\Windows\System32\DriverStore\FileRepository\nv_dispi.inf_amd64_7a39871618b19f06\nvlddmkm.sys
product: NVIDIA Windows Kernel Mode Driver, Version 390.77
company: NVIDIA Corporation
description: NVIDIA Windows Kernel Mode Driver, Version 390.77
Bug check description: This indicates that invalid system memory has been referenced.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
A third party driver was identified as the probable root cause of this system error. It is suggested you look for an update for the following driver: nvlddmkm.sys (NVIDIA Windows Kernel Mode Driver, Version 390.77 , NVIDIA Corporation).
Google query: nvlddmkm.sys NVIDIA Corporation PAGE_FAULT_IN_NONPAGED_AREA


 
Upvote 0 Downvote


BIOS is updated to the latest
and am using cooler master 450W power supply
 
Upvote 0 Downvote
the memory management code 0x61941 is not listed in the docs but it might be related to code 0x61940
which is a device becoming unexpectedly disconnected.

this can happen with loose cables or with software driver issues (or firmware)

I have seen this happen for various reasons such as:
- loose sata drive, data cable (the drive cable was actually connecting and disconnecting several times a second)
- bug in BIOS sata port related hotswapping setting. Drive would get slow, the system would reset the drive but the BIOS would not let the drive reconnect.
- bugs in SATA firmware, related to garbage collection, caused the drive to take too long to respond.
- issues where sata drives had no free space.

then there were others related to audio driver, old usb drivers from before 2012 that were responding to usb packets that did not belong to them. you can also have something like a USB mouse that has old firmware in it.

on newer machines try to route a lot of things thru the pci/e so any problem can mess up everything.
(ie usb devices messing up GPU driver. something you would not expect 10 years ago)

the only way to figure these out was to debug a kernel mode memory dump.
and it looks like you have one of these. c:\windows\memory.dmp

you should put it on a cloud server, share it for public access and post a link. I can take a quick look and see if I can see what the problem is.

 
Upvote 0 Downvote


here is the MEMORY.dmp file
https://files.fm/f/25czhv8h
 
Upvote 0 Downvote
just had these recently


On Mon 26-Feb-18 4:37:10 PM your computer crashed or a problem was reported
crash dump file: C:\Windows\Minidump\022618-23671-01.dmp
This was probably caused by the following module: ntfs.sys (0xFFFFF805B171C461)
Bugcheck code: 0x50 (0xFFFF8B09CCE73268, 0x0, 0xFFFFF805B171C461, 0x2)
Error: PAGE_FAULT_IN_NONPAGED_AREA
file path: C:\Windows\system32\drivers\ntfs.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT File System Driver
Bug check description: This indicates that invalid system memory has been referenced.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in a file system driver. Since there is no other responsible driver detected, this could be pointing to a malfunctioning drive or corrupted disk. It's suggested that you run CHKDSK.



On Mon 26-Feb-18 4:37:10 PM your computer crashed or a problem was reported
crash dump file: C:\Windows\MEMORY.DMP
This was probably caused by the following module: ntfs.sys (0xFFFFF805B171C461)
Bugcheck code: 0x50 (0xFFFF8B09CCE73268, 0x0, 0xFFFFF805B171C461, 0x2)
Error: PAGE_FAULT_IN_NONPAGED_AREA
file path: C:\Windows\system32\drivers\ntfs.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT File System Driver
Bug check description: This indicates that invalid system memory has been referenced.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in a file system driver. Since there is no other responsible driver detected, this could be pointing to a malfunctioning drive or corrupted disk. It's suggested that you run CHKDSK.
 
Upvote 0 Downvote
both files are from the same bugcheck
all it says is that the file system called a bugchmaeck because it could not read from a particular location.

At this point I would go into control panel and turn off virtual memory, reboot, make sure the hidden c:\pagefile.sys is deleted then turn on the virtual memory to have a new pagefile created. I might also run Microsoft rammap64.exe and go to the menu item empty and empty the working set (just run all of the empty menu items)

all on the assumption that you might have something hidden in your pagefile.sys or in your standby memory.

I would also google about how to make a kernel memory dump file and check the settings for your machine.
Ie make sure there is plenty of pagefile space, plenty of disk space free. I would move the drives data cable to a different sata controller just in case the problem is with the sata driver. If I had a SSD drive I might look to see if there is a firmware update. for a HDD you might turn off cache writes to the drive, (lazy writes) just in case there is some problem. The ultimate goal would b e to get a readable kernel memory dump file.

you might also run processor diagnostic tests from the cpu vendors website.

you might download and run crystaldiskinfo.exe and read the SMART error report from each drive to see if the drive is reporting errors.




 
Upvote 0 Downvote
Solution
You must log in or register to reply here.

TRENDING THREADS

Latest posts

Moderators online

Share this page

COMPANY
RESOURCES
FOLLOW
Top Bottom