code 43hmm, maybe my brain is tired.search didn't really helpHelp didn't do much either,video controller has been stoppednever give upbut somehow I feel I know nothingcan anybody show me how I can Write myself a compatible driver?what can the average person do when manufacturers don't update the drivers?I am not complaining, I love my computerJust asking I used to think I was really smart :D

llynne said: code 43hmm, maybe my brain is tired.search didn't really helpHelp didn't do much either,video controller has been stoppednever give upbut somehow I feel I know nothingHi llynneSee Error Codes in Device Managerfor the details. Device Manager displays the following message in the Device Properties dialog box, on the General tab, in the Device Status text box: Windows has stopped this device because it has reported problems. (Code 43) DiagnosisA device driver notified the operating system that the device failed. ResolutionFor more information about how to diagnose the problem, see the hardware documentation. can anybody show me how I can Write myself a compatible driver? what can the average person do when manufacturers don't update the drivers? I'm afraid there isn't much we can do if the device manufacturer decides not to support that device?Thank You for testing Windows 7 Beta Ronnie Vernon MVP

thanks Ronnie but I already got that far.Something told the system the device stopped working, windows refuses to start it, If it spoke English I believe I could talk it round. .the thing I angst about is that someone writes the drivers and I am, like, so sure- it will be three lines of code and easy for me to fix, just for my machine that has a good twelve months of useful life in it. Not worth it to anybody else. It is all to do with the dual graphics accelerator and the fact that it is embedded, and multifunctional graphics memory.It is probably the same fundamental problem the upmarket graphics systems are having and really deserves a better answer than "we can't help it if manufacturer doesn't back their product." I got really worried when I saw reports of new out of box vista machines that couldn't install their own drivers. Of course this is the hardware vendor's problem and they will lose business. My question is can anyone help me to override the hardware installation at startupand instruct windows to do as I tell it, even if I am wrong... because maybe I am not. Same with compatability mode it just keeps trying the same failed setting so far as I can see. If it was only me I wouldn't mind, it is the principal of the thing

From how the error code reads, it sounds as if the problem is actually with the physical device and not with the driver.

I sat in the computer repair shop while five people went through, every one a dead motherboard, or is it? I have lost count of how many times I was notified a faileddevice was broken when it was software.Is everyone's graphics unit phfft or is it a driver problem? I have no doubt that I will be getting myself better computers and graphics cards in times to come. The problem will still be there to be solved though. If I assume the solution to every question is to give up I would. But computers are like art and poetry and math and stellar clouds. There is an over-riding elegance to a good solution which (while not an end in itself) breeds functionality (too much?)Remember, I am the poor who inherit the computers that operating systems throw out.I am the mathematical type who wants a program to add up. I only bother asking this very sad question because I KNOW the parts are not broken, I know there is a compatable driver or setting with enough trial and error. I have spent hours, days and weeks on funky reconditioned machines till something worked (and then I forgot what it was I had done and had to do it all over again) I am happy, more than happy to nut it out till I get an answer that works for me. Currently I say it is not enough for me that windows didn't want to crash so it switches the hardware off. It makes it look cowardly. I think the average computer user is tough enough for windows to say to them I don't like this driver, do you want to try it anyway? not "I switched off for an unknown reason" (and end discussion)

This SODIMM sure looks good. I am sure it is good. I know it is good. Oh, but wait. It is not. There is a difference when a half-butt tech informs someone that hardware may be bad, but it is completely different when the device driver informs the OS the device is bad. Does that mean the device is really bad? No. However, being that this is a rare occurrence, I will err on the side of believing the device driver. Errors such as the device cannot start, unable to allocate resources, etc are workable errors that knowledgeable people can get through. However, devices do go bad. If you want to see a rash of bad hardware get shaken out, go work at an HPC center for while, run LINPACK to push the hardware to its limits and get ready to catch your eyeballs when they come flying out of your sockets from disbelief. I fully agree with you that here is a bunch of old hardware that was put out and misdiagnosed hardware, that in reality is just a good as it was on day one. Currently I say it is not enough for me that windows didn't want to crash so it switches the hardware off. It makes it look cowardly. I think the average computer user is tough enough for windows to say to them I don't like this driver, do you want to try it anyway? not "I switched off for an unknown reason" So you would rather the OS crash and puke instead of protecting itself and the users data? If a user tried to load unsigned, unverified drivers, Windows does ask the user what he or she wants to do. Code 43 is not an unknown reason; the reason was, A device driver notified the operating system that the device failed. If you think you can write a better, more robust driver than the vender, then do so: http://www.microsoft.com/whdc/devtools/wdk/default.mspx.

Darianhawke said "So you would rather the OS crash and puke instead of protecting itself and the users data? If a user tried to load unsigned, unverified drivers, Windows does ask the user what he or she wants to do. Code 43 is not an unknown reason; the reason was, A device driver notified the operating system that the device failed. Too right mate! I RESPECT AND LOVE THAT IT WOULD NOT DO SO WITHOUT MY DIRECT AND PERSISTANT INTERVENTION,The main thing that I do with my spare time is crash the poor computer Only once was it fatal I put the wrong hardware in the wrong slot and saw the smoke curling up instantly and too late . That is once in thousands of goes. I have dropped them, rearranged them had sixteen goes at doing the same failed thing and then eurika! But remember I don't get the brand new ones (except for the very first one because they didn't have old ones then.) I get the broken ones that people said do not work. I don't leave my files in danger deliberately.My use of my computers is different They get passed on once they are Stable and happy. I cannot tell if ram is good by looking at it but I can produce obscure scientific evidence that sub atomic physics explains why a healthy routine of counting the memory checking the disk and running screen savers like mystify and fractal generators ect begin to noticeably improve a computers performance. A busy computer is a happy computeralso Darianhawke67 "If you think you can write a better, more robust driver than the vender, then do so: http://www.microsoft.com/whdc/devtools/wdk/default.mspx. "Thanks I cannot tell if that is a friendly response to a question like can I? I thought there might be a law against it. I know I am too dumb To write a for to loop OK. (I used to fix graphics problems in early windows by installing and uninstalling certain game programs which I had noticed directly addressed the graphics adapter without asking. Always left the computer in better condition than it was before: )

Correct, egads.although it could be way less than five yearsmy effort isn't wasted. the beauty is that under the code languages are the machine languages and under that the binary. An artist who makes an artwork that is instantly destroyed has not wasted the time. They learn more about what they are doing they have the springboard and inspiration to move on.Today I learn how to custom build a bodgy driver to satisify a unique need in my computer infrastructure, Tomorrow I learn to build a unit than will support some non standard peripherals. then a robot..... yep, I can teach the laptop to ........ we are still only limited by our imagination. I believe with all my heart that we need to work together no finger pointing, no defensive posturing. They remember Rome because they built such worthy roads. Will they remember us for computing or finger pointing?