|
Youc CANT use the local o;ption to debug the machine. You HAVE to use remote debugging.Period.
==============================
Nothing to say.
|
|
|
|
|
How can a machine that is frozen in the kernel runa user mode app?
Also csrss hangs also lock the UI. How can you manipulate an app with no UI?
You HAVE to use a second machine.
==============================
Nothing to say.
|
|
|
|
|
Ah, do you have power off to the USB devices when the screen saver kicks in?
You can disable power saving on the various host controlers in Device manager, try that.
You can also debug using the USB com ports by the way.
And no, you canot locally debug the kernel. Period. You have to use a second machine.
==============================
Nothing to say.
|
|
|
|
|
I'll have to find another machine then I guess, what other choice do I have 
Do you know of a tutorial on the cabling? Or can I just use a standard female to female usb cable between two machines to do this? My machine does not power off usb devices at any point.
|
|
|
|
|
Did you say you have USB to COM port adapters? If so then get a second machine, the host, with a COM port, and debug the target machine with a NULL modem cable attatched to its USB to COM adaper https://www.google.co.uk/search?hl=en&gs_nf=1&cp=8&gs_id=1m&xhr=t&q=usb+com+port&bav=on.2,or.r_gc.r_pw.r_qf.,cf.osb&biw=1233&bih=606&um=1&ie=UTF-8&tbm=isch&source=og&sa=N&tab=wi&ei=kTtaT4WrHpDZ8gPguJDfDg[^].
If not it is firewire.
One can, aparently, do US to USB debuging, but since you have trouble with your USB subsys it might be affected. WHo knows.
Firewire is the best.
For a tutorial on connecting the machines look on line, in windbg help, and in the DDK (now called WDK).
==============================
Nothing to say.
|
|
|
|
|
There is another way of finding out which driver is responsible (more tedious perhaps). If the machine doesn't freeze in safe mode, then start to add drivers one by one until the freeze occurs. Add one, then use the machine for a period of time, add another then use the machine for a period of time, and so on.
Of course, this will only help in cases where the freezing occurs regularly (let's say at least once or twice per day).
|
|
|
|
|
Thanks Albert, it is once every 2 to 20 days, it drives me crazy.
I'm going to try the usb configuration this week
|
|
|
|
|
still not really understand about notebook and ultrabook battery nowdays.
some said that charging while using notebook will shorten the battery life, some said after full charge, using the notebook without removing the battery won't reduce the battery life.
some said that Lithium Ion Batteries automatically stop charging when it's full and directly use the charger power, so removing the battery to keep it at good condition is not needed.
i love ultrabooks and all of them use built-in batteries, i won't buy an ultrabook if i'll end up destroy the batteries.
there's too many 'some said' and i don't know which one i should believe.
sorry for bad grammar,
please help me battery expert. 
oh i forgot, some said keeping notebook battery in fridge is good. 
|
|
|
|
|
Actually, cold batteries retain their charge for a shorter time.
But, in any and all cases, usually, you're going to get about 2 years out of the batteries no matter what you do. Then you replace them.
|
|
|
|
|
so do you know the best way to use ultrabook?
full charged before using? (keep charging)
full charged before using? (stop charging)
charge while using?
btw thankyou very much for answering almost all of my thread dave. 
|
|
|
|
|
STOP WORRYING ABOUT IT!! There is no "best way"!
You're going to be walking on egg shells around this thing and not enjoying using it!
|
|
|
|
|
|
Agree with Dave... there's really no great, special way of dealing with batteries... you can try to be efficient with your charge easily enough (stop background tasks, dim display when possible) but trying to extend your battery life is not really worth worrying that much about.
|
|
|
|
|
So I have a windoze box at work that is acting up. It has been doing this since I got it.
Randomly, the usb drive port will shut the computer off when I plug something in. The monitor goes to "no signal" and all running programs seem to have died (tried to remote once to make sure). The power to the box is still on, but it's just dead. The only way I can find to revive it is to shut off the power, and turn it back on.
Any ideas?
If it moves, compile it
modified 5-Mar-12 16:35pm.
|
|
|
|
|
Yeah, it's both of my front ports though. The computer sits under my desk, so it's annoying not to be able to use them.
I've been avoiding it for now, but I was looking for a solution.
If it moves, compile it
|
|
|
|
|
If it happens with anything you plug into those ports, then it sounds like you've either got a short in the cables between the ports on the case and the motherboard, or you've got a bad motherboard.
|
|
|
|
|
Looks like ESD (ElectroStatic Discharge).
|
|
|
|
|
To the downvoters:
thanks a lot for your downvotes.
A few years ago, I worked for a manufacturer of USB devices. Problems with electrostatic discharges were very common for that manufacturer. Consequently, I have seen many effects of such discharges.
Discharges often occur when someone plugs-in the device, but they can also occur later on. They occur more often during winter, when the offices are heated and thus the air is very dry.
In my opinion, the downvoters provided proof of their lack of knowledge, though they are high-ranking CP members.
Thanks in advance for downvoting this message.
|
|
|
|
|
You havent booted into denug mode have you?
Anyway, whats the OS, whats the device, are there upgraded drivers (because thats whats doing it).
Can you boot into debug mode and attach a kernel debugger to it and find the stalled thread?
==============================
Nothing to say.
|
|
|
|
|
It's windoze xp professional. It doesn't matter what device it is, it only happens at random. I can plug the usb drive in 19 times, and one of those times the screen goes black. Likewise I can plug in the e-cig many times, and one random time it will have the same effect.
I don't think it has much to do with the drivers. I'm leaning towards the short.
If it moves, compile it
|
|
|
|
|
I think it's probably a short too... the leads in USB are relatively close together. If the connector is damaged, it's easy for them to touch one another.
|
|
|
|
|
I would be very surprised. The USB plug is pretty crude, and it happens with lots of devices, only with his front panel conectors.
Thats says its a particular UHCI driver or eben a UHCI chip that is misbehaving and causing system driver to mess up.
I have worked a lot with USB in the kernel, you would be surprised what plugging a device a thousand times can do to a system eventually.
==============================
Nothing to say.
|
|
|
|
|
Erudite_Eric wrote: The USB plug is pretty crude
I mention the short because the same thing happened to my desktop. I accidentally broke the plastic portion when I pulled sideways on a thumb drive (it was stuck on my shirt). The plastic piece broke and the leads were left behind, so if I forget and plug something into that port it causes a short.
Drivers can cause the same types of issues, but the most common is the all dreaded blue screen of death. I guess he has to cover the basis to find out what's really wrong.
|
|
|
|
|
Yes,, drivers BSOD, but if they have an endles wait or dealock that will lock the machined up, and those can be quite common driver faults too.
Verifier will tell you if a driver is making those kinds of errors.
==============================
Nothing to say.
|
|
|
|
|
loctrice wrote: I don't think it has much to do with the drivers
Dxont believe it. A driver can fail very very randomly. It all depends on what memory id over written and what tries to use that memory.
If you like, ie, its a good idea, run Verifier (type Verifier at a command prompt) and check each USB driver on the syste, in turn. Select all but low resource simulation.
What it will do is check a driver very thouroughly and BSOD the machine with a usefull dump. (Have the machine set up to create full kernel dumps).
THen open the dump, mempry.dmp, in windbg and see what it says (need to type analyse -v in the command line at the bvottom of windb after it has loaded the dmp file)
It is very good verifier. If you have a driver issue, it will find it.
==============================
Nothing to say.
|
|
|
|
General 
News 
Suggestion 
Question 
Bug 
Answer 
Joke 
Praise 
Rant 
Admin 
Submit an article or tip
