I managed to run p95 alongside and provoked: a frozen screen, a BSOD after logging in after the reset after that freeze "SYSTEM_SERVICE_EXCEPTION", and another BSOD while running p95. Again, no dump files were written : (
I've attached the latest zipped SF-folder...
Last edited by Useless User; 02 Sep 2014 at 15:41.
I ran verifier.exe again from the SF tool and obtained this BSOD:
To disable verifier.exe, I restarted the PC in safe mode, where I am greeted by Startup Repair, which, after a couple of minutes, fails. The repair error details window shows this:
After which now I can't even start in safe mode. Bollards!
Ok, eventually, I got into Windows again, where I disabled verifier.exe.
Last edited by Useless User; 03 Sep 2014 at 00:11.
Bump...
Grump...
Deinstalled everything AMD/ATI related down to the registry. Still, I get BSOD 0x0000001e and 0x0000000a and, of course, no minidump file written. I'm running the PC in safe mode now and try stressing it with IntelBurnTest on maximum setting and the maxwell equation light simulation software I'm running on it.
Bump... bump... bump...
So, no minidumps for me, whatever I tried (how is that at all possible?). In safe mode with network drivers, IntelBurnTest runs ok on its maximum setting, while the software I use also runs. I just continue letting both run overnight to see, whether yet another BSOD occurs (all previous BSODs occurred in "normal" mode). If not - where should I go from there?
Could someone have a look at the last SF-folder attached above? Maybe some clues can be found there, even without fresh minidumps?
Thanks!
We cant do much without DMP Files.
However here is some information on the 0x50 Bugcheck you are receiving.
Code:PAGE_FAULT_IN_NONPAGED_AREA (50)Tip
Win32k.sys - page_fault_in_nonpaged_area -
A stop message that occurs when the demanded data is not found in memory. The system produces a fault, which usually specifies that the system looks for data in the paging file. The system cannot locate the data and recover it.
An Antivirus program, damaged hardware, a buggy system service and a ruined NTFS volume can all generate this type of error message.
If the BSOD is after the installation of new hardware, In order to fix this issue, remove the hardware to see if the error reappears, if the hardware has been added to the system newly. If the existing hardware is at fault, remove or change the faulty component and run the hardware diagnostics.
Warning
Please make sure all of your drivers are up to date before continuing!
Scan the system for possible virus infection with the following programs.
How can I get the PC to write minidumps though? The settings are ok. There is much SSD space. What I also can't figure is: Why did minidump writing fail from 23rd August onwards? No hardware has been removed or added. No new software installed (apart from some of the diagnostic tools recommended here).
The display freezes in safe mode with network drivers eventually : (
I could see from the clock in the task bar when the display froze, but there is nothing in the event viewer relating even remotely to that time hours before or after. I scanned for rootkit viruses and with Microsoft's software as per above but found nothing.
That leaves "only" the non-Microsoft network drivers loaded in safe mode and hardware as main culprits, right?
Besides - how could I ever get my PC to write minidumps again?
Last edited by Useless User; 04 Sep 2014 at 01:38.
You're referring to the minidump tutorial? Well, the PC always wrote minidumps until a BSOD on the 23rd August. Since then, it just stopped. The PC is set to write minidumps as per what I found recommended on sevenforums. I spent several hours looking around why minidumps, kernel dumps, etc. can't be written but found nothing pertaining to my situation : (
I did it via [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CrashControl] “CrashDumpEnabled”=dword:00000003 and all combinations here
Quote
