|
First i would go about finding out if it actally is a hardware problem, as it could just be windows thats all broken down. A simple way to test this is to burn out a Linux live on CD (Like Knoppix or Ubuntu) and then sit and click around in that for a while, surf the web, check email etc. If it still crashes then hardware is you problem. If not, then windows/program/malware is the problem. (a re-install would probably help)
If its hardware it can be anything really, RAM is an important part in any computer, but it could just as well be any other part.
It could also be that some setting in your BIOS is overclocking your computer/parts of it, this is a common reason for freezing, so maybe you should load BIOS defaults too.
This type of problem can be hard, as anything can affect everything else (in a odd way)...
I hope this is a start...
//Johannes
|
|
|
|
|
ei thanks!
i ll try to reset my bios i havent try that.. and i wish that would solve this..
i havent done any overclocking yet but yeah maybe the previous user of my motherboard tried something else..
also i ll try to burn out too.. but first i need to download the ubuntu or knoppix but i think it will finish downloading tomorrow cause its more than 500 mb size..
i never really like this... being a programmer...whhargghh!!
|
|
|
|
|
download a memtest86 CD, boot it, have it run a stress test overnight. If it passes with no errors you've proved the ram innocent. Running prime95 (24hrs per test type) in windows will stress your CPU and to an extent your mobo/ram. If it's erroring out you've got a hardware problem.
If your new CPU uses more power than the old one but you're using the same heatsink it might be overheating and crashing. For a socketA board motherboard monitor should be able to keep an eye on your CPU temp. If you're going above 60C it might be a problem, 70C definitely would be. To test the PSU, get a multimeter and with the system fully loaded check the voltage between +5V(red) and ground(black) and +12V(yellow) and ground in the ATX plug. Depending on the probes you might need to supplement with bent paperclips to make contact. +-5% is within spec anything outside is a problem.
Otherwise [Microsoft is] toast in the long term no matter how much money they've got. They would be already if the Linux community didn't have it's head so firmly up it's own command line buffer that it looks like taking 15 years to find the desktop.
-- Matthew Faithfull
|
|
|
|
|
thanks guys for all your replies man and guess what!!?
last night i did reset the bios to default and i think it did solve it
cause ive used it more than 5 hrs straight without halting..
before it hangs just within an hour.. and last night i did enjoy playing my warcraft(DOTA) and had a 'BEYOND GOD LIKE' ai hero killings hehe!! thanks to johpoke and also to dan neely
but i still need to to burn out to be sure.. and yeah i should check my cpu temp..
you guys are great man i love this site more than ever
i never really like this... being a programmer...whhargghh!!
|
|
|
|
|
Lucky that only reseting the bios fixed the problem, sometimes it can take forever to find the problem. Running prime95 for a few days as dan neely said is a way of ensuring 100% stability, and is a very good test to do on any computers you use.
To check CPU temps use SpeedFan
//Johannes
|
|
|
|
|
I orignally posted this question under OS/SYSADMIN
But then while looking at this section I noticed questions about DDK So I posted the question here too
Hi,
I was looking to use WinDbg remotely to debug device driver anyway was looking at some documentation
and it looked like there were one or more ways of connecting 1) null modem via a com port specfying those paramters in the boot.ini
also in addition or maybe just another method of connecting remotely was starting WinDbg with a TCP:PORT number
I have a wireless router and can open up a port by typing the IP address of the router and from one the menus opening up a port
My question is when connecting through a port dont I have to know the IP address of the machine I connecting to
or maybe this isn't necessary since the machine I am connecting to is the one that is connected via the null modem
Thankx in Advance
|
|
|
|
|
The DDK is the best source of info on this. You can also find it on the internet genrally. Check out OSR online for good driver resources.
Anyway, a null modem cable is the easiest. Fire wire also works and is quick, and the lates is supposed to be USB based, havent tried it yet thgough.
You cannot use an IP stack for debugging though.
So, stick your nuull modem cable into COM1 on each machine. Add to boot.ini on the target machine /debugport=COM1 /baudrate=115200 to the stock boot option (remove the other switches).
Start WinDbg on the host and open a kernel debug session on COM1 at 115200 then reboot the target.
Away you go. Then set the symbol path, source path and so on and you can step through your driver code.
Morality is indistinguishable from social proscription
|
|
|
|
|
I have gotten a conection with a fireware on dual core laptop windows XP to Dual core tower windwos XP however laptop dual core XP to TOwer XP quad core gives me a problem
|
|
|
|
|
Hi
Moving asp.net files over from a citrix server to a web server?
What sort of problems am I going to have regarding how the code works, the .net framework and interfacing with sql server?
I was thinking of using ssl for the link between web server and citrix server]
any help would be great
cheers
|
|
|
|
|
Hi everyone!
I have a GA-965P-DQ6 motherboard from Gigabyte and I'm trying to install a PCI to IDE card with Sil0680 chipset on it, the hardware is detected and driver is installed but the install wizard returns (Code 10) so windows could not run the device.
I have win vista and i have downloaded the last driver for my device!
What should I do to run it?!
Sojaner!
|
|
|
|
|
Hello All,
Which is the best place to look for the information about the various facts technology about hardware. I am an application programmer with a very limited knowledge of how we access the hardware through software.
Basically what I need to learn is the basic knowledge about various topics as PCI buses (want to undersatand what bus-function-device-offset way of reading PCI space), ISa, SPD, SMBus etc etc.
I am able to download specification documents for each of above mentioend technology bit they are very detailed and indepth. What exactlly I am looking for is brief and to the point stuff for a programmer.
Pleas help
Thanks
|
|
|
|
|
vikrantc1355 wrote: What exactlly I am looking for is brief and to the point stuff for a programmer.
The average programmer doesn't need to know this stuff. The hardware, in conjunction with its driver and the OS, expose an interface to the user-mode world which is used to access the hardware - things like a drive letter, a custom IOCTL, a com port indicator (COMx), ... User-mode programs use that to communicate with the hardware.
If you're looking at actually talking to the hardware, you're entering the realm of writing a device driver. "Brief and to the point stuff" for this subject doesn't exist. How a driver talks to a piece of hardware depends on each piece of hardware, and the operating system it is written for. This is not a simple straight-forward subject.
Here's my usual list that I give when asked about info on device drivers.
The WDK itself - documentation andthe samples are improving but it assumes you already have a good knowledge of the OS
"Programming the Windows Driver Model" 2nd ed by Walter Oney - make sure it is the 2nd edition
"Microsoft Windows Internals, Fourth Edition: Microsoft Windows
Server(TM) 2003, Windows XP, and Windows 2000" by Mark Russinovich and David Solomon
"Windows NT Device Driver Development" by Peter Viscarola and Tony Mason - dated but the stuff they discuss hasn't changed and it's a good foundation.
"Developing Drivers with the Windows® Driver Foundation" by Penny Orwick and Guy Smith - this one is from Microsoft Press and is the only book currently published with a good description of KMDF
This one should be excellent (if they ever get it published) "Introduction to the Windows Driver Foundation Kernel Mode Driver Framework " by Peter Viscarola, Tony Mason, Mark Cariddi, Brenda Ryan, Scott Noone, and OSR
|
|
|
|
|
My requirment is not something related to driver develoment.
The books you menmtioned seems to be specific to that peupose.
Waht I am looking is like I want for example lets assume I want to show the content of PCI Config space to show this I should have a good understanding of PCI spacce and its structure and other stuff. Smilarly for SPD and SMBus etc.
|
|
|
|
|
The problem is, from a coding point of view, that only drivers are allowed to access this information from the hardware. You cannot write a user-mode program to access this directly - the OS flat out won't let you. The content of the PCI config space, for instance, is the way it is described in the spec. You can look in the DDK files to see the data structure(s) used by a driver to query for the config space (search for PCI_COMMON_CONFIG for the PCI stuff). All those tools that show stuff like the config space (I've written some myself) all commmunicate with a driver to actually get that info.
My suggestion to learn about this type of hardware stuff is to look at the specs for each class of hardware and then the appropriate sample drivers in the DDK to see how those data structures and interfaces are manipulated. You can't really draw a line between the knowledge and the driver since the driver is the only one who gets to use it. The knowledge is in the spec and the "how to" use it is in the driver.
If you have access to a Linux box, it is much simpler to write a Linux driver and play with the structures under that OS. However, you have the problem of what piece of hardware to play with since you probably don't have a spare piece of hardware laying around to serve as your guinea pig.
Judy
|
|
|
|
|
extending on what judy said, what information is exposed in userland is exposed via WMI (which in turn is populated by talking to drivers).
Otherwise [Microsoft is] toast in the long term no matter how much money they've got. They would be already if the Linux community didn't have it's head so firmly up it's own command line buffer that it looks like taking 15 years to find the desktop.
-- Matthew Faithfull
|
|
|
|
|
I would start with any A+ certification book and go from there into your specific area of interest.
PS Real computers interface with real hardware - don't let anybody tell you that you do not need hardware knowledge to be a computer geek!
Cheers
Vaclav
|
|
|
|
|
I konw that in windows, with "extended desktop" I can use two monitors to form a big virtual screen.
But, how can I make the two monitors display part of the same screen.
For example:
I have two monitors with the same 1024*768 display mode, if I use windows to set the virtual screen ,it gets 2048*768 display mode.
But now, I want to get the 2024*768 display mode.
The first one displays [top-left](0,0)-[bottom-rigth](1023,767) of virtual screen, and the second one displays [top-left](1000,0)-[bottom-right](2023, 767).
As a result, left of first one and left of the second one displays the same region((1000,0)-(1023,767))
thank you for any suggestion
|
|
|
|
|
Hi,
I am using the following two API (which are in WinDDK, and included in cfgmgr32.h):
res = CM_Locate_DevNode_Ex(pdnDevInst_OUT, hid, CM_LOCATE_DEVNODE_NORMAL, hMachine);
res = CM_Request_Device_Eject_Ex(dnDevInst, NULL, NULL, 0, 0, hMachine );
I tried these APIS (on VC++ 6.0 & WinDDK 1.7) and it is compiling successfully. But I get 2 linker errors as shown below:
error LNK2001: unresolved external symbol __imp__CM_Request_Device_Eject_ExA@24
error LNK2001: unresolved external symbol __imp__CM_Locate_DevNode_ExA@16
Aslo I checked the Tools->Options->Dirctories->Library files, the path for the lib file "cfgmgr32.lib" is included as:
C:\WINDDK\6001.17048\LIB\WXP\I386
I don't understand still why there is this linker error.
Any one know this problem? Any solution for this?
Thanks in Adv...
Thanks & Regards,
Neeraj
|
|
|
|
|
You're trying to use Visual C++ 6.0 to build with the Windows Server 2008 DDK? Something tells me that's not going to work. Use the build environment from the DDK, or Visual Studio 2005. Microsoft have basically abandoned the old tools.
DoEvents : Generating unexpected recursion since 1991
|
|
|
|
|
hi ...
any please help me in finding the correct DDK VERSION for building NT
based driver in windows VISTA
|
|
|
|
|
|
the 2003 DDK is OK for drivers for 2k, XP and Vista, provided its not a Ndis 6 driver. If it isyou need the Vista DDK.
NT 4 has its own DDK too.
Morality is indistinguishable from social proscription
|
|
|
|
|
What's the best solution for fast hard disk access in a home PC? From what I've read it looks like multiple drives in RAID 0 configuration would be best.
|
|
|
|
|
Personally I'm not sure there's much benefit for RAID 0 in a home PC. You only get any benefit from striping if you have multiple concurrent disk accesses which target different disks, which tends to be the case if you have random access I/Os. The vast majority of I/Os in most systems are sequential - we've all written the code, open a file, read it to the end into memory data structures, close the file. When finished editing, open the file for writing, spew out the data structures again, close the file. All sequential.
With sequential I/Os, each drive in a striped array (RAID 0 or 5) effectively becomes active in sequence as the file pointer moves across the disks. Only if you have a lot of concurrent I/Os to different files might you get a benefit, but even then you don't get a lot of advantage.
RAID 0 has the obvious greater risk that if you lose one of the disks, you lose the volume. The probabilities are greater that you'll lose at least one of the disks than if you were to lose a single standalone disk. Compensating for this by using RAID 5 has a large disadvantage in write speeds.
The best place to start is to get disks with high spindle speeds. The higher spindle speed increases maximum bandwidth from the platter, and slightly decreases access times as the desired block will appear under the head more quickly, on average. At the very least get 7200rpm drives, 10,000rpm SATA drives are also available for a premium and generally have lower capacity than 7200rpm drives. (750GB 7200rpm drives are available for about the same price as 150GB 10k rpm drives).
Because of the varied access patterns for different applications and the different loads to which systems are put, it's really difficult to tune the disk subsystem to any degree for a home PC. You might get most benefit from simply throwing lots of memory at the system, so that more data is cached.
DoEvents : Generating unexpected recursion since 1991
|
|
|
|
|
Recently, I've found myself running out of contiguous storage space. (I've got a lot of small drives installed over many computers. Some of them are even lying in my cabinets.) I decided it would be best to have a centralized (or at least portable) storage medium to stuff my files in. I've been hunting around the internet scrutinizing many products being advertised.
My requirements for the products were:
- Does not require installation of packaged software
- Can be accessed using one, any combination, or all of these: Firewire, Ethernet, or eSATA
- RAID-5 support (and by extension, it holds at least 3 hard drives)
- Supports NTFS
- Internal use of SATA preferred over IDE
- Massive amounts of storage (3 to 4 TB preferred)
- Something that is asthetically pleasent (e.g.: no giantic logos or company name carved in cursive…)
iOmega's 2TB Power Pro[^] seem to have hit most of the points. I'm considering getting one.
Does anyone have something that they think is better?
Thanks in advance…
ROFLOLMFAO
|
|
|
|