Windows 7 Forums
Welcome to Windows 7 Forums. Our forum is dedicated to helping you find support and solutions for any problems regarding your Windows 7 PC be it Dell, HP, Acer, Asus or a custom build. We also provide an extensive Windows 7 tutorial section that covers a wide range of tips and tricks.


Windows 7: BSOD Stop 50 (once 51) after logging in; Safe mode works fine


16 Feb 2012   #1

Windows 7 Home Premium 64 bit
 
 
BSOD Stop 50 (once 51) after logging in; Safe mode works fine

Hello. First of all, sorry about just registering and asking a question - I don't like it much, but I've been unable to solve this on my own, and I've run out of places to look for answers.

Specs (Fujitsu Amilo Pi 3660):
2 years old

OS: Windows 7 Home Premium x64 (last reinstalled about 6 months ago)
CPU: Intel Core 2 Duo T6600 2.2GHz
Mobo: Intel PM45
Memory: 4096 MB, DDR2: PC2-6400 (400MHz)
GPU: NVIDIA GeForce GT 240M
Sound: Realtek ALC272

Problem:

It started yesterday. The computer boots as normal, but a short while after logging in, I get BSOD Page fault in nonpaged area, and once Registry Error. I had not installed anything for several days beforehand, nor have I changed the hardware since I bought the computer. I had to do a fresh install of Windows about 6 months back, but I've had no problems since then. Safe mode works just fine.

Things I've done:
CHKDSK - No problems
Malwarebytes - 1 trojan
Memtest - 2 passes (was told this was "good enough" for starters)
Booting without sound, graphics, network, bluetooth, webcam, DVD reader - Problem persists
Last BSOD occured after running verifier on all non-Microsoft drivers.

I tried to generate a system health report, but I get an error if I try running it from cmd - I get to perfmon, but I cannot generate a report, nor can I find it manually (the curse of having a Swedish-language OS). I have attached the dumpfiles at least.


My System SpecsSystem Spec
.

16 Feb 2012   #2
JMH

Win 7 Ultimate 64-bit. SP1.
 
 

Great first post!
Well done!

>
What AV are you using?

>
Suggest you run Memtest for longer as per the instructions below.

>
Yes we realize your Verifier is enabled, is an iffy proposition & it didn't catch the culprit this time.
Keep trying please.


Attachment 198555


These crashes were caused by memory corruption/exception (probably a driver).
Please run these two tests to verify your memory and find which driver is causing the problem.

If you are overclocking anything reset to default before running these tests.
In other words STOP!!!

If you have raid > update its Driver.


Memtest.
Quote:
*Download a copy of Memtest86 and burn the ISO to a CD using Iso Recorder or another ISO burning program. Memtest86+ - Advanced Memory Diagnostic Tool

*Boot from the CD, and leave it running for at least 5 or 6 passes.

Just remember, any time Memtest reports errors, it can be either bad RAM or a bad motherboard slot.

Test the sticks individually, and if you find a good one, test it in all slots.

Any errors are indicative of a memory problem.

If a known good stick fails in a motherboard slot it is probably the slot.

RAM - Test with Memtest86+



Driver verifier

Quote:
Using Driver Verifier is an iffy proposition. Most times it'll crash and it'll tell you what the driver is. But sometimes it'll crash and won't tell you the driver. Other times it'll crash before you can log in to Windows. If you can't get to Safe Mode, then you'll have to resort to offline editing of the registry to disable Driver Verifier.

So, I'd suggest that you first backup your stuff and then make sure you've got access to another computer so you can contact us if problems arise. Then make a System Restore point (so you can restore the system using the Vista/Windows 7 Startup Repair feature).

Then, here's the procedure:
- Go to Start and type in "verifier" (without the quotes) and press Enter
- Select "Create custom settings (for code developers)" and click "Next"
- Select "Select individual settings from a full list" and click "Next"
- Select everything EXCEPT FOR "Special Pool", "Force Pending I/O Requests" and "Low Resource Simulation" and click "Next"
- Select "Select driver names from a list" and click "Next"
Then select all drivers NOT provided by Microsoft and click "Next"
- Select "Finish" on the next page.

Reboot the system and wait for it to crash to the Blue Screen.
Continue to use your system normally, and if you know what causes the crash, do that repeatedly.
The objective here is to get the system to crash because Driver Verifier is stressing the drivers out.
If it doesn't crash for you, then let it run for at least 36 hours of continuous operation.


Reboot into Windows (after the crash) and turn off Driver Verifier by going back in and selecting "Delete existing settings" on the first page, then locate and zip up the memory dump file and upload it with your next post.

If you can't get into Windows because it crashes too soon, try it in Safe Mode.
If you can't get into Safe Mode, try using System Restore from your installation DVD to set the system back to the previous restore point that you created.
Using Driver Verifier to identify issues with Windows drivers for advanced users
My System SpecsSystem Spec
16 Feb 2012   #3

Windows 7 Home Premium 64 bit
 
 

Thanks for the quick response

AV: I believe I'm using Windows AV
Memtest: Will do.
Verifier: Have run three more BSODs with your settings. Dumps attached.

Overclocking: All hardware is factory spec.
My System SpecsSystem Spec
.


16 Feb 2012   #4
JMH

Win 7 Ultimate 64-bit. SP1.
 
 

> Windows AV?
You mean Microsoft Security Essentials?

> Noted re Overclocking: All hardware is factory spec. { Nice!}

> Please update your Malwarebytes & do a FULL System Scan.
Let us know the results at the end.
My System SpecsSystem Spec
16 Feb 2012   #5

Win 8 Release candidate 8400
 
 

Quote   Quote: Originally Posted by JonasW View Post
Thanks for the quick response

AV: I believe I'm using Windows AV
Memtest: Will do.
Verifier: Have run three more BSODs with your settings. Dumps attached.

Overclocking: All hardware is factory spec.

JonasW

After running the Malwarebytes scan as JMH suggested please re-run verifier as indicated below


Your DMPs are verifier enabled but not catching the driver, Please reset and select all the Microsoft drivers instead and re-run verifier.
My System SpecsSystem Spec
16 Feb 2012   #6

Windows 7 Home Premium 64 bit
 
 

Malwarebytes full scan found 0 problems. Going ahead with verifier now.
My System SpecsSystem Spec
16 Feb 2012   #7

Windows 7 Home Premium 64 bit
 
 

Three BSODs with new verifier settings, plus one older one with JMH's settings (Registry Error) attached.
My System SpecsSystem Spec
16 Feb 2012   #8

Win 8 Release candidate 8400
 
 

Quote   Quote: Originally Posted by JonasW View Post
Malwarebytes full scan found 0 problems. Going ahead with verifier now.
Good news abt malwarebytes, and good luck with verifier.
My System SpecsSystem Spec
16 Feb 2012   #9

Windows 7 Home Premium 64 bit
 
 

Looking in BlueScreen Viewer, the BSODs after new verifier settings look exactly the same. Should I go ahead and do more? Or should the verifier settings be changed again?
My System SpecsSystem Spec
16 Feb 2012   #10

Win 8 Release candidate 8400
 
 

Quote   Quote: Originally Posted by JonasW View Post
Looking in BlueScreen Viewer, the BSODs after new verifier settings look exactly the same. Should I go ahead and do more? Or should the verifier settings be changed again?
I am a big fan of Nir Sofer's work, BUT blueScreen View more often than not, doesn't point out the correct causes. Similarly Who crashed is even worse.

I prefer to use WinDbg (the Windows Debugging Tools) to read the memory dumps. It is the Gold standard for those of us that do this and often will give us the answer by itself. (we don't need the full jcgriff2 report each time).

Please upload any DMP files you get.
My System SpecsSystem Spec
Reply

 BSOD Stop 50 (once 51) after logging in; Safe mode works fine




Thread Tools




Our Sites

Site Links

About Us

Find Us

Windows 7 Forums is an independent web site and has not been authorized, sponsored, or otherwise approved by Microsoft Corporation. "Windows 7" and related materials are trademarks of Microsoft Corp.

Designer Media Ltd

All times are GMT -5. The time now is 10:51 AM.
Twitter Facebook Google+



Windows 7 Forums

Seven Forums Android App Seven Forums IOS App
  

1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33