BlueScreen error (monitor has no display) - Mac Pro 2008 running Win7


  1. Posts : 4
    Windows 7 Professional x64
       #1

    BlueScreen error (monitor has no display) - Mac Pro 2008 running Win7


    Hello, I'm new to this forum, so apologises in advance if I do anything wrong in terms of posting content, etc.

    I've been having a reoccurring issue for some time now whereby when I'm using the computer, often for trivial tasks such as web browsing, the monitor will suddenly lose connection and display a "cable not connected" message, as it normally does before you switch the PC on. I have to resolve this by switching off the computer and booting it up again. This same issue sometimes occurs when I first boot up the PC, the loud fan that starts up for 3 - 4 seconds (which I think is the GFX card) continues to do so continuously and the monitor has the "cable not connected" message. I've also sometimes had a single beeping noise when I first boot up the computer, and on rare occasions the beep is prologued until I turn it off.

    Unfortunately this behaviour is somewhat random and it may behave completely normally for several hours or even a couple of days, and often when one of the aforementioned faults does occur, when I boot it back up, it's ok.

    I thought the culprit was the graphics card, so I got a new replacement, but I'm still getting the issue. Then today, I had the same issue but the PC actually restarted itself and when I went back into Windows 7, there was an error saying "Windows has recovered from an unexpected shutdown", and the Problem Event Name was BlueScreen, noting:

    Problem signature:
    Problem Event Name: BlueScreen
    OS Version: 6.1.7601.2.1.0.256.48
    Locale ID: 2057

    Additional information about the problem:
    BCCode: 124
    BCP1: 0000000000000000
    BCP2: FFFFFA80089958F8
    BCP3: 0000000000000000
    BCP4: 0000000000000000
    OS Version: 6_1_7601
    Service Pack: 1_0
    Product: 256_1


    FYI, I have attached the dump file to this post.

    I then went to Windows Event Viewer, and in the System log, I found three errors. All were "Event 18 WHEA-Logger", and the general description was:

    "A fatal hardware error has occurred.

    Reported by component: Processor Core
    Error Source: Machine Check Exception
    Error Type: Bus/Interconnect Error
    Processor ID: 5

    The details view of this entry contains further information."

    Two others had the same description except the Processor ID was 4. Furthermore, 'friendly view' gives the following details:

    - EventData

    ErrorSource 3

    ApicId 4

    MCABank 0

    MciStat 0xf200084000000800

    MciAddr 0x0

    MciMisc 0x0

    ErrorType 10

    TransactionType 256

    Participation 0

    RequestType 0

    MemorIO 0

    MemHierarchyLvl 0

    Timeout 0

    OperationType 256

    Channel 256

    Length 928

    RawData 435045521002FFFFFFFF03000100000002000000A00300003201120010051014000000000000000000000000000000000000 0000000000000000000000000000BDC407CF89B7184EB3C41F732CB57131FE6FF5E89C91C54CBA8865ABE14913BBA6846AFB 9CAFD10102000000000000000000000000000000000000000000000058010000C00000000102000001000000ADCC7698B447 DB4BB65E16F193C4F3DB00000000000000000000000000000000010000000000000000000000000000000000000000000000 18020000800000000102000000000000B0A03EDC44A19747B95B53FA242B6E1D000000000000000000000000000000000100 0000000000000000000000000000000000000000000098020000080100000102000000000000011D1E8AF94257459C33565E 5CC3F7E8000000000000000000000000000000000100000000000000000000000000000000000000000000007F0100000000 0000000204000000000076060100000000000000000000000000000000000000000000000000000000000000000000000000 0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000 0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000004000000 0000000000000000000000000000000000000000000000000000000000000000000000000700000000000000040000000000 00007606010000080404BDE30C00FFFBEBBF0000000000000000000000000000000000000000000000000000000000000000 B3F8F31CB1C5A249AA595EEF92FFA63C01000000000000009E07002600000000000000000000000000000000000000000000 0000000000000000000000000000010000000100000064C526059DAFD1010400000000000000000000000000000000000000 0000000000080000400800F20000000000000000000000000000000000000000000000000000000000000000000000000000 0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000 0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000 0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000 00000000000000000000000000000000000000000000000000000000

    EventData

    ErrorSource 3

    ApicId 4

    MCABank 5

    MciStat 0xf200001034000e0f

    MciAddr 0x0

    MciMisc 0x0

    ErrorType 10

    TransactionType 256

    Participation 3

    RequestType 0

    MemorIO 3

    MemHierarchyLvl 3

    Timeout 0

    OperationType 256

    Channel 256

    Length 928

    RawData 435045521002FFFFFFFF03000100000002000000A00300003201120010051014000000000000000000000000000000000000 0000000000000000000000000000BDC407CF89B7184EB3C41F732CB57131FE6FF5E89C91C54CBA8865ABE14913BBA7846AFB 9CAFD10102000000000000000000000000000000000000000000000058010000C00000000102000001000000ADCC7698B447 DB4BB65E16F193C4F3DB00000000000000000000000000000000010000000000000000000000000000000000000000000000 18020000800000000102000000000000B0A03EDC44A19747B95B53FA242B6E1D000000000000000000000000000000000100 0000000000000000000000000000000000000000000098020000080100000102000000000000011D1E8AF94257459C33565E 5CC3F7E8000000000000000000000000000000000100000000000000000000000000000000000000000000007F0100000000 0000000204000003000076060100000000000000000000000000000000000000000000000000000000000000000000000000 0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000 0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000004000000 0000000000000000000000000000000000000000000000000000000000000000000000000700000000000000040000000000 00007606010000080404BDE30C00FFFBEBBF0000000000000000000000000000000000000000000000000000000000000000 B3F8F31CB1C5A249AA595EEF92FFA63C01000000000000009E07C0E606000000000000000000000000000000000000000000 0000000000000000000000000000010000000100000064C526059DAFD1010400000000000000000000000000000000000000 050000000F0E0034100000F20000000000000000000000000000000000000000000000000000000000000000000000000000 0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000 0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000 0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000 00000000000000000000000000000000000000000000000000000000

    EventData

    ErrorSource 3

    ApicId 5

    MCABank 5

    MciStat 0xf200001010000e0f

    MciAddr 0x0

    MciMisc 0x0

    ErrorType 10

    TransactionType 256

    Participation 3

    RequestType 0

    MemorIO 3

    MemHierarchyLvl 3

    Timeout 0

    OperationType 256

    Channel 256

    Length 928

    RawData 435045521002FFFFFFFF03000100000002000000A00300003201120010051014000000000000000000000000000000000000 0000000000000000000000000000BDC407CF89B7184EB3C41F732CB57131FE6FF5E89C91C54CBA8865ABE14913BBA8846AFB 9CAFD10102000000000000000000000000000000000000000000000058010000C00000000102000001000000ADCC7698B447 DB4BB65E16F193C4F3DB00000000000000000000000000000000010000000000000000000000000000000000000000000000 18020000800000000102000000000000B0A03EDC44A19747B95B53FA242B6E1D000000000000000000000000000000000100 0000000000000000000000000000000000000000000098020000080100000102000000000000011D1E8AF94257459C33565E 5CC3F7E8000000000000000000000000000000000100000000000000000000000000000000000000000000007F0100000000 0000000204000003000076060100000000000000000000000000000000000000000000000000000000000000000000000000 0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000 0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000005000000 0000000000000000000000000000000000000000000000000000000000000000000000000700000000000000050000000000 00007606010000080405BDE30C00FFFBEBBF0000000000000000000000000000000000000000000000000000000000000000 B3F8F31CB1C5A249AA595EEF92FFA63C01000000000000009E07C0E606000000000000000000000000000000000000000000 0000000000000000000000000000010000000100000064C526059DAFD1010500000000000000000000000000000000000000 050000000F0E0010100000F20000000000000000000000000000000000000000000000000000000000000000000000000000 0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000 0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000 0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000 00000000000000000000000000000000000000000000000000000000

    I hope somebody can provide some help on what the issue may be and how I may be able to resolve it. Thanks in advance.

    EDIT: I have now also attached the .zip file created by DM Log Collector.
    Last edited by tranquility2k4; 19 May 2016 at 08:56.
      My Computer


  2. Posts : 7,050
    Windows 10 Pro
       #2
      My Computer


  3. Posts : 4
    Windows 7 Professional x64
    Thread Starter
       #3

    axe0 said:
    I've now done this...
      My Computer


  4. Posts : 7,050
    Windows 10 Pro
       #4

    The cause is probably the BIOS seeing it is dating before the release of Windows 7.
    Given the type of the crashes (0x124 = hardware crash) and the reported error (no time-out between data on the bus) it could be incompatibility (incompatibility doesn't have to show up on day 1 but can occur some time after installation) if there is no BIOS update available.
    Code:
    ===============================================================================
    Section 2     : x86/x64 MCA
    -------------------------------------------------------------------------------
    Descriptor    @ fffffa8008995a08
    Section       @ fffffa8008995b90
    Offset        : 664
    Length        : 264
    Flags         : 0x00000000
    Severity      : Fatal
    
    Error         : BUSL0_SRC_ERR_M_NOTIMEOUT_ERR (Proc 4 Bank 0)
      Status      : 0xf200084000000800
      My Computer


  5. Posts : 4
    Windows 7 Professional x64
    Thread Starter
       #5

    axe0 said:
    The cause is probably the BIOS seeing it is dating before the release of Windows 7.
    Given the type of the crashes (0x124 = hardware crash) and the reported error (no time-out between data on the bus) it could be incompatibility (incompatibility doesn't have to show up on day 1 but can occur some time after installation) if there is no BIOS update available.
    Code:
    ===============================================================================
    Section 2     : x86/x64 MCA
    -------------------------------------------------------------------------------
    Descriptor    @ fffffa8008995a08
    Section       @ fffffa8008995b90
    Offset        : 664
    Length        : 264
    Flags         : 0x00000000
    Severity      : Fatal
    
    Error         : BUSL0_SRC_ERR_M_NOTIMEOUT_ERR (Proc 4 Bank 0)
      Status      : 0xf200084000000800
    That's strange as I had the Mac pro since 2008 and these issues have only been occurring in the past few months.

    How would I go about resolving the issue?
      My Computer


  6. Posts : 25,847
    Windows 10 Pro. 64/ version 1709 Windows 7 Pro/64
       #6

    axe0 can this be causing a bios and driver problem?

    From tranquility2k4 System Specs

    System Manufacturer/Model Number Mac Pro (2008)
    OS Windows 7 Professional x64
      My Computer


  7. Posts : 7,050
    Windows 10 Pro
       #7

    The 0x101 has as common causes
    • BIOS,
    • Hardware,
    • Drivers

    The 0x124 has as common causes,
    • BIOS,
    • Hardware,
    • Drivers,

    I've not included overclocking, overheating and improper cooling but you can include it with hardware.

    Though it is difficult to say what exactly is the cause, especially because of the 0x124 which only reports why a crash has occured but not what caused the crash.

    The BIOS is dating 2008 as the systeminfo.txt file is showing, this is before the release of Windows 7 as everyone knows and could be a reason for incompatibility.
    Code:
    BIOS Version:              Apple Inc.     MP31.88Z.006C.B05.0802291410, 29/02/2008
    If drivers are also causing problems then my guess would be the chipset drivers as the reported error is a bus error, though as with other 0x124 it cannot be said with 100% certainty until it is being tested by updating (or reinstalling).

    @tranquility2k4, if no BIOS update is available it can be quite difficult to troubleshoot this completely and for the sake of ease I would go for incompatibility.
    We could run some tests, but I'm afraid that those tests may make things worse as some are stress tests which let the component work harder raising the temperature what may cause hardware damage if not aborted in time or if errors show up it is a faulty component.

    That's strange as I had the Mac pro since 2008 and these issues have only been occurring in the past few months.
    That isn't really strange, if nothing has been replaced your hardware is 8 years old, most hardware don't survive that long and start to fail.
      My Computer


  8. Posts : 4
    Windows 7 Professional x64
    Thread Starter
       #8

    Ok so to update. I often have this problem when I boot the computer and the monitor shows no display and I get a constant high pitched beeping noise. I also had it when bringing the PC back from 'sleep' mode.

    Yesterday I had this issue from sleep and I've looked in the logs and found this - firstly: Event 42 Kernel-Power: "The system is entering sleep. Sleep Reason: Application API".

    Then the error is: Event 12, HAL: "The platform firmware has corrupted memory across the previous system power transition. Please check for updated firmware for your system."

    System

    - Provider


    [ Name] Microsoft-Windows-HAL


    [ Guid] {63D1E632-95CC-4443-9312-AF927761D52A}



    EventID 12


    Version 0


    Level 2


    Task 0


    Opcode 0


    Keywords 0x8000000000000001

    - TimeCreated


    [ SystemTime] 2016-05-21T12:35:41.607013800Z



    EventRecordID 708032


    Correlation

    - Execution


    [ ProcessID] 4


    [ ThreadID] 4988



    Channel System


    Computer LAA-PC


    Security
    - EventData

    Count 1

    FirstPage 143

    LastPage 143


    Don't know if this helps you diagnose anything? I would be highly surprised if there is a temperature problem. I am not overclocking and the monitor losing connection seems so random, sometimes at start up, and often when I'm not doing anything intensive with the PC.

    How could I check if there is a BIOS update available and how would I apply this? Can you advise? Also, could it be that my graphics card drivers for the Nvidia Geforce 8800gt may be causing it if they're outdated? I doubt that would explain issues at startup however.
      My Computer


  9. Posts : 7,050
    Windows 10 Pro
       #9

    Then the error is: Event 12, HAL: "The platform firmware has corrupted memory across the previous system power transition. Please check for updated firmware for your system."
    The BIOS.

    I cannot answer your questions because I'm not familiair with Mac, I have no idea how Apple provides BIOS updates if they provide them nor where to find them or how to go about it.

    Also, could it be that my graphics card drivers for the Nvidia Geforce 8800gt may be causing it if they're outdated?
    These kind of speculations aren't necessary, currently your BIOS is what you need to focus on.
      My Computer


 

  Related Discussions
Our Sites
Site Links
About Us
Windows 7 Forums is an independent web site and has not been authorized, sponsored, or otherwise approved by Microsoft Corporation. "Windows 7" and related materials are trademarks of Microsoft Corp.

© Designer Media Ltd
All times are GMT -5. The time now is 16:08.
Find Us