DID PBO BREAK MY PC, OR JUST EXPOSE A REAL PROBLEM?

Solvedbsodcpuwhea2 replies 路 244 views 路 started

Accepted solution

by TomasJump to the reply

been there man in Event Viewer, open WHEA-Logger Event 18 and note teh APIC ID or processor core it names... if its alawys teh same core, that core needs a smaller offset or none at all. worked for me anyway 馃し

  1. ugh. heres my crash:

    Your PC ran into a problem and needs to restart. We're

    Your PC ran into a problem and needs to restart. We're
    just collecting some error info, and then we'll restart for
    you.
    42% complete
    For more information about this issue and possible fixes, visit
    our support site.
    
    If you call a support person, give them this info:
    Stop code: IRQL_NOT_LESS_OR_EQUAL
    

    it happens at idle, maybe twice a week. WHEA-Logger Event ID 18 says smth about a processor core and a cache hierarchy error. I have no idea what that means in human terms. if someone can translate those log entries into plain language, that would help a lot. id like to know whether to tweak settings or contact support.

    thinking

    8
  2. Accepted solution

    been there man in Event Viewer, open WHEA-Logger Event 18 and note teh APIC ID or processor core it names... if its alawys teh same core, that core needs a smaller offset or none at all. worked for me anyway 馃し

    0 4 helpful
  3. I'd disagree with going straight back to stock. You can usually keep most of the benefit by easing the offset only on the core that fails.

    2 0 helpful

Reply to this topic

Sign in or create an account to reply.