BCCodes 24, 50, and 'be' on February built Win7 computer

rgnieman · Aug 30, 2012

Thank you in advance for taking the time to help...

My BSODs began on 8/17 and continued into the next day, at which point I said to myself "I'll deal with this later…" so I guess this is later!

OS - Windows 7 Ultimate SP1 x64
Original OS - same
Hardware Age - February 2012
OS Installed - February 2012

CPU - AMD Phenom II x64 3 GHz
Video - ATI Radeon HD 4250 (integrated)
Mobo - ASUS M4A88T-M
P/S - Unsure of brand, 350 watts

Home built machine, no manufacturer/model number

I have run memtest for a few hours with no errors, and it doesn't appear to blue screen in safe mode. I'll run Driver Verifier and report my findings...

JaidynM · Aug 31, 2012

Problem Devices

Code:

Security Processor Loader Driver    ROOT\LEGACY_SPLDR\0000    This device is not present, is not working properly, or does not have all its drivers installed.

You will need to either uninstall the drivers and reinstall the latest version or perform a clean installation of the driver. If the device is disabled please enable it.

Drivers

The following drivers need to be updated:

Code:

PxHlpa64.sys                Wed Jun 24 09:16:35 2009 (4A416253)
atikmpag.sys                Wed Apr 20 11:22:32 2011 (4DAE3558)

These drivers can be found by searching them in Google and then finding the associated software or driver. Finally, find the latest version of this driver or software and download and install it. Some of the drivers may also be found here (if the driver says 'Windows Update' simply make sure all Windows Updates are installed).

You should also update any other drivers you can think of including graphics, audio, chipset, SSD etc.

Hardware

Run a chkdsk on the system partition to check for bad sectors or system errors.
http://support.microsoft.com/kb/315265

Test your RAM using Memtest86+. Let it run until 6-8 passes have completed or errors have been found.
http://memtest.org/#downiso

Vir Gnarus · Aug 31, 2012

Pretty much all of these involve some form of registry activity, most often querying key values. Follow Jaidyn's advice on doing a full CHKDSK. Also you may wanna run Seatools on your drive (all tests except Advanced) to see if you're in the clear there. If you can describe us what drive you have that would be splendid.

rgnieman · Aug 31, 2012

JaidynM said:
Problem Devices

Code:

Security Processor Loader Driver ROOT\LEGACY_SPLDR\0000 This device is not present, is not working properly, or does not have all its drivers installed.

You will need to either uninstall the drivers and reinstall the latest version or perform a clean installation of the driver. If the device is disabled please enable it.

I'm not sure how to go about doing this. This morning before I left for work I poked around in Device Manager and saw nothing by that name, and nothing with a little yellow indicator next to it. Could you get me started?

JaidynM said:
Drivers

The following drivers need to be updated:

Code:

PxHlpa64.sys Wed Jun 24 09:16:35 2009 (4A416253) atikmpag.sys Wed Apr 20 11:22:32 2011 (4DAE3558)

PxHlpa64.sys points to CD/DVD problems. I have Virtual CloneDrive installed to mount ISOs. Should I try uninstalling that? It seems strange to me that this would be causing the issue as it has been installed practically since the beginning, but I'm willing to try.

atikmpag.sys looks like an ATI driver issue... faaaaaantastic. I had a lot of trouble with this driver when I first installed everything. I had to go into the registry and tweak a few things in order for 'scaling' settings to be retained on reboot when outputting to a 1080p display.

I failed to mention in my original post that a full CHKDSK has been run twice, once with many errors and a second time with no errors. My hard drive is a cheapo Seagate Barracuda ST1500DL003 1.5TB "Green" series drive, and I also have an old Fujitsu 160GB drive from a retired macbook that I use for music only. It is rarely accessed.

Overnight, the computer blue screened twice with code 'be'... I'm not sure if this is a result of Driver Verifier or not, but I assume it has been running...?

When I get home from work this afternoon I'll update drivers and run seatools. After that, I'll let memtest run overnight if the problems persist.

writhziden · Aug 31, 2012

Code:

Security Processor Loader Driver    ROOT\LEGACY_SPLDR\0000    This device is not present, is not working properly, or does not have all its drivers installed.

The above can point to the display card driver, so the atimpag.sys re-install may resolve it. The SPLDR problem can also be caused by a malicious item on the system, i.e. a virus, malware, etc.

When you re-install your ATI driver, use the following steps:

Uninstall AMD Catalyst Install Manager if it is listed (this should remove all AMD graphics software and drivers)
If AMD Catalyst Install Manager is not listed, use the following method to uninstall the graphics drivers:
- Click Start Menu
- Right Click My Computer/Computer
- Click Manage
- Click Device Manager from the list on the left
- Expand Display adapters
- Do the following for each adapter (in case you have multiple display cards)
  - Right click the adapter
  - Click Uninstall (do not click OK in the dialog box that pops up after hitting Uninstall)
  - Put a tick in Delete driver software for this device (if this option is available, otherwise just hit OK) and hit OK
Alternatively:
- Login as an adminstrative user
- Click Start Menu
- Click Control Panel
- Click Hardware and Sound
- Click Device Manager (the last link under Devices and Printers)
- Expand Display adapters
- Do the following for each adapter (in case you have multiple display cards)
  - Right click the adapter
  - Click Uninstall (do not click OK in the dialog box that pops up after hitting Uninstall)
  - Put a tick in Delete driver software for this device (if this option is available, otherwise just hit OK) and hit OK
Restart your computer after uninstalling drivers for all display cards
Install the driver you selected for the display cards once Windows starts

You can also install the ATI Drivers without the Catalyst Control Center/AMD Vision Engine Control Center software: ATI video cards - DRIVER ONLY installation procedure - Steps courtesy of usasma.

Vir Gnarus · Aug 31, 2012

You can verify (punny) if Driver Verifier is running by going into command prompt (type 'cmd' in start menu) then type "verifier /query". Or go into Driver Verifier as usual and click "Display existing settings". If either of these show up no drivers being verified, then it's not on. The 0xBE crashes kinda hint to me that it isn't on, but send us the crashdumps anyways.

rgnieman · Sep 1, 2012

Thank you for your help so far!

I updated the ATI drivers following the instructions posted and gladly left out the Catalyst Control Center. Just now I ran Seatools and it failed the long test with about 100 bad sectors which were repaired and it now passes.

I'm leaving for several hours so I'll leave it booted to Windows while I'm gone and see what happens.

More to come...

Edit: This hard drive is still under warranty... even though the sectors were repaired, do you think I should look into getting an RMA?

writhziden · Sep 2, 2012

If it had bad sectors, it is probably a good idea to see if you can RMA it. A lot of companies I know of will not mess around with bad sectors, so in the corporate world, any sign of bad sectors leads to an RMA and/or drive replacement.

rgnieman · Sep 3, 2012

I don't want to get ahead of myself here, but I think the issues have been resolved. It has been over 24 hours now without a BSOD.

Thank you again for all your help. It really is very much appreciated!

rgnieman · Sep 3, 2012

Yep. Ahead of myself. Here are two crash dump files.

Driver Verifier is running now (but might not have been when those were dumped).

jcgriff2 · Sep 3, 2012

Hi -

The bugchecks on the last 2 dumps -

0xbe = Attempt to write to read-only memory

See if Driver Verifier flags any 3rd party drivers -

https://www.sysnative.com/forums/showthread.php/29-Driver-Verifier-BSOD-related

Regards. . .

jcgriff2

BSOD SUMMARY

Code:


Debug session time: Mon Sep  3 18:59:04.082 2012 (GMT-4)
Loading Dump File [C:\Users\PalmDesert\SysnativeBSODApps\090312-21184-01.dmp]
Built by: 7601.17835.amd64fre.win7sp1_gdr.120503-2030
System Uptime: 0 days 0:27:06.908
BugCheck BE, {fffff8a0019fd000, 80000001d3bc4121, fffff88007c7a7a0, b}
Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+4522e )
Bugcheck code 000000bE
Arguments fffff8a0`019fd000 80000001`d3bc4121 fffff880`07c7a7a0 00000000`0000000b
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0xBE
PROCESS_NAME:  svchost.exe
FAILURE_BUCKET_ID:  X64_0xBE_nt!_??_::FNODOBFM::_string_+4522e
BiosVersion = 2403   
BiosReleaseDate = 12/23/2010
SystemManufacturer = System manufacturer
SystemProductName = System Product Name

¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``

Debug session time: Mon Sep  3 18:30:49.944 2012 (GMT-4)
Loading Dump File [C:\Users\PalmDesert\SysnativeBSODApps\090312-28017-01.dmp]
Built by: 7601.17835.amd64fre.win7sp1_gdr.120503-2030
System Uptime: 0 days 18:37:07.115
BugCheck BE, {fffff8a000a88000, bf2000011ebf8820, fffff880099917a0, e}
*** WARNING: Unable to verify timestamp for win32k.sys
*** ERROR: Module load completed but symbols could not be loaded for win32k.sys
Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+457ff )
Bugcheck code 000000bE
Arguments fffff8a0`00a88000 bf200001`1ebf8820 fffff880`099917a0 00000000`0000000e
DEFAULT_BUCKET_ID:  VERIFIER_ENABLED_VISTA_MINIDUMP
BUGCHECK_STR:  0xBE
PROCESS_NAME:  svchost.exe
FAILURE_BUCKET_ID:  X64_0xBE_VRF_nt!_??_::FNODOBFM::_string_+457ff
BiosVersion = 2403   
BiosReleaseDate = 12/23/2010
SystemManufacturer = System manufacturer
SystemProductName = System Product Name
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``

         
       J. C. Griffith, Microsoft MVP (jcgriff2)   
             
           https://mvp.support.microsoft.com/profile/Griffith   

           [url]www.sysnative.com[/url]
             
           [url]www.jcgriff2.com[/url] 


¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨

Vir Gnarus · Sep 4, 2012

Your Seagate drive having 100 bad sectors ain't a good thing, plus I'm sure there were more found previously from CHKDSK when you had it check for bad sectors. You'd best backup data from it and RMA it as soon as you can.

rgnieman · Sep 18, 2012

update... got the new hard drive in the mail today. Thanks again for your help.

writhziden · Sep 19, 2012

Glad you got the new drive. Let us know whether your system is now stable once you've had a chance to do your normal routine for a while.

Search

Search

BCCodes 24, 50, and 'be' on February built Win7 computer

rgnieman

Member

Attachments

JaidynM

BSOD Kernel Dump Senior Analyst

Vir Gnarus

BSOD Kernel Dump Expert

rgnieman

Member

writhziden

Administrator, .NET/UWP Developer

Vir Gnarus

BSOD Kernel Dump Expert

rgnieman

Member

writhziden

Administrator, .NET/UWP Developer

rgnieman

Member

rgnieman

Member

Attachments

jcgriff2

Co-Founder / Admin
BSOD Instructor/Expert
Microsoft MVP (Ret.)

Vir Gnarus

BSOD Kernel Dump Expert

rgnieman

Member

writhziden

Administrator, .NET/UWP Developer

BCCodes 24, 50, and 'be' on February built Win7 computer

Member

Attachments

BSOD Kernel Dump Senior Analyst

BSOD Kernel Dump Expert

Member

Administrator, .NET/UWP Developer

BSOD Kernel Dump Expert

Member

Administrator, .NET/UWP Developer

Member

Member

Attachments

Co-Founder / AdminBSOD Instructor/ExpertMicrosoft MVP (Ret.)

BSOD Kernel Dump Expert

Member

Administrator, .NET/UWP Developer

Co-Founder / Admin
BSOD Instructor/Expert
Microsoft MVP (Ret.)