BSOD's Again on My Sony Vaio - Windows 7 x64

A

Amcgrap

Well-known member
Joined
Jun 21, 2012
Posts
95
Hello all,

Since 2012 your site and experts have been very impressive in helping me solve BSOD problems with my Sony Vaio VPCSA43FX. It has excellent features but has always had a seemingly overheating problem (Sony never acknowledged fully) and you can tell by the high volume emitted by the fan. In the past there were several excellent solutions which you offered and which worked for a period of time.

What can I sen to you to see what the problems have been. From mid-December 2014 until 2 days ago I did not have a problem, but the last two days I've had BSOD's. It has happened on and off for 4 months. It almost always was when returning from or trying to go to sleep mode, but yesterday for the first time, it happened while I was typing away on the unit. I believe it could have been caused by my video driver but I am not sure, as I can't read my .dmp files.

I have all sorts of utilities that may help define the problem(s) and also have yours which we used previously to define the potential problems.

Thanks, as always, in advance.
 
Am doing as instructed. Waiting for reports to be generated and will upload as soon as ready. I am very impressed with information assessing system that you have developed. It is quite different than the last time I contacted you.
 
Time has flown by since, we're still developing it; we plan to bring a new one out soon.
 
All testing is done but I cannot find the ZIP file in the indicated directory. Should I zip all the files myself and send to you?
 
Strange.. Yes, just upload the dump files here in a .zip folder. We'll go from there.
 
Thanks for the kind words regarding the app.

Amcgrap said:
Found the file in "My Documents" and not in the Sysnative Directory.
Click to expand...

Correct, that is the intended output location. The collection app generates the SysnativeFileCollection folder in %userprofile%\Documents and then zips up the folder after confirmed completion.
 
Code: 
2: kd> .bugcheck
Bugcheck code 1000007E
Arguments ffffffff`c0000005 fffff880`018bad10 fffff880`03395458 fffff880`03394cb0

[COLOR="#800080"]//System thread exception, referenced memory which wasn't allowed to be addressed[/COLOR]

2: kd> kn
 # Child-SP          RetAddr           Call Site
00 fffff880`03395690 fffff880`018bb241 ndis!ndisOidRequestComplete+0x390 [COLOR="#800080"]//Here we have the faulting instruction, bad Oid[/COLOR]
01 fffff880`03395720 fffff880`0453e078 ndis!NdisFOidRequestComplete+0x91
02 fffff880`033957a0 fffff880`018babc4 pacer!PcFilterRequestComplete+0x68
03 fffff880`033957d0 fffff880`01905ffe ndis!ndisOidRequestComplete+0x244
04 fffff880`03395860 fffff880`0190627e ndis!ndisMOidRequestCompleteInternal+0xde [COLOR="#800080"]//Oid requests, usually to view adapter parameters[/COLOR]
05 fffff880`033958e0 fffff880`01952579 ndis!ndisCompleteLegacyRequest+0x10e
06 fffff880`03395940 fffff880`055d8dd7 ndis!NdisMSetInformationComplete+0xa9 [COLOR="#800080"]//Ndis functions, looks like a completion confirmation[/COLOR]
07 fffff880`03395980 fffffa80`0608a888 SBFWIM+0x8dd7 [COLOR="#800080"]//Sunbelt filewall[/COLOR]
08 fffff880`03395988 00000000`c0000001 0xfffffa80`0608a888 [COLOR="#800080"]//Context not saved, cannot identify the function[/COLOR]
09 fffff880`03395990 fffffa80`0da31590 0xc0000001
0a fffff880`03395998 fffffa80`0608a888 0xfffffa80`0da31590 [COLOR="#800080"]//Context not saved, cannot identify the function[/COLOR]
0b fffff880`033959a0 00000000`00000000 0xfffffa80`0608a888 [COLOR="#800080"]//Context not saved, cannot identify the function[/COLOR]

2: kd> lmvm sbfwim
start             end                 module name
fffff880`055d0000 fffff880`055f1000   SBFWIM   T (no symbols)           
    Loaded symbol image file: SBFWIM.sys
    Image path: \SystemRoot\system32\DRIVERS\SBFWIM.sys
    Image name: SBFWIM.sys
    Timestamp:        Thu Sep 22 10:11:58 2011 (4E7AFBDE) [COLOR="#800080"]//Out of date[/COLOR]
    CheckSum:         0002C485
    ImageSize:        00021000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4

Code: 
0: kd> .bugcheck
Bugcheck code 00000116
Arguments fffffa80`0fa3a010 fffff880`04b64a2c 00000000`00000000 00000000`00000002

0: kd> kn
 # Child-SP          RetAddr           Call Site
00 fffff880`029bd758 fffff880`044aa134 nt!KeBugCheckEx [COLOR="#800080"]//Failed to respond, bugcheck[/COLOR]
01 fffff880`029bd760 fffff880`044a9e3e dxgkrnl!TdrBugcheckOnTimeout+0xec [COLOR="#800080"]//If TDR fails, doesn't respond within the allocated time interval, bugcheck[/COLOR]
02 fffff880`029bd7a0 fffff880`04551f13 dxgkrnl!TdrIsRecoveryRequired+0x1a2 [COLOR="#800080"]//TDR recovery is required[/COLOR]
03 fffff880`029bd7d0 fffff880`0457fed6 dxgmms1!VidSchiReportHwHang+0x40b [COLOR="#800080"]//Report display driver/graphics card hang[/COLOR]
04 fffff880`029bd8b0 fffff880`0457b82b dxgmms1!VidSchWaitForCompletionEvent+0x196 [COLOR="#800080"]//Wait for completion event, wait state[/COLOR]
05 fffff880`029bd8f0 fffff880`0457a19f dxgmms1!VidSchiWaitForEmptyHwQueue+0x8f [COLOR="#800080"]//Empty Hw queue?[/COLOR]
06 fffff880`029bd9e0 fffff880`0457a47a dxgmms1!VidSchiHandleControlEvent+0x3b [COLOR="#800080"]//Handle the event[/COLOR]
07 fffff880`029bda10 fffff880`0454d2d2 dxgmms1!VidSchiWaitForSchedulerEvents+0x23e [COLOR="#800080"]//Wait for the events[/COLOR]
08 fffff880`029bdab0 fffff880`04579ff6 dxgmms1!VidSchiScheduleCommandToRun+0x1da [COLOR="#800080"]//Schedule to instruction to execute[/COLOR]
09 fffff880`029bdbc0 fffff800`0395f73a dxgmms1!VidSchiWorkerThread+0xba [COLOR="#800080"]//Schedule worker thread[/COLOR]
0a fffff880`029bdc00 fffff800`036b48e6 nt!PspSystemThreadStartup+0x5a
0b fffff880`029bdc40 00000000`00000000 nt!KxStartSystemThread+0x16 [COLOR="#800080"]//Start system thread[/COLOR]

atikmpag+7a2c
fffff880`04b64a2c 4883ec28        sub     rsp,28h [COLOR="#800080"]//Faulting instruction, either caused the driver unresponsiveness or happened to be the instruction at the time, most likely the former.[/COLOR]

0: kd> lmvm atikmpag
start             end                 module name
fffff880`04b5d000 fffff880`04bae000   atikmpag T (no symbols)           
    Loaded symbol image file: atikmpag.sys
    Image path: \SystemRoot\system32\DRIVERS\atikmpag.sys
    Image name: atikmpag.sys
    Timestamp:        Thu Dec 22 06:12:38 2011 (4EF2CA56) [COLOR="#800080"]//Out of date[/COLOR]
    CheckSum:         0004BAE7
    ImageSize:        00051000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4

I suggest you start off by updating your AMD display drver, and removing Sunbelt software.
Lets go from there.
 
Thanks for the response. I was unaware that I had any Sunbelt software existing in the system as two years ago I stopped using and uninstalled VIPRE from Sunbelt. As to the AMD driver, I will attempt to find the newest driver through the SONY site, as I've had problems previously with new drivers directly from the developers that were not compatible with my system.

Thanks again and I will do the above in a while as I will be away from the system for approx. 1 hour.
 
Evidently, I have the latest update of the AMD driver. I also can't find any evidence of Sunbelt software except for the different versions I downloaded, but they are executable files and not installed. From what you have seen in the files I sent today, do you see any other possibilities of what could be causing the BSOD's?

I would like not to think it is simply a hardware problem (overheating), as it would probably require getting into another notebook. Vaio products are very expensive to repair and I can't afford to be without a system for x weeks / months.

Some of the BSOD messages about the failures are the same but some have not been. From your experience, and what you see in the files, could the overheating possibly trigger different drivers to fail and cause BSOD's?

Thanks.
 
I am running a couple of utilities to see if the SBFWIM.sys (Sunbelt Firewall) is running. I am having a hard time locating it. Please see my previous message and advise.

Thanks, as always.
 

Has Sysnative Forums helped you? Please consider donating to help us support the site!

Back
Top