BSOD ERROR WHEA UNCORRECTABLE AND DPC VIOLATION

J

jaseemabdu

Member
Joined
May 10, 2018
Posts
20
2 PC is having BSOD Error ,



On one i have updated bios still issue persists.

1)The system has rebooted without cleaning shutting down first.This could be caused if system stopped responding, crashed or lost power unexpectadly (Both system)

2) the previous shuntdown at ___ on___ was unexpected (Both system)

[FONT=Verdana, Tahoma, Nimbus Sans L, arial, sans-serif]3) the system firmware has changed the processors memory range registers across a sleep state transition. this can result in reduced resume performance [/FONT]

System 1 (WHEA UNCORRECTABLE ERROR)
Intel(R) Core(TM) i7-6800K CPU @ 3.40GHz
ASUS X99A
32 GBytes DDR4
NVDIA QUADRO M2000 4GB
POWERSUPPLY CORSAIR CX750
Kingston SSD 256GB
Microsoft Windows 10 (10.0) Professional 64-bit 1709 (was auto updated )

1) Tried and cleaning ram and graphics card dust
2)Turned off fast boot
3)Turned off HDD turn off after minutes to higher minutes)
4)Reinstalled graphics driver from Windows (not safe mode)
5)Updated bios ( again a new bios update came which is beta that i dint update now)
6)No firmware for SSD update available


System 2 (DPC WATCH DOG VIOLATION 0%)
Intel(R) Core(TM) i7-7700K CPU @ 4.20GHz
Asus H270 PRIME
32 GBytes DDR4
NVIDIA Quadro P2000 5gb
Microsoft Windows 10 (10.0) Professional 64-bit 1709 (AUTO UPDATED)

1)Turned off fast boot
2)Turned off HDD turn off after minutes to higher minutes)
3)Reinstalled graphics driver from Windows (not safe mode)
4)No SSD update available
5)Updated BIOS


Still issue persists, and this occurs only 4- 10 days between . hOw to solve this issue? Dumps are not getting created even after enabling on both systems...
 

Attachments

Hi,

Which memory dump should i actually select in the windows? KERNEL MEMORY DUMP with overrite option and disabled automatic restart? Or Is it Small Memory dump? (Which all option need to be CHECKED and UNCHECKED?
 
Hi jaseemabdu,

Please check the following options
- Write an event to the system log
- Automatically restart

Select the following memory dump
- Kernel memory dump
 
axe0 said:
Hi jaseemabdu,

Please check the following options
- Write an event to the system log
- Automatically restart

Select the following memory dump
- Kernel memory dump
Click to expand...

What about overwrite existing file? If this all are done are you sure dump file will be created?
 
Overwriting existing file needs to be checked and 'disable automatic deletion of memory dumps when disk space is low' should be unchecked.

With these configurations you have it configured like it came out of the box. If, with these configurations, no dump file is created we'll need logs from Blue Screen of Death (BSOD) Posting Instructions - Windows 10, 8.1, 8, 7 + Vista to see what other issues are present.
 
The time on system 1 doesn't seem right, did you notice this?

The crash dump initialization fails, all in all it might indicate a motherboard issue, that is, if the time issue is a consistent issue with the CMOS battery.

Please run Test RAM with PassMark MemTest86 to ensure the RAM is fine.
 
Last edited:
time on system is right. Its in UNITED ARAB EMIRATES time zone (+4). So what would be the issue checking that? How you confirmed its motherboard issue? What about graphics? Since it happens very rarely like once, twice or thrice in a month difficult...the user is also frustrated :(...

Even before the beginning of problem crash dump was logged....may be after 2 months of issue it stopped writing dumps...i have used bluescreenviewer from nirsoft during this time...and it showed dumps...

i forgot to mention there is old hard drive where the user saves data also...
 
see this image saying minidump was saved in event viewer...but its not shown in the folder...
 

Attachments

  • 21.JPG
    21.JPG
    82.4 KB · Views: 7
Please run the memory test I linked in my previous post.
 
axe0 said:
Please run the memory test I linked in my previous post.
Click to expand...

So your saying most probably RAM? Memory test will take how many hours? Because its a production system...is it okay if i reemove one ram and check because i already changed slots...if the reason for no crash dump is known its easy for us i believe
 
RAM is one of the most likely causes to contribute to the issue with saving dumps.

If you can switch the modules, go for it, that's better than software tests.
 
I will remove one ram then because already interchanged modules... but this is only for regarding crash not being saved? And not for bsod?
 
Not immediately for the BSODs, although the BSODs are basically meaning unknown hardware error occured so there's a chance the RAM may very well be a remedy for the BSODs as well.
 

Has Sysnative Forums helped you? Please consider donating to help us support the site!

Back
Top