Sponsor for PC Pals Forum
« previous next »
Pages: 1 ... 3 4 [5] 6 7 ... 9   Go Down

Author Topic: Display problem  (Read 12433 times)

Adept

  • Guest
Re:Display problem
« Reply #60 on: March 30, 2004, 18:37 »
If I were you Clive I'd let the bunch of cowboys that you bought it from have a look at for you :-X

Letting them have it for a few days would be far preferable to you cocking it up being without your PC permanently  :-\
Logged

Offline ketamininja

  • Full Member
  • ***
  • Posts: 270
Re:Display problem
« Reply #61 on: March 30, 2004, 18:53 »
The repair options looks like DOS, but doesn't really behave in that way at all. I would do some research before attempting to repair - otherwise you'll just be left confused!  :D
Logged

Offline Clive

  • Administrator
  • *****
  • Posts: 75152
  • Won Quiz of the Year 2015,2016,2017, 2020, 2021
Re:Display problem
« Reply #62 on: March 30, 2004, 18:55 »
:aarrgh:  But their best man has left!   ;D  If the worst really does come to the worst I can take it to Mad Eddie.  He's a TV repair guy who is a genius with computers but completely around the twist.
Logged

Offline Clive

  • Administrator
  • *****
  • Posts: 75152
  • Won Quiz of the Year 2015,2016,2017, 2020, 2021
Re:Display problem
« Reply #63 on: March 30, 2004, 18:58 »
Well if it's DOS, that is Mad Eddie's forte.   :D
Logged

Offline Clive

  • Administrator
  • *****
  • Posts: 75152
  • Won Quiz of the Year 2015,2016,2017, 2020, 2021
Re:Display problem
« Reply #64 on: March 31, 2004, 07:43 »
Today's BSOD sends different greetings  ;D
Logged

Offline ketamininja

  • Full Member
  • ***
  • Posts: 270
Re:Display problem
« Reply #65 on: March 31, 2004, 19:55 »
0x50 - basically data was requested from memory, and it wasn't found... or what was found was incorrect and had a bad effect on the pc.


Ok, well TEST YOUR MEMORY! - if you have 2 sticks, pull one out. Test until BSOD/other problems - then swap with the pulled out stick with the one thats in there.

If you still get errors, then I would probably suggest that the mainboard is faulty - with the problems with the graphics, I would suggest that the NORTHBRIDGE CHIPSET is damaged in some way - this is the chip usually found below the CPU, and will normally (these days) have a heatsink on it (and perhaps a small fan).

This NBC is like traffics lights for data flowing between CPU, MEMORY, AGP and SOUTHBRIDGE CHIPSET (another story), so if this goes faulty then replace mainboard - as you can tell from the heatsink, it does get stressed.

Good luck with that memory testing! I hope its a stick of memory because that will probably be cheaper to replace (mainboards are quite reasonable now tho)...
Logged

Adept

  • Guest
Re:Display problem
« Reply #66 on: March 31, 2004, 20:21 »
Isn't symevent.sys part of Norton Crashguard?

If it is and you have Crashguard installed Clive, you would be well advised to remove it. Crashguard is the cause of more and varied BSODs that I care to mention :(

Logged

Offline Clive

  • Administrator
  • *****
  • Posts: 75152
  • Won Quiz of the Year 2015,2016,2017, 2020, 2021
Re:Display problem
« Reply #67 on: March 31, 2004, 22:14 »
I don't, to the best of my knowledge, have Norton Crashguard installed, unless it is part of Norton Utilities suite.  If it is, it's not very apparent.  But I'll uninstall Norton Utilities to see of that helps as I've always had it on this machine.  If it proves to be a memory stick or motherboard then I will cast my fate to Mad Eddie.   :)

Ha!  Norton's Utilities will not uninstall as it reckons it is unable to locate the installation log file!
Logged

Offline Simon

  • Administrator
  • *****
  • Posts: 77921
  • First to score 7/7 in Quiz of The Week's News 2017
Re:Display problem
« Reply #68 on: March 31, 2004, 22:31 »
If you have the CD, reinstall it on top of itself, then either uninstall it again, or see what happens in the morning!
Logged
Many thanks to all our members, who have made PC Pals such an outstanding success!   :thumb:

Offline Clive

  • Administrator
  • *****
  • Posts: 75152
  • Won Quiz of the Year 2015,2016,2017, 2020, 2021
Re:Display problem
« Reply #69 on: March 31, 2004, 22:59 »
That was a good tip Simon!   ;D  I've uninstalled it now and I'm so excited about the morning that I probably won't sleep tonight!  ;D
Logged

Offline lobo

  • Full Member
  • ***
  • Posts: 342
    • http://www.burnleywood.com
Re:Display problem
« Reply #70 on: March 31, 2004, 23:00 »
In my humble opinion if the memory is OK do a new install. the system/registry  files are corrupt and I'm not certain that a repair will fix it, if its not the memory it could be the hard drive going legs up.

Brian ;D
Logged
url=http://pc-pals.com/userpics/loboPC.swf]Flash[/url]

All the survivors of the war had reached their homes and so put the perils of battle and the sea behind them.
Homer   , The Odyssey, line 1

Offline Clive

  • Administrator
  • *****
  • Posts: 75152
  • Won Quiz of the Year 2015,2016,2017, 2020, 2021
Re:Display problem
« Reply #71 on: April 01, 2004, 07:17 »
Uninstalling Utilities didn't make any difference.  But we have a different BSOD message today.  I'm beginning to think that these messages are pretty meaningless if they are so inconsistent.
Logged

Adept

  • Guest
Re:Display problem
« Reply #72 on: April 01, 2004, 07:29 »
A STOP 0x8E message indicates a problem/corruption of a Kernel mode device driver. It can also indicate faulty RAM :(

I also found this MS Knowledgebase article, which appears interesting as it mentions the GDI or Grphical Device Interface :-\

Is there any more info in the Event Viewer for that BSOD Clive?

Logged

Adept

  • Guest
Re:Display problem
« Reply #73 on: April 01, 2004, 07:32 »
Clive, I've just read something which mentioned Quicktime as the source of a problem similar to yours.

It may be worth downloading and installing the latest version :-\
Logged

Offline Clive

  • Administrator
  • *****
  • Posts: 75152
  • Won Quiz of the Year 2015,2016,2017, 2020, 2021
Re:Display problem
« Reply #74 on: April 01, 2004, 07:53 »
There was a flurry of activity in the event log referring to:

The scriptblocking service entered the stopped state.

The SSDP service entered the running state.

The NVAP service was successfully sent a start control.

The NAVEX 15 service was succesfully sent a start control.

The NAVENG service was succesfully sent a start control.

The SSDP service was succesfully sent a start control.

The fast user switching compatibility service entered the running state.

The SymEvent service was succesfully sent a start control.

The Terminal Services service entered the running state.


All these took place at 07:11:18 and are in reverse order.  But just before that it logged Application popups and Save Dump (07:09)





Logged

Show unread posts since last visit.
Pages: 1 ... 3 4 [5] 6 7 ... 9   Go Up
« previous next »
Sponsor for PC Pals Forum