Pages: 1

 

2007-03-14 17:52:53
Mongoose
That 70's guy
+156|6994|Sydney, in 1978
Hey, ive noticed lately that exactly 5 minutes and 5 seconds after i sign into windows live messenger ive gotten the blue screen of death and i have absolutely no idea why. Ive tried uninstalling and reinstalling (and yes deleting every single file related to msn) and it continues to happen, so i took a picture of the screen in the hope that some of you will be able to make sence of it. And if anyone knows any altrnitives to msn that would be greatly apprecatied. (but i still need to communicate with people that have msn)

P.S anyone know what the crap about the hardware is about?

https://i32.photobucket.com/albums/d33/699/100_0418.jpg
2007-03-14 17:59:18
weasel_thingo
Member
+74|6791
i havnt seen it before.
Try installing an older msn.
2007-03-14 18:00:41
Mongoose
That 70's guy
+156|6994|Sydney, in 1978
yea, but my problem is that i cant find them anywhere
2007-03-14 18:01:51
Cheez
Herman is a warmaphrodite
+1,027|6903|King Of The Islands

the 'Hardware crap' is a generic message, like the Windows 98 'You didn't shut down the computer properly, dickhead! Do it right next time!'

Unfortunately, microsoft.com didn't turn up anything of use. Maybe reinstall MSN?

Edit: Oh, you tried that, I didn't read that far

Last edited by Cheez (2007-03-14 18:04:42)

My state was founded by Batman. Your opinion is invalid.
2007-03-14 19:03:43
joker3327
=IBF2=
+305|7062|Cheshire. UK
What OS you running...and system specs please
2007-03-14 19:27:04
Mongoose
That 70's guy
+156|6994|Sydney, in 1978
dell dimension XPS, intel pentium 4, 3.39GHz, 1GB of RAM (thats a 1GB block, not dual 512's). i dont know much, if you could PM and i can give more deatals, any help is greatly apprecaited

EDIT: P.S its Microsoft windows XP home edition version 2002 service pack 2

Last edited by Mongoose (2007-03-14 19:28:22)

2007-03-14 19:30:29
Fenix14
scout rush kekeke ^___^
+116|7021|Brisbane, Aus

amazing no one's said don't use msn yet.

umm try running msn in compatability mode, can't think of anything else.

but in worst case senario, use yahoo messanger, you can chat to win live though that.
2007-03-14 19:31:28
Mongoose
That 70's guy
+156|6994|Sydney, in 1978
hahahah yea thanks, but i havent used msn for a few days, i would have posted this earlier, but bf2s was down witch kinda sucks
2007-03-14 20:04:41
joker3327
=IBF2=
+305|7062|Cheshire. UK
Which version of WLM you running??
2007-03-14 20:18:04
Mongoose
That 70's guy
+156|6994|Sydney, in 1978
and wher can i get V7.5?
2007-03-14 20:25:53
joker3327
=IBF2=
+305|7062|Cheshire. UK

Mongoose wrote:

and wher can i get V7.5?
The bottom link ...takes you to it!!

http://www.oldversion.com/program.php?n=msnm

Last edited by joker3327 (2007-03-14 20:26:30)

2007-03-14 21:53:42
I.M.I Militant
We Are Not Alone In Here
+297|7183|Melbourne, Australia
o well mongoose atleast this stops u from sending obcene sexauly explicit material to me...

iv told you once IM ONLY GAY ON FRIDAYS!!! :@
2007-03-14 22:00:02
SplinterStrike
Roamer
+250|6875|Eskimo land. AKA Canada.
Do you have auto sign-int? or does this happen anytime you log in?
If its because you auto-log, you'Re not giving your computer enough time to warm up. Deactivate it and just wait a minute or two before loggin on.

If you don't, I can't really help you.
2007-03-14 22:07:07
DaBigDragon
Member
+3|7204|USA
You could try these steps:

   1.  Examine the “System” and “Application” logs in Event Viewer for other recent errors that might give further clues. To do this, launch EventVwr.msc from a Run box; or open “Administrative Tools” in the Control Panel then launch Event Viewer.
   2. If you’ve recently added new hardware, remove it and retest.
   3. Run hardware diagnostics supplied by the manufacturer.
   4. Make sure device drivers and system BIOS are up-to-date.
   5. However, if you’ve installed new drivers just before the problem appeared, try rolling them back to the older ones.
   6. Open the box and make sure all hardware is correctly installed, well seated, and solidly connected.
   7. Confirm that all of your hardware is on the Hardware Compatibility List. If some of it isn’t, then pay particular attention to the non-HCL hardware in your troubleshooting.
   8. Check for viruses.
   9. Investigate recently added software.
  10. Examine (and try disabling) BIOS memory options such as caching or shadowing.

I'd also suggest downloading and running CCleaner and the registry cleaner built into CCleaner. It is free and is an awesome little program: http://www.ccleaner.com/
2007-03-14 22:15:34
I.M.I Militant
We Are Not Alone In Here
+297|7183|Melbourne, Australia

DaBigDragon wrote:

You could try these steps:

   1.  Examine the “System” and “Application” logs in Event Viewer for other recent errors that might give further clues. To do this, launch EventVwr.msc from a Run box; or open “Administrative Tools” in the Control Panel then launch Event Viewer.
   2. If you’ve recently added new hardware, remove it and retest.
   3. Run hardware diagnostics supplied by the manufacturer.
   4. Make sure device drivers and system BIOS are up-to-date.
   5. However, if you’ve installed new drivers just before the problem appeared, try rolling them back to the older ones.
   6. Open the box and make sure all hardware is correctly installed, well seated, and solidly connected.
   7. Confirm that all of your hardware is on the Hardware Compatibility List. If some of it isn’t, then pay particular attention to the non-HCL hardware in your troubleshooting.
   8. Check for viruses.
   9. Investigate recently added software.
  10. Examine (and try disabling) BIOS memory options such as caching or shadowing.

I'd also suggest downloading and running CCleaner and the registry cleaner built into CCleaner. It is free and is an awesome little program: http://www.ccleaner.com/
can u include in ur list

11. not sending I.M.I_Militant Explicit images of himself

 

Pages: 1

Board footer

Privacy Policy - © 2025 Jeff Minard