Jump to content


 


Register a free account to unlock additional features at BleepingComputer.com
Welcome to BleepingComputer, a free community where people like yourself come together to discuss and learn how to use their computers. Using the site is easy and fun. As a guest, you can browse and view the various discussions in the forums, but can not create a new topic or reply to an existing one unless you are logged in. Other benefits of registering an account are subscribing to topics and forums, creating a blog, and having no ads shown anywhere on the site.


Click here to Register a free account now! or read our Welcome Guide to learn how to use this site.

Photo

Possible graphics card related BSOD


  • Please log in to reply
7 replies to this topic

#1 forever_insane

forever_insane

  • Members
  • 17 posts
  • OFFLINE
  •  
  • Local time:10:24 PM

Posted 11 March 2010 - 04:59 PM

Hey,

Iv been getting help with BSOD and viruses (Look here for me info!)

Heres the BSOD erros I got (Using 'bluescreenview' to get it):

==================================================
Dump File : 031010-57969-01.dmp
Crash Time : 10/03/2010 11:05:51 PM
Bug Check String :
Bug Check Code : 0x00000124
Parameter 1 : 0x00000004
Parameter 2 : 0x858c7024
Parameter 3 : 0x00000000
Parameter 4 : 0x00000000
Caused By Driver : halmacpi.dll
Caused By Address : halmacpi.dll+ef3f
File Description : Hardware Abstraction Layer DLL
Product Name : Microsoft® Windows® Operating System
Company : Microsoft Corporation
File Version : 6.1.7600.16385 (win7_rtm.090713-1255)
Processor : 32-bit
Computer Name :
Full Path : C:\Windows\minidump\031010-57969-01.dmp
Processors Count : 1
Major Version : 15
Minor Version : 7600
==================================================

==================================================
Dump File : 031010-63804-01.dmp
Crash Time : 10/03/2010 10:54:32 PM
Bug Check String :
Bug Check Code : 0x00000124
Parameter 1 : 0x00000004
Parameter 2 : 0x858c36a4
Parameter 3 : 0x00000000
Parameter 4 : 0x00000000
Caused By Driver : halmacpi.dll
Caused By Address : halmacpi.dll+ef3f
File Description : Hardware Abstraction Layer DLL
Product Name : Microsoft® Windows® Operating System
Company : Microsoft Corporation
File Version : 6.1.7600.16385 (win7_rtm.090713-1255)
Processor : 32-bit
Computer Name :
Full Path : C:\Windows\minidump\031010-63804-01.dmp
Processors Count : 1
Major Version : 15
Minor Version : 7600
==================================================


Iv taken out my graphics card and the problem seems to have stopped, but it started when I reinstalled Windows 7. Any idea how I can fix this?

Thank you.

BC AdBot (Login to Remove)

 


#2 forever_insane

forever_insane
  • Topic Starter

  • Members
  • 17 posts
  • OFFLINE
  •  
  • Local time:10:24 PM

Posted 14 March 2010 - 11:02 AM

No idea? :thumbsup: The driver and software was installed fine :/

#3 computerxpds

computerxpds

    Bleepin' Comp


  • Moderator
  • 4,487 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:USA
  • Local time:06:24 PM

Posted 14 March 2010 - 03:21 PM

so the graphics card is now in the computer right? if so try taking it out and putting back in and make sure there is no dust in there either, could you specify what graphics card it is?
sigcomp.png 
If I have replied to a topic and you reply and I haven't gotten back to you within 48 hours (2 days) then send me a P.M.
Some important links: BC Forum Rules | Misplaced Malware Logs | BC Tutorials | BC Downloads |
Follow BleepingComputer on: Facebook! | Twitter! | Google+| Come join us on the BleepingComputer Live Chat on Discord too! |

#4 forever_insane

forever_insane
  • Topic Starter

  • Members
  • 17 posts
  • OFFLINE
  •  
  • Local time:10:24 PM

Posted 14 March 2010 - 05:24 PM

so the graphics card is now in the computer right? if so try taking it out and putting back in and make sure there is no dust in there either, could you specify what graphics card it is?


No, its been taken out to stop the BSOD from occurring.

its a Saphire AT Radeon HD 512mb 3450.

#5 pnjunction

pnjunction

  • Members
  • 10 posts
  • OFFLINE
  •  
  • Local time:05:24 PM

Posted 15 March 2010 - 07:10 PM

hal is the hardware abstraction layer. Its what communicates directly with the hardware and (manages the irq sharing etc.) communicates with the outer rings so that hardware can be interfaced with. If there is a problem there you almost always get a BSOD. I'm not intimatly familiar with win7 yet, but i doubt there is that much difference under the hood.

I would say you have a harware sharing conflict, or you have malfunctioning hardware. If removing the vid card solves the problem it could be overheating, or have a bad connection. the fan and heatsink need cleaned every couple of months, and if they have overheated badly at some point could be permanently damaged.

First check any resource sharing conflicts in windows. Sorry I cant tell you how as I dont know how to in win7 yet.

To rule out the card you will need to put it in another machine and se what you get. If thats not possible, pull out every other card, disconnect everthing you dont absolutely have to have, slick the drive, and reinstall windows.

If it still wont behave, install win XP, and see if you still have a problem, it could be isolated to win7. As a last resort you could try to manage irqs in the bios manually if you bios even allows it. Though even if its a resource conflict it could be a memory range, and not irq at all.

All things considered I'm leaning toward your problem being resource sharing conflict due to bad drivers or faulty hardware.

Good luck

#6 forever_insane

forever_insane
  • Topic Starter

  • Members
  • 17 posts
  • OFFLINE
  •  
  • Local time:10:24 PM

Posted 17 March 2010 - 04:18 AM

Hey,

Thanks for the reply, gave the card 1 more go, installing a driver from their site instead of the disc and its been ok for 24hrs but iv just got BSOD again, but with an apparent different problem, although possibly related to my GFX card again (I also have a PCI network adapter and a SATA PCI card connected).

==================================================
Dump File : 031710-41979-01.dmp
Crash Time : 17/03/2010 09:10:40 AM
Bug Check String :
Bug Check Code : 0x00000122
Parameter 1 : 0x0000000a
Parameter 2 : 0x00000004
Parameter 3 : 0x00000000
Parameter 4 : 0x00000000
Caused By Driver : pci.sys
Caused By Address : pci.sys+8571
File Description : NT Plug and Play PCI Enumerator
Product Name : Microsoft® Windows® Operating System
Company : Microsoft Corporation
File Version : 6.1.7600.16385 (win7_rtm.090713-1255)
Processor : 32-bit
Computer Name :
Full Path : C:\Windows\minidump\031710-41979-01.dmp
Processors Count : 1
Major Version : 15
Minor Version : 7600
==================================================


GFX card related? Thank you.

#7 cryptodan

cryptodan

    Bleepin Madman


  • Members
  • 21,868 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:Catonsville, Md
  • Local time:10:24 PM

Posted 20 March 2010 - 01:47 AM

Have you updated the chipset drivers and kept up to dates with Windows?

#8 pnjunction

pnjunction

  • Members
  • 10 posts
  • OFFLINE
  •  
  • Local time:05:24 PM

Posted 20 March 2010 - 03:08 AM

PCI Enumerator is windows way of saying that two pieces of hardware want the same resources and this is our name for that. I cant tell from what you posted, but it looks like it may be a memory address conflict.

I think the driver may be the issue here, but since I have little experience with ATI and also with win7 it's hard to say.

goto device manager (or whatever they have now), pull up the properties for the video card, look on the resources tab, and scroll down, if you see something with a red circle with a slash through it, that means there is a conflict. This most likely means your DRIVER is the issue. Make sure you are selecting the correct video card when you install, and you might try something like driver sweeper, but make sure you run it in safe mode.

Honestly, I would load XP. Might sound a crappy soulition, but Win7 just isnt mature. I'm waiting unitl SP1 myself.




0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users