Jump to content

Welcome to Geeks to Go - Register now for FREE

Need help with your computer or device? Want to learn new tech skills? You're in the right place!
Geeks to Go is a friendly community of tech experts who can solve any problem you have. Just create a free account and post your question. Our volunteers will reply quickly and guide you through the steps. Don't let tech troubles stop you. Join Geeks to Go now and get the support you need!

How it Works Create Account
Photo

Windows 7 Ultimate x64 Bluescreen (0x124)


  • Please log in to reply

#1
SabRinaa

SabRinaa

    Member

  • Member
  • PipPip
  • 20 posts
hey everybody,

First, sorry for my bad english ^^
hope you'll understand what i mean.

Of course I've used google.
I found some posts from people, who do have the same problems, too.
But i found nothing that could help me. However.

I've installed Windows 7 ultimate x64 some month ago.
And i'm getting a bluescreen (0x124) very often.

I don't get it, when I'm playing any Computer games.
However - I've tried to analyse the dump- file.
The Bluescreens are caused by a Driver. But I don't know wich one.

Maybe you guys could take a look. Please help me. This Bluescreens are getting me realy nuts.

I've attached a .txt file (outcome from the debugging tool).


Thanks.

Best regards,
Sabrina

Attached Files


Edited by SabRinaa, 20 August 2009 - 11:08 AM.

  • 0

Advertisements


#2
Neil Jones

Neil Jones

    Member 5k

  • Member
  • PipPipPipPipPipPipPipPip
  • 8,476 posts
WHEA_UNCORRECTABLE_ERROR (124) - fatal hardware error.

Your log suggests a hardware error (most likely faulty memory).
  • 0

#3
SabRinaa

SabRinaa

    Member

  • Topic Starter
  • Member
  • PipPip
  • 20 posts
thx for your answer.

so the 4GB RAM are faulty?
how can i check them?


DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
doesn't that mean, that the bluescreens are caused by a driver?

Edited by SabRinaa, 21 August 2009 - 04:42 PM.

  • 0

#4
Neil Jones

Neil Jones

    Member 5k

  • Member
  • PipPipPipPipPipPipPipPip
  • 8,476 posts

thx for your answer.

so the 4GB RAM are faulty?
how can i check them?


DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
doesn't that mean, that the bluescreens are caused by a driver?


Not necessarily. Many error messages are either generic or lean towards certain issues that are misleading.
For example a Vista Stop 0x44 error usually refers to an issue with resuming from standby or hibernation. In one case it had nothing to do with this and the issue was a faulty modem.
In this case the driver may be corrupt because it's being loaded into a damaged part of memory.

With regards memory testing, type in "memory" (no quotes) into the bar at the bottom of the start menu in Windows 7 (this also applies to Vista).

# click on Windows Memory Diagnostic
# When the Windows Memory Diagnostic screen loads, click Restart now and check for problems
# You computer will restart
# The memory diagnostic will run and may take some time
# Windows will restart and report any errors to you
  • 0

#5
SabRinaa

SabRinaa

    Member

  • Topic Starter
  • Member
  • PipPip
  • 20 posts
alright.

i tried to run memtest86.
but everytime when it started to test the memory, the computer restarted.

so i used the windows- memtest.
that worked... but it found no results.

so the memory's are okay, i think.
  • 0

#6
SabRinaa

SabRinaa

    Member

  • Topic Starter
  • Member
  • PipPip
  • 20 posts
i scanned my computer with BlueScreenView now.
maybe someone could help me now ^^

see attached file.

Attached Files


Edited by SabRinaa, 24 August 2009 - 04:14 PM.

  • 0

#7
Broni

Broni

    Kraków my love :)

  • Member
  • PipPipPipPipPipPipPipPip
  • 12,300 posts
1. Where did Windows 7 installation file come from?

2. To really test the RAM, forget memtest. Remove all RAN sticks, but one. Run the computer for a while, and see, if it works OK. If so, add another stick of RAM, and so on.

3. All BSODs come from hal.dll, but it's hard to say more at this time without knowing some info from 1 and 2.

4. Was Win 7 installation a clean install? What did you have on that hard drive before? Worked OK?
  • 0

#8
SabRinaa

SabRinaa

    Member

  • Topic Starter
  • Member
  • PipPip
  • 20 posts
1. From the official Microsoft Page

2. i'll try that. but what if both RAM sticks are broken? xD

3. cant i just replace the probably broken hal.dll with a "clean" one?

4. yes, it was. definitly. i had xp professional 32bit installed before. worked very well and without any problems.

Edited by SabRinaa, 24 August 2009 - 05:09 PM.

  • 0

#9
Broni

Broni

    Kraków my love :)

  • Member
  • PipPipPipPipPipPipPipPip
  • 12,300 posts
In that case, we're left with 2 and 3.
You have to try #2 first, so we can eliminate bad RAM.
It's not a good idea to try two fixes at the same time.
  • 0

#10
SabRinaa

SabRinaa

    Member

  • Topic Starter
  • Member
  • PipPip
  • 20 posts
i was able to test both ram sticks separated with memtest86.
no failures found.

now i'm using the 2 other RAM slots from the board.
but i dont know whether this will help.

Edited by SabRinaa, 25 August 2009 - 12:02 PM.

  • 0

Advertisements


#11
SabRinaa

SabRinaa

    Member

  • Topic Starter
  • Member
  • PipPip
  • 20 posts
mh. had a bluescreen again -.-
seems not to help.

what now?


btw. - i typed sfk /scannow in cmd.
it found some broken files, but it cant repair the files.

Edited by SabRinaa, 25 August 2009 - 02:34 PM.

  • 0

#12
Broni

Broni

    Kraków my love :)

  • Member
  • PipPipPipPipPipPipPipPip
  • 12,300 posts
Well, it looks like your Windows installation got messed up.
hal.dll error is pretty nasty one.
I think, your best option is to reinstall.
  • 0

#13
SabRinaa

SabRinaa

    Member

  • Topic Starter
  • Member
  • PipPip
  • 20 posts
alright.
well, i'll post some pics from my bios settings.
maybe you could take a look ^^

but this one i wanna post now:
i found HDD S.M.A.R.T. Capability [Disabled] and HPET Mode [32-Bit-Mode] (changed it to 64-Bit-Mode). Is that right?
  • 0

#14
Broni

Broni

    Kraków my love :)

  • Member
  • PipPipPipPipPipPipPipPip
  • 12,300 posts

HPET Mode [32-Bit-Mode] (changed it to 64-Bit-Mode). Is that right?

Yes.

i found HDD S.M.A.R.T. Capability [Disabled]

Most likely, you won't miss it. Explained here: http://www.techarp.c...lang=0&bogno=95

S.M.A.R.T. is supported by all current hard disks and it allows the early prediction and warning of impending hard disk disasters. You should enable it if you want to use S.M.A.R.T.-aware utilities to monitor the hard disk's condition. Enabling it also allows the monitoring of the hard disk's condition over a network.

While S.M.A.R.T. looks like a really great safety feature, it isn't really that useful or even necessary for most users. For S.M.A.R.T. to work, it is not just a matter of enabling it in the BIOS. You must also keep a S.M.A.R.T.-aware hardware monitoring utility running in the background all the time.

That's quite alright if the hard disk you are using has a spotty reputation and you need advanced warning of any impending failure. However, hard disks these days are mostly reliable enough to make S.M.A.R.T. redundant. Unless you are running mission-critical applications, it is very unlikely that S.M.A.R.T. will be of any use at all.


  • 0

#15
SabRinaa

SabRinaa

    Member

  • Topic Starter
  • Member
  • PipPip
  • 20 posts
okay. i made a clean windows 7 install.
but i got a bluescreen again. "hal.dll" again.

If you ask me - either the CPU is broken, or the Motherboard.
Mh... But its working well on WinXP Pro. x86....

i made some pics from my bios settings:
http://www.xup.in/dl...1/100_2321.JPG/
http://www.xup.in/dl...7/100_2322.JPG/
http://www.xup.in/dl...5/100_2323.JPG/
http://www.xup.in/dl...1/100_2324.JPG/
http://www.xup.in/dl...9/100_2325.JPG/
http://www.xup.in/dl...5/100_2326.JPG/
http://www.xup.in/dl...5/100_2327.JPG/
http://www.xup.in/dl...7/100_2328.JPG/

Edited by SabRinaa, 26 August 2009 - 10:24 AM.

  • 0






Similar Topics

0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users

As Featured On:

Microsoft Yahoo BBC MSN PC Magazine Washington Post HP