Diagnosing BSOD problem on startup

Topic

New Reply

My PC is now giving BSOD problems. Sometimes using Repair/Restore I can get it to boot up. PC is Dell i7 processor Windows 7 Pro 64 bit 8Gb RAM 2 x 1Tb disks. The BDOS says:
FAULT_IN_NON_PAGED_AREA. I haven’t really fitted any new hardware recently. But ensured all my drivers for printers, monitor are latest. Did a memory check appears OK. Did a disk check not faults found. The memory dump gives:082514-27019-01.dmp 25/08/2014 09:30:32 PAGE_FAULT_IN_NONPAGED_AREA 0x00000050 fffff901`c063debc 00000000`00000000 fffff960`000fcca3 00000000`00000005 ntoskrnl.exe ntoskrnl.exe+75bc0 NT Kernel & System Microsoft® Windows® Operating System Microsoft Corporation 6.1.7601.18409 (win7sp1_gdr.140303-2144) x64 ntoskrnl.exe+75bc0 C:WindowsMinidump82514-27019-01.dmp 8 15 7601 283,664 25/08/2014 09:53:32. So don’t think ntoskrnl.exe is corrupt as it eventually from a restore point boots up. But how do I track down these addresses at ….c063debc and 000fcca3 etc… I can restore a system image if all else fails. But as an ex UNIX engineer seems to me it would be nicer to locate the bug/error and fix that. So any help on tracking this error down from the dump information.

Reply | Quote

Replies

Welcome to the Lounge Graham.

There are BSOD experts on here but WhoCrashed may be able to nail down what is causing the problem http://www.resplendence.com/whocrashed

Reply | Quote

Welcome to the Lounge Graham.

There are BSOD experts on here but WhoCrashed may be able to nail down what is causing the problem http://www.resplendence.com/whocrashed

I having created a recovery DVD/CD and an image stored on an external disk I have restored the image and the PC boots up OK. It seemed to me that a working out what had crashed from long addresses was like looking for a needle in a haystack! When I worked on UNIX (Solaris) it was so much easier. If the worst came to worst you could just send the crash dump to Sun and they told you exactly what crashed the kernel etc… and what to do to fix it. Sorry but Windows is so much harder. I will bear in mind the tool. But I often find with these free utilities my virus checker won’t let me load them as it says they are suspicious, I just don’t like taking the risk. But thanks for the reply. I have noted the utility for future reference.

Reply | Quote

Welcome to the Lounge Graham.

There are BSOD experts on here but WhoCrashed may be able to nail down what is causing the problem http://www.resplendence.com/whocrashed

WhoCrashed is the best tool around for normal people trying to solve MSoDs. It does require that you have configured your system for crash dumps. The application will analyze the dumps and tell you what it thinks is causing the problem.

Reply | Quote

Stop 0×00000050 or PAGE_FAULT_IN_NONPAGED_AREA
The Stop 0×50 message indicates that requested data was not in memory. The system generates an exception error when using a reference to an invalid system memory address. Defective memory (including main memory, L2 RAM cache, video RAM) or incompatible software (including remote control and antivirus software) might cause Stop 0×50 messages.
Possible Resolutions:
• If you added new hardware recently, remove and replace the hardware to determine if it is causing or contributing to the problem. Run diagnostics software supplied by the hardware manufacturer to determine if the component has failed.
• Stop 0×50 messages can also occur after installing faulty drivers or system services. If the file name is listed, you need to disable, remove, or roll back that driver. If not, disable the recently installed service or application to determine if this resolves the error. If this does not resolve the problem, contact the hardware manufacturer for updates. Using updated drivers and software is especially important for network interface cards, video adapters, backup programs, multimedia applications, antivirus scanners, and CD mastering tools. If an updated driver is not available, attempt to use a driver from a similar device in the same family. For example, if printing to a Model 1100C printer causes Stop 0×50 errors, using a printer driver meant for a Model 1100A or Model 1000 might temporarily resolve the problem.

Drivers would be my first suspicion, next would be memory.

You’re certainly right about Windows being harder in this sense of it. 99% of the time you are totally on your own.
I do wish they would come up with a better (more specificity) way to track these things.

Reply | Quote

Drivers would be my first suspicion, next would be memory.

You’re certainly right about Windows being harder in this sense of it. 99% of the time you are totally on your own.
I do wish they would come up with a better (more specificity) way to track these things.

I hadn’t installed any new hardware, but I unplugged my 2 printers. I also ensured that the NVIDIA monitor driver was uptodate. I had also made sure the printer drivers were uptodate. I checked the disk for errors with correction using dskchk. I also checked the memory for errors. What bugs me is I have the diagnostic information from the dump with HEX addresses but no way of tracking these back to a particular driver or piece of hardware!! It struck me that this was looking for a needle in a haystack. But as I backup my PC etc… I used my Recovery DVD and the image of the windows system and restored from the image. Now it boots up cleanly every time. But then of course 36 critical updates and quite a few application updates etc… So many cups of coffee (or being a Brit lots of tea) the PC is now up and running. I have made a new image today. O how I love Microsoft Windows!! I was happier with Sun Solaris UNIX when I was an IT engineer before I retired. But thanks for your reply. I do appreciate these forums, they often are better than the manufactures Help Desks!

Reply | Quote

Appears that you are having a problem with the August 12 Microsoft Patch Tuesday updates. I experienced the identical BSOD problem as you described with my system also. Had to do an image restore to get things back to normal. Did another windows update the next day and died again with same BSOD shortly thereafter. Could not reboot. Image restore time again. Microsoft made corrections to the patches sometime around the 15th or 16th. Updated system on 16th and have had no problems since.

Reply | Quote

The KB2982791 gdi32.dll & win32k.sys MS14-035 security updates were the prime cause of the BSOD crashes at startup on different versions of Windows. On the 15th of August, Microsoft advised users to uninstall the bad KB2982791 patches to get things working again and removed KB2982791 from Windows Update and Microsoft Download Center. Then on August 27, Microsoft released the KB2993651 patches to fix the problems caused by the KB2982791 patches.

Reply | Quote