CPU_CALL_ERROR?

Patrick · Sep 28, 2013

Interesting *D1 I came across, I've attached it if anyone wants to take a look.

Code:

*** Possible invalid call from 83a3541e ( hal!HalpTscQueryPerformanceCounter+0x28 )
*** Expected target 83a37120 ( hal!_aullshr+0x0 )

MODULE_NAME: hardware

IMAGE_NAME:  hardware

BUCKET_ID:  CPU_CALL_ERROR

I've never seen CPU_CALL_ERROR before. Can't seem to locate any info about it either other than threads it was mentioned in from pasting a dump. What does this imply?

Regards,

Patrick

View attachment 092813-69701-01.rar

x BlueRobot · Sep 30, 2013

On the face of it, I'm considering the CPU has ran into a problem calling a certain instruction or any instruction for that matter. Have you checked the CPU documentation? It may be listed in there.

Deek · Sep 30, 2013

Step 1: BIOS UPDATE

Some bios update will update the microcode on the CPU, others will not, but they sometimes have a separate microcode update. Compaq/HP is a common one that will have a separate microcode update.

Step 2: look for microcode update.

Did any of your hardware change? I would also do a mem test with memtest86, at least 8-10 passes. Also consider a cpu stability tester like this: Download CPU Stability Test - MajorGeeks that will test your CPU for problems with the on-die cache.

When does the error occur?

Deek

Patrick · Sep 30, 2013

Deek said:
Step 1: BIOS UPDATE

Some bios update will update the microcode on the CPU, others will not, but they sometimes have a separate microcode update. Compaq/HP is a common one that will have a separate microcode update.

Step 2: look for microcode update.

Did any of your hardware change? I would also do a mem test with memtest86, at least 8-10 passes.

I'm asking what a CPU_CALL_ERROR is, not the troubleshooting steps that should be taken :grin1:

I've never seen this error before. I cannot find any documentation on MSDN or any of my debugging books.

x BlueRobot said:
On the face of it, I'm considering the CPU has ran into a problem calling a certain instruction or any instruction for that matter. Have you checked the CPU documentation? It may be listed in there.

That's exactly what I thought. I have not due to the OP not replying. If and when they do, I will go further and keep updated.

Deek · Sep 30, 2013

I see...in that case, the error may indicate a call being made to the CPU instruction set that the CPU doesn't know how to handle...It can happen when the CPU is not detected correctly or when the specific CPU isn't supported by bios....The being said, bad memory or bad cache on the CPU can also cause the issue.

Does it happen during post? In windows?

Patrick · Sep 30, 2013

Yep, you two are definitely onto something. That's what I was possibly thinking as well. I will be sure to keep you both informed if and when the OP replies. I hope he or she does... it'd be interesting to find out.

x BlueRobot · Sep 30, 2013

Code:

[Processor Information (Type 4) - Length 35 - Handle 0004h]
  Socket Designation            Socket 775
  Processor Type                Central Processor
  Processor Family              01h - Other
  Processor Manufacturer        Intel
  Processor ID                  640f0000fffbebbf
  Processor Version             Intel(R) Pentium(R) D CPU
  Processor Voltage             8ch - 1.2V
  External Clock                200MHz
  Max Speed                     3000MHz
  Current Speed                 3000MHz
  Status                        Enabled Populated
  Processor Upgrade             ZIF Socket
  L1 Cache Handle               0008h
  L2 Cache Handle               0009h
  L3 Cache Handle               [Not Present]
  Serial Number                  
  Asset Tag Number               
  Part Number

Code:

0: kd> !sysinfo cpumicrocode
Initial Microcode Version: 00000004:00000000
 Cached Microcode Version: 00000004:00000000
         Processor Family: 0f
          Processor Model: 06
       Processor Stepping: 04

Just some information about the CPU from the dump file, which may be helpful when checking the CPU documentation, I may actually check the documentation myself tomorrow afternoon.

muhahaa · Oct 1, 2013

I think it implies that the processor executed something else than what the CALL instruction told. However, I'd first consider the possibility of a stack buffer overflow, a common software vulnerability that can cause the function return address to be overwritten (possibly with an attacker-supplied value).

Stack buffer overflow - Wikipedia, the free encyclopedia

Search

Search

CPU_CALL_ERROR?

Patrick

Sysnative Staff

x BlueRobot

Administrator

Deek

Well-known member

Patrick

Sysnative Staff

Deek

Well-known member

Patrick

Sysnative Staff

x BlueRobot

Administrator

muhahaa

Windows Specialist