SN78SH7 woes

[kadil]

Hi,

I have the sn78sh7 and have had problems since I bought the system, mainly with video. Watching HD video tends to make it BSOD. I was running linux and bought a copy of W7 (since linux) is not supported and it crashes just the same in windows. I have windows dmp files but don't know what to do with them. I can get it to fail normally by watching a HD video (off vimeo) and after a while BSOD.

I tried different RAM options, all the experimenting and paying for an OS I don't need and memory options is getting very expensive.


Please help.

[kadil]

And where can I get XPCTools. Looks like shuttle did a takedown

[kadil]

here is the debugchk.exe output :


0: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

KMODE_EXCEPTION_NOT_HANDLED (1e)
This is a very common bugcheck.  Usually the exception address pinpoints
the driver/function that caused the problem.  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: fffff88002c1b36a, The address that the exception occurred at
Arg3: 0000000000000001, Parameter 0 of the exception
Arg4: 0000000000000000, Parameter 1 of the exception

Debugging Details:
------------------

***** Kernel symbols are WRONG. Please fix symbols to do analysis.

*************************************************************************
***                                                                   ***
***                                                                   ***
***    Your debugger is not using the correct symbols                 ***
***                                                                   ***
***    In order for this command to work properly, your symbol path   ***
***    must point to .pdb files that have full type information.      ***
***                                                                   ***
***    Certain .pdb files (such as the public OS symbols) do not      ***
***    contain the required information.  Contact the group that      ***
***    provided you with these symbols if you need this command to    ***
***    work.                                                          ***
***                                                                   ***
***    Type referenced: nt!_KPRCB                                     ***
***                                                                   ***
*************************************************************************
*************************************************************************
***                                                                   ***
***                                                                   ***
***    Your debugger is not using the correct symbols                 ***
***                                                                   ***
***    In order for this command to work properly, your symbol path   ***
***    must point to .pdb files that have full type information.      ***
***                                                                   ***
***    Certain .pdb files (such as the public OS symbols) do not      ***
***    contain the required information.  Contact the group that      ***
***    provided you with these symbols if you need this command to    ***
***    work.                                                          ***
***                                                                   ***
***    Type referenced: nt!_KPRCB                                     ***
***                                                                   ***
*************************************************************************
*************************************************************************
***                                                                   ***
***                                                                   ***
***    Your debugger is not using the correct symbols                 ***
***                                                                   ***
***    In order for this command to work properly, your symbol path   ***
***    must point to .pdb files that have full type information.      ***
***                                                                   ***
***    Certain .pdb files (such as the public OS symbols) do not      ***
***    contain the required information.  Contact the group that      ***
***    provided you with these symbols if you need this command to    ***
***    work.                                                          ***
***                                                                   ***
***    Type referenced: nt!_KPRCB                                     ***
***                                                                   ***
*************************************************************************

ADDITIONAL_DEBUG_TEXT: 
Use '!findthebuild' command to search for the target build information.
If the build information is available, run '!findthebuild -s ; .reload' to set symbol path and load symbols.

MODULE_NAME: dxgkrnl

FAULTING_MODULE: fffff80002a0c000 nt

DEBUG_FLR_IMAGE_TIMESTAMP:  4ce799fa

EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.

FAULTING_IP:
dxgkrnl+436a
fffff880`02c1b36a 0000            add     byte ptr [rax],al

EXCEPTION_PARAMETER1:  0000000000000001

EXCEPTION_PARAMETER2:  0000000000000000

WRITE_ADDRESS: unable to get nt!MmSpecialPoolStart
unable to get nt!MmSpecialPoolEnd
unable to get nt!MmPoolCodeStart
unable to get nt!MmPoolCodeEnd
 0000000000000000

ERROR_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.

BUGCHECK_STR:  0x1E_c0000005

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

CURRENT_IRQL:  0

LAST_CONTROL_TRANSFER:  from fffff80002ad4588 to fffff80002a88c40

STACK_TEXT: 
fffff880`0ac0c088 fffff800`02ad4588 : 00000000`0000001e ffffffff`c0000005 fffff880`02c1b36a 00000000`00000001 : nt+0x7cc40
fffff880`0ac0c090 00000000`0000001e : ffffffff`c0000005 fffff880`02c1b36a 00000000`00000001 00000000`00000000 : nt+0xc8588
fffff880`0ac0c098 ffffffff`c0000005 : fffff880`02c1b36a 00000000`00000001 00000000`00000000 fffffa80`03efbd01 : 0x1e
fffff880`0ac0c0a0 fffff880`02c1b36a : 00000000`00000001 00000000`00000000 fffffa80`03efbd01 fffffa80`03efbdf8 : 0xffffffff`c0000005
fffff880`0ac0c0a8 00000000`00000001 : 00000000`00000000 fffffa80`03efbd01 fffffa80`03efbdf8 fffff880`02d1b11b : dxgkrnl+0x436a
fffff880`0ac0c0b0 00000000`00000000 : fffffa80`03efbd01 fffffa80`03efbdf8 fffff880`02d1b11b fffffa80`04860010 : 0x1


STACK_COMMAND:  kb

FOLLOWUP_IP:
dxgkrnl+436a
fffff880`02c1b36a 0000            add     byte ptr [rax],al

SYMBOL_STACK_INDEX:  4

SYMBOL_NAME:  dxgkrnl+436a

FOLLOWUP_NAME:  MachineOwner

IMAGE_NAME:  dxgkrnl.sys

BUCKET_ID:  WRONG_SYMBOLS

Followup: MachineOwner
---------