BSOD's

[yellowpc]

2 mouses share same drivers

As long as the mouse is installed, it will find the driver and load it. Disable that mouse in Device Manager. Then navigate to c:\windows\system32\drivers and see if the driver is still there. If it is, rename it from XXXX.sys to XXXX.bak. That way you can always activate it again easily..

Just when I was about to rename them, I found that both mouses seem to share the same drivers except the working one has 2 more listed. see attached.

anything else i should do?

 

[CarlTR6]

Reventon suggested that it is OK and he has it running on his system; so I think you can safely ignore that one.

 

[yellowpc]

modem drivers

I think it pertains to dialup modems. I suggest if you don't have a dialup modem, don't worry about it. I suspect that is why it is disabled; Win 7 did not find a dialup modem on your system.

so i went to gateway site to see all the drivers listed for modem and i installed the following 2:

Pro-Nets Modem 56K MDM USB_x64
LITE-ON Modem 56K MDM ATX(PCI-E x1)_x64

both didn't make the warning disappear. alternatively to installing using their setup file i tried updating from device manager and look for the above folders but didn't work as well.

i'll go through gateway site to see what else i haven't installed and report back

 

[CarlTR6]

Very good. Have you tried to let Device Manager find drivers for your PCI Simple Communications?

 

[yellowpc]

PCI drivers found!

hey carlTR6!

yes did that 'let it find' option probably when i first noticed it but of no use. however - good news: just when i religiously trying to download all that gateway offered, i found it!

it is this (tho i've no clue what it is):
Intel iAMT Generic Driver_x64

so device manager has no error now. i'm not sure if this resolves the blue screen problem though. and since it is so sporadic i may have to wait...

on the other hand, for the amd driver i saw some other amd stuff (attached) which i think i don't have any amd compnent at all (after decided to not use the vid card). is 'bak'-ing them a good idea?

 

[CarlTR6]

yes did that 'let it find' option probably when i first noticed it but of no use. however - good news: just when i religiously trying to download all that gateway offered, i found it!

it is this (tho i've no clue what it is):
Intel iAMT Generic Driver_x64

Kudos! Great detective work and good persistence.

so device manager has no error now. i'm not sure if this resolves the blue screen problem though. and since it is so sporadic i may have to wait...

on the other hand, for the amd driver i saw some other amd stuff (attached) which i think i don't have any amd compnent at all (after decided to not use the vid card). is 'bak'-ing them a good idea?

If you are sure have no AMD components on your system you can do that. However, I researched this a bit and I don't think it is necessary. Read through the posts in the link below. The remaining AMD drivers are all current drivers and should not be causing problems. I think I would leave them alone. They are on my computer also.

It looks like your updating drivers updated the amdxdata driver, too. You can probably safely rename it to .sys or leave it like it is. Your choice.

amdide.sys - Sistema IDE AMD system driver file. It seems to be one of the standard Windows drivers that are included in the System32 file. Rather than differentiate between Intel, or AMD, Microsoft puts in all relevant files for use by any processor. If you are running AMD, you will need. If you are running Intel, it is not required. - what is amdide.sys - Norton Community

amdk8.sys - The process AMD Processor Driver belongs to the software AMD Processor Driver or AMD Athlon64 Processor Driver by Advanced Micro Devices.

amdppm.sys - AMD Processor driver.

 

[yellowpc]

more on amdxdata driver

It looks like your updating drivers updated the amdxdata driver, too.

out of curiorsity - what made you say that? i can only guess by looking at the 7/13/2009 date but it is 2009.

so let's see if i run into any bluescreen again and hope you'll still get to provide inputs if so.

i appreciate your help!! and thx for the kudos. kudos to you too!

 

[CarlTR6]

Yes, you nailed it. July 13th 2009 (July 14th in Australia) is the magic date. That is the date drivers were updated for Win 7. Anything prior to that date is old. However there are a few drivers that were not updated and did not need to be updated. One of these is dated 2006 and works fine.