[font=lucida console]
hidusbf.sys Wed Feb 11 05:25:00 2009 (4992A77C) - SweetLow USB Mouse Rate Adjuster - http://sweetlow.at.tut.by/
[/font]
[font=lucida console]
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Debug session time: Sat Dec 18 20:04:58.224 2010 (GMT-5)
System Uptime: 0 days 0:12:50.660
Probably caused by : ntkrnlmp.exe ( nt!IoWithinStackLimits+60 )
DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
BUGCHECK_STR: 0x3B
PROCESS_NAME: steam.exe
Bugcheck code 0000003B
Arguments 00000000`c0000005 fffff800`030ec2b0 fffff880`07d02a30 00000000`00000000
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Debug session time: Thu Dec 16 17:14:46.466 2010 (GMT-5)
System Uptime: 0 days 0:00:12.544
Probably caused by : ntkrnlmp.exe ( nt!RtlDispatchException+122 )
DEFAULT_BUCKET_ID: VERIFIER_ENABLED_VISTA_MINIDUMP
BUGCHECK_STR: 0xA
PROCESS_NAME: System
Bugcheck code 0000000A
Arguments fffff800`033a4608 00000000`00000002 00000000`00000000 fffff800`030b37a2
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Debug session time: Wed Dec 15 20:43:00.451 2010 (GMT-5)
System Uptime: 0 days 0:30:48.887
Probably caused by : ntkrnlmp.exe ( nt!IoWithinStackLimits+60 )
DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
BUGCHECK_STR: 0x3B
PROCESS_NAME: steam.exe
Bugcheck code 0000003B
Arguments 00000000`c0000005 fffff800`030962b0 fffff880`06d69a30 00000000`00000000
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
by [color=navy]jcgriff2
J. C. Griffith, Microsoft MVP[/color]
[B]Link Removed - Invalid URL[/B]
[url=www.sysnative.com][color=#000033][u]www.sysnative.com[/u][/color][/url]
[url=www.jcgriff2.com][color=#000055][u]www.jcgriff2.com[/u][/color][/url]
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
[/font]
No need to bother with Memtest or Driver Verifier. I haven't posted references to either in a long time and don't rely on them whatsoever any longer.
Never once in history have I suggested to replace memory when it was not the issue.
Memory is surely 100% defective if Bs Recorder driver or hid driver (good find) is not the culprit.
(That 0xA....surely defective memory though.)
Never once in history have I suggested to replace memory when it was not the issue.
0xa = driver attempted to access pageable memory when IRQL too high or attempted to access bad memory
Only 1 BSOD was 0xa; there were two others = 0x3b (0xc0000005,,,)
Bugcheck 0xa does not mean RAM failure 100% of the time. If you state that 0xa is always RAM issue, then you must state that 0xd1 is always RAM as well as the two bugchecks are very similar in nature. Driver Verifier can be of help for 0xa, 0xd1, 0x3b, .... many others.
Much cheaper to run Driver Verifier and see if it flags a driver before spending $$$ to replace RAM.
There is no way whatsoever to determine from a mini kernel memory dump that RAM itself is the absolute cause of ANY BSOD.
There could be underlying other unknown hardware issues affecting RAMs ability to properly hold kernel code such as PSU, mobo, etc... not to mention driver issues as well.
Happy Holidays !
jcgriff2
`