Victor2K Posted March 7, 2019 ID:1302463 Share Posted March 7, 2019 I don't know what to do These days there was a lot of BSODs here with multiple messages such as -BAD POOL HEADER/CALLER -PAGE FAULT IN NONPAGED AREA (this was the most recent, as I was doing the Sysnative scan, and pointed me to win32kfull.sys file as the issue) -KERNEL SECURITY CHECK FAILURE and others I don 't know what causes that, tried to install drivers or uninistall stuff and even are days there is no BSOD, but they always come back. I have a W10 Enterprise 64bits here btw Here are the files (The Sysnative I had to stop it due to being stuck at Waiting for SystemInfo and decided to interrupt and zip by myself) And the Perfmon it says there I can't make the report as 'somehing was using the data collecting' SysnativeFileCollectionApp.zip Link to post Share on other sites More sharing options...
Victor2K Posted March 7, 2019 Author ID:1302465 Share Posted March 7, 2019 EDIT: Had to reboot to do the Perfmon, so here it is perfmon.zip Link to post Share on other sites More sharing options...
usasma Posted March 7, 2019 ID:1302686 Share Posted March 7, 2019 I’ve asked someone else to gave a look at your reports (due to my eye problems) Whilevwaiting, often random BSODs are due to hardware problems. - so please start with the hardware diagnostics at this link. https://www.carrona.org/hwdiag.html Link to post Share on other sites More sharing options...
jcgriff2 Posted March 7, 2019 ID:1302703 Share Posted March 7, 2019 Hi. . . It appears that we are looking at unknown hardware failure here as there are 8 dumps in your zip attachment, but 5 of them are empty. This usually means that a catastrophic hardware failure occurred and that Windows shut down before it even had a chance to write the dump files. It did this to save itself (Windows). Of the 3 dumps that survived, "memory corruption" is the common theme. This does not definitively mean that RAM is bad - but it could be. Otherwise there is some type of unknown hardware failure that is causing RAM to be unable to properly hold kernel code. It could be any piece of hardware from RAM itself, PSU, CPU, motherboard, etc... Unfortunately, the dumps are incapable of telling us which piece of hardware has failed. Dumps are only good for figuring out software problems. All I can really do here is to give you some hardware diagnostic programs to run. RAM - memtest86+ - run 1 stick at a time; alternate the slots - https://www.sysnative.com/forums/hardware-tutorials/3909-test-ram-memtest86.html HDD - SeaTools for DOS, LONG test - https://www.sysnative.com/forums/hardware-tutorials/4072-hard-drive-hdd-diagnostics-sea-tools-dos-ssd-test.html FurMark video card test - https://www.sysnative.com/forums/hardware-tutorials/3907-furmark-display-card-stress-test.html Prime95 CPU - https://www.sysnative.com/forums/hardware-tutorials/3908-prime95-hardware-stress-testing.html The driver that you mentioned - win32kfull.sys - is a Microsoft Windows win32 sub-system driver and cannot be the cause as Microsoft drivers are considered to be sacrosanct. It is listed merely as a default because the real culprit could not be found or identified. As I've mentioned, the real cause here is unknown hardware failure. How old is the system? Regards. . . jcgriff2 Loading Dump File [C:\Users\PalmDesert\_jcgriff2_\dbug\__Kernel__\030619-39265-01.dmp] Built by: 17134.1.amd64fre.rs4_release.180410-1804 Debug session time: Wed Mar 6 17:44:12.991 2019 (UTC - 5:00) System Uptime: 0 days 2:06:00.810 Probably caused by : ntkrnlmp.exe ( nt!KiFastFailDispatch+d0 ) DEFAULT_BUCKET_ID: LIST_ENTRY_CORRUPT BUGCHECK_STR: 0x139 FAILURE_BUCKET_ID: 0x139_3_nt!KiFastFailDispatch Bugcheck code 00000139 Arguments 00000000`00000003 fffffd0d`01068750 fffffd0d`010686a8 00000000`00000000 BiosVersion = F4 BiosReleaseDate = 08/14/2013 SystemManufacturer = Gigabyte Technology Co., Ltd. SystemProductName = H81M-S2PV MaxSpeed: 3400 CurrentSpeed: 3392 ¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨`` Loading Dump File [C:\Users\PalmDesert\_jcgriff2_\dbug\__Kernel__\030619-63156-01.dmp] Built by: 17134.1.amd64fre.rs4_release.180410-1804 Debug session time: Wed Mar 6 15:36:19.250 2019 (UTC - 5:00) System Uptime: 0 days 16:43:54.001 *** WARNING: Unable to verify timestamp for win32kfull.sys *** ERROR: Module load completed but symbols could not be loaded for win32kfull.sys *** WARNING: Unable to verify timestamp for win32k.sys *** ERROR: Module load completed but symbols could not be loaded for win32k.sys Probably caused by : memory_corruption DEFAULT_BUCKET_ID: CODE_CORRUPTION BUGCHECK_STR: AV PROCESS_NAME: firefox.exe FAILURE_BUCKET_ID: MEMORY_CORRUPTION_LARGE Bugcheck code 00000050 Arguments ffffc283`000000f0 00000000`00000000 ffffc0b0`88878b32 00000000`0000000c BiosVersion = F4 BiosReleaseDate = 08/14/2013 SystemManufacturer = Gigabyte Technology Co., Ltd. SystemProductName = H81M-S2PV MaxSpeed: 3400 CurrentSpeed: 3392 ¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨`` Loading Dump File [C:\Users\PalmDesert\_jcgriff2_\dbug\__Kernel__\030419-65062-01.dmp] Built by: 17134.1.amd64fre.rs4_release.180410-1804 Debug session time: Mon Mar 4 16:05:41.113 2019 (UTC - 5:00) System Uptime: 0 days 4:26:21.794 Probably caused by : memory_corruption DEFAULT_BUCKET_ID: CODE_CORRUPTION BUGCHECK_STR: AV PROCESS_NAME: explorer.exe FAILURE_BUCKET_ID: MEMORY_CORRUPTION_LARGE Bugcheck code 00000050 Arguments fffff802`2e97d188 00000000`00000000 fffff802`b00c1cf0 00000000`00000002 BiosVersion = F4 BiosReleaseDate = 08/14/2013 SystemManufacturer = Gigabyte Technology Co., Ltd. SystemProductName = H81M-S2PV MaxSpeed: 3400 CurrentSpeed: 3392 ¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨`` Link to post Share on other sites More sharing options...
Victor2K Posted March 7, 2019 Author ID:1302704 Share Posted March 7, 2019 I remind I've bought the computer a long time, the I believe 2012 or 2013, only changed the power source and some motherboard stuff so far as I can recall Link to post Share on other sites More sharing options...
jcgriff2 Posted March 8, 2019 ID:1302705 Share Posted March 8, 2019 How long ago did you replace the motherboard and PSU? They are obviously 2 pieces of hardware for which there are no software tests for. Regards. . . jcgriff2 Link to post Share on other sites More sharing options...
Victor2K Posted March 8, 2019 Author ID:1302708 Share Posted March 8, 2019 The PSU is the one I know it was being replaced, it was about two or three years ago because of a thunderstorm who burned it. The motherboard I think it was replaced but I really wonder that isn't, but I must been mistaken. The issue with BSODs only happened some days from now and computer sometimes acts smooth without them and other days It appear once, twice or more Link to post Share on other sites More sharing options...
jcgriff2 Posted March 8, 2019 ID:1302709 Share Posted March 8, 2019 I unfortunately am no hardware expert. The extent of my hardware knowledge is replacing RAM and one HDD in one of my many OEM laptops. Link to post Share on other sites More sharing options...
jcgriff2 Posted March 8, 2019 ID:1302710 Share Posted March 8, 2019 (edited) 6 of the BSODs are recent - starting on 4 March 2019. There are 2 BSODs (empty dump files) from 2 June 2018 as well. No idea what caused the Summer 2018 BSODs. Nothing at all changed ~3 days ago -- i.e., the BSODs just began suddenly, then you had 6 of them. Edited March 8, 2019 by jcgriff2 Link to post Share on other sites More sharing options...
jcgriff2 Posted March 8, 2019 ID:1302711 Share Posted March 8, 2019 (edited) Quote The motherboard I think it was replaced but I really wonder that isn't, but I must been mistaken. What does that mean exactly.... that the mobo was replaced or was not? Quote ........... computer sometimes acts smooth without them and other days It appear once, twice or more That is normal for BSODs! Here are your system up-times -- ranging from 2 hours of use up to 16.75 hours of continuous use - System Uptime: 0 days 2:06:00.810 System Uptime: 0 days 16:43:54.001 System Uptime: 0 days 4:26:21.794 Edited March 8, 2019 by jcgriff2 Link to post Share on other sites More sharing options...
Victor2K Posted March 8, 2019 Author ID:1302741 Share Posted March 8, 2019 I am sure the mobo wasn't replaced as recently, I meant Well, I did teh memtest, but I can't find where the file is saved so I can upload here Link to post Share on other sites More sharing options...
Victor2K Posted March 8, 2019 Author ID:1302744 Share Posted March 8, 2019 Nevermind, found it at the boot flash drive I made Sending it right now MemTest86-Report-20190307-211029.zip Link to post Share on other sites More sharing options...
jcgriff2 Posted March 8, 2019 ID:1302808 Share Posted March 8, 2019 The RAM failed: Report Date 2019-03-07 23:30:44 Generated by MemTest86 V8.1 Free (64-bit) Result FAIL Time for new RAM. Regards. . . jcgriff2 Link to post Share on other sites More sharing options...
Victor2K Posted March 8, 2019 Author ID:1302813 Share Posted March 8, 2019 If my current monetary situation allowed me to afford it... Link to post Share on other sites More sharing options...
jcgriff2 Posted March 8, 2019 ID:1302837 Share Posted March 8, 2019 I know.... it is not exactly cheap. Good luck to you... jcgriff2 Link to post Share on other sites More sharing options...
Victor2K Posted March 8, 2019 Author ID:1302841 Share Posted March 8, 2019 Don't worry, I'll see what I can do here So, shall I need to do the other tests? And which of the stress tests on video card and CPU I need to do, since are too many Link to post Share on other sites More sharing options...
jcgriff2 Posted March 9, 2019 ID:1302954 Share Posted March 9, 2019 I don't believe the other tests are necessary at this point since you found bad RAM. If after the new RAM is installed you get BSODs, then post back and we'll figure out what to do next. Regards. . . jcgriff2 Link to post Share on other sites More sharing options...
jcgriff2 Posted March 9, 2019 ID:1302961 Share Posted March 9, 2019 How many RAM sticks do you have? Did you run memtest 1 stick at a time or all sticks together? Point being - only 1 stick of RAM is likely bad. Remove that from your system and run on less RAM. Regards. . . jcgriff2 Link to post Share on other sites More sharing options...
Victor2K Posted March 11, 2019 Author ID:1303184 Share Posted March 11, 2019 I tested it wiht all the sticks. Have somehow fear to open it and wreck the system by doing any ill-done RAM stick removing, but I'll see if that is the source Link to post Share on other sites More sharing options...
jcgriff2 Posted March 11, 2019 ID:1303275 Share Posted March 11, 2019 Take the chance so that you can remove the [likely] one bad RAM stick. Be careful when handling RAM. Touch some metal first to drain any electric shock out of yourself. Link to post Share on other sites More sharing options...
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now