Question BSOD ntoskrnl.exe+743c0 adress

[Ashckroft]

Hello,

Recently my pc randomly freezes when starting games.

Here is the main error code in the dump file.

Dump File : 050519-17534-01.dmp
Crash Time : 5/5/2019 2:20:15 AM
Bug Check String :
Bug Check Code : 0x00000101
Parameter 1 : 0000000000000031 Parameter 2 : 0000000000000000
Parameter 3 : fffff88002fd4180 Parameter 4 : 0000000000000003
Caused By Driver : ntoskrnl.exe
Caused By Address : ntoskrnl.exe+743c0
File Description : NT Kernel & System
Product Name : Microsoft® Windows® Operating System
Company : Microsoft Corporation
File Version : 6.1.7601.19135 (win7sp1_gdr.160121-1718)
Processor : x64
Crash Address : ntoskrnl.exe+743c0
Stack Address 1 :
Stack Address 2 :
Stack Address 3 :
Computer Name :
Full Path : C:\Windows\Minidump\050519-17534-01.dmp
Processors Count : 4
Major Version : 15
Minor Version : 7601
Dump File Size : 262,144
Dump File Time : 5/5/2019 2:21:02 AM
=


Any suggestions are welcome!

 

[Colif]

Clock watchdog timout is a error called by the CPU but not necessarily caused by it, it could be a driver.

What are specs of PC?

can you go to C:\Windows\Minidump and copy the files from in there to another folder.
Upload the copies from new folder to a fle sharing website and show a link here, we see if dumps can reveal more info for you

ntoskrnl = windows kernel. It sits between hardware and applications, It was blamed but not the cause

 

[Ashckroft]

Clock watchdog timout is a error called by the CPU but not necessarily caused by it, it could be a driver.

What are specs of PC?

can you go to C:\Windows\Minidump and copy the files from in there to another folder.
Upload the copies from new folder to a fle sharing website and show a link here, we see if dumps can reveal more info for you

ntoskrnl = windows kernel. It sits between hardware and applications, It was blamed but not the cause

I am providing DxDiag and the initial crash dump file plus second I received today.

https://files.fm/u/qa589eck

For the moment the PC stopped freezing after changing the RAM form dual channel to single and then back to dual.

 

[Colif]

Try running memtesst86 on each of your ram sticks, one stick at a time, up to 8 passes. Only error count you want is 0, any higher could be cause of the BSOD. Remove/replace ram sticks with errors.

I will get someone to convert dumps and we see what they show.

 

[gardenman]

Hi, I ran the dump files through the debugger and got the following information: https://pste.eu/p/z6g2.html

File information:	050519-17534-01_(1).dmp (May 4 2019 - 19:20:15)
Bugcheck:	CLOCK_WATCHDOG_TIMEOUT (101)
Probably caused by:	Unknown_Image (Process: ?)
Uptime:	0 Day(s), 0 Hour(s), 09 Min(s), and 23 Sec(s)

File information:	123101-18766-01_(1).dmp (Dec 31 2001 - 17:00:56)
Bugcheck:	MEMORY_MANAGEMENT (1A)
Probably caused by:	ntkrnlmp.exe (Process: wmpnscfg.exe)
Uptime:	0 Day(s), 0 Hour(s), 00 Min(s), and 36 Sec(s)

Possible Motherboard page: https://www.asus.com/us/Motherboards/M3A78/
You have the latest BIOS already installed.

This information can be used by others to help you. I can't help you with this. Someone else will post with more information. Please wait for additional answers. Good luck.

 

[Colif]

well, PC wasn't on long enough for any drivers to load apart from an AMD driver so thats not going to tell me a lot.

Think I should ignore the 1st error since its from 2001?

that date seems wrong, PC isn't even that old. Taking a 2008 machine back to 2001 would be an achievement.... oh right, I was going to ignore it.

 

[Ashckroft]

well, PC wasn't on long enough for any drivers to load apart from an AMD driver so thats not going to tell me a lot.

Think I should ignore the 1st error since its from 2001?

that date seems wrong, PC isn't even that old. Taking a 2008 machine back to 2001 would be an achievement.... oh right, I was going to ignore it.

I'm gonna re-run memtest again soon.The last time I ran it it showed no error and prime95 also.

The date may be different,because I reset the default settings on BIOS and removed the battery for the CMOS.

Gonna write soon when im home.Thank you guys very much!!

 

[Satan-IR]

I ran the 123101-18766-01_(1).dmp too. It's a 1A bugcheck and the process named it wmpnscfg.exe indeed.

I didn't check is that a Windows Media Sharing service? Do you have Windows Media Sharing enabled and use it?

As colif said earlier, running memtest is a good idea. Do 8 passes or more for each module.

 

[Ashckroft]

I ran the 123101-18766-01_(1).dmp too. It's a 1A bugcheck and the process named it wmpnscfg.exe indeed.

I didn't check is that a Windows Media Sharing service? Do you have Windows Media Sharing enabled and use it?

As colif said earlier, running memtest is a good idea. Do 8 passes or more for each module.

Yes I did actually.

 

[Satan-IR]

I ran the other dump too and in both I see

+0x01c UsedPageTableEntries : ??

This might indeed indicate physically faulty RAM and not as much a faulty driver.

Not saying it's definitely not a driver but I suggest you do memtest with each single RAM module for at least 8 passes.

 

[Ashckroft]

I ran the other dump too and in both I see

+0x01c UsedPageTableEntries : ??

This might indeed indicate physically faulty RAM and not as much a faulty driver.

Not saying it's definitely not a driver but I suggest you do memtest with each single RAM module for at least 8 passes.

I just made the flash USB to run it again will show results soon.