Question windows system exception error [solved]

[gorobei]

im trying to get an old system i havent touched in a few years running and got this error.

the minidump

Windows Server 2008/Windows Vista Kernel Version 6002 (Service Pack 2) MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 6002.18005.amd64fre.lh_sp2rtm.090410-1830
Machine Name:
Kernel base = 0xfffff800`01c0f000 PsLoadedModuleList = 0xfffff800`01dd3dd0
Debug session time: Fri Jan 4 03:11:56.046 2019 (UTC - 5:00)
System Uptime: 0 days 0:00:27.968
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

SYSTEM_SERVICE_EXCEPTION (3b)
An exception happened while executing a system service routine.
Arguments:
Arg1: 00000000c0000005, Exception code that caused the bugcheck
Arg2: fffffa6002592c36, Address of the instruction which caused the bugcheck
Arg3: fffffa600671ee60, Address of the context record for the exception that caused the bugcheck
Arg4: 0000000000000000, zero.

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

TRIAGER: Could not open triage file : e:\dump_analysis\program\triage\modclass.ini, error 2

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

FAULTING_IP:
ks!KspPinPropertyHandler+17a
fffffa60`02592c36 448b0a mov r9d,dword ptr [rdx]

CONTEXT: fffffa600671ee60 -- (.cxr 0xfffffa600671ee60)
rax=fffffa80067d9758 rbx=0000000000000000 rcx=0000000000000000
rdx=6ac96e8300000002 rsi=fffffa80067d9520 rdi=0000000000000008
rip=fffffa6002592c36 rsp=fffffa600671f6c0 rbp=0000000000000001
r8=0000000000000001 r9=0000000000000002 r10=fffff880008ab590
r11=00000000fffffff8 r12=0000000000000008 r13=fffff880008ab590
r14=00000000ffffffff r15=0000000000000001
iopl=0 nv up ei pl nz na pe nc
cs=0010 ss=0018 ds=002b es=002b fs=0053 gs=002b efl=00010202
ks!KspPinPropertyHandler+0x17a:
fffffa60`02592c36 448b0a mov r9d,dword ptr [rdx] ds:002b:6ac96e83`00000002=????????
Resetting default scope

CUSTOMER_CRASH_COUNT: 2

DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT

BUGCHECK_STR: 0x3B

PROCESS_NAME: svchost.exe

CURRENT_IRQL: 0

LAST_CONTROL_TRANSFER: from fffffa600259904b to fffffa6002592c36

STACK_TEXT:
fffffa60`0671f6c0 fffffa60`0259904b : fffffa80`067d9520 fffffa80`06b31f20 fffffa80`067d9520 fffff880`00878010 : ks!KspPinPropertyHandler+0x17a
fffffa60`0671f710 fffffa60`0349ff3e : fffffa80`06b31f20 fffffa80`067d9758 00000000`00000000 fffff880`008950f0 : ks!KsPinPropertyHandler+0x1b
fffffa60`0671f750 fffffa60`025902ab : fffffa80`067d9520 fffffa80`063bc7a0 00000000`00000000 00000000`00000003 : portcls!PcPinPropertyHandler+0x152
fffffa60`0671f790 fffffa60`025995cb : 00000000`00000000 fffff800`00000003 fffffa60`0671f8a0 fffff880`00878240 : ks!KspPropertyHandler+0x6cb
fffffa60`0671f7f0 fffffa60`034a0904 : fffffa60`0671f8a0 fffff880`00878240 fffffa80`067d9520 00000000`00000001 : ks!KsPropertyHandler+0x1b
fffffa60`0671f840 fffffa60`034b3688 : 00000000`00000001 fffffa80`067d9520 fffffa80`063bc8f0 fffffa60`034840cb : portcls!PcHandlePropertyWithTable+0x64
fffffa60`0671f870 fffffa60`0349fb01 : fffffa80`067d9520 fffffa80`063bc7a0 fffffa80`063bc8f0 fffff800`01c954e2 : portcls!CPortFilterWaveRT:eviceIoControl+0x144
fffffa60`0671f8d0 fffffa60`025906d8 : 00000000`c000000d fffffa80`067d9758 fffffa80`063bc7a0 fffff880`06af7030 : portcls!DispatchDeviceIoControl+0x79
fffffa60`0671f900 fffffa60`0349f06c : 00000000`0139f490 11cf51ad`8c134960 0000c101`f8948a87 00000001`00000003 : ks!KsDispatchIrp+0xd8
fffffa60`0671f930 fffffa60`0347e765 : 00000000`00000001 fffffa80`067d97a0 fffffa60`0671fa20 fffffa60`034e1a87 : portcls!PcDispatchIrp+0x5c
fffffa60`0671f960 00000000`00000001 : fffffa80`067d97a0 fffffa60`0671fa20 fffffa60`034e1a87 fffffa80`067d9520 : AtihdLH6+0x1b765
fffffa60`0671f968 fffffa80`067d97a0 : fffffa60`0671fa20 fffffa60`034e1a87 fffffa80`067d9520 00000000`00000000 : 0x1
fffffa60`0671f970 fffffa60`0671fa20 : fffffa60`034e1a87 fffffa80`067d9520 00000000`00000000 00000000`00000001 : 0xfffffa80`067d97a0
fffffa60`0671f978 fffffa60`034e1a87 : fffffa80`067d9520 00000000`00000000 00000000`00000001 fffffa80`067d9520 : 0xfffffa60`0671fa20
fffffa60`0671f980 fffffa60`034e17dd : 00000000`00000001 fffffa80`067d9758 fffffa80`067d97a0 fffffa80`067d9520 : ksthunk!CKSThunkDevice:ispatchIoctl+0xcf
fffffa60`0671f9b0 fffff800`01ecbb1e : fffffa80`067d9700 fffffa60`0671fca0 00000000`00000000 fffffa80`06ad6930 : ksthunk!CKernelFilterDevice:ispatchIrp+0x11d
fffffa60`0671fa10 fffff800`01ed4586 : fffffa80`06a46040 00000000`00000000 00000000`00000000 00000000`00000000 : nt!IopXxxControlFile+0x5be
fffffa60`0671fb40 fffff800`01c68ef3 : fffff880`0673e620 fffffa80`06aaf530 00000000`00000220 fffff800`01ed3314 : nt!NtDeviceIoControlFile+0x56
fffffa60`0671fbb0 00000000`77436d8a : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
00000000`0139f488 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x77436d8a


FOLLOWUP_IP:
ks!KspPinPropertyHandler+17a
fffffa60`02592c36 448b0a mov r9d,dword ptr [rdx]

SYMBOL_STACK_INDEX: 0

SYMBOL_NAME: ks!KspPinPropertyHandler+17a

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: ks

IMAGE_NAME: ks.sys

DEBUG_FLR_IMAGE_TIMESTAMP: 49e02bbf

STACK_COMMAND: .cxr 0xfffffa600671ee60 ; kb

FAILURE_BUCKET_ID: X64_0x3B_ks!KspPinPropertyHandler+17a

BUCKET_ID: X64_0x3B_ks!KspPinPropertyHandler+17a

Followup: MachineOwner

can anyone help me fix this?

 

[gorobei]

is this a stick the cd in the pc and let it try to "repair system" or just reinstall?

the odd part is i havent changed anything on the system or even touched it in 6 years.

 

[Ketchup]

That's a driver error. Update your Intel drivers (both chip and graphics if you are using) and see if the problem goes away.

 

[gorobei]

hmm, i think any update may be too old for the intel support site to have for download. the p35 chipset is proving hard to find in the interface.

what is this part about? EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at "0x%08lx" referenced memory at "0x%08lx". The memory could not be "%s".

 

[Ketchup]

From what I have read/ understand about those, the driver is using up all the memory in the stack (meaning there in no room left in memory for the CPU to accept other functions), so the dump is telling you that there was not room for the next instruction to be loaded into memory.

As for the driver itself, how far do you get before the BSOD? Will the computer load properly in "safe mode with networking?"

 

[crashtech]

Seems possible there is some file corruption, before continuing I would run something like GSmartControl from a bootable Linux stick and make sure the HDD is okay.

Even if the drive checks out, there still could be some random corruption, a re-install might be the easiest way to fix the thing.

 

[gorobei]

Seems possible there is some file corruption, before continuing I would run something like GSmartControl from a bootable Linux stick and make sure the HDD is okay.

Even if the drive checks out, there still could be some random corruption, a re-install might be the easiest way to fix the thing.

yeah, i was thinking something similar. i may try a repair and if that doesnt work, then wiping the drive and reinstalling.

 

[gorobei]

stuck the install disk in and did an os repair, 1 item came up. seems to have fixed it.

sorry for the lack of response, car issue came up and took away most of my day. to answer, safemode worked and would allow me to get the debug dump. the failed boots were pretty early into the os load. it was a pretty clean hd/installation at the time so i was pretty sure it wasnt a software conflict, and no new hardware or hw changes. thanks for the responses though.

friken cosmic radiation corruptin muh hard disks, gid off a my lawn.

 

[crashtech]

Glad it ended well!