If this is your first visit, be sure to check out the FAQ by clicking the link above. You may have to register before you can post: click the register link above to proceed. To start viewing messages, select the forum that you want to visit from the selection below. |
|
|
Thread Tools | Display Modes |
#1
|
|||
|
|||
BSOD?
A mate came round about a week ago, he said that his card reader would not
work on W7 but would work on XP......... yes, okay. He had this very large 20 year old Kodak card reader, it did not work on my XP and he then remembered that he may need the CD. Then, the Windows firewall on my aging computer turned off. I of course turned it back on again, weird. Then a few days later I lost Internet and got the BSOD, panicked and turned off on the button, all okay until the next day when it happened again. I did a system restore to before he arrived with his card reader and all has been fine for the past few days. Updates have been turned off for ages, I got fed up of being nagged. Can anybody see any connection to the BSOD and his very old card reader? |
Ads |
#2
|
|||
|
|||
BSOD?
Mr Pounder Esquire wrote:
A mate came round about a week ago, he said that his card reader would not work on W7 but would work on XP......... yes, okay. He had this very large 20 year old Kodak card reader, it did not work on my XP and he then remembered that he may need the CD. Then, the Windows firewall on my aging computer turned off. I of course turned it back on again, weird. Then a few days later I lost Internet and got the BSOD, panicked and turned off on the button, all okay until the next day when it happened again. I did a system restore to before he arrived with his card reader and all has been fine for the past few days. Updates have been turned off for ages, I got fed up of being nagged. Can anybody see any connection to the BSOD and his very old card reader? When you install a driver, just about anything can happen. Let's say for example, I wrote you a driver. Well, of course it's going to suck. Writing drivers is hard, because only a subset of program constructs are allowed down there. At work, we used to send people on a three month course, to learn how to do that (seasoned programmers, not idiots). Kodak doesn't make much of anything, and is just a brand name, so we can blame whatever company name is stamped on that USB chip inside the reader :-) USB uses "custom" drivers, for any item which does not follow a Class standard. And custom drivers should be viewed with suspicion. (Like Chinese webcam drivers that no CD comes in the box and you're forced to scavenge some virii-laden chinese web site to make your webcam work.) UVC webcams use Class drivers, whereas the older camera controllers, use custom drivers (and a CD should come in the box for those, a CD you should still *scan* with your AV). ******* There is a Driver Verifier. https://www.techrepublic.com/article...ifier-manager/ You'll need a *much* better article than that. The Verifier can do weird stuff, such as cause a problem to "go away" when the tougher enforcement requirements or stress are present. It's pretty hard to study a problem, if the tool used, changes the nature of the problem. Since Verifier can be invasive, the results should be treated with skepticism. And a proper article on Verifier, will tell you how to use it. https://en.wikipedia.org/wiki/Driver_Verifier https://www.reviversoft.com/blog/201...reen-of-death/ "following your adviced on driver verifier caused my windows 10 computer to go into a loop of death (previously just crashed a fee times a day, now never starts)" "the same happened to me, i had to make system restore to be able to start the windows" But at least it's a hobby. Now, if you didn't install drivers, I haven't a clue why it's behaving like that. Paul |
#3
|
|||
|
|||
BSOD?
Paul wrote:
Mr Pounder Esquire wrote: A mate came round about a week ago, he said that his card reader would not work on W7 but would work on XP......... yes, okay. He had this very large 20 year old Kodak card reader, it did not work on my XP and he then remembered that he may need the CD. Then, the Windows firewall on my aging computer turned off. I of course turned it back on again, weird. Then a few days later I lost Internet and got the BSOD, panicked and turned off on the button, all okay until the next day when it happened again. I did a system restore to before he arrived with his card reader and all has been fine for the past few days. Updates have been turned off for ages, I got fed up of being nagged. Can anybody see any connection to the BSOD and his very old card reader? When you install a driver, just about anything can happen. Ahh. Let's say for example, I wrote you a driver. Well, of course it's going to suck. Writing drivers is hard, because only a subset of program constructs are allowed down there. At work, we used to send people on a three month course, to learn how to do that (seasoned programmers, not idiots). Kodak doesn't make much of anything, and is just a brand name, so we can blame whatever company name is stamped on that USB chip inside the reader :-) He said it was Kodak and was 20 years old. Biggest USB thing I'd ever seen. USB uses "custom" drivers, for any item which does not follow a Class standard. And custom drivers should be viewed with suspicion. (Like Chinese webcam drivers that no CD comes in the box and you're forced to scavenge some virii-laden chinese web site to make your webcam work.) UVC webcams use Class drivers, whereas the older camera controllers, use custom drivers (and a CD should come in the box for those, a CD you should still *scan* with your AV). ******* There is a Driver Verifier. https://www.techrepublic.com/article...ifier-manager/ You'll need a *much* better article than that. The Verifier can do weird stuff, such as cause a problem to "go away" when the tougher enforcement requirements or stress are present. It's pretty hard to study a problem, if the tool used, changes the nature of the problem. Since Verifier can be invasive, the results should be treated with skepticism. And a proper article on Verifier, will tell you how to use it. https://en.wikipedia.org/wiki/Driver_Verifier https://www.reviversoft.com/blog/201...reen-of-death/ "following your adviced on driver verifier caused my windows 10 computer to go into a loop of death (previously just crashed a fee times a day, now never starts)" "the same happened to me, i had to make system restore to be able to start the windows" But at least it's a hobby. Now, if you didn't install drivers, I haven't a clue why it's behaving like that. Paul Nothing installed here. Thanks and respects for your input. |
Thread Tools | |
Display Modes | |
|
|