How do I check for outdated drivers in W7?

[bulletng]

I know you can use a minidump file to check for outdated drivers, but what if you don't have any dump files or anything recent? I want to know if there's a way to check all my drivers like you would in the dump file for outdated drivers? aka drivers that need to be updated and could possibly cause problems.
I've tried Google but all I see are using Windows Update or checking Device Manager which isn't very helpful.

As an example, from this thread I created a long time ago, this user gave me a list of outdated drivers:

ASACPI.sys    3/27/2005 10:30:36 PM    fffff880`0451c000    fffff880`04524000    0x00008000    0x42476c4c                            
secdrv.SYS    9/13/2006 09:18:38 AM    fffff880`078d6000    fffff880`078e1000    0x0000b000    0x4508052e                            
regi.sys    4/16/2007 11:19:10 AM    fffff880`06fd9000    fffff880`06fe1000    0x00008000    0x462393ee                            
RivaTuner64.sys    7/17/2007 03:13:42 PM    fffff880`07d9c000    fffff880`07da3000    0x00007000    0x469d14e6                            
000.fcl    9/26/2008 09:11:22 AM    fffff880`07937000    fffff880`07962000    0x0002b000    0x48dcdf7a                            
spldr.sys    5/11/2009 12:56:27 PM    fffff880`015e1000    fffff880`015e9000    0x00008000    0x4a0858bb                            
spsys.sys    5/11/2009 01:20:58 PM    fffff880`07c00000    fffff880`07c71000    0x00071000    0x4a085e7a                            
GEARAspiWDM.sys    5/18/2009 08:17:04 AM    fffff880`044c4000    fffff880`044d1000    0x0000d000    0x4a1151c0                            
amdxata.sys    5/19/2009 01:56:59 PM    fffff880`010f2000    fffff880`010fd000    0x0000b000    0x4a12f2eb                            
yk62x64.sys    5/20/2009 04:14:06 AM    fffff880`0443d000    fffff880`044a1000    0x00064000    0x4a13bbce                            
ADIHdAud.sys    5/21/2009 04:21:06 AM    fffff880`05b46000    fffff880`05bbf000    0x00079000    0x4a150ef2                            
LHidFilt.Sys    6/17/2009 12:49:39 PM    fffff880`06a9a000    fffff880`06aad000    0x00013000    0x4a391ea3                            
LMouFilt.Sys    6/17/2009 12:49:43 PM    fffff880`06aba000    fffff880`06ace000    0x00014000    0x4a391ea7                            
PxHlpa64.sys    6/23/2009 07:16:35 PM    fffff880`0115d000    fffff880`01168e00    0x0000be00    0x4a416253

I was never able to figure out how he did that, so I'm hoping one of you know. The reason I'm doing this is because I recently had to do a System Repair and I remember having driver issues (like in that thread) before. Currently my desktop icons that I have set to transparent are showing as black boxes.

 

[bulletng]

Well I was looking through some random CMD commands and found Driverquery... It appears to give me similar information, but I'm still curious how the user got that from what I gave him. There's got to be other ways of doing this.

Another nice thing to note for those who don't know about this command is you can type Driverquery > driver.txt to export it to a text file.

 

[whs]

There are some programs that can do that for you, but they can be a pain. I think this method is simpler: How to Check If My Drivers Are Up to Date | eHow.com

 

[bulletng]

Thanks but the only problem I see with using Device Manager is that you have to check every single device. My concern is that some drivers may be out of date but I don't know what they're associated with.

 

[whs]

You worry too much. I only update drivers when there are problems (like recently with my audio output). Else I go by the old saying :" If it ain't broke, don't fix it".

 

[bulletng]

You see the thing is I think something is broken. I have three desktop shortcuts that I like to set as blank (invisible) icons, but they're appearing black everytime I reboot. (After a recent System Repair) Then I switch them back and the black boxes return when I reboot. This happened to me several years back and it was just the calm before the storm if you know what I mean.

I do admit I worry too much, but I want to make sure I'm not missing anything critical. Those moments when you really don't want a BSOD but you get one. Not to mention this is something I'd like to learn how to do for future reference, not just for me, but my job as well!

 

[indianacarnie]

Probably was a 3rd party program/application and theres no way to know which one. My $.02s worth.