Jump to content

Welcome to Geeks to Go - Register now for FREE

Geeks To Go is a helpful hub, where thousands of volunteer geeks quickly serve friendly answers and support. Check out the forums and get free advice from the experts. Register now to gain access to all of our features, it's FREE and only takes one minute. Once registered and logged in, you will be able to create topics, post replies to existing threads, give reputation to your fellow members, get your own private messenger, post status updates, manage your profile and so much more.

Create Account How it Works
Photo

Physical Memory Dump


  • Please log in to reply

#1
Xadam

Xadam

    New Member

  • Member
  • Pip
  • 1 posts
Sorry new to all this but I have this report for why it's crashing and I just need to know how to fix it. Can anyone help?
Crash dump directory: C:\Windows\Minidump

Crash dumps are enabled on your computer.

On Fri 11/15/2013 9:46:45 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\111513-20779-01.dmp
This was probably caused by the following module: hal.dll (hal+0x12A3B)
Bugcheck code: 0x124 (0x0, 0xFFFFFA8007B97028, 0xB614C000, 0x135)
Error: WHEA_UNCORRECTABLE_ERROR
file path: C:\Windows\system32\hal.dll
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Hardware Abstraction Layer DLL
Bug check description: This bug check indicates that a fatal hardware error has occurred. This bug check uses the error data that is provided by the Windows Hardware Error Architecture (WHEA).
This is likely to be caused by a hardware problem problem. This problem might be caused by a thermal issue.
The crash took place in a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system that cannot be identified at this time.



On Fri 11/15/2013 9:46:45 PM GMT your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: hal.dll (hal!HalBugCheckSystem+0x1E3)
Bugcheck code: 0x124 (0x0, 0xFFFFFA8007B97028, 0xB614C000, 0x135)
Error: WHEA_UNCORRECTABLE_ERROR
file path: C:\Windows\system32\hal.dll
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Hardware Abstraction Layer DLL
Bug check description: This bug check indicates that a fatal hardware error has occurred. This bug check uses the error data that is provided by the Windows Hardware Error Architecture (WHEA).
This is likely to be caused by a hardware problem problem. This problem might be caused by a thermal issue.
The crash took place in a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system that cannot be identified at this time.



On Fri 11/15/2013 8:38:18 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\111513-23992-01.dmp
This was probably caused by the following module: hal.dll (hal+0x12A3B)
Bugcheck code: 0x124 (0x0, 0xFFFFFA8008065028, 0xB614C000, 0x175)
Error: WHEA_UNCORRECTABLE_ERROR
file path: C:\Windows\system32\hal.dll
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Hardware Abstraction Layer DLL
Bug check description: This bug check indicates that a fatal hardware error has occurred. This bug check uses the error data that is provided by the Windows Hardware Error Architecture (WHEA).
This is likely to be caused by a hardware problem problem. This problem might be caused by a thermal issue.
The crash took place in a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system that cannot be identified at this time.



On Wed 11/13/2013 10:37:33 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\111313-22136-01.dmp
This was probably caused by the following module: hal.dll (hal+0x12A3B)
Bugcheck code: 0x124 (0x0, 0xFFFFFA8007B8C028, 0xB67E2000, 0x135)
Error: WHEA_UNCORRECTABLE_ERROR
file path: C:\Windows\system32\hal.dll
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Hardware Abstraction Layer DLL
Bug check description: This bug check indicates that a fatal hardware error has occurred. This bug check uses the error data that is provided by the Windows Hardware Error Architecture (WHEA).
This is likely to be caused by a hardware problem problem. This problem might be caused by a thermal issue.
The crash took place in a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system that cannot be identified at this time.



On Mon 11/11/2013 7:35:17 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\111113-16894-01.dmp
This was probably caused by the following module: hal.dll (hal+0x12A3B)
Bugcheck code: 0x124 (0x0, 0xFFFFFA8006994028, 0xB669C000, 0xA8000135)
Error: WHEA_UNCORRECTABLE_ERROR
file path: C:\Windows\system32\hal.dll
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Hardware Abstraction Layer DLL
Bug check description: This bug check indicates that a fatal hardware error has occurred. This bug check uses the error data that is provided by the Windows Hardware Error Architecture (WHEA).
This is likely to be caused by a hardware problem problem. This problem might be caused by a thermal issue.
The crash took place in a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system that cannot be identified at this time.



On Mon 11/11/2013 12:13:45 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\111013-19266-01.dmp
This was probably caused by the following module: hal.dll (hal+0x12A3B)
Bugcheck code: 0x124 (0x0, 0xFFFFFA8007B37028, 0xB61FA000, 0x135)
Error: WHEA_UNCORRECTABLE_ERROR
file path: C:\Windows\system32\hal.dll
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Hardware Abstraction Layer DLL
Bug check description: This bug check indicates that a fatal hardware error has occurred. This bug check uses the error data that is provided by the Windows Hardware Error Architecture (WHEA).
This is likely to be caused by a hardware problem problem. This problem might be caused by a thermal issue.
The crash took place in a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system that cannot be identified at this time.



On Thu 11/7/2013 8:03:24 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\110713-26083-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x75BC0)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF80002CB14F5, 0xFFFFF8800CAE6A30, 0x0)
Error: SYSTEM_SERVICE_EXCEPTION
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that an exception happened while executing a routine that transitions from non-privileged code to privileged code.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.
  • 0

Advertisements


#2
Xadam2

Xadam2

    Member

  • Member
  • PipPip
  • 10 posts
Bump.
  • 0

#3
dbreeze

dbreeze

    Trusted Helper

  • Malware Removal
  • 2,216 posts
From the reports it looks like you have faulty or failed hardware. What changes have you made to the system just before these errors occurred? Can you boot into Safe Mode?
  • 1

#4
Xadam2

Xadam2

    Member

  • Member
  • PipPip
  • 10 posts
The only things I did was I went to windows 8 didn't like it and went back to windows 7 Home Prem. Yes I can boot safe mode.
  • 0

#5
dbreeze

dbreeze

    Trusted Helper

  • Malware Removal
  • 2,216 posts
Did you update any hardware drivers when you upgraded to Win8 (Win8 or Win8.1?)? How did you do the upgrade to Win8 and return to Win7?

If you updated any hardware drivers when you 'installed' Win8, then you should reinstall the Win7 drivers for your hardware (if you did an over the top of installation of Win8 and a return to Win7 (previous OS) via the setup / installation application of Win8).
  • 1

#6
Xadam2

Xadam2

    Member

  • Member
  • PipPip
  • 10 posts
I did a clean install each time would this not cause all driver to reset to default and then be updated to win 7 after?
  • 0

#7
dbreeze

dbreeze

    Trusted Helper

  • Malware Removal
  • 2,216 posts
A clean install should set the drivers back to MS defaults (drivers that are supplied with the OS) IF you formatted the hard drive during the installation. Usually specific drivers are supplied for various hardware by the hardware OEM. The memory dump you included last (oldest dated dump) refers to a video driver; have you updated your video driver(s) since returning to Win7? Did your system come with a Recovery Setup disk(s)?
  • 1

#8
Xadam2

Xadam2

    Member

  • Member
  • PipPip
  • 10 posts
I'm pretty sure I installed the new drivers for my new video graphics card but I'll double check and get back to you
  • 0

#9
Xadam2

Xadam2

    Member

  • Member
  • PipPip
  • 10 posts
So I went and checked my Nvidia drivers and it says they are up-to-date. Sadly software isn't my thing. But I went into the system info of the Nvidia control panel and it stated that it was windows 7 home prem. updated to 331.65 Hope this helps let me know what you got.
  • 0

#10
Xadam2

Xadam2

    Member

  • Member
  • PipPip
  • 10 posts
I don't know why I didn't do this before but I scanned my computer for virus and surprise I found 1 win32/obfuscator.xz but this my not be the source of the problem so. I'll see if I can run my computer for a few days and what happens.
  • 0

#11
phillpower2

phillpower2

    Mechanised Mod

  • Moderator
  • 24,053 posts
:welcome: Xadam2

Some malware is so deep rooted that not even a full format and fresh installation of the OS will clear it, you may need the assistance of the experts over on the Malware Forums so can I ask that you refer to the GTG malware redirection information below;

I suspect that you have some malware on your computer causing issues that we are not able to solve through means we can use here in the Tech Forums. I suggest you read the 'Start Here' topic found here. With these self-help tools you have a high chance of fixing the problems on your own. If you are still having problems after following Step 3 of the guide, continue with Step 4 and 5 and post in the Malware Forum. If you are unable to run any programs, Please create a topic stating what you have tried so far and that you are unable to run any programs. Also, Please do NOT post the logs in this thread.

If you are still having issues after the malware expert gives you a clean bill of health, Please return to THIS thread and we will pursue other options to help you solve your current problem(s).
  • 1

#12
sari

sari

    GeekU Admin

  • Community Leader
  • 21,805 posts
  • MVP
Xadam/Xadam2,

It appears that you have created two accounts, which is a violation of our Terms of Use. Since you only have one post under the first account, does that mean you forgot how to log it with that one after you created it?

sari
  • 0

#13
Xadam2

Xadam2

    Member

  • Member
  • PipPip
  • 10 posts
No when I went to log into my first account it said it didn't exist so I just made a new one. Both are under the same email too so. Is it really that big of a deal?

And Tech Staff after doing all the steps and waiting (3 days) i've gotten no reply over there on the virus forums.
  • 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