Tech Support banner
Not open for further replies.
1 - 2 of 2 Posts

2 Posts
Discussion Starter · #1 · (Edited)
Basically at the beginning of last month my computer started to have random BSOD issues. I have uninstalled/re-installed drivers and tried several other recommended fixes. Now I come to you for help. The requested files are attached in a compressed folder.

Running windows 7 64 bit, Radeon 5450, AMD Athlon II x 4 640 Processor (at stock speed). Age...approx 2 1/2 - 3 years old (maybe a little more). Age of OS installation - same as age of computer. System manufacturer - HP.

Model : p6754y

If additional information is needed please just ask.

Thank you for taking the time to look at this post.


TSF Team, Emeritus
4,349 Posts

We have various bug checks:


A fatal hardware error has occurred. This fatal error displays data from the Windows Hardware Error Architecture (WHEA).

If we run an !errrec on the 2nd parameter of the bugcheck (address of the WER structure) we get the following:

Section 0     : Processor Generic
Descriptor    @ fffffa8006baf978
Section       @ fffffa8006bafa50
Offset        : 344
Length        : 192
Flags         : 0x00000001 Primary
Severity      : Fatal

Proc. Type    : x86/x64
Instr. Set    : x64
[COLOR=Red]Error Type    : BUS error[/COLOR]
Operation     : Generic
Flags         : 0x00
Level         : 3
CPU Version   : 0x0000000000100f53
Processor ID  : 0x0000000000000000
^^ BUS error.

Section 2     : x86/x64 MCA
Descriptor    @ fffffa8006bafa08
Section       @ fffffa8006bafb90
Offset        : 664
Length        : 264
Flags         : 0x00000000
Severity      : Fatal

[COLOR=Red]Error         : BUSLG_GENERIC_ERR_*_TIMEOUT_ERR (Proc 0 Bank 4)[/COLOR]
  Status      : 0xfa00000000070f0f
^^ Specifically, a timeout occurred somewhere along the bus (Processor 0 - Cache Bank 4 - *main CPU core*)


This indicates that an exception happened while executing a routine that transitions from non-privileged code to privileged code.

This error has been linked to excessive paged pool usage and may occur due to user-mode graphics drivers crossing over and passing bad data to the kernel code.

BugCheck 3B, {c0000005, fffff8000359d9d9, fffff8800857b3e0, 0}

1: kd> ln fffff8000359d9d9
(fffff800`0359d8b0)   [COLOR=Red]nt!CmpGetNameControlBlock+0x12e[/COLOR]   |  (fffff800`035654a8)   nt!ExEnumHandleTable
^^ The exception occurred in nt!CmpGetNameControlBlock.


This indicates that invalid system memory has been referenced.

Bug check 0x50 usually occurs after the installation of faulty hardware or in the event of failure of installed hardware (usually related to defective RAM, be it main memory, L2 RAM cache, or video RAM).

Another common cause is the installation of a faulty system service.

Antivirus software can also trigger this error, as can a corrupted NTFS volume.

-- PROCESS_NAME: kldw.exe

^^ Kaspersky related process.Interestingly enough, it appears there is no Kaspersky driver(s) listed and loaded as of the latest 0x124 crash. Did you since then remove it? If not, it's likely just an incomplete dump of the modules list (not surprising in 0x124 minidumps).


1. Remove and replace AVG + Kaspersky with Microsoft Security Essentials for temporary troubleshooting purposes. I noticed at one point you had AVG + Kaspersky installed, and as said above, if the modules list is incomplete, you still do.

One of the biggest problems as far as antivirus suites go in terms of conflicts, is if there is more than one antivirus or anti-malware suite installed on the system. In the most basic example, I will use AVG and Norton. Let's say you have both installed and running, this is not a good scenario at all. Most/if not all modern day antivirus suites are allowed direct access (come and go, whenever they want) to the kernel because an antivirus installs interceptors of system events within the kernel code, which passes intercepted data to the antivirus engine for analysis. What's analyzed are things such as - network packets, files, and other various critical data.

AVG removal -

Kaspersky removal - Service articles

MSE - Microsoft Security Essentials - Microsoft Windows
2. Update your chipset - Support & Drivers


If the above fail, there is only so much you can do with a bugcheck like this until it comes down to a faulty processor that will need to be replaced. Start from 1 and work downward:

1. Ensure your temperatures are within standard and nothing's overheating. You can use a program such as Speccy if you'd like to monitor temps - Speccy - System Information - Free Download

2. Clear your CMOS (or load optimized BIOS defaults) to ensure there's no improper BIOS setting - How To Clear CMOS (Reset BIOS)

3. Ensure your BIOS is up to date.

4. The only software conflict that can usually cause *124 bugchecks are OS to BIOS utilities from manufacturer's like Asus' AI Suite. If you have something like this software-wise, remove it ASAP.

5. Run Memtest for NO LESS than ~8 passes (several hours):


Download Memtest86+ here:

Memtest86+ - Advanced Memory Diagnostic Tool

Which should I download?

You can either download the pre-compiled ISO that you would burn to a CD and then boot from the CD, or you can download the auto-installer for the USB key. What this will do is format your USB drive, make it a bootable device, and then install the necessary files. Both do the same job, it's just up to you which you choose, or which you have available (whether it's CD or USB).

Do note that some older generation motherboards do not support USB-based booting, therefore your only option is CD (or Floppy if you really wanted to).

How Memtest works:

Memtest86 writes a series of test patterns to most memory addresses, reads back the data written, and compares it for errors.

The default pass does 9 different tests, varying in access patterns and test data. A tenth test, bit fade, is selectable from the menu. It writes all memory with zeroes, then sleeps for 90 minutes before checking to see if bits have changed (perhaps because of refresh problems). This is repeated with all ones for a total time of 3 hours per pass.

Many chipsets can report RAM speeds and timings via SPD (Serial Presence Detect) or EPP (Enhanced Performance Profiles), and some even support changing the expected memory speed. If the expected memory speed is overclocked, Memtest86 can test that memory performance is error-free with these faster settings.

Some hardware is able to report the "PAT status" (PAT: enabled or PAT: disabled). This is a reference to Intel Performance acceleration technology; there may be BIOS settings which affect this aspect of memory timing.

This information, if available to the program, can be displayed via a menu option.

Any other questions, they can most likely be answered by reading this great guide here:

FAQ : please read before posting

6. If all of the above fail, the only left to do is replace your processor as it is faulty.


1 - 2 of 2 Posts
Not open for further replies.