Windows 7 64-bit BSOD, Stop error 0x00000001E, 3B and 50

[Kwan164]

Hi Everyone,

My OS is getting numerous Blue screen errors since last week. When i turn on my computer it oftenly results a BSOD in a Stop Code: 0x00000001E or 0x00000003B error and sometimes a 0x000000050 error. However, it works fine if it can start normally.

for example:
-------------------------------------------------------------------------------
The computer has rebooted from a bugcheck. The bugcheck was: 0x0000001e (0xffffffffc0000005, 0xfffff80002c6e047, 0x0000000000000000, 0x000000007ef90000). A dump was saved in: C:\Windows\MEMORY.DMP. Report Id: 012512-49155-01.

The computer has rebooted from a bugcheck. The bugcheck was: 0x0000003b (0x00000000c0000005, 0xfffff9600012e4cb, 0xfffff88003a93d80, 0x0000000000000000). A dump was saved in: C:\Windows\MEMORY.DMP. Report Id: 012412-91182-01.

The computer has rebooted from a bugcheck. The bugcheck was: 0x00000050 (0xfffff8a00c8c4000, 0x0000000000000000, 0xfffff8000292476a, 0x0000000000000000). A dump was saved in: C:\Windows\MEMORY.DMP. Report Id: 012312-37097-01.
-------------------------------------------------------------------------------

System:
Gateway DX 4831
MB Intel H57 Express
Intel i3 530
6 Gb (2 x 2Gb and 2 x 1Gb) RAM, Samsung
500W PSU, Pc Power and Cooling
HIS HD 6770 iceq turbo X
1 x 1 TB SATA
Windows 7 Home Premium OEM x64
appromimately two years old

 

[JMH]

These crashes were caused by memory 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!!!


1-Memtest.

*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.

http://www.sevenforums.com/tutorials/105647-ram-test-memtest86.html



2-Driver verifier

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/Win7 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 (an estimate on my part).

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.

If that doesn't work, post back and we'll have to see about fixing the registry entry off-line:

Delete these registry keys to stop Driver Verifier from loading (works in XP, Vista, Win7):
        HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Session Manager\Memory Management\VerifyDrivers
        HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Session Manager\Memory Management\VerifyDriverLevel

Using Driver Verifier to identify issues with Windows drivers for advanced users

 

[zigzag3143]

Besides doing the tests that JMH suggests, if you still have Symantec installed, please remove it at least to test. Many of this reflect it presence.

Symantec is a frequent cause of BSOD's. I would remove and replace it with Microsoft Security Essentials AT LEAST TO TEST

http://us.norton.com/support/kb/web_view.jsp?wv_type=public_web&docurl=20080710133834EN

Microsoft Security Essentials - Free Antivirus for Windows

 

[Kwan164]

thank you for helping

I uninstalled the Symantec antivirus by using the official tool, and Tested my memory with Memtest86+ today, but there were no errors found. However i can not login my OS, and keep getting the stop code 3b and 50 even i use the Safe Mode. Therefore, i can not test the drivers with Driver verifier. Should i reinstall my OS? In addtion, all my browsers are hijacking by "datingpuma.com" and attacked by "Win 7 Antispyware 2012" virus (before i restored to factory setting).

 

[JMH]

thank you for helping
Should i reinstall my OS?

FYI,
http://www.sevenforums.com/tutorials/1649-clean-install-windows-7-a.html