Jump to content


 


Register a free account to unlock additional features at BleepingComputer.com
Welcome to BleepingComputer, a free community where people like yourself come together to discuss and learn how to use their computers. Using the site is easy and fun. As a guest, you can browse and view the various discussions in the forums, but can not create a new topic or reply to an existing one unless you are logged in. Other benefits of registering an account are subscribing to topics and forums, creating a blog, and having no ads shown anywhere on the site.


Click here to Register a free account now! or read our Welcome Guide to learn how to use this site.

Photo

BSOD windows 10


  • Please log in to reply
2 replies to this topic

#1 Houwitser

Houwitser

  • Members
  • 1 posts
  • OFFLINE
  •  
  • Local time:11:26 AM

Posted 11 December 2017 - 11:42 AM

Hello

can anyone help me with this BSOD-s

I recently bought a new pc and instaled a windows 10 and then problems begins

i updated the drivers with driver booster

i did it memtest everything it's ok

bios is up to date

and sometimes freezes  when doing something or nothing

update 21:55 :new BSOD right now

clock_watchdog_timeout

 

P.S. sorry for my bad english

 

Crash dump directory: C:\WINDOWS\Minidump

Crash dumps are enabled on your computer.

On Mon 12/11/2017 16:58:43 your computer crashed
crash dump file: C:\WINDOWS\Minidump\121117-31640-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x1637D0)
Bugcheck code: 0x4E (0x2, 0x18AAE8, 0x23EFFF, 0x400)
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 appears to be a typical software driver bug and is not likely to be caused by a hardware problem. This might be a case of memory corruption. More often memory corruption happens because of software errors in buggy drivers, not because of faulty RAM modules.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.



On Mon 12/11/2017 16:58:43 your computer crashed
crash dump file: C:\WINDOWS\memory.dmp
This was probably caused by the following module: ntkrnlmp.exe (nt!KeBugCheckEx+0x0)
Bugcheck code: 0x4E (0x2, 0x18AAE8, 0x23EFFF, 0x400)
Error: PFN_LIST_CORRUPT
Bug check description: This indicates that the page frame number (PFN) list is corrupted.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem. This might be a case of memory corruption. More often memory corruption happens because of software errors in buggy drivers, not because of faulty RAM modules.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.






On Mon 12/11/2017 15:30:51 your computer crashed
crash dump file: C:\WINDOWS\Minidump\121117-92328-01.dmp
This was probably caused by the following module: hal.dll (hal+0x26FD)
Bugcheck code: 0xBE (0xFFFF898000002994, 0x8A000000BF400121, 0xFFFF860EA3702870, 0xA)
Error: ATTEMPTED_WRITE_TO_READONLY_MEMORY
file path: C:\WINDOWS\system32\hal.dll
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Hardware Abstraction Layer DLL
Bug check description: This is issued if a driver attempts to write to a read-only memory segment.
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 standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system that cannot be identified at this time.



On Mon 12/11/2017 00:32:50 your computer crashed
crash dump file: C:\WINDOWS\Minidump\121117-23890-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x1637D0)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF802902F708B, 0xFFFF8B0E5C1D3820, 0x0)
Error: SYSTEM_SERVICE_EXCEPTION
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 an exception happened while executing a routine that transitions from non-privileged code to privileged code.
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.

 

 

 

 

 

 

 

 

http://speccy.piriform.com/results/nhFazRDslL8yhwD1ZhS3Oit
 

Attached Files


Edited by Houwitser, 11 December 2017 - 07:06 PM.


BC AdBot (Login to Remove)

 


#2 usasma

usasma

    Still visually handicapped (avatar is memory developed by my Dad


  • BSOD Kernel Dump Expert
  • 25,089 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:Southeastern CT, USA
  • Local time:06:26 AM

Posted 14 December 2017 - 07:13 AM

Sorry for the delay in responding.  I'm having some serious eye problems right now.

Will come back and post more after I shovel some snow (about an hour).


My browser caused a flood of traffic, sio my IP address was banned. Hope to fix it soon. Will get back to posting as soon as Im able.

- John  (my website: http://www.carrona.org/ )**If you need a more detailed explanation, please ask for it. I have the Knack. **  If I haven't replied in 48 hours, please send me a message. My eye problems have recently increased and I'm having difficult reading posts. (23 Nov 2017)FYI - I am completely blind in the right eye and ~30% blind in the left eye.<p>If the eye problems get worse suddenly, I may not be able to respond.If that's the case and help is needed, please PM a staff member for assistance.

#3 usasma

usasma

    Still visually handicapped (avatar is memory developed by my Dad


  • BSOD Kernel Dump Expert
  • 25,089 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:Southeastern CT, USA
  • Local time:06:26 AM

Posted 14 December 2017 - 08:05 AM

I'm back!  :0)

 

Unfortunately it appears that the system has pirated software.
Please get a legitimate copy installed and we'll be glad to help.

Here's suggestions on how to ensure that your version is legitimate:  http://windows.microsoft.com/en-us/windows/genuine

Please be aware that we may not be able to fix it (as the hacks that were done to activate it will cause the OS to behave differently than we expect it to). If that's the case, our efforts to help may just waste your time. Secondly, the forum rules prohibit assisting with pirated software - so the topic would be closed if that is the case.

As a courtesy, I will offer an analysis of your issues using the reports you provided.
I will not answer any questions about the analysis until the system is made legitimate.
If you do make it legitimate, please submit a new set of reports for us to check.

Just FYI, sometimes the owner won't know about this.  So here's 2 scenarios that might ring a bell:
- if they had a "friend" help with the computer - and the "friend" installed a pirated copy.
- or they used a copy that they had from another OEM computer.  The OEM license is tied to the hardware that it came from - so you can't just use it on another system (that means that it's pirated).

And here's the analysis:
 

 

Your UEFI/BIOS (version P2.80) dates from 2016.  Please check at the manufacturer's website to see if there are any UEFI/BIOS updates available for your system.  This is just in case there has been a more recent update.
FYI - W8 and W10 communicate more with the UEFI/BIOS than previous versions of Windows, so it's important to ensure that the UEFI/BIOS is kept up to date (and that outdated UEFI/BIOS' may be the cause of some compatibility issues).

Only 2 Windows Update hotfixes installed.  Most build 16299 (1709/Fall Creators Update) systems have more than this.  Please visit Windows Update and get ALL available Windows Updates.
The actual number is not important.  Rather it's important that you checked manually, installed any available updates, and didn't experience any errors when checking or updating.

 

D: drive and H: drive only have about 6% free space.  Windows likes 15% free space in order to perform stuff "behind the scenes" without adversely affecting the system's performance.  Please free up 15% on ALL hard drives (you can get away with 10% on larger drives and won't notice a large performance penalty).  Low free space can cause BSOD's - but the actual amount depends on the files being used by the system.

The WER section of the MSINFO32 report shows a wide range of BSOD's - to include stack buffer overruns.  These may be symptomatic of an infection - so I suggest that you scan for malware:  Could you be infected?  It's possible that malware has corrupted your current protection, so please try a couple of these, independent scans (from this link: https://www.us-cert.gov/ncas/alerts/TA15-286A ).  This is in case your current protection is compromised by malware and giving false results:

           F-Secure
           https://www.f-secure.com/en/web/home_global/online-scanner (link is external)

           McAfee
           http://www.mcafee.com/uk/downloads/free-tools/stinger.aspx (link is external)

           Microsoft
           http://www.microsoft.com/security/scanner/en-us/default.aspx (link is external)

           Sophos
           https://www.sophos.com/en-us/products/free-tools/virus-removal-tool.aspx (link is external)

           Trend Micro
           http://housecall.trendmicro.com/ (link is external)

    The above are examples only and do not constitute an exhaustive list. The U.S. Government does not endorse or support any particular product or vendor.

 

Out of 7 memory dumps there were 6 different BSOD  (aka STOP or BugCheck) error codes.  The differing error codes are usually symptomatic of a lower level problem within the system. They are usually caused by one of these things (the list is not in any sort of order):
- borked (broken) hardware (several different procedures used to isolate the problem device)
- BIOS issues (check for updates at the motherboard manufacturer's website)
- overclocking/overheating - You'll know if you're overclocking or not. If uncertain we can suggest things to check.
- dirt/dust/hair/fur/crud inside the case.  Blow out the case/vents with canned air (DO NOT use an air compressor or vacuum as they can cause damage to the system)
- missing Windows Updates
- compatibility issues (3rd party hardware/drivers), older systems, or even pirated systems
- overfull hard drives (drives with less than 15% free space)
- low-level driver problems
- or even malware (scanned for when we ask for hardware diagnostics from http://www.carrona.org/initdiag.html or http://www.carrona.org/hwdiag.html ).

Please get a head start on the hardware diagnostics - they are located here:  http://www.carrona.org/hwdiag.html
Please finish ALL of them .

If ALL of them pass, then use this procedure to help isolate the problem device(s):  http://www.carrona.org/strpdown.html

Analysis:
The following is for information purposes only.
The following information contains the relevant information from the blue screen analysis:
**************************Mon Dec 11 18:52:42.811 2017 (UTC - 5:00)**************************
Loading Dump File [C:\Users\john\SysnativeBSODApps\121217-24390-01.dmp]
Windows 10 Kernel Version 16299 MP (8 procs) Free x64
Built by: 16299.15.amd64fre.rs3_release.170928-1534
System Uptime:0 days 0:51:35.547
*** ERROR: Module load completed but symbols could not be loaded for NTFS.sys
*** WARNING: Unable to verify timestamp for win32k.sys
*** ERROR: Module load completed but symbols could not be loaded for win32k.sys
Probably caused by :memory_corruption
BugCheck 101, {18, 0, ffff980182be2180, 2}
BugCheck Info: CLOCK_WATCHDOG_TIMEOUT (101)
Arguments:
Arg1: 0000000000000018, Clock interrupt time out interval in nominal clock ticks.
Arg2: 0000000000000000, 0.
Arg3: ffff980182be2180, The PRCB address of the hung processor.
Arg4: 0000000000000002, The index of the hung processor.
BUGCHECK_STR:  CLOCK_WATCHDOG_TIMEOUT_8_PROC
PROCESS_NAME:  System
FAILURE_BUCKET_ID: MEMORY_CORRUPTION_LARGE
  BIOS Version                  P2.80
  BIOS Release Date             05/31/2016
  Manufacturer                  To Be Filled By O.E.M.
  Baseboard Manufacturer        ASRock
  Product Name                  To Be Filled By O.E.M.
  Baseboard Product             970 Pro3 R2.0
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
**************************Mon Dec 11 18:00:32.342 2017 (UTC - 5:00)**************************
Loading Dump File [C:\Users\john\SysnativeBSODApps\121217-24656-01.dmp]
Windows 10 Kernel Version 16299 MP (8 procs) Free x64
Built by: 16299.15.amd64fre.rs3_release.170928-1534
System Uptime:0 days 2:08:45.079
*** ERROR: Module load completed but symbols could not be loaded for afd.sys
*** ERROR: Module load completed but symbols could not be loaded for tcpip.sys
*** WARNING: Unable to verify timestamp for rt640x64.sys
*** ERROR: Module load completed but symbols could not be loaded for rt640x64.sys
*** ERROR: Module load completed but symbols could not be loaded for Wdf01000.sys
*** WARNING: Unable to verify timestamp for win32k.sys
*** ERROR: Module load completed but symbols could not be loaded for win32k.sys
Probably caused by :memory_corruption
BugCheck A, {ffffce8cce62c470, 2, 0, fffff803dda86f03}
BugCheck Info: IRQL_NOT_LESS_OR_EQUAL (a)
Arguments:
Arg1: ffffce8cce62c470, memory referenced
Arg2: 0000000000000002, IRQL
Arg3: 0000000000000000, bitfield :
    bit 0 : value 0 = read operation, 1 = write operation
    bit 3 : value 0 = not an execute operation, 1 = execute operation (only on chips which support this level of status)
Arg4: fffff803dda86f03, address which referenced memory
BUGCHECK_STR:  AV
DEFAULT_BUCKET_ID:  CODE_CORRUPTION
PROCESS_NAME:  System
FAILURE_BUCKET_ID: MEMORY_CORRUPTION_ONE_BYTE
  BIOS Version                  P2.80
  BIOS Release Date             05/31/2016
  Manufacturer                  To Be Filled By O.E.M.
  Baseboard Manufacturer        ASRock
  Product Name                  To Be Filled By O.E.M.
  Baseboard Product             970 Pro3 R2.0
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
**************************Mon Dec 11 15:51:07.482 2017 (UTC - 5:00)**************************
Loading Dump File [C:\Users\john\SysnativeBSODApps\121117-57187-01.dmp]
Windows 10 Kernel Version 16299 MP (8 procs) Free x64
Built by: 16299.15.amd64fre.rs3_release.170928-1534
System Uptime:0 days 4:51:52.234
Probably caused by :memory_corruption
BugCheck 101, {18, 0, ffffb101fec79180, 3}
BugCheck Info: CLOCK_WATCHDOG_TIMEOUT (101)
Arguments:
Arg1: 0000000000000018, Clock interrupt time out interval in nominal clock ticks.
Arg2: 0000000000000000, 0.
Arg3: ffffb101fec79180, The PRCB address of the hung processor.
Arg4: 0000000000000003, The index of the hung processor.
BUGCHECK_STR:  CLOCK_WATCHDOG_TIMEOUT_8_PROC
PROCESS_NAME:  uTorrent.exe
FAILURE_BUCKET_ID: MEMORY_CORRUPTION_STRIDE
  BIOS Version                  P2.80
  BIOS Release Date             05/31/2016
  Manufacturer                  To Be Filled By O.E.M.
  Baseboard Manufacturer        ASRock
  Product Name                  To Be Filled By O.E.M.
  Baseboard Product             970 Pro3 R2.0
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
The rest of the memory dump summaries are hidden in the Spoiler tag below.  Click on "Show" to reveal them.

Spoiler



3rd Party Drivers:
The following is for information purposes only.
My recommendations were given above. The drivers that follow belong to software or devices that were not developed by Microsoft.  You can find links to the driver information and where to update the drivers in the section after the code box:

**************************Mon Dec 11 18:52:42.811 2017 (UTC - 5:00)**************************
MpKsl5f5559a3.sys           Mon Feb 27 20:54:41 1989 (2409FBE1)
MpKsl633c77a4.sys           Mon Feb 27 20:54:41 1989 (2409FBE1)
MpKsl2cef6e6e.sys           Mon Feb 27 20:54:41 1989 (2409FBE1)
amdide64.sys                Tue Dec  4 04:49:28 2012 (50BDC728)
HWiNFO64A.SYS               Tue Mar 31 05:51:32 2015 (551A6E24)
BazisVirtualCDBus.sys       Sat Sep 26 22:51:28 2015 (560759B0)
nvhda64v.sys                Thu Sep 14 05:55:42 2017 (59BA521E)
nvvad64v.sys                Tue Sep 19 04:38:04 2017 (59C0D76C)
rt640x64.sys                Tue Oct  3 04:31:47 2017 (59D34AF3)
nvlddmkm.sys                Fri Oct 27 11:49:39 2017 (59F35593)
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
**************************Mon Dec 11 18:00:32.342 2017 (UTC - 5:00)**************************
MpKslbb23baad.sys           Mon Feb 27 20:54:41 1989 (2409FBE1)
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
**************************Sun Dec 10 18:32:50.673 2017 (UTC - 5:00)**************************
MpKsladbe227e.sys           Mon Feb 27 20:54:41 1989 (2409FBE1)


MpKsl5f5559a3.sys - this driver hasn't been added to the DRT as of this run. Please search Google/Bing for the driver if additional information is needed.
MpKsl633c77a4.sys - this driver hasn't been added to the DRT as of this run. Please search Google/Bing for the driver if additional information is needed.
MpKsl2cef6e6e.sys - this driver hasn't been added to the DRT as of this run. Please search Google/Bing for the driver if additional information is needed.
http://www.carrona.org/drivers/driver.php?id=amdide64.sys
http://www.carrona.org/drivers/driver.php?id=HWiNFO64A.SYS
http://www.carrona.org/drivers/driver.php?id=BazisVirtualCDBus.sys
http://www.carrona.org/drivers/driver.php?id=nvhda64v.sys
http://www.carrona.org/drivers/driver.php?id=nvvad64v.sys
http://www.carrona.org/drivers/driver.php?id=rt640x64.sys
http://www.carrona.org/drivers/driver.php?id=nvlddmkm.sys
MpKslbb23baad.sys - this driver hasn't been added to the DRT as of this run. Please search Google/Bing for the driver if additional information is needed.
MpKsladbe227e.sys - this driver hasn't been added to the DRT as of this run. Please search Google/Bing for the driver if additional information is needed.



 

XXXXX


My browser caused a flood of traffic, sio my IP address was banned. Hope to fix it soon. Will get back to posting as soon as Im able.

- John  (my website: http://www.carrona.org/ )**If you need a more detailed explanation, please ask for it. I have the Knack. **  If I haven't replied in 48 hours, please send me a message. My eye problems have recently increased and I'm having difficult reading posts. (23 Nov 2017)FYI - I am completely blind in the right eye and ~30% blind in the left eye.<p>If the eye problems get worse suddenly, I may not be able to respond.If that's the case and help is needed, please PM a staff member for assistance.




0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users