{"id":468,"date":"2011-05-15T17:00:41","date_gmt":"2011-05-16T00:00:41","guid":{"rendered":"http:\/\/mattfife.net\/wordpress\/?p=468"},"modified":"2012-08-12T19:17:08","modified_gmt":"2012-08-13T02:17:08","slug":"windows-7-blue-screens-due-to-stdriver64sys","status":"publish","type":"post","link":"https:\/\/mattfife.com\/?p=468","title":{"rendered":"Windows 7 blue-screens due to stdriver64.sys"},"content":{"rendered":"<p>I recently started getting blue-screens with stdriver64.sys. In doing my blue-screen debug, very little useful information was given:<\/p>\n<p><code><br \/>\nSYSTEM_THREAD_EXCEPTION_NOT_HANDLED (7e)<br \/>\nThis is a very common bugcheck.\u00a0 Usually the exception address pinpoints<br \/>\nthe driver\/function that caused the problem.\u00a0 Always note this address<br \/>\nas well as the link date of the driver\/image that contains this address.<br \/>\nArguments:<br \/>\nArg1: ffffffffc0000005, The exception code that was not handled<br \/>\nArg2: fffff8800970bbe8, The address that the exception occurred at<br \/>\nArg3: fffff8800676d7f8, Exception Record Address<br \/>\nArg4: fffff8800676d050, Context Record Address<\/code><\/p>\n<p><code>Debugging Details:<br \/>\n------------------<\/code><\/p>\n<p><code>EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.<\/code><\/p>\n<p><code>FAULTING_IP:<br \/>\nstdriver64+1be8<br \/>\nfffff880`0970bbe8 49\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 dec\u00a0\u00a0\u00a0\u00a0 ecx<\/p>\n<p>EXCEPTION_RECORD:\u00a0 fffff8800676d7f8 -- (.exr 0xfffff8800676d7f8)<br \/>\nExceptionAddress: 0000000000000000<br \/>\nExceptionCode: c0000005 (Access violation)<br \/>\nExceptionFlags: 00000000<br \/>\nNumberParameters: 158383080<br \/>\nParameter[0]: fffffffffffff880<br \/>\nParameter[1]: 0000000000000002<br \/>\nParameter[2]: 0000000000000000<br \/>\nParameter[3]: 0000000000000000<br \/>\nParameter[4]: 0000000000000000<br \/>\nParameter[5]: 000000000022dba8<br \/>\nParameter[6]: 0000000000000000<br \/>\nParameter[7]: 0000000000000000<br \/>\nParameter[8]: 0000000000000000<br \/>\nParameter[9]: 0000000000000018<br \/>\nParameter[10]: 0000000000000000<br \/>\nParameter[11]: ffffffffffffffff<br \/>\nParameter[12]: 000000000000007f<br \/>\nParameter[13]: 0000000000000000<br \/>\nParameter[14]: 0000000000000000<br \/>\nAttempt to execute non-executable address 0000000000000002<\/p>\n<p>CONTEXT:\u00a0 fffff8800676d050 -- (.cxr 0xfffff8800676d050)<br \/>\nUnable to read context, NTSTATUS 0xC0000147<\/p>\n<p>DEFAULT_BUCKET_ID:\u00a0 VISTA_DRIVER_FAULT<\/p>\n<p>BUGCHECK_STR:\u00a0 0x7E<\/p>\n<p>CURRENT_IRQL:\u00a0 0<\/p>\n<p>LAST_CONTROL_TRANSFER:\u00a0 from 0000000000000000 to 0000000000000000<\/p>\n<p>STACK_TEXT:<br \/>\n00000000 00000000 00000000 00000000 00000000 0x0<\/p>\n<p>STACK_COMMAND:\u00a0 .bugcheck ; kb<\/p>\n<p>FOLLOWUP_IP:<br \/>\nstdriver64+1be8<br \/>\nfffff880`0970bbe8 49\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 dec\u00a0\u00a0\u00a0\u00a0 ecx<\/p>\n<p>SYMBOL_NAME:\u00a0 stdriver64+1be8<br \/>\nFOLLOWUP_NAME:\u00a0 MachineOwner<br \/>\nMODULE_NAME: Unknown_Module<br \/>\nIMAGE_NAME:\u00a0 Unknown_Image<br \/>\nDEBUG_FLR_IMAGE_TIMESTAMP:\u00a0 0<\/p>\n<p><\/code><code><\/code><code><\/code><code>BUCKET_ID:\u00a0 INVALID_KERNEL_CONTEXT<br \/>\n<\/code><\/p>\n<p>I dug around on my support forums, and exception 7E has been related to loads of different problems: bad logitech mice drivers, cardbus adapters, audio drivers, failed USB drivers when it happens on awake from hibernate, etc.\u00a0 Basically, any and all services seem to be known to cause it.\u00a0 Also, having the module and image names completely unknown wasn&#8217;t very hopeful either.\u00a0 I considered the idea of stepping into the memory location specificed until I found <a href=\"http:\/\/www.techsupportforum.com\/forums\/showpost.php?p=2770536\" target=\"_blank\">this write-up<\/a>.\u00a0 It mentions the program SoundTap as a very common source.\u00a0 I had recently got Soundtap as part of a kit including the excellent Switch sound converter.\u00a0 I uninstalled Sound Tap and sure enough &#8211; bluescreens went away.\u00a0 Soundtap installs an audio driver to divert playback so you can do raw rips of anything you play on your pc (think sound ripper for youtube\/shoutcast streams\/shockwave players\/etc).<\/p>\n<p>So, it&#8217;s always a good idea to keep track of what you&#8217;ve changed on your pc and suspect even the unlikely things such as a simple software install.\u00a0 That and googling for others with the same problems. \ud83d\ude42<\/p>\n","protected":false},"excerpt":{"rendered":"<p>I recently started getting blue-screens with stdriver64.sys. In doing my blue-screen debug, very little useful information was given: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED (7e) This is a very common bugcheck.\u00a0 Usually the exception address pinpoints the driver\/function that caused the problem.\u00a0 Always note this address as well as the link date of the driver\/image that contains this address. Arguments: Arg1: ffffffffc0000005, The exception code that was not handled Arg2: fffff8800970bbe8, The address that the exception occurred at Arg3: fffff8800676d7f8, Exception Record Address Arg4: fffff8800676d050,&#8230;<\/p>\n<p class=\"read-more\"><a class=\"btn btn-default\" href=\"https:\/\/mattfife.com\/?p=468\"> Read More<span class=\"screen-reader-text\">  Read More<\/span><\/a><\/p>\n","protected":false},"author":2,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"jetpack_post_was_ever_published":false,"_jetpack_newsletter_access":"","_jetpack_dont_email_post_to_subs":false,"_jetpack_newsletter_tier_id":0,"_jetpack_memberships_contains_paywalled_content":false,"_jetpack_memberships_contains_paid_content":false,"footnotes":"","jetpack_publicize_message":"","jetpack_publicize_feature_enabled":true,"jetpack_social_post_already_shared":false,"jetpack_social_options":{"image_generator_settings":{"template":"highway","default_image_id":0,"font":"","enabled":false},"version":2}},"categories":[6],"tags":[],"class_list":["post-468","post","type-post","status-publish","format-standard","hentry","category-technicalproblemsolutions"],"jetpack_publicize_connections":[],"jetpack_featured_media_url":"","jetpack_sharing_enabled":true,"jetpack_shortlink":"https:\/\/wp.me\/p4WECr-7y","jetpack-related-posts":[],"_links":{"self":[{"href":"https:\/\/mattfife.com\/index.php?rest_route=\/wp\/v2\/posts\/468","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/mattfife.com\/index.php?rest_route=\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/mattfife.com\/index.php?rest_route=\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/mattfife.com\/index.php?rest_route=\/wp\/v2\/users\/2"}],"replies":[{"embeddable":true,"href":"https:\/\/mattfife.com\/index.php?rest_route=%2Fwp%2Fv2%2Fcomments&post=468"}],"version-history":[{"count":1,"href":"https:\/\/mattfife.com\/index.php?rest_route=\/wp\/v2\/posts\/468\/revisions"}],"predecessor-version":[{"id":572,"href":"https:\/\/mattfife.com\/index.php?rest_route=\/wp\/v2\/posts\/468\/revisions\/572"}],"wp:attachment":[{"href":"https:\/\/mattfife.com\/index.php?rest_route=%2Fwp%2Fv2%2Fmedia&parent=468"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/mattfife.com\/index.php?rest_route=%2Fwp%2Fv2%2Fcategories&post=468"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/mattfife.com\/index.php?rest_route=%2Fwp%2Fv2%2Ftags&post=468"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}