locked
BSOD 0x124 wow-64.exe TLB RRS feed

  • Question

  • I've been having some BSOD's which bluescreenview says "seems to be caused by the following file: hal.dll" but, to me, it looks like windbg is saying something with the processor.  I really dont know either way so figured i'd get opinion(s) from those that can better understand these dmp files.  

    Some additional info:  it is a laptop, lenovo b575 with an AMD E350 APU, 4gb ram, win7 64 bit OS.  I've only had this BSOD while running world of warcraft 64 bit.  I was thinking it was related to whether it was running in direct x 11 or direct x 9, but just had a BSOD while running WoW-64.exe in direct x 9... so the dX version's outta the equation.  Havent yet had enough time to test if 32 bit wow causes the same crash, or any crash, since i was thinking it was Dx9/Dx11 related.. but that theory (Dx9/Dx11) was disproved last night when wow-64 Dx9 was going and had another BSOD.  

    here's the .dmp's and an xml of system info: 

    https://docs.google.com/open?id=0BzrYLO9UAZa1MmVNeUs4bFpzSDg
    https://docs.google.com/open?id=0BzrYLO9UAZa1Qk9rdVhwbHptb0E
    https://docs.google.com/open?id=0BzrYLO9UAZa1QnhfSGZoY0hJeXc
    https://docs.google.com/open?id=0BzrYLO9UAZa1UlFWVUZIUkFudFk

    https://docs.google.com/open?id=0BzrYLO9UAZa1NnBUZWNDZVRnaXM

    i've done:

    !analyze -v and

    !errrec <Address of the WHEA_ERROR_RECORD structure> (this is not the same 'address' across all the dumps, but to me the result seems to be pointing to the same thing.. possibly different cores or something.... then again i'm not fluent with all this debugging stuff either) 

    not fluent in all windbg commands, but i'm sure there's someone(s) here that knows of other commands that would fetch useful information if there are any, and better be able to understand the output than myself.  

    Sunday, September 23, 2012 10:04 PM

Answers

All replies

  • 124 is usually a crtitical hardware error,

    http://mikemstech.blogspot.com/2010/07/windbgkd-debugging-processor-cache.html

    Looking at one of the dumps, it might be worth seeing if there is a newer BIOS version for your system,

    0: kd> !sysinfo machineid
    Machine ID Information [From Smbios 2.6, DMIVersion 38, Size=1719]
    BiosMajorRelease = 0
    BiosMinorRelease = 1
    BiosVendor = LENOVO
    BiosVersion = 52CN11WW
    BiosReleaseDate = 05/12/2011
    SystemManufacturer = LENOVO
    SystemProductName = 1450A5U
    SystemFamily = IDEAPAD        
    SystemVersion = Lenovo B575
    SystemSKU = System SKU Number Unknown
    BaseBoardManufacturer = LENOVO
    BaseBoardProduct = Inagua
    BaseBoardVersion = 109-B78210-00A


    If it's still under warranty, you could also contact Lenovo.

    • Proposed as answer by Jeremy_Wu Tuesday, September 25, 2012 6:44 AM
    Monday, September 24, 2012 3:30 AM
  • When checking for BIOS update make sure look at the Chipset see if there is a update for that as well.

    Monday, September 24, 2012 8:34 PM
  • I've actually contacted lenovo, and the first resolution was to change the hard drive and memory (imagine that sort of response with what i can find as pointing to the processor and/or graphics)....

    I've currently got the laptop trying to load some POJ "recovery" disks onto a new hard drive that i don't know if it was totally blank at the start of the process, but it's some disks lenovo's put together that allegedly puts the B575 back to out of box condition, starting with a diskpart clean, so i'd assume they've built those disks to do that "recovery" from a totally blank disk since diskpart wipes the disk... but it's been on disk two (one of two dvd's.. first was a CD) for 8 hours now.  Disk one (a CD) is labeled start your recovery here... and the odd thing is disk two (a DVD) says applications and drivers while disk 3 says operating system or somesuch.  If i had the actual disks i would start by installing win7 then do the unincluded applications and drivers... not do the applications and drivers before finishing the OS.

    But my reasoning behind doing what the laptop's doing at the moment is to hopefully prove to lenovo their first prognosis of hard drive and HALF the memory was incorrect (has 2x2 GB ram, they only sent 1x2 GB ram), along with a hard drive. 

    BIOS update sounds like a possible culprit because that's one of the base drivers that has a large hand in how the computer operates.. so i'll see if lenovo has a bios update available for the motherboard they made... and hopefully these "recovery" disks finish sometime before tomorrow evening or i'm pulling the plug on 'em with them having ran longer than microsoft's longest estimated time for win7 install of 20 hours and some change. 

    Wednesday, September 26, 2012 7:39 AM
  • Hi,


    Just check how is the issue going now.


    Thanks.


    Jeremy Wu

    TechNet Community Support


    • Edited by Jeremy_Wu Thursday, September 27, 2012 3:42 PM
    Thursday, September 27, 2012 3:42 PM
  • I asked lenovo about a bios update they said there wasn't an update. 

    Been working on getting a new hard drive operational enough to see if the BSOD happens with the fresh 'install' of windows, windows updates, graphical driver, and see if the crash happens while running the same program in 64 bit.  Some odd somehow lenovo's first response to the information provided in the crash files was "oh lets change the hard drive and memory" (half the memory mind you, with no way to know which one to change either lol)

    For now i've just been running the program in 32 bit and haven't seen a crash while running it 32 bit. 

    If i haven't already stated such: i've set the virtual memory to a fixed amount of 5,000 something mb (whatever it said for 'reccomended')

    And if the person that suggested chipset driver means the processor driver, i'd previously checked that since all this BSOD started and have the most recent version (unless they JUST put out a new one)

    Thursday, September 27, 2012 10:42 PM
  • I'm inclined to say that the processor could be bad too. The TLB keeps all of the cores in sync in terms of the memory that they are accessing and operating on. I've never seen a hard drive issue manifest itself with a WHEA_UNCORRECTABLE_ERROR bugcheck. If you talk with Lenovo, you might see if they have any specialized diagnostic tools for the processor or the motherboard on the system. Have you run a memory test yet?

    http://mikemstech.blogspot.com/2011/11/troubleshooting-memory-errors.html

    • Marked as answer by Jeremy_Wu Sunday, October 7, 2012 11:06 PM
    Friday, September 28, 2012 3:57 AM