I'm gettin BSOD from time to time for over a month, it happens randomly, one-two times a day, but even not every day... I don't know what's wrong the system just hangs and the screen becomes blurry, after a while there comes the Blue screen on which I cannot read anything, because the image is blurry like I said... It's freakin me out already... I'm using BIOS 1.18, and recent drivers... the last two times the error messages in event viewer were - Event ID-10016; Source - DCOM; User - NT AUTHORITY\NETWORK SERVICE... please help
-
Well, I hope you've already found your answer, but it sounds like a hardware issue. You can run Memtest86 to see if the memory is okay, and perhaps a hard drive diagnostic program (from the manufacturer who made your HDD) to see if there are any issues there.
Could it be an overheating issue? Try taking off the heatsink for the CPU/GPU, cleaning it up, and reapplying some quality TIM. Also, may be a good time to clear out any accumulated dust from the vents and HSF. -
Yop, I had the same issue, luckily my warranty wasn't over and a got my MoBo and VGA replaced. What freaks me out is that the system died two time through a year of usage with the same syndromes. I hope the new MoBo I got has a fix of whatever caused it to brake in BSoD’s with time.
-
Well... I'm without a laptop for a month! No, I haven't resolved the problem, but it doesn't matter, cause the video card died... Luckily, like Dirt, my warranty is not over, so I'm waiting to receive 'something' next week (as they told me), I'll let you know what happens...
-
8600m dying?
-
I would think that two, if BSoD's would applier on 3D intensive operation and not in idle work, but they stroke randomly even when you less expect it.
-
Just run memtest for a long time to see if it's the ram that is causing a problem if nothing comes up, test you gpu with the furmak stress test.
Also install the debugging tool for vista 32bits, the corresponding symbols and open your bsod dumps with it to see if the info about what went wrong isn't there. -
haha are you kiddin with me guys? I post a thread and no one answers... months later, when my laptop is on a major repair and might even be replaced, you start to answer like crazy. Thanks anyway, hope this helps someone. I remember I ran memtest - nothing disturbing, I'm using XP, so I just read the eventlog to see something that might help to solve the problem, but it's Windows after all... so the BSOD remained a mistery right until my fl90 bitter end. If they send me a new machine it will be with my old hard drive, so if it happens again, we'll be sure that's from some f***** drivers or windows bull****. greets, and good night
-
Heh, that was funny. It's called necromancing.
-
Problem solved: Since I got my FL90 back, with only the RAM and the Hard drive from the old laptop, I knew it would be the RAM or the bloody Windows that's causing the BSOD. So it happened again on the first day BAM - BSOD... I read a lot about this DCOM error, and finally I killed it, seemingly it was the cause of the BSOD, because I haven't got any BSOD since (about 2 weeks). The problem was with the Intel 4965 AGN wireless drivers! To switch off the component that messes it all you should go to - Control Panel/Component Services/Computers/My Computer/DCOM Config/ then you have to find RegSvc and disable it! It's not an important component, the wireless works perfektly after that, so don't worry. That's it! No DCOM error anymore = no BSOD! Cheers guys, hope this helps someone.
Compal FL90 BSOD
Discussion in 'Other Manufacturers' started by Layne, Dec 5, 2008.