BSOD New Computer

[billp]

Hi,
Would appreciate your help with this few day old computer that is suffering BSOD few times.
Computer seems to work well except when I leave it alone for awhile I return to find the BSOD.

File attached

Thank you kindly.

 

[yowanvista]

BSOD may be cause by Sensorview from STV Software - Home, remove this software

sensorsview32_64.sys        fffff880`02f7c000    fffff880`02f83000    0x00007000    0x488b26c1    26/07/2008 17:29:37

*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

KERNEL_DATA_INPAGE_ERROR (7a)
The requested page of kernel data could not be read in.  Typically caused by
a bad block in the paging file or disk controller error. Also see
KERNEL_STACK_INPAGE_ERROR.
If the error status is 0xC000000E, 0xC000009C, 0xC000009D or 0xC0000185,
it means the disk subsystem has experienced a failure.
If the error status is 0xC000009A, then it means the request failed because
a filesystem failed to make forward progress.
Arguments:
Arg1: 0000000000000020, lock type that was held (value 1,2,3, or PTE address)
Arg2: ffffffffc000009d, error status (normally i/o status code)
Arg3: fffffa800f79f7c8, current process (virtual address for lock type 3, or PTE)
Arg4: 0000000000000000, virtual address that could not be in-paged (or PTE contents if arg1 is a PTE address)

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


ERROR_CODE: (NTSTATUS) 0xc000009d - STATUS_DEVICE_NOT_CONNECTED

DISK_HARDWARE_ERROR: There was error with disk hardware

BUGCHECK_STR:  0x7a_c000009d

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

PROCESS_NAME:  System

CURRENT_IRQL:  1

LAST_CONTROL_TRANSFER:  from fffff80002d03bec to fffff80002ccbf00

STACK_TEXT:  
fffff880`035087e8 fffff800`02d03bec : 00000000`0000007a 00000000`00000020 ffffffff`c000009d fffffa80`0f79f7c8 : nt!KeBugCheckEx
fffff880`035087f0 fffff800`02cb5e67 : fffffa80`0f79f760 00000000`c000009d 00000000`00000000 fffffa80`0f79f7f8 : nt! ?? ::FNODOBFM::`string'+0x4c830
fffff880`035088b0 fffff800`02ca892f : fffffa80`0d088680 fffffa80`0d0886d0 00000000`00000010 00000000`00000246 : nt!IopCompletePageWrite+0x57
fffff880`035088e0 fffff800`02cd325d : fffffa80`0d088680 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiDeliverApc+0x1d7
fffff880`03508960 fffff800`02ccf54b : 00000000`60000001 00000000`00000103 fffffa80`00000000 fffff880`01a97e91 : nt!KiCommitThreadWait+0x3dd
fffff880`035089f0 fffff800`02c64a8f : fffffa80`00000002 fffff880`03508ce0 00000000`00000001 fffffa80`00000013 : nt!KeWaitForMultipleObjects+0x271
fffff880`03508ca0 fffff800`02f6f166 : fffffa80`0d088680 00040a0c`00040a0c 00000000`00000080 00000000`00000001 : nt!MiModifiedPageWriter+0xcf
fffff880`03508d00 fffff800`02caa486 : fffff880`03164180 fffffa80`0d088680 fffff880`0316efc0 00060c10`00060c10 : nt!PspSystemThreadStartup+0x5a
fffff880`03508d40 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxStartSystemThread+0x16


STACK_COMMAND:  kb

FOLLOWUP_IP: 
nt! ?? ::FNODOBFM::`string'+4c830
fffff800`02d03bec cc              int     3

SYMBOL_STACK_INDEX:  1

SYMBOL_NAME:  nt! ?? ::FNODOBFM::`string'+4c830

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nt

IMAGE_NAME:  ntkrnlmp.exe

DEBUG_FLR_IMAGE_TIMESTAMP:  4a5bc600

FAILURE_BUCKET_ID:  X64_0x7a_c000009d_nt!_??_::FNODOBFM::_string_+4c830

BUCKET_ID:  X64_0x7a_c000009d_nt!_??_::FNODOBFM::_string_+4c830

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

 

[billp]

Thanks for the quick reply.

Out of curiousity can you walk me through how you came up with Sensorsview as possibly the problem?

Thanks again!

 

[Maguscreed]

bugcheck string and arg3 I would guess.

Bugchecks almost always point to a core windows file that was crashed, the trick is backing it to what actually crashed it though so the straight forward looking data that
IMAGE_NAME: ntkrnlmp.exe

actually crashed is pretty much useless.

 

[yowanvista]

Thanks for the quick reply.

Out of curiousity can you walk me through how you came up with Sensorsview as possibly the problem?

Thanks again!

It uses an old driver which can cause BSODs

 

[billp]

Thanks again. I appreciate it.