Seems To Crash a the worst time Possible - Windows 10 BSOD

A

Aduckfan

Member
Joined
Nov 20, 2019
Posts
9
I've checked HD with sea tools. Ram is new but checked anyway. Did a fresh install a couple weeks ago because of crashes and did a renew yesterday. I've been into messing inside PC's since trsdos but never got into examining dump files. Certainly need all the help I can get.

Thanks in advance
Aduckfan
 

Attachments

Hi. . .

I processed the 4 dumps in your Sysnative zip file attachment.

The bugchecks -
(2) - 0x1a - severe memory management error; bad PTE (Page Table Entry)
(1) - 0xa - driver attempted to access memory that it should not have or the memory is just plain bad
(1) - 0x1000007e = 0x7e (0xc5) = thread threw an exception; excp = 0xc5 = memory access violation

Code: 
BugCheck 1A, {41792, fffffe00fd2b7590, 4000000000, 0}
Probably caused by : memory_corruption ( ONE_BIT )
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
BugCheck 1A, {41792, ffffb1000003b218, 4000000000, 0}
Probably caused by : memory_corruption ( ONE_BIT )
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
BugCheck 1000007E, {ffffffffc0000005, fffff805152617f4, fffff40f44578c08, fffff40f44578450}
Probably caused by : dxgmms2.sys ( dxgmms2!VIDMM_PAGE_TABLE_BASE::IsResident+0 )
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
BugCheck A, {4000000000, 2, 1, fffff80674a05e4e}
Probably caused by : WdFilter.sys ( WdFilter!MpScanFile+ce2 )
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``

Probable causes -
- memory corruption
- Microsoft DirectX
- Microsoft antimalware file system filter driver

Microsoft drivers are considered sacrosanct, so the probable causes listing Microsoft are likely a default of sorts as the real culprit/cause could not be determined.

Run Driver Verifier in the background for at least 24 hours. If Driver Flags a driver, it will BSOD your system immediately, so save your work often.

Driver Verifier - BSOD related - Windows 10, 8.1, 8, 7 + Vista

Your BSODs appear to be caused by unknown hardware failure. Let's see if Driver Verifier flags any 3rd party drivers.

Regards. . .

jcgriff2
 
Last edited:
Hi. . .

Yes it does.

You can use your system while it runs.

It is rather resource intensive, so you may notice some system slowness, depending on your system specs.

Regards. . .

jcgriff2
 
PC seems to crash when downloading and installing apps. After renewing windows of course I have a lot to install. Creative cloud especially also office 365 took a few attempts to get apps installed. So far no crash after these apps were installed and I started this process with you. Maybe some magic happened.
Aduckfan
 
Bugcheck on the latest dump is 0xa - very similar to the other one you had.

Cause is listed as memory corruption.

Run memtest86+ one stick at a time; alternate the slots.

Test RAM with memtest.org MemTest86+

Regards. . .

jcgriff2

p.s. Forget about Driver Verifier - we are dealing with unknown hardware failure here.
 
I'm halfway thru test 8 on first stick. Driver verifier or something is making a mess of my PC. You did say it's a memory hog. How can u tell it's running. Nothing I can find in apps running or services. How do you stop it if it is running
 
Stick 2 being tested now and I see the problem, maybe, all four are ddr3 1600 but the first stick of a pair runs at 668 mhz and shows ddr3-1337.
Stick one of a pair runs at 802 mph and shows ddr3-1605
Every thing else is the same. Maybe MOB isn't up to this difference
 
Aduckfan said:
Stick 2 being tested now and I see the problem, maybe, all four are ddr3 1600 but the first stick of a pair runs at 668 mhz and shows ddr3-1337.
Stick one of a pair runs at 802 mph and shows ddr3-1605
Every thing else is the same. Maybe MOB isn't up to this difference
Click to expand...
That is expected. DDR stands for "Double Data Rate", so you have to double the base frequency (e.g. 668) to get the actual speed (668x2=1366).

By default, DDR3 runs at 1366Mhz. To get the rated speeds of faster kits, you would need to enable XMP overclocking in the BIOS, which we recommend disabling for troubleshooting. More info here How to Enable Intel XMP to Make Your RAM Run at Its Advertised Speeds

Memtest86+ is old software and has bugs correctly identifying and reading details about some RAM. The tests are still valid though. It is also worth running 4 passes of the newer Passmark Memtest86 tool here MemTest86 - Official Site of the x86 Memory Testing Tool
 
Memory checks ok. I did change the 4 Kingston's to 4 Patriots so now there all Patriots. Assume that wont make a diff so if it's not the memory then what?
 

Attachments

  • 15743750678032086156446212597412.jpg
    15743750678032086156446212597412.jpg
    366.8 KB · Views: 2
Good news! Keep us posted.

Most likely you had a bad Kingston module that may not have been flagged with the tests. I've had to run tests multiple times for 10+ passes to find a bad module before. Did you also test with Memtest86 after Stephen's suggestion (below)?
Tekno Venus said:
Memtest86+ is old software and has bugs correctly identifying and reading details about some RAM. The tests are still valid though. It is also worth running 4 passes of the newer Passmark Memtest86 tool here MemTest86 - Official Site of the x86 Memory Testing Tool
Click to expand...

At any rate, I hope the crashes are a thing of the past. Good luck!
 

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

Back
Top