Windows 8 and 8.1 Forums


BSOD problems, mostly caused by halmacpi.dll

  1. #1

    BSOD problems, mostly caused by halmacpi.dll


    My Dell Venue 8 Pro most of the time reboots when waking up from standby, this also could happen on itself too (mostly by timer wakeups), or somewhen while using it.

    ==================================================
    Dump File : 031614-11812-01.dmp
    Crash Time : 16.03.2014 18:01:09
    Bug Check String :
    Bug Check Code : 0x00000101
    Parameter 1 : 0x00000030
    Parameter 2 : 0x00000000
    Parameter 3 : 0x825db120
    Parameter 4 : 0x00000003
    Caused By Driver : halmacpi.dll
    Caused By Address : halmacpi.dll+4f28
    File Description : Hardware Abstraction Layer DLL
    Product Name : Microsoft® Windows® Operating System
    Company : Microsoft Corporation
    File Version : 6.3.9600.16500 (winblue_gdr.131226-1506)
    Processor : 32-bit
    Crash Address : ntoskrnl.exe+100584
    Stack Address 1 : ntoskrnl.exe+6df4d
    Stack Address 2 : ntoskrnl.exe+6def6
    Stack Address 3 : ntoskrnl.exe+17a7a7
    Computer Name :
    Full Path : C:\Windows\Minidump\031614-11812-01.dmp
    Processors Count : 4
    Major Version : 15
    Minor Version : 9600
    Dump File Size : 153.328
    Dump File Time : 16.03.2014 18:01:49
    ==================================================
    Last edited by dfgfgd; 16 Mar 2014 at 17:38.

      My System SpecsSystem Spec

  2. #2


    Posts : 5,139
    Win8.1Pro - Finally!!!


    Please provide this information so we can provide a complete analysis (from the Pinned Topic at the top of the forum): Blue Screen of Death (BSOD) Posting Instructions Please use Option 1 as it provides Event Viewer logs.

    Please note the drivers below that date from before the release of Windows 8.1 (17 Oct 2013) - check to see that each and every one is compatible w/Windows 8.1 (at the manufacturer's website). If not, you must either remove the device and it's software - or locate a Windows 8.1 compatible update on the web.




    Analysis:
    The following is for informational purposes only.
    Code:
    **************************Sun Mar 16 16:52:07.158 2014 (UTC - 4:00)**************************
    Loading Dump File [C:\Users\John\SysnativeBSODApps\031614-11281-01.dmp]
    Windows 8 Kernel Version 9600 MP (4 procs) Free x86 compatible
    Built by: 9600.16452.x86fre.winblue_gdr.131030-1505
    System Uptime:0 days 3:50:29.657
    Probably caused by :Unknown_Image ( ANALYSIS_INCONCLUSIVE )
    BugCheck 101, {30, 0, 829db120, 3}
    BugCheck Info: CLOCK_WATCHDOG_TIMEOUT (101)
    Arguments: 
    Arg1: 00000030, Clock interrupt time out interval in nominal clock ticks.
    Arg2: 00000000, 0.
    Arg3: 829db120, The PRCB address of the hung processor.
    Arg4: 00000003, 0.
    BUGCHECK_STR:  CLOCK_WATCHDOG_TIMEOUT_4_PROC
    PROCESS_NAME:  System
    FAILURE_BUCKET_ID: CLOCK_WATCHDOG_TIMEOUT_4_PROC_ANALYSIS_INCONCLUSIVE
    CPUID:        "Intel(R) Atom(TM) CPU  Z3740D @ 1.33GHz"
    MaxSpeed:     1330
    CurrentSpeed: 1333
      BIOS Version                  A05
      BIOS Release Date             02/27/2014
      Manufacturer                  DellInc.
      Product Name                  Venue 8 Pro 5830
    ¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
    **************************Sun Mar 16 13:01:09.737 2014 (UTC - 4:00)**************************
    Loading Dump File [C:\Users\John\SysnativeBSODApps\031614-11812-01.dmp]
    Windows 8 Kernel Version 9600 MP (4 procs) Free x86 compatible
    Built by: 9600.16452.x86fre.winblue_gdr.131030-1505
    System Uptime:0 days 4:07:47.234
    Probably caused by :Unknown_Image ( ANALYSIS_INCONCLUSIVE )
    BugCheck 101, {30, 0, 825db120, 3}
    BugCheck Info: CLOCK_WATCHDOG_TIMEOUT (101)
    Arguments: 
    Arg1: 00000030, Clock interrupt time out interval in nominal clock ticks.
    Arg2: 00000000, 0.
    Arg3: 825db120, The PRCB address of the hung processor.
    Arg4: 00000003, 0.
    BUGCHECK_STR:  CLOCK_WATCHDOG_TIMEOUT_4_PROC
    PROCESS_NAME:  System
    FAILURE_BUCKET_ID: CLOCK_WATCHDOG_TIMEOUT_4_PROC_ANALYSIS_INCONCLUSIVE
    CPUID:        "Intel(R) Atom(TM) CPU  Z3740D @ 1.33GHz"
    MaxSpeed:     1330
    CurrentSpeed: 1333
      BIOS Version                  A05
      BIOS Release Date             02/27/2014
      Manufacturer                  DellInc.
      Product Name                  Venue 8 Pro 5830
    ¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
    
    3rd Party Drivers:
    The following is for information purposes only.
    Any drivers in red should be updated or removed from your system. And should have been discussed in the body of my post.
    Code:
    **************************Sun Mar 16 16:52:07.158 2014 (UTC - 4:00)**************************
    bdfwfpf.sys                 Wed Oct 17 08:12:03 2012 (507EA093)
    avchv.sys                   Wed Oct 31 13:04:29 2012 (50915A1D)
    bdselfpr.sys                Thu Jul 25 12:07:59 2013 (51F14D5F)
    TXEI.sys                    Sun Aug  4 03:23:26 2013 (51FE016E)
    trufos.sys                  Wed Aug  7 06:46:01 2013 (52022569)
    intelppm.sys                Wed Aug 21 21:58:53 2013 (5215705D)
    HalExtIntcLpioDma.dll       Thu Aug 22 00:14:35 2013 (5215902B)
    gzflt.sys                   Fri Aug 23 06:48:39 2013 (52173E07)
    qcbtuart.sys                Thu Aug 29 02:54:50 2013 (521EF03A)
    rtii2sac.sys                Mon Sep  2 05:55:05 2013 (52246079)
    iaiouart.sys                Tue Sep  3 01:28:29 2013 (5225737D)
    iaiogpiovirtual.sys         Tue Sep  3 01:28:33 2013 (52257381)
    PMIC.sys                    Tue Sep 10 22:02:55 2013 (522FCF4F)
    dump_dumpsd.sys             Sat Sep 21 03:04:42 2013 (523D450A)
    ar6knwf81.sys               Tue Sep 24 02:09:39 2013 (52412CA3)
    iwdbus.sys                  Thu Sep 26 17:38:27 2013 (5244A953)
    iaioi2ce.sys                Thu Sep 26 21:57:05 2013 (5244E5F1)
    DptfDevGen.sys              Mon Sep 30 01:20:15 2013 (52490A0F)
    DptfManager.sys             Mon Sep 30 01:20:36 2013 (52490A24)
    DptfDevDisplay.sys          Mon Sep 30 01:20:39 2013 (52490A27)
    DptfDevPower.sys            Mon Sep 30 01:20:41 2013 (52490A29)
    DptfDevProc.sys             Mon Sep 30 01:20:50 2013 (52490A32)
    MBI.sys                     Mon Oct 14 05:08:52 2013 (525BB4A4)
    iaiospi.sys                 Mon Oct 14 22:01:04 2013 (525CA1E0)
    isstrtc.sys                 Wed Oct 16 23:16:16 2013 (525F5680)
    MT9M114.sys                 Mon Oct 21 12:26:11 2013 (526555A3)
    ov5693.sys                  Mon Oct 21 12:26:19 2013 (526555AB)
    iaiogpioe.sys               Thu Oct 24 22:52:48 2013 (5269DD00)
    igdkmd32.sys                Sat Nov  2 13:11:37 2013 (52753249)
    avc3.sys                    Mon Dec  2 04:37:21 2013 (529C54D1)
    avckf.sys                   Mon Dec  2 04:38:52 2013 (529C552C)
    
    http://www.carrona.org/drivers/driver.php?id=bdfwfpf.sys
    http://www.carrona.org/drivers/driver.php?id=avchv.sys
    http://www.carrona.org/drivers/driver.php?id=bdselfpr.sys
    TXEI.sys - this driver hasn't been added to the DRT as of this run. Please search Google/Bing for the driver if additional information is needed.
    http://www.carrona.org/drivers/driver.php?id=trufos.sys
    http://www.carrona.org/drivers/driver.php?id=intelppm.sys
    HalExtIntcLpioDma.dll - this driver hasn't been added to the DRT as of this run. Please search Google/Bing for the driver if additional information is needed.
    http://www.carrona.org/drivers/driver.php?id=gzflt.sys
    qcbtuart.sys - this driver hasn't been added to the DRT as of this run. Please search Google/Bing for the driver if additional information is needed.
    rtii2sac.sys - this driver hasn't been added to the DRT as of this run. Please search Google/Bing for the driver if additional information is needed.
    iaiouart.sys - this driver hasn't been added to the DRT as of this run. Please search Google/Bing for the driver if additional information is needed.
    iaiogpiovirtual.sys - this driver hasn't been added to the DRT as of this run. Please search Google/Bing for the driver if additional information is needed.
    PMIC.sys - this driver hasn't been added to the DRT as of this run. Please search Google/Bing for the driver if additional information is needed.
    dump_dumpsd.sys - this driver hasn't been added to the DRT as of this run. Please search Google/Bing for the driver if additional information is needed.
    ar6knwf81.sys - this driver hasn't been added to the DRT as of this run. Please search Google/Bing for the driver if additional information is needed.
    http://www.carrona.org/drivers/driver.php?id=iwdbus.sys
    iaioi2ce.sys - this driver hasn't been added to the DRT as of this run. Please search Google/Bing for the driver if additional information is needed.
    DptfDevGen.sys - this driver hasn't been added to the DRT as of this run. Please search Google/Bing for the driver if additional information is needed.
    DptfManager.sys - this driver hasn't been added to the DRT as of this run. Please search Google/Bing for the driver if additional information is needed.
    DptfDevDisplay.sys - this driver hasn't been added to the DRT as of this run. Please search Google/Bing for the driver if additional information is needed.
    DptfDevPower.sys - this driver hasn't been added to the DRT as of this run. Please search Google/Bing for the driver if additional information is needed.
    DptfDevProc.sys - this driver hasn't been added to the DRT as of this run. Please search Google/Bing for the driver if additional information is needed.
    MBI.sys - this driver hasn't been added to the DRT as of this run. Please search Google/Bing for the driver if additional information is needed.
    iaiospi.sys - this driver hasn't been added to the DRT as of this run. Please search Google/Bing for the driver if additional information is needed.
    http://www.carrona.org/drivers/driver.php?id=isstrtc.sys
    MT9M114.sys - this driver hasn't been added to the DRT as of this run. Please search Google/Bing for the driver if additional information is needed.
    ov5693.sys - this driver hasn't been added to the DRT as of this run. Please search Google/Bing for the driver if additional information is needed.
    iaiogpioe.sys - this driver hasn't been added to the DRT as of this run. Please search Google/Bing for the driver if additional information is needed.
    http://www.carrona.org/drivers/driver.php?id=igdkmd32.sys
    http://www.carrona.org/drivers/driver.php?id=avc3.sys
    http://www.carrona.org/drivers/driver.php?id=avckf.sys
      My System SpecsSystem Spec

  3. #3


    Here. It is a Windows 8.1 tablet btw, it came preinstalled with Windows 8.1. All drivers and bios are uptodate as provided by Dell. I already reset Windows a few times, installed all Windows and Dell updates, but it mostly always breaks after another Windows patch day, or (it seems) after random time, and a bsod/reboot happens (mostly out of standby). I ran memtest too a few times, didnt find any errors.
    Last edited by dfgfgd; 18 Mar 2014 at 08:10.
      My System SpecsSystem Spec

  4. #4


    Posts : 5,139
    Win8.1Pro - Finally!!!


    Only 253 MB of free memory. This will make the system slow and may even cause BSOD's I don't know how this will affect a tablet, but I'm pretty sure that using about 88% of the RAM will have adverse affects on any system.

    If possible, please add more memory in order to have more free RAM - I look for anything less than 1 gB free when I do my analysis'
    While waiting to add RAM (or if you can't add RAM) - please only run one program at a time, and trim your startup entries so that only essential programs are loading there.

    One of the memory dumps (in the WER section of MSINFO32) blames AbilisBdaTuner.sys - a driver for your TV Tuner program.
    Try uninstalling that to see if it helps (then, if needed, download and install the latest, Win8.1 compatible version from the Dell website). Info on this driver here: Driver Reference Table - AbilisBdaTuner.sys

    Finally, if the BSOD's continue, please run Driver Verifier according to these instructions: Driver Verifier Settings
      My System SpecsSystem Spec

  5. #5


    1.) it is a tablet, it has 2gb ram fixed.
    2.) there is nothing installed, windows bufferes that much ram after booting itself. also your value of 2xxmb seems wrong to me. maybe your seven log tool was using that much ram at the same it build the logs. when I boot the tablet it shows 43% usage, by windows itself.
    3.) bda driver cant be the reason for the bsod, what do you mean with "blames", that it is "outdated", like made before windows 8.1 release?

    my build in system doctor (by dell) says that skydrive.exe could be the reason behind the bsod (see screenshots), but I cant see how. dont you see this in your tools? or that maybe bitdefender could be the reason too? because when I google about skydrive.exe and bsod I find some bitdefender related stuff.
      My System SpecsSystem Spec

  6. #6


    Posts : 5,139
    Win8.1Pro - Finally!!!


    If you choose to rely on the Dell diagnostics, then I'd suggest that you contact Dell for support.

    I am only able to offer an opinion based on the information that you provide to me.
    Admittedly, we do not do much work with tablets - but Windows remains that same.
    On any Windows system - if you use more than about 15 to 20% of the RAM you will start to experience problems.

    Why do you say that the BDA driver can't be the reason for the BSOD?
    Here is the exact text from the WER section of MSINFO32 (I have highlighted the driver in RED) This is what I mean by it "blames" the TVTuner driver.:
    Code:
    14.02.2014 11:52    Windows Error Reporting    Fehlerbucket 0x1E_c0000005_R_AbilisBdaTuner+1995, Typ 0
    Ereignisname: BlueScreen
    Antwort: http://wer.microsoft.com/responses/resredir.aspx?sid=10&Bucket=0x1E_c0000005_R_AbilisBdaTuner+1995&State=1&ID=8a2e7cb0-739b-45fb-9499-8ed9f61109c8
    CAB-Datei-ID: 8a2e7cb0-739b-45fb-9499-8ed9f61109c8
    
    Problemsignatur:
    P1: 1e
    P2: c0000005
    P3: b120b995
    P4: 0
    P5: 2c
    P6: 6_3_9600
    P7: 0_0
    P8: 768_1
    P9: 
    P10: 
    
    Angefügte Dateien:
    C:\Windows\Minidump\021414-11750-01.dmp
    C:\Users\marc\AppData\Local\Temp\WER-27718-0.sysdata.xml
    C:\Windows\MEMORY.DMP
    C:\Users\marc\AppData\Local\Temp\WER7781.tmp.WERInternalMetadata.xml
    
    Diese Dateien befinden sich möglicherweise hier:
    C:\ProgramData\Microsoft\Windows\WER\ReportArchive\Kernel_1e_e0693a64f988a8d2912a1a61c249768bb141587c_00000000_cab_0c3ca529
    
    Analysesymbol: 
    Es wird erneut nach einer Lösung gesucht: 0
    Berichts-ID: 021414-11750-01
    Berichtstatus: 0
    Bucket mit Hash:
    Here are the latest 2 crashes from the WER section of MSINFO32:
    Code:
    17.03.2014 18:00    Windows Error Reporting    Fehlerbucket CLOCK_WATCHDOG_TIMEOUT_4_PROC, Typ 0
    Ereignisname: BlueScreen
    Antwort: http://wer.microsoft.com/responses/resredir.aspx?sid=10&Bucket=CLOCK_WATCHDOG_TIMEOUT_4_PROC&State=1&ID=5ab32c2f-426f-42b6-9df5-7cccd0bbaa03
    CAB-Datei-ID: 5ab32c2f-426f-42b6-9df5-7cccd0bbaa03
    
    Problemsignatur:
    P1: 101
    P2: 30
    P3: 0
    P4: 829db120
    P5: 3
    P6: 6_3_9600
    P7: 0_0
    P8: 768_1
    P9: 
    P10: 
    
    Angefügte Dateien:
    C:\Windows\Minidump\031614-11281-01.dmp
    C:\Users\marc\AppData\Local\Temp\WER-36625-0.sysdata.xml
    C:\Users\marc\AppData\Local\Temp\WER9470.tmp.WERInternalMetadata.xml
    
    Diese Dateien befinden sich möglicherweise hier:
    C:\ProgramData\Microsoft\Windows\WER\ReportArchive\Kernel_101_24105e21bfa55f5221a59fcb50e6bbc9adc47ef_00000000_cab_04de45ef
    
    Analysesymbol: 
    Es wird erneut nach einer Lösung gesucht: 0
    Berichts-ID: 031614-11281-01
    Berichtstatus: 0
    Bucket mit Hash:
    16.03.2014 18:11    Windows Error Reporting    Fehlerbucket CLOCK_WATCHDOG_TIMEOUT_4_PROC, Typ 0
    Ereignisname: BlueScreen
    Antwort: http://wer.microsoft.com/responses/resredir.aspx?sid=10&Bucket=CLOCK_WATCHDOG_TIMEOUT_4_PROC&State=1&ID=861eb869-3c6f-49c5-9672-4bf5ecd74a48
    CAB-Datei-ID: 861eb869-3c6f-49c5-9672-4bf5ecd74a48
    
    Problemsignatur:
    P1: 101
    P2: 30
    P3: 0
    P4: 825db120
    P5: 3
    P6: 6_3_9600
    P7: 0_0
    P8: 768_1
    P9: 
    P10: 
    
    Angefügte Dateien:
    C:\Windows\Minidump\031614-11812-01.dmp
    C:\Users\marc\AppData\Local\Temp\WER-4160953-0.sysdata.xml
    C:\Windows\MEMORY.DMP
    C:\Users\marc\AppData\Local\Temp\WER8848.tmp.WERInternalMetadata.xml
    
    Diese Dateien befinden sich möglicherweise hier:
    C:\ProgramData\Microsoft\Windows\WER\ReportArchive\Kernel_101_9d8197503ccfe647355e2cab4bc1874758a675c_00000000_cab_0b0bae4e
    
    Analysesymbol: 
    Es wird erneut nach einer Lösung gesucht: 0
    Berichts-ID: 031614-11812-01
    Berichtstatus: 0
    Bucket mit Hash:
    In general, .exe's do not cause BSOD's - because they operate in the user space - not the kernel space (where BSOD's come from).

    The first screen shot that you show is very similar to BlueScreenView or WhoCrashed. Those programs have some serious limitations (I had discussed them with the maker of BlueScreenView several years ago) and cannot be counted on for accurate reporting.
    This screen shot blames intelppm.sys - a driver (that works in the kernel space) for the processor (CPU). Unfortunately there are several exceptions that likely apply to this diagnosis:
    - Windows protects this driver, so it's not likely to be corrupted.
    - if the driver was corrupted, you would see many more problems other than just an occasional BSOD - as the drive controls the processor - which does the work for all programs.
    - the most common cause of STOP 0x101 BSOD's is hardware, but a large proportion can also be traced to driver issues.
    - as the Windows drivers are protected, the most likely driver issues are due to 3rd party (non-Windows) drivers
    - How does this happen? Here's a possible scenario:
    - Driver A writes to memory space owned by Driver B
    - Driver A exits, leaving no trace of it's presence
    - later, Driver B tries to access the memory space that Driver A wrote to
    - Driver B finds unexpected data at that location, so it panics and crashes
    - as nothing else was present, the debugger has nothing else to blame it on other than the driver that owns that memory space
    The second screenshot is an application crash. It is in the user space and cannot cause a BSOD directly.
    When doing BSOD analysis', I rarely look at more than the names of the application crashes.
    There is a possibility that something else is causing skydrive.exe to crash - so that bears looking into after the BSOD's are fixed (and, coincidentally, it may even help to fix the skydrive.exe crashes).

    Finally, here's how I do BSOD analysis:
    Just FYI - here's how I do BSOD analysis':
    - first I rule out 3rd party drivers (over 90% of BSOD's are due to this)
    - then I rule out hardware (less than 10% of BSOD's are due to this)
    - then I look at Windows problems (less than 1% of BSOD's are due to this - as long as Windows Updates are fully up to date).
    Finally, it is possible that BitDefender (actually it's the drivers that we're concerned with) is a problem.
    The "fix" is to remove it and see if the problem goes away.
    But you'll have to use another antivirus/firewall while testing - so that you don't get infected.
      My System SpecsSystem Spec

  7. #7


    I dint say I rely on Dell diagnostics too, I asked YOU if you can see something the same it tells.


    "if you use more than about 15 to 20% of the RAM you will start to experience problems." and thats superficial of course, especially saying too much ram used leads to bsods.


    Windows always use about 40-50% already after boot, if it's by superfetch, or other reasons, like "take as much as you can", for buffering. For example Windows takes 44% of 4GB ram too on my laptop after boot.


    Because the one you are referring to is some other problem from 14.03. (where mostly something else happened that day I cannot remember, maybe I was handling with DVB that day), but the two bsods I was referring here were from 16.03.2014.


    Please dont think I am trying to talk into you, I believe in your skills and I appreciate the help.


    So these CLOCK_WATCHDOG_TIMEOUT_4_PROC are the right ones, that tells the Dell tool, and says skydrive was the reason behind it, and if you google about it, skydrive can produce bsods (because it's mostly some kind of driver for using cloud/drive sync stuff).


    I've disabled skydrive and uninstalled bitdefender. And hope it wll stay stable now. But I still would like to know what really was the issue. I have to use Windows Bitdefender then, it is doing a complete scan right now and seem to take 20h or so for that...


    Both screenshots are from the same time event (bsod at 16.03.2014 21:21:54), I cannot post it because it has no log output, and I would have to scroll down and take like 20 screenshots to capcure the whole event.
      My System SpecsSystem Spec

  8. #8


    Posts : 5,139
    Win8.1Pro - Finally!!!


    I would suggest that you start another topic and see if you can find someone else to help you.
    I shall not respond further to this topic.
    Last edited by usasma; 19 Mar 2014 at 09:36.
      My System SpecsSystem Spec

  9. #9


    Honestly, yes youre a debug expert, but what help did you provide yet? I cant see any (I really want to see one, but I dont). You pointed to the problem (Here are the latest 2 crashes from the WER section of MSINFO32)

    But what is the conclusion of it? You haven't posted one. The "conclusion" you posted before was about a crash at 14.02.2014 11:52, a total different.

    What caused 16.03.2014 18:11 Windows Error Reporting Fehlerbucket CLOCK_WATCHDOG_TIMEOUT_4_PROC, Typ 0Ereignisname: BlueScreen... Or the one afterwards around 21:21.

    You said STOP 0x101 BSOD's is hardware, so youre saying the device has a hardware failure, not something driver realted?

    Ive opened device manager, enabled show disabled devices, and removed the BDA device by clicking deinstall. Is it removed by this from load process? Also I cant see how it could be the reason for the BSODs from 16., because it's a usb device, and the driver isnt loaded anymore since some days.
      My System SpecsSystem Spec

BSOD problems, mostly caused by halmacpi.dll
Related Threads
Solved BSOD being caused by on-board NIC? in BSOD Crashes and Debugging
I need a little help and hope someone here can lend a hand. I'm having very regular BSOD on my system, which appear to be due to the ethernet card on the motherboard. I think this because at the same time the BSOD occurs, , there is a event log entry from e1dexpress saying a network link has...
BSOD halmacpi.dll and sorahci.sys in BSOD Crashes and Debugging
Hey guys since a week I despair of installing my new SSD from Samsung (840 EVO 250GB) and don't know what I can do anymore. I own an Alienware M17 R1 Laptop with a Seagate Momentus 7200.3 160GB HDD for 5 years now. Due to the fact that there was still a free Slot for another harddrive, I bought...
I ran 'Wise Registry Cleaner' on my Windows 8 upgraded to 8.1 Dell Inspiron 17R 7720 Laptop. After the software finished scanning and cleaned up 47 errors I re-booted I found I had problems. When I inserted a USB key I got no notification popup asking me what I wanted to do and the contents of the...
Solved BSOD halmacpi.dll and ntoskrnl.exe WINDOWS 8 in BSOD Crashes and Debugging
Hello, in 2014 i had 7 BSOD's all happened when i was browsing the web. I did looked in google about halmacpi.dll and ntoskrnl.exe and did as some people suggested. I've run my antivirus and checked HDD, both programs passed the test. Strange is that blue screen in header have big smiley face...
After spending an inordinate amount of time getting my old applications to work with Win 8 (and giving up for some) I finally had a system that seemed to be working. Then File Explorer started to freeze. I saw that I had not installed the recent updates. So I did this. Now a whole bunch of programs...
BSOD Caused by WudfPf.sys in BSOD Crashes and Debugging
After I installed Windows 8 and update all of my drivers, Sometime I got a short freeze with no warning But only a short freeze(2-5 secs). It is not BSOD,But it makes me annoyed. Thanks in advanced.
BSOD caused by rdboost.sys, but RAM seems OK in BSOD Crashes and Debugging
Hi all, I have some crashes upon booting Win8. This actually always happens right after the boot process is done, right before the lock screen. Upon automatic reboot the system always works as expected. As you will be able to see in the Minidumps the error is almost always caused by...
Eight Forums Android App Eight Forums IOS App Follow us on Facebook