User Pass
Home Sign Up Contact Log In
Forum > GLB Notes > CPL > Someone fix my CPU plz
Page:
 
Serious Bob
offline
Link
 
Originally posted by gart888
step 1) get a mac
step 2) there is no step 2... macs don't break


Macs are so shit.
 
islander1
offline
Link
 
Mini101708-02.dmp

this file would really help. Something dopey about windows though. At least server 2003 --> the minidump self deletes after telling you it's been created. You have to search for it and copy it somewhere else before you get the notification on next logon. again, this might not apply to your version of Windows though!

I found this out the hard way when I was looking into some WMI problems about 6 months ago here at work.

In any event, if you send that minidump to Microsoft (or some other expert) they can tell you exactly what is wrong.

Additionally, check your event logs (eventvwr from the run prompt) for errors in both the application and system logs that might point to something around the same time as the crash.

hope this made sense.
Last edited Oct 17, 2008 12:32:14
 
Cuivienen
offline
Link
 
Originally posted by kb916
wait people really use macs?



o_O



Only cool people.
 
islander1
offline
Link
 
Originally posted by Serious Bob
Originally posted by gart888

step 1) get a mac
step 2) there is no step 2... macs don't break


Macs are so shit.


Macs are OK imo, but I'd never own an iphone.
 
Serenity
offline
Link
 
Originally posted by islander1
Mini101708-02.dmp

this file would really help. Something dopey about windows though. At least server 2003 --> the minidump self deletes after telling you it's been created. You have to search for it and copy it somewhere else before you get the notification on next logon. again, this might not apply to your version of Windows though!

I found this out the hard way when I was looking into some WMI problems about 6 months ago here at work.

In any event, if you send that minidump to Microsoft (or some other expert) they can tell you exactly what is wrong.

Additionally, check your event logs (eventvwr from the run prompt) for errors in both the application and system logs that might point to something around the same time as the crash.

hope this made sense.


I have Vista. And I can't find that file at all
 
Serenity
offline
Link
 
Originally posted by Cuivienen
Originally posted by gart888

step 1) get a mac
step 2) there is no step 2... macs don't break


Then why does this website exist? http://www.macfixit.com/

I'd be willing to bet that you have a micro-fracture in your motherboard. The trace will remain in contact in certain temperature ranges, but if the mobo gets too hot or cold, it will separate, causing your computer to shut down.

If your computer turns itself back on, this is definitely the problem.


How would I find out?
 
jeffgarcia
offline
Link
 
Take out motherboard.

Get hammer.

???

Tell CPL what happens
 
Gart888
things!
offline
Link
 
Originally posted by jeffgarcia
Take out motherboard.

Get hammer.

???

Tell CPL what happens


but how would she tell us what happens?
 
jeffgarcia
offline
Link
 
someone else's computer obviously.




or telepathically to Vando.
 
islander1
offline
Link
 
Originally posted by Serenity
Originally posted by islander1

Mini101708-02.dmp

this file would really help. Something dopey about windows though. At least server 2003 --> the minidump self deletes after telling you it's been created. You have to search for it and copy it somewhere else before you get the notification on next logon. again, this might not apply to your version of Windows though!

I found this out the hard way when I was looking into some WMI problems about 6 months ago here at work.

In any event, if you send that minidump to Microsoft (or some other expert) they can tell you exactly what is wrong.

Additionally, check your event logs (eventvwr from the run prompt) for errors in both the application and system logs that might point to something around the same time as the crash.

hope this made sense.


I have Vista. And I can't find that file at all


Oh, I'm sorry (you have Vista). Vista is a crap OS for at home computers that aren't being used for business primarily. But enough of that.

OK, my hands on with Vista is limited, but from what I read, you should be able to find this file even after you crash and reboot. Do a file search for something like *.dmp and see if it pops up.
 
islander1
offline
Link
 
Originally posted by gart888
Originally posted by jeffgarcia

Take out motherboard.

Get hammer.

???

Tell CPL what happens


but how would she tell us what happens?


from the public library
 
Serenity
offline
Link
 
Originally posted by islander1
Originally posted by Serenity

Originally posted by islander1


Mini101708-02.dmp

this file would really help. Something dopey about windows though. At least server 2003 --> the minidump self deletes after telling you it's been created. You have to search for it and copy it somewhere else before you get the notification on next logon. again, this might not apply to your version of Windows though!

I found this out the hard way when I was looking into some WMI problems about 6 months ago here at work.

In any event, if you send that minidump to Microsoft (or some other expert) they can tell you exactly what is wrong.

Additionally, check your event logs (eventvwr from the run prompt) for errors in both the application and system logs that might point to something around the same time as the crash.

hope this made sense.


I have Vista. And I can't find that file at all


Oh, I'm sorry (you have Vista). Vista is a crap OS for at home computers that aren't being used for business primarily. But enough of that.

OK, my hands on with Vista is limited, but from what I read, you should be able to find this file even after you crash and reboot. Do a file search for something like *.dmp and see if it pops up.


I tried that as well as a search for that filename and nothing popped up

 
Cuivienen
offline
Link
 
Originally posted by Serenity
How would I find out?



Very painfully tbh.

You can't test for a microfracture without a voltmeter, basic electronics & computer hardware knowledge and a lot of patience (and you'll still probably miss it, there are a shit ton of traces on a motherboard).

The easiest way to test for it is to actually test every other component in your system. If they all work, you need a new mobo.

Now, that is painful and time consuming, yet doable with a desktop. Unfortunately for you, that is nearly impossible with a laptop.

Proprietary hardware formats make it very difficult to test all the other components. Even if you wanted to try, good luck getting all the components out of your laptop without damaging them. If by some miracle, you determine it is the motherboard, good luck actually doing anything about it (in a laptop, the problem could be with a trace in the connection between your GPU and your LCD for instance, instead of on the motherboard proper).

Basically, get on ebay/craigslist and look for a replacement that you can afford. You could also send the laptop into the manufacturer for a repair quote, but I can guarantee you won't be willing to pay what they ask for.

The other option is just to live with it until you were going to get a new laptop anyway.
 
islander1
offline
Link
 
Originally posted by Serenity
Originally posted by islander1

Originally posted by Serenity


Originally posted by islander1



Mini101708-02.dmp

this file would really help. Something dopey about windows though. At least server 2003 --> the minidump self deletes after telling you it's been created. You have to search for it and copy it somewhere else before you get the notification on next logon. again, this might not apply to your version of Windows though!

I found this out the hard way when I was looking into some WMI problems about 6 months ago here at work.

In any event, if you send that minidump to Microsoft (or some other expert) they can tell you exactly what is wrong.

Additionally, check your event logs (eventvwr from the run prompt) for errors in both the application and system logs that might point to something around the same time as the crash.

hope this made sense.


I have Vista. And I can't find that file at all


Oh, I'm sorry (you have Vista). Vista is a crap OS for at home computers that aren't being used for business primarily. But enough of that.

OK, my hands on with Vista is limited, but from what I read, you should be able to find this file even after you crash and reboot. Do a file search for something like *.dmp and see if it pops up.


I tried that as well as a search for that filename and nothing popped up



damn Microsoft.

did you check your event log? Wish I could help more but going home for the day. Won't be back online here til about 8.
 
islander1
offline
Link
 
Originally posted by Cuivienen
Originally posted by Serenity

How would I find out?



Very painfully tbh.

You can't test for a microfracture without a voltmeter, basic electronics & computer hardware knowledge and a lot of patience (and you'll still probably miss it, there are a shit ton of traces on a motherboard).

The easiest way to test for it is to actually test every other component in your system. If they all work, you need a new mobo.

Now, that is painful and time consuming, yet doable with a desktop. Unfortunately for you, that is nearly impossible with a laptop.

Proprietary hardware formats make it very difficult to test all the other components. Even if you wanted to try, good luck getting all the components out of your laptop without damaging them. If by some miracle, you determine it is the motherboard, good luck actually doing anything about it (in a laptop, the problem could be with a trace in the connection between your GPU and your LCD for instance, instead of on the motherboard proper).

Basically, get on ebay/craigslist and look for a replacement that you can afford. You could also send the laptop into the manufacturer for a repair quote, but I can guarantee you won't be willing to pay what they ask for.

The other option is just to live with it until you were going to get a new laptop anyway.


He's spot on. This all falls into the 'not worth all the trouble' category.
 
Page:
 


You are not logged in. Please log in if you want to post a reply.