Windows 7 Forums
Welcome to Windows 7 Forums. Our forum is dedicated to helping you find support and solutions for any problems regarding your Windows 7 PC be it Dell, HP, Acer, Asus or a custom build. We also provide an extensive Windows 7 tutorial section that covers a wide range of tips and tricks.



Windows 7: Random BSOD's every 1-2 hours, error hal.dll

12 Nov 2011   #1

Win 7 Home Premium 64
 
 
Random BSOD's every 1-2 hours, error hal.dll

Hi guys, I've been getting this for over 3-4 months now.. and I have done a system restore twice and it's not helping.. the BSOD still lives. The BSOD occurs in a random fashion, even during browsing the internet with just a few tabs, sometimes during idle (happened a few times when I leave home and left my laptop idle)

I notice that every time the BSOD is about to appear, my laptop fan goes all noisy. Not sure if that actually has anything to do with it.

I've even tried running on Ubuntu and got crashes too.. although with no description.. it just froze.

Also when I tried to run perfmon /report, I get an error when trying to generate a report saying:

"An error occured while attempting to generate the report.
The wait for the report generation tool to finish has timed out. "


specs are:

ASUS G53 Sw 3D:
Intel Core i7 2630QM 2.0 Ghz (upto 2.9ghz Turbo Boost), 6MB L3 Cache
Win 7 Home Premium 64bit
8GB DDR3 Ram
NVIDIA GTX 460M 1.5GB
650GB SATA 5krpm
Bluray DVD Combo
Atheros Wireless Card
Realtek LAN Card

I have attached all the stuff I could think of relating to the BSODS:

My System SpecsSystem Spec
12 Nov 2011   #2

Microsoft Windows 7 Ultimate: x64 (SP1)
 
 

Hello Duffed and Welcome to SevenForums!

Would likely be a Memory corruption as it's even crashing on your Ubuntu also. So the first thing we're going to do, is to test your sticks of memory.

MemTest86+

Please read this Tutorial.

Pay attention to part 3:
Quote:
The goal is to test all the RAM sticks and all the motherboard slots.

Check your motherboard manual to ensure the RAM sticks are in the recommended motherboard slots. Some motherboards have very specific slots required for the number of RAM sticks installed.

If you get errors, stop the test and continue with the next step.

1. Remove all but one stick of RAM from your computer (this will be RAM stick #1), and run Memtest86 again, for 7 passes.
Be sure to note the RAM stick, use a piece of tape with a number, and note the motherboard slot.
If this stick passes the test then go to step #3.

2. If RAM stick #1 has errors, repeat the test with RAM stick #2 in the same motherboard slot.
If RAM stick #2 passes, this indicates that RAM stick #1 may be bad. If you want to be absolutely sure, re-test RAM stick #1 in another known good slot.
If RAM stick #2 has errors, this indicates another possible bad RAM stick, a possible motherboard slot failure or inadequate settings.
3. Test the next stick of RAM (stick #2) in the next motherboard slot.
If this RAM stick has errors repeat step #2 using a known good stick if possible, or another stick.
If this RAM stick has no errors and both sticks failed in slot#1, test RAM stick #1 in this slot.
4. If you find a stick that passes the test, test it in all the other motherboard slots.

If Part 2 testing shows errors, and all tests in Part 3 show errors, you will need to test the RAM sticks in another computer and/or test other RAM in your computer to identify the problem.

In this way, you can identify whether it is a bad stick of RAM, a bad motherboard, or incompatibility between the sticks.
Carry on.
Frederik
My System SpecsSystem Spec
12 Nov 2011   #3

Win 7 Home Premium 64
 
 

I've also posted about this on microsoft answers; and their response was the following:

"This issue occurs because resource rebalancing is triggered after you hot plug a PCI (Peripheral Component Interconnect) device. During the rebalancing process, the system does not configure the Max Payload Size value correctly on the root port of the PCI Express bus. The incorrect value causes a mismatch between the root port of the PCI Express bus and the device on the PCI Express bus. Therefore, the operating system triggers a Machine Check Architecture (MCA) exception, and the operating system returns a “0x00000124” exception."


I've also tried their suggestions:

Method 1: Disconnect all the external devices (printers, scanner, USB (universal serial bus) drives, etc...) Except mouse and the keyboard and then boot up.

Method 2: Run Memory Diagnostics test to check for any memory problems. Refer the below mentioned link for the same.

.. but alas, all the same.. Memory's all good, and the did the first bit as well.. nothing changed.

Please please help!
My System SpecsSystem Spec
.


13 Nov 2011   #4

Win 7 Home Premium 64
 
 

Quote   Quote: Originally Posted by FredeGail View Post
Hello Duffed and Welcome to SevenForums!

Would likely be a Memory corruption as it's even crashing on your Ubuntu also. So the first thing we're going to do, is to test your sticks of memory.

MemTest86+

Please read this Tutorial.

Pay attention to part 3:
Quote:
The goal is to test all the RAM sticks and all the motherboard slots.

Check your motherboard manual to ensure the RAM sticks are in the recommended motherboard slots. Some motherboards have very specific slots required for the number of RAM sticks installed.

If you get errors, stop the test and continue with the next step.

1. Remove all but one stick of RAM from your computer (this will be RAM stick #1), and run Memtest86 again, for 7 passes.
Be sure to note the RAM stick, use a piece of tape with a number, and note the motherboard slot.
If this stick passes the test then go to step #3.

2. If RAM stick #1 has errors, repeat the test with RAM stick #2 in the same motherboard slot.
If RAM stick #2 passes, this indicates that RAM stick #1 may be bad. If you want to be absolutely sure, re-test RAM stick #1 in another known good slot.
If RAM stick #2 has errors, this indicates another possible bad RAM stick, a possible motherboard slot failure or inadequate settings.
3. Test the next stick of RAM (stick #2) in the next motherboard slot.
If this RAM stick has errors repeat step #2 using a known good stick if possible, or another stick.
If this RAM stick has no errors and both sticks failed in slot#1, test RAM stick #1 in this slot.
4. If you find a stick that passes the test, test it in all the other motherboard slots.

If Part 2 testing shows errors, and all tests in Part 3 show errors, you will need to test the RAM sticks in another computer and/or test other RAM in your computer to identify the problem.

In this way, you can identify whether it is a bad stick of RAM, a bad motherboard, or incompatibility between the sticks.
Carry on.
Frederik
Okay, I just did a 10 hour Memtest with 5 Passes (on 8Gb ram 2x4gb, wanted to leave it longer but had to make an urgent skype call. So far nothing wrong with my sticks I take it?

Please HELP!
My System SpecsSystem Spec
13 Nov 2011   #5

Microsoft Windows 7 Ultimate: x64 (SP1)
 
 

Do you have any new dumps to be uploaded?

Fred.
My System SpecsSystem Spec
13 Nov 2011   #6

Win 7 Home Premium 64
 
 

Yeah, here:Attachment 183503
My System SpecsSystem Spec
13 Nov 2011   #7

Microsoft Windows 7 Ultimate: x64 (SP1)
 
 

Something went wrong.

Check your %\Windows\Mindump and make sure you zip the latest dump file and attach it here.

Fred.
My System SpecsSystem Spec
13 Nov 2011   #8

Win 7 Home Premium 64
 
 

My System SpecsSystem Spec
13 Nov 2011   #9

Microsoft Windows 7 Ultimate: x64 (SP1)
 
 

Thank you.

It indicates some arguments with your processor.

Code:
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

WHEA_UNCORRECTABLE_ERROR (124)
A fatal hardware error has occurred. Parameter 1 identifies the type of error
source that reported the error. Parameter 2 holds the address of the
WHEA_ERROR_RECORD structure that describes the error conditon.
Arguments:
Arg1: 0000000000000000, Machine Check Exception
Arg2: fffffa8009cff028, Address of the WHEA_ERROR_RECORD structure.
Arg3: 00000000b2000000, High order 32-bits of the MCi_STATUS value.
Arg4: 0000000000010005, Low order 32-bits of the MCi_STATUS value.
Please test your processor with Prime95

Prime95 will test the stability and heat problems by stressing it.

Fred.
My System SpecsSystem Spec
13 Nov 2011   #10

Win 7 Home Premium 64
 
 

Okay, can you tell me exactly what I'm looking for? After a few seconds of starting it I get 4 of my cores to hover around 70-90c
My System SpecsSystem Spec
Reply

 Random BSOD's every 1-2 hours, error hal.dll





Thread Tools



Similar help and support threads for2: Random BSOD's every 1-2 hours, error hal.dll
Thread Forum
help! random bsod for 6 hours BSOD Help and Support
Solved BSoD after a few hours of leaving computer on (seemingly random) BSOD Help and Support
Solved Random BSOD after 1-2 hours 0x0000007A BSOD Help and Support
BSOD - Random Crashes Started Today, Three in Few Hours BSOD Help and Support
BSOD at random times... even when idle during e.g. 2 hours BSOD Help and Support
BSOD 5 times in 3 hours - PlugAndPlay error?? BSOD Help and Support
Random BSOD after a few Hours of a fresh install BSOD Help and Support

Our Sites

Site Links

About Us

Find 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 11:04 PM.
Twitter Facebook Google+



Windows 7 Forums

Seven Forums Android App Seven Forums IOS App
  

1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33