Question bsod ntoskrnl.exe+3f72e0 - PLEASE HELP!

Toggle sidebar Toggle sidebar
prosper777

prosper777

Jan 16, 2022
5
1
10
hello. recently i've started having bsod's with error messages like: INTERRUPT_EXCEPTION_NOT_HANDLED, KMODE_EXCEPTION_NOT_HANDLED, and MEMORY_MANAGEMENT. i've done sfc about 2-3 times now and it still happens. i've done ddu and fresh install of the newest graphics card updates for my 6700xt and have done a bios update for my mobo due to having improved memory compatibility. now i have added 16gb more ram to my already 16 with the same timings and whatnot. i think the ram or something else may be the problem. i've seen on forums to post my dump files so here goes. i hope someone can help me find a solution because i would not like to lose my stuff. its very important to my career.

==================================================

Dump File : 011622-8125-01.dmp

Crash Time : 1/16/2022 3:32:16 PM

Bug Check String : INTERRUPT_EXCEPTION_NOT_HANDLED

Bug Check Code : 0x0000003d

Parameter 1 : fffff8051a27fb58 Parameter 2 : fffff8051a27f390

Parameter 3 : 0000000000000000 Parameter 4 : 0000000000000000

Caused By Driver : ntoskrnl.exe

Caused By Address : ntoskrnl.exe+3f72e0

File Description :

Product Name :

Company :

File Version :

Processor : x64

Crash Address : ntoskrnl.exe+3f72e0

Stack Address 1 :

Stack Address 2 :

Stack Address 3 :

Computer Name :

Full Path : C:\WINDOWS\Minidump\011622-8125-01.dmp

Processors Count : 12

Major Version : 15

Minor Version : 19041

Dump File Size : 1,466,220

Dump File Time : 1/16/2022 4:13:50 PM

==================================================

==================================================

Dump File : 011622-12718-01.dmp

Crash Time : 1/16/2022 3:30:02 PM

Bug Check String : KMODE_EXCEPTION_NOT_HANDLED

Bug Check Code : 0x0000001e

Parameter 1 : ffffffffc0000005 Parameter 2 : 0000000000000000

Parameter 3 : 0000000000000008 Parameter 4 : 0000000000000000

Caused By Driver : ucx01000.sys

Caused By Address : ucx01000.sys+28900

File Description :

Product Name :

Company :

File Version :

Processor : x64

Crash Address : ntoskrnl.exe+3f72e0

Stack Address 1 :

Stack Address 2 :

Stack Address 3 :

Computer Name :

Full Path : C:\WINDOWS\Minidump\011622-12718-01.dmp

Processors Count : 12

Major Version : 15

Minor Version : 19041

Dump File Size : 1,738,188

Dump File Time : 1/16/2022 3:31:26 PM

==================================================

==================================================

Dump File : 011622-11750-01.dmp

Crash Time : 1/16/2022 2:43:19 PM

Bug Check String : MEMORY_MANAGEMENT

Bug Check Code : 0x0000001a

Parameter 1 : 0000000000041792 Parameter 2 : ffffa83ffea50308

Parameter 3 : 000a000000000000 Parameter 4 : 0000000000000000

Caused By Driver : ntoskrnl.exe

Caused By Address : ntoskrnl.exe+3f72e0

File Description :

Product Name :

Company :

File Version :

Processor : x64

Crash Address : ntoskrnl.exe+3f72e0

Stack Address 1 :

Stack Address 2 :

Stack Address 3 :

Computer Name :

Full Path : C:\WINDOWS\Minidump\011622-11750-01.dmp

Processors Count : 12

Major Version : 15

Minor Version : 19041

Dump File Size : 1,766,860

Dump File Time : 1/16/2022 2:46:27 PM

==================================================

==================================================

Dump File : 011522-15578-01.dmp

Crash Time : 1/15/2022 11:28:25 PM

Bug Check String : MEMORY_MANAGEMENT

Bug Check Code : 0x0000001a

Parameter 1 : 0000000000061948 Parameter 2 : 0000000000520809

Parameter 3 : 0000000000000001 Parameter 4 : 0000000000520809

Caused By Driver : ntoskrnl.exe

Caused By Address : ntoskrnl.exe+3f72e0

File Description :

Product Name :

Company :

File Version :

Processor : x64

Crash Address : ntoskrnl.exe+3f72e0

Stack Address 1 :

Stack Address 2 :

Stack Address 3 :

Computer Name :

Full Path : C:\WINDOWS\Minidump\011522-15578-01.dmp

Processors Count : 12

Major Version : 15

Minor Version : 19041

Dump File Size : 2,499,204

Dump File Time : 1/15/2022 11:29:47 PM

==================================================

==================================================

Dump File : 011522-10625-01.dmp

Crash Time : 1/15/2022 12:30:55 AM

Bug Check String : KMODE_EXCEPTION_NOT_HANDLED

Bug Check Code : 0x0000001e

Parameter 1 : ffffffffc0000005 Parameter 2 : fffff80549bfc120

Parameter 3 : 0000000000000000 Parameter 4 : ffffffffffffffff

Caused By Driver : ntoskrnl.exe

Caused By Address : ntoskrnl.exe+3f72e0

File Description :

Product Name :

Company :

File Version :

Processor : x64

Crash Address : ntoskrnl.exe+3f72e0

Stack Address 1 :

Stack Address 2 :

Stack Address 3 :

Computer Name :

Full Path : C:\WINDOWS\Minidump\011522-10625-01.dmp

Processors Count : 12

Major Version : 15

Minor Version : 19041

Dump File Size : 2,030,428

Dump File Time : 1/15/2022 12:31:46 AM

==================================================
 
Sort by date Sort by votes
  1. Open Windows File Explore
  2. Navigate to C:\Windows\Minidump
  3. Copy the mini-dump files out onto your Desktop
  4. Do not use Winzip, use the built in facility in Windows
  5. Select those files on your Desktop, right click them and choose 'Send to' - Compressed (zipped) folder
  6. Upload the zip file to the Cloud (OneDrive, DropBox . . . etc.)
  7. Then post a link here to the zip file, so we can take a look for you . . .
 
Upvote 0 Downvote
Colif said:
  1. Open Windows File Explore
  2. Navigate to C:\Windows\Minidump
  3. Copy the mini-dump files out onto your Desktop
  4. Do not use Winzip, use the built in facility in Windows
  5. Select those files on your Desktop, right click them and choose 'Send to' - Compressed (zipped) folder
  6. Upload the zip file to the Cloud (OneDrive, DropBox . . . etc.)
  7. Then post a link here to the zip file, so we can take a look for you . . .
Click to expand...
there are no files in that folder you told me to go to.
 
Upvote 0 Downvote
Colif said:
  1. Open Windows File Explore
  2. Navigate to C:\Windows\Minidump
  3. Copy the mini-dump files out onto your Desktop
  4. Do not use Winzip, use the built in facility in Windows
  5. Select those files on your Desktop, right click them and choose 'Send to' - Compressed (zipped) folder
  6. Upload the zip file to the Cloud (OneDrive, DropBox . . . etc.)
  7. Then post a link here to the zip file, so we can take a look for you . . .
Click to expand...
maybe you can read it from the dump files i got from bluescreenviewer. i'll attach a link, but i think it was my new ram that is faulty after doing a memtest86 and having errors then taking it out and having 0 errors and no more bsod. please go thru the dump files if have to time to see if thats the problem or if theres more i need to fix... thank you

https://www.dropbox.com/s/ynp4onrxhzgkx1f/bsod jan. 16.rar?dl=0
 
Upvote 0 Downvote
The minidump files were there previously as you stated above:
prosper777 said:
Full Path : C:\WINDOWS\Minidump\011622-12718-01.dmp
Click to expand...
prosper777 said:
Full Path : C:\WINDOWS\Minidump\011622-11750-01.dmp
Click to expand...
prosper777 said:
Full Path : C:\WINDOWS\Minidump\011522-15578-01.dmp
Click to expand...
prosper777 said:
Full Path : C:\WINDOWS\Minidump\011522-10625-01.dmp
Click to expand...


So you may have a program that is deleting them. Maybe CCleaner or some type of file cleaning program that needs to be disabled.
 
Upvote 0 Downvote
well, it lets me look at the reports but its not the actual dumps.
One of them is showing UCX01000.sys to be cause.
It is: USB Controller Extention driver (made by Microsoft)
Microsoft drivers don't cause BSOD... so its not right.

When did you run memtest? Any error count higher than 0 is too many on Memtest, so take that stick out. I assume that is only one stick, as if its more, you can't tell which one caused the error. And would need to test them individually.

prosper777 said:
now i have added 16gb more ram to my already 16 with the same timings and whatnot.
Click to expand...

Were you getting BSOD before adding ram?
adding new ram to existing ram can lead to errors anyway, as even with same timings they might be just a little different internally to make them trip over each other.
 
Upvote 0 Downvote
Vitaakas said:
Could someone help me?
I have received an error: ntoskrnl.exe+4b442a; pshed.dll
I have attached the log collector: https://www.dropbox.com/s/rfokb20qbj3co3w/SERVER_EASYPRO-(2022-03-30_12-20-00).zip?dl=0
Click to expand...

can you start your own question and I will copy this reply below into it, I didn't realise you didn't start thread.

i will ask @gardenman to convert dumps

just based on 2 files names I could guess it was a WHEA error or clock watchdog timeout?
pshed.dll - platform specific hardware error Driver
ntoskrnl - windows kernel. It was less of a clue than top one
 
Last edited:
Upvote 0 Downvote
You must log in or register to reply here.

TRENDING THREADS

Latest posts

Moderators online

Share this page

COMPANY
RESOURCES
FOLLOW
Top Bottom