L luizguuus Well-known member Joined Aug 30, 2018 Posts 48 Sep 5, 2018 #61 ''The bugcheck of the memory dump was EF. There was a symbol problem in the Microsoft database and the file was not able to be debugged.'' An user on other forum said that the today crash was because of this, nothing related to drivers, memory, hd, etc.
''The bugcheck of the memory dump was EF. There was a symbol problem in the Microsoft database and the file was not able to be debugged.'' An user on other forum said that the today crash was because of this, nothing related to drivers, memory, hd, etc.
xilolee Moderator Staff member Joined Dec 31, 2013 Posts 3,677 Location World, Europe, Italy Sep 5, 2018 #62 luizguuus said: ''The bugcheck of the memory dump was EF. There was a symbol problem in the Microsoft database and the file was not able to be debugged.'' An user on other forum said that the today crash was because of this, nothing related to drivers, memory, hd, etc. Click to expand... Yes, I had the same error, but I don't know if it's a MS server problem. Probably it is. But that's not an error regarding your machine. xilolee said: Could you check the correct model looking directly the stick? Or its package? Does device manager show yellow exclamation marks? Click to expand... luizguuus said: I'll run MemTest today when i go sleep, i'll run this CrystalDiskInfo and see what is shows, tyvm for your reply. Click to expand... And what was the memtest result? Please try also this (click)
luizguuus said: ''The bugcheck of the memory dump was EF. There was a symbol problem in the Microsoft database and the file was not able to be debugged.'' An user on other forum said that the today crash was because of this, nothing related to drivers, memory, hd, etc. Click to expand... Yes, I had the same error, but I don't know if it's a MS server problem. Probably it is. But that's not an error regarding your machine. xilolee said: Could you check the correct model looking directly the stick? Or its package? Does device manager show yellow exclamation marks? Click to expand... luizguuus said: I'll run MemTest today when i go sleep, i'll run this CrystalDiskInfo and see what is shows, tyvm for your reply. Click to expand... And what was the memtest result? Please try also this (click)
L luizguuus Well-known member Joined Aug 30, 2018 Posts 48 Sep 5, 2018 #63 The MemTest detected nothing. I'll try this test.
jcgriff2 Co-Founder / AdminBSOD Instructor/ExpertMicrosoft MVP (Ret.) Staff member Joined Feb 19, 2012 Posts 21,541 Location New Jersey Shore Sep 5, 2018 #64 luizguuus said: I just got ''KERNEL DATA IN PAGE ERROR'' and ''CRITICAL PROCESS DIED''. Kernel BSOD seems different now, take a look. Click to expand... It may seem different, but the latter actually compliments the former. If anything, the new BSODs confirm what everyone thought was the cause when working with the initial BSOD dumps. I have read this entire thread and initially when seeing ''KERNEL DATA IN PAGE ERROR'' - I thought the HDD was bad. Now seeing new BSODs with ''CRITICAL PROCESS DIED'' (likely 0xf4 bugcheck), it absolutely strengthens my resolve that the HDD is somehow involved here. I have rarely seen a 0xf4 BSOD that did not involve the HDD. I see that you have a 1 TB HDD; model - Code: ST1000DM010-2EP102 Run SeaTools for DOS, LONG test - https://www.sysnative.com/forums/hardware-tutorials/4072-hard-drive-hdd-diagnostics.html It will likely take hours to run, but running SeaTools for DOS at this time is very important. You'll need a CD-R CD to burn SeaTools on to, then you'll boot from the CD, following the instructions. Regards. . . jcgriff2
luizguuus said: I just got ''KERNEL DATA IN PAGE ERROR'' and ''CRITICAL PROCESS DIED''. Kernel BSOD seems different now, take a look. Click to expand... It may seem different, but the latter actually compliments the former. If anything, the new BSODs confirm what everyone thought was the cause when working with the initial BSOD dumps. I have read this entire thread and initially when seeing ''KERNEL DATA IN PAGE ERROR'' - I thought the HDD was bad. Now seeing new BSODs with ''CRITICAL PROCESS DIED'' (likely 0xf4 bugcheck), it absolutely strengthens my resolve that the HDD is somehow involved here. I have rarely seen a 0xf4 BSOD that did not involve the HDD. I see that you have a 1 TB HDD; model - Code: ST1000DM010-2EP102 Run SeaTools for DOS, LONG test - https://www.sysnative.com/forums/hardware-tutorials/4072-hard-drive-hdd-diagnostics.html It will likely take hours to run, but running SeaTools for DOS at this time is very important. You'll need a CD-R CD to burn SeaTools on to, then you'll boot from the CD, following the instructions. Regards. . . jcgriff2
E elstaci Member Joined Dec 28, 2016 Posts 9 Location MIami, Florida Sep 5, 2018 #65 Good test to run in a Windows Environment. Testing my RAM with MEMTEST to see how it works. 1) Started Windows 10 in a Clean Windows Desktop to have the most available RAM to test - (Total RAM installed 16 gbytes) a) Before Windows 10 Clean startup had 8.4 gigabytes of RAM available b) After Windows 10 Clean Startup now have 13.4 gigabytes of RAM available 2) Divided 13.4 gigabytes of RAM by 8 (8 core cpu) and then divided by 1 megabyte to give me total megabytes per CPU core = 1675 megabytes 3) Started MEMTEST eight times and inputted all eight MEMTEST screens with 1675 and started testing. 4) Running 8 instances of MEMTEST. Ran each core from 100.6% to 112.4% without any errors while browsing the internet. 5) computer runs very slow due to the stress put on CPU and RAM Memory while testing. Note: make sure you have a good CPU cooler. My CPU is running at 100% but with my Cooler Master 212 EVO CPU temp is stable at 52 c.
Good test to run in a Windows Environment. Testing my RAM with MEMTEST to see how it works. 1) Started Windows 10 in a Clean Windows Desktop to have the most available RAM to test - (Total RAM installed 16 gbytes) a) Before Windows 10 Clean startup had 8.4 gigabytes of RAM available b) After Windows 10 Clean Startup now have 13.4 gigabytes of RAM available 2) Divided 13.4 gigabytes of RAM by 8 (8 core cpu) and then divided by 1 megabyte to give me total megabytes per CPU core = 1675 megabytes 3) Started MEMTEST eight times and inputted all eight MEMTEST screens with 1675 and started testing. 4) Running 8 instances of MEMTEST. Ran each core from 100.6% to 112.4% without any errors while browsing the internet. 5) computer runs very slow due to the stress put on CPU and RAM Memory while testing. Note: make sure you have a good CPU cooler. My CPU is running at 100% but with my Cooler Master 212 EVO CPU temp is stable at 52 c.
L luizguuus Well-known member Joined Aug 30, 2018 Posts 48 Sep 5, 2018 #66 Thank you very much for the replies guys, i'll follow the steps.
L luizguuus Well-known member Joined Aug 30, 2018 Posts 48 Sep 7, 2018 #67 Guys, i got ''System Service Exception''. What is that?
philc43 BSOD Forum Moderator, BSOD Academy Instructor, BSOD Kernel Dump Expert Staff member Joined Jul 7, 2017 Posts 1,962 Location Cambridge, UK Sep 8, 2018 #68 It doesn't help to be posting the same questions in multiple forums. You are wasting peoples time, BSOD analysts who volunteer their help and expertise for free are few and far between and if they find you are posting on multiple sites then they can never be sure if someone else is going to already be answering the question or working on a solution for you. This then leads to your posts being ignored. Just stick with one site for now and avoid this confusion!
It doesn't help to be posting the same questions in multiple forums. You are wasting peoples time, BSOD analysts who volunteer their help and expertise for free are few and far between and if they find you are posting on multiple sites then they can never be sure if someone else is going to already be answering the question or working on a solution for you. This then leads to your posts being ignored. Just stick with one site for now and avoid this confusion!