TechSpot

New hardware and Win XP Pro 64-bit with random halts/BSOD

By nevyn2
Sep 10, 2009
  1. Hi!

    ## General description ##

    I just bought some new hardware and it is giving me a problem that i don't know what to do with. After the assembly and installation of an OS the computer hangs/freezez from time to time. I haven't found a single action that is causing this, it is totally random, i could be surfing the web, playing WoW etc. When it freezez it stops responding in any way, i can't even turn on Caps and i have to restart it with the reset/power button.

    There is no articfacts on the screen or no BSOD and the audio totally dissappears (no stuttering left or anything). The freezez/hangs always occurs inside windows, as of yet it has never done this during the POST or boot of the OS. Sometimes i get a BSOD just after i have typed in my password and the system is on its way loading my profile etc.

    ## Log from Event viewer ##

    These are the only logs that i think is related to these freezez/halts:

    Windows Vista 64-bit:

    EventID 106

    "Event filter with query "SELECT * FROM __InstanceModificationEvent WITHIN 60 WHERE TargetInstance ISA "Win32_Processor" AND TargetInstance.LoadPercentage > 99" could not be reactivated in namespace "//./root/CIMV2" because of error 0x80041003. Events cannot be delivered through this filter until the problem is corrected."

    Windows XP Pro 64-bit SP2:

    Source: WMIxWDM
    Event ID: 106

    Description:

    Machine Check Event reported is a corrected error.

    0000: 00000001 00000001 dde4c3f4 01ca2bb5
    0010: 00000000 00000000 00000004 00000000
    0020: 001d018b 94324c50 2b6eab00 00000001
    0030: 00000000 00000000 00000000 00000000
    0040: 00000000 00000000 00000000 00000000
    0050: 00000000 00000000 00000000 00000000
    0060: 00000000 00000000 00000000 00000000

    This one dissappeared when i changed connector on the motherboard for the front fan from SYS_FAN1 to PWR_FAN. I noticed that front fan was running 3-400 rpm slower than the rear fan so i changed to a different connector and then the WMIxWDM logs dissappeard under Windows XP. Under Vista i don't know if they dissapeared since i hadn't done this change yet when it was installed. I am now seeing new WMIxWDM logs with a different machinecode:

    0000: 00000001 00000001 3c723ef2 01ca2ef3
    0010: 00000000 00000000 00000004 00000000
    0020: 001d017b 94324c50 82a8ab00 00000000
    0030: 00000000 00000000 00000000 00000000
    0040: 00000000 00000000 00000000 00000000
    0050: 00000000 00000000 00000000 00000000
    0060: 00000000 00000000 00000000 00000000
    0070: 00000000 00000000 00000000 00000000
    0080: 00000000 00000000 00000000 00000000
    0090: 00000000 00000000 00000000 00000000
    00a0: 00000000 00000000 00000000 00000000
    00b0: 00000000 00000000 00000000 00000000
    00c0: 00000000 00000000 00000000 00000000
    00d0: 00000000 00000000 00000000 00000000
    00e0: 00000000 00000000 00000000 00000000
    00f0: 00000000 00000000 00000000 00000000

    ----------------------------------------------

    0000: 00000001 00000001 e9fcb950 01ca30b8
    0010: 00000000 00000000 00000004 00000000
    0020: 001d018b 94324c50 8c18ab00 00000000
    0030: 00000000 00000000 00000000 00000000
    0040: 00000000 00000000 00000000 00000000
    0050: 00000000 00000000 00000000 00000000
    0060: 00000000 00000000 00000000 00000000
    0070: 00000000 00000000 00000000 00000000
    0080: 00000000 00000000 00000000 00000000
    0090: 00000000 00000000 00000000 00000000
    00a0: 00000000 00000000 00000000 00000000
    00b0: 00000000 00000000 00000000 00000000
    00c0: 00000000 00000000 00000000 00000000
    00d0: 00000000 00000000 00000000 00000000
    00e0: 00000000 00000000 00000000 00000000
    00f0: 00000000 00000000 00000000 00000000

    I have had several BSOD and here are the log from event viewer for that:

    Error signature

    Error code 000000001000007e, parameter1 ffffffffc0000005, parameter2 fffffadf82564256, parameter3 fffffadf90c68b00, parameter4 fffffadf90c68510.

    0000: 53 79 73 74 65 6d 20 45 System E
    0008: 72 72 6f 72 20 20 45 72 rror Er
    0010: 72 6f 72 20 63 6f 64 65 ror code
    0018: 20 30 30 30 30 30 30 30 0000000
    0020: 30 31 30 30 30 30 30 37 01000007
    0028: 65 20 20 50 61 72 61 6d e Param
    0030: 65 74 65 72 73 20 66 66 eters ff
    0038: 66 66 66 66 66 66 63 30 ffffffc0
    0040: 30 30 30 30 30 35 2c 20 000005,
    0048: 66 66 66 66 66 61 64 66 fffffadf
    0050: 38 32 35 36 34 32 35 36 82564256
    0058: 2c 20 66 66 66 66 66 61 , fffffa
    0060: 64 66 39 30 63 36 38 62 df90c68b
    0068: 30 30 2c 20 66 66 66 66 00, ffff
    0070: 66 61 64 66 39 30 63 36 fadf90c6
    0078: 38 35 31 30 8510

    I have attached all the minidumps i have so hopefully can decipher these and tell what is causing these halts and BSOD. I am running out of ideas what do, i have tested everything that i can think of.

    Thanks in advance
     
  2. nevyn2

    nevyn2 TS Rookie Topic Starter

    I'm sorry but i meant to post this thread i the BSOD part of this forum. Maybe some nice admin can move this thread.

    Again so sorry!
     
  3. Route44

    Route44 TechSpot Ambassador Posts: 12,167   +37

    I read all five minidumps dated 9/10/09 and all are error code 0x7E: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED
    A system thread generated an exception which the error handler did not catch. There are numerous individual causes for this problem, including hardware incompatibility, a faulty device driver or system service, or some software issues. Check Event Viewer (EventVwr.msc) for additional information and note yellow triangles with an exclamation mark or a red x..

    The driver cited as the problem is the Portcls.sys component of your Windows operating system that according to MS provides a collection of audio port drivers and a set of helper functions that can be called by the adapter driver. The PortCls driver provides kernel-streaming capabilities for ISA/DMA and PCI audio device drivers and is implemented in the portcls.sys file as an export driver (a kernel-mode DLL).

    Normally OS drivers are too general to be of much help but other information was contained in the dumps that stated that portcls.sys was preventing the Realtek audio driver rtkhda64.sys from loading resulting in crashes. This is a Realtek Audio Function Driver.

    If this is onboard audio update your Realtec drivers from your motherboard's website.
     
  4. nevyn2

    nevyn2 TS Rookie Topic Starter

    Hi and thanks for your reply!

    And you are correct! This is a Gigabyte GA-MA790XT-UD4P motherboard with onboard RealTek audio!

    Now hopefully this piece of hardware is the casue for both the BSOD and the random system halts without BSOD, the image just freezez and the computer stops responding and the audio dissappear.

    I will uninstall the audio driver and disable the onboard audio in BIOS en run the system for a few days to see if the halts and BSOD are gone.

    Again thanks for taking your time reading the dumps and posting a reply!!!
     
  5. nevyn2

    nevyn2 TS Rookie Topic Starter

    I guess the minidumps are from the BSOD right? I have now disabled the onboard sound card and haven't had any BOSD yet.

    The sad thing is that the random freezez are still happening and when it does this warning show up in the System part of event viewer:

    Source WMIxWDM
    Category: None
    Event ID: 106

    Machine Check Event reported is a corrected error

    Data: Bytes

    0000: 01 00 00 00 01 00 00 00 ........
    0008: 6a ab e3 84 5b 32 ca 01 j«ã„[2Ê.
    0010: 00 00 00 00 00 00 00 00 ........
    0018: 04 00 00 00 00 00 00 00 ........
    0020: 1b 01 1d 00 52 4c 32 d4 ....RL2Ô
    0028: 00 ab 2a a8 00 00 00 00 .«*¨....
    0030: 00 00 00 00 00 00 00 00 ........
    0038: 00 00 00 00 00 00 00 00 ........
    0040: 00 00 00 00 00 00 00 00 ........
    0048: 00 00 00 00 00 00 00 00 ........
    0050: 00 00 00 00 00 00 00 00 ........
    0058: 00 00 00 00 00 00 00 00 ........
    0060: 00 00 00 00 00 00 00 00 ........
    0068: 00 00 00 00 00 00 00 00 ........
    0070: 00 00 00 00 00 00 00 00 ........
    0078: 00 00 00 00 00 00 00 00 ........
    0080: 00 00 00 00 00 00 00 00 ........
    0088: 00 00 00 00 00 00 00 00 ........
    0090: 00 00 00 00 00 00 00 00 ........
    0098: 00 00 00 00 00 00 00 00 ........
    00a0: 00 00 00 00 00 00 00 00 ........
    00a8: 00 00 00 00 00 00 00 00 ........
    00b0: 00 00 00 00 00 00 00 00 ........
    00b8: 00 00 00 00 00 00 00 00 ........
    00c0: 00 00 00 00 00 00 00 00 ........
    00c8: 00 00 00 00 00 00 00 00 ........
    00d0: 00 00 00 00 00 00 00 00 ........
    00d8: 00 00 00 00 00 00 00 00 ........
    00e0: 00 00 00 00 00 00 00 00 ........
    00e8: 00 00 00 00 00 00 00 00 ........
    00f0: 00 00 00 00 00 00 00 00 ........
    00f8: 00 00 00 00 00 00 00 00 ........

    And in Words:

    0000: 00000001 00000001 84e3ab6a 01ca325b
    0010: 00000000 00000000 00000004 00000000
    0020: 001d011b d4324c52 a82aab00 00000000
    0030: 00000000 00000000 00000000 00000000
    0040: 00000000 00000000 00000000 00000000
    0050: 00000000 00000000 00000000 00000000
    0060: 00000000 00000000 00000000 00000000
    0070: 00000000 00000000 00000000 00000000
    0080: 00000000 00000000 00000000 00000000
    0090: 00000000 00000000 00000000 00000000
    00a0: 00000000 00000000 00000000 00000000
    00b0: 00000000 00000000 00000000 00000000
    00c0: 00000000 00000000 00000000 00000000
    00d0: 00000000 00000000 00000000 00000000
    00e0: 00000000 00000000 00000000 00000000
    00f0: 00000000 00000000 00000000 00000000

    Can you or someone else decipher this bytes or word code? Since these are always logged after or right before a system halt/freeze happends i guess they are linked. There are no other warnings. Would be nice to dechipher the code there and maybe see what causing this. Could they be linked to the onboard audio? I have disabled the onboard audio in BIOS and uninstalled the driver from Realtek but when i restarted the machine Windows wanted to install a High def driver for the audio. Should that even show up in device manager after being disabled??

    Thanks in advance.
     
Topic Status:
Not open for further replies.


Add New Comment

TechSpot Members
Login or sign up for free,
it takes about 30 seconds.
You may also...


Get complete access to the TechSpot community. Join thousands of technology enthusiasts that contribute and share knowledge in our forum. Get a private inbox, upload your own photo gallery and more.