Recent Content by Thaychris

Hello my KH-Vids friends! I Have a BSOD problem with my computer and I have tried about everything I can to get rid of BSODs off of my computer but it all fails. My computer is an Dell XPS720 with an Intel Core 2 Extreme CPU Q6850 @ 3.00ghz, 4gb of RAM and is running Windows Vista Ultimate 32bit Service Pack 2 with an NVIDIA GeForce 8800 Ultra graphics card. I usually recieve a BSOD that is 0x0000000A at random, but after installing both service packs I recieve a new BSOD along with the other one at random times. Here are the details.


Microsoft ® Windows Debugger Version 6.11.0001.404 X86
Copyright © Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Windows\Minidump\Mini081309-02.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*c:\symbols*http://msdl.microsoft.com/download/symbols
Executable search path is:
Windows Server 2008/Windows Vista Kernel Version 6002 (Service Pack 2) MP (4 procs) Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 6002.18005.x86fre.lh_sp2rtm.090410-1830
Machine Name:
Kernel base = 0x8224b000 PsLoadedModuleList = 0x82362c70
Debug session time: Thu Aug 13 15:09:07.081 2009 (GMT-4)
System Uptime: 0 days 0:03:26.859
Loading Kernel Symbols
...............................................................
................................................................
...............................
Loading User Symbols
Loading unloaded module list
......
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 1000008E, {c0000005, 8247e5bb, b0375924, 0}

Probably caused by : ntkrpamp.exe ( nt!ObpWaitForMultipleObjects+120 )

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

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

KERNEL_MODE_EXCEPTION_NOT_HANDLED_M (1000008e)
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.
Some common problems are exception code 0x80000003. This means a hard
coded breakpoint or assertion was hit, but this system was booted
/NODEBUG. This is not supposed to happen as developers should never have
hardcoded breakpoints in retail code, but ...
If this happens, make sure a debugger gets connected, and the
system is booted /DEBUG. This will let us see why this breakpoint is
happening.
Arguments:
Arg1: c0000005, The exception code that was not handled
Arg2: 8247e5bb, The address that the exception occurred at
Arg3: b0375924, Trap Frame
Arg4: 00000000

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


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

FAULTING_IP:
nt!ObpWaitForMultipleObjects+120
8247e5bb 8b4110 mov eax,dword ptr [ecx+10h]

TRAP_FRAME: b0375924 -- (.trap 0xffffffffb0375924)
ErrCode = 00000000
eax=ffe0fffc ebx=85595d78 ecx=04b957b8 edx=852f33b8 esi=852f33b8 edi=ac3d3730
eip=8247e5bb esp=b0375998 ebp=b0375bfc iopl=0 nv up ei pl nz na po nc
cs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000 efl=00010202
nt!ObpWaitForMultipleObjects+0x120:
8247e5bb 8b4110 mov eax,dword ptr [ecx+10h] ds:0023:04b957c8=????????
Resetting default scope

CUSTOMER_CRASH_COUNT: 2

DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT

BUGCHECK_STR: 0x8E

PROCESS_NAME: firefox.exe

CURRENT_IRQL: 0

LAST_CONTROL_TRANSFER: from 8247e460 to 8247e5bb

STACK_TEXT:
b0375bfc 8247e460 00000004 00000001 00000001 nt!ObpWaitForMultipleObjects+0x120
b0375d48 82295c7a 00000004 0f63fc64 00000001 nt!NtWaitForMultipleObjects+0xcc
b0375d48 77b85e74 00000004 0f63fc64 00000001 nt!KiFastCallEntry+0x12a
WARNING: Frame IP not in any known module. Following frames may be wrong.
0f63fcac 00000000 00000000 00000000 00000000 0x77b85e74


STACK_COMMAND: kb

FOLLOWUP_IP:
nt!ObpWaitForMultipleObjects+120
8247e5bb 8b4110 mov eax,dword ptr [ecx+10h]

SYMBOL_STACK_INDEX: 0

SYMBOL_NAME: nt!ObpWaitForMultipleObjects+120

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: nt

IMAGE_NAME: ntkrpamp.exe

DEBUG_FLR_IMAGE_TIMESTAMP: 49e0199e

FAILURE_BUCKET_ID: 0x8E_nt!ObpWaitForMultipleObjects+120

BUCKET_ID: 0x8E_nt!ObpWaitForMultipleObjects+120

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


Microsoft ® Windows Debugger Version 6.11.0001.404 X86
Copyright © Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Windows\Minidump\Mini081309-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*c:\symbols*http://msdl.microsoft.com/download/symbols
Executable search path is:
Windows Server 2008/Windows Vista Kernel Version 6002 (Service Pack 2) MP (4 procs) Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 6002.18005.x86fre.lh_sp2rtm.090410-1830
Machine Name:
Kernel base = 0x82215000 PsLoadedModuleList = 0x8232cc70
Debug session time: Wed Aug 12 19:58:34.841 2009 (GMT-4)
System Uptime: 0 days 3:45:26.619
Loading Kernel Symbols
...............................................................
................................................................
...............................
Loading User Symbols
Loading unloaded module list
......
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck A, {5616b0c, 1b, 0, 822c0dd8}

Probably caused by : ntkrpamp.exe ( nt!KiInsertTimerTable+42 )

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

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

IRQL_NOT_LESS_OR_EQUAL (a)
An attempt was made to access a pageable (or completely invalid) address at an
interrupt request level (IRQL) that is too high. This is usually
caused by drivers using improper addresses.
If a kernel debugger is available get the stack backtrace.
Arguments:
Arg1: 05616b0c, memory referenced
Arg2: 0000001b, IRQL
Arg3: 00000000, bitfield :
bit 0 : value 0 = read operation, 1 = write operation
bit 3 : value 0 = not an execute operation, 1 = execute operation (only on chips which support this level of status)
Arg4: 822c0dd8, address which referenced memory

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


READ_ADDRESS: GetPointerFromAddress: unable to read from 8234c868
Unable to read MiSystemVaType memory at 8232c420
05616b0c

CURRENT_IRQL: 1b

FAULTING_IP:
nt!KiInsertTimerTable+42
822c0dd8 8b5ffc mov ebx,dword ptr [edi-4]

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT

BUGCHECK_STR: 0xA

PROCESS_NAME: mxtask.exe

TRAP_FRAME: a4adfc14 -- (.trap 0xffffffffa4adfc14)
ErrCode = 00000000
eax=82312c50 ebx=8230d920 ecx=89daa3f0 edx=7e7e8117 esi=82312c50 edi=05616b10
eip=822c0dd8 esp=a4adfc88 ebp=a4adfca8 iopl=0 ov up ei ng nz na pe cy
cs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000 efl=00010a87
nt!KiInsertTimerTable+0x42:
822c0dd8 8b5ffc mov ebx,dword ptr [edi-4] ds:0023:05616b0c=????????
Resetting default scope

LAST_CONTROL_TRANSFER: from 822c0dd8 to 82262fb9

STACK_TEXT:
a4adfc14 822c0dd8 badb0d00 7e7e8117 00000002 nt!KiTrap0E+0x2e1
a4adfca8 822be9e4 89daa3f0 0000010d 00000000 nt!KiInsertTimerTable+0x42
a4adfd08 8244895c 8230d801 00000000 a4adfd2c nt!KeDelayExecutionThread+0x448
a4adfd54 8225fc7a 00000000 031df984 031df9a8 nt!NtDelayExecution+0x8d
a4adfd54 77115e74 00000000 031df984 031df9a8 nt!KiFastCallEntry+0x12a
WARNING: Frame IP not in any known module. Following frames may be wrong.
031df9a8 00000000 00000000 00000000 00000000 0x77115e74


STACK_COMMAND: kb

FOLLOWUP_IP:
nt!KiInsertTimerTable+42
822c0dd8 8b5ffc mov ebx,dword ptr [edi-4]

SYMBOL_STACK_INDEX: 1

SYMBOL_NAME: nt!KiInsertTimerTable+42

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: nt

IMAGE_NAME: ntkrpamp.exe

DEBUG_FLR_IMAGE_TIMESTAMP: 49e0199e

FAILURE_BUCKET_ID: 0xA_nt!KiInsertTimerTable+42

BUCKET_ID: 0xA_nt!KiInsertTimerTable+42

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

Any help is much appreciated!

EDIT: Make it 3 BSODs

Microsoft (R) Windows Debugger Version 6.11.0001.404 X86
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Windows\Minidump\Mini081309-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*c:\symbols*http://msdl.microsoft.com/download/symbols
Executable search path is:
Windows Server 2008/Windows Vista Kernel Version 6002 (Service Pack 2) MP (4 procs) Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 6002.18005.x86fre.lh_sp2rtm.090410-1830
Machine Name:
Kernel base = 0x8224a000 PsLoadedModuleList = 0x82361c70
Debug session time: Thu Aug 13 17:58:14.618 2009 (GMT-4)
System Uptime: 0 days 0:31:36.771
Loading Kernel Symbols
...............................................................
................................................................
...............................
Loading User Symbols
Loading unloaded module list
......
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 1000007E, {c0000005, 8a937c92, 8b6a7c60, 8b6a795c}

Probably caused by : volsnap.sys ( volsnap!VspWriteVolumePhase35+12 )

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

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

SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M (1000007e)
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.
Some common problems are exception code 0x80000003. This means a hard
coded breakpoint or assertion was hit, but this system was booted
/NODEBUG. This is not supposed to happen as developers should never have
hardcoded breakpoints in retail code, but ...
If this happens, make sure a debugger gets connected, and the
system is booted /DEBUG. This will let us see why this breakpoint is
happening.
Arguments:
Arg1: c0000005, The exception code that was not handled
Arg2: 8a937c92, The address that the exception occurred at
Arg3: 8b6a7c60, Exception Record Address
Arg4: 8b6a795c, Context Record Address

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


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

FAULTING_IP:
volsnap!VspWriteVolumePhase35+12
8a937c92 8b4710 mov eax,dword ptr [edi+10h]

EXCEPTION_RECORD: 8b6a7c60 -- (.exr 0xffffffff8b6a7c60)
ExceptionAddress: 8a937c92 (volsnap!VspWriteVolumePhase35+0x00000012)
ExceptionCode: c0000005 (Access violation)
ExceptionFlags: 00000000
NumberParameters: 2
Parameter[0]: 00000000
Parameter[1]: 05668658
Attempt to read from address 05668658

CONTEXT: 8b6a795c -- (.cxr 0xffffffff8b6a795c)
eax=86bff340 ebx=85934008 ecx=ab340674 edx=00000000 esi=86bff340 edi=05668648
eip=8a937c92 esp=8b6a7d28 ebp=8b6a7d38 iopl=0 nv up ei pl zr na pe nc
cs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000 efl=00010246
volsnap!VspWriteVolumePhase35+0x12:
8a937c92 8b4710 mov eax,dword ptr [edi+10h] ds:0023:05668658=????????
Resetting default scope

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT

PROCESS_NAME: System

CURRENT_IRQL: 0

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

EXCEPTION_PARAMETER1: 00000000

EXCEPTION_PARAMETER2: 05668658

READ_ADDRESS: GetPointerFromAddress: unable to read from 82381868
Unable to read MiSystemVaType memory at 82361420
05668658

FOLLOWUP_IP:
volsnap!VspWriteVolumePhase35+12
8a937c92 8b4710 mov eax,dword ptr [edi+10h]

BUGCHECK_STR: 0x7E

LAST_CONTROL_TRANSFER: from 8a937f18 to 8a937c92

STACK_TEXT:
8b6a7d38 8a937f18 86bff340 00000000 8776155c volsnap!VspWriteVolumePhase35+0x12
8b6a7d50 8a937f4e 86813978 868d5cc4 8b6a7d7c volsnap!VspWriteTableUpdatesCompletionLoop+0x5c
8b6a7d60 8a9349bd 87761558 00000000 879a95c8 volsnap!VspWriteTableUpdatesCompletionWorker+0x20
8b6a7d7c 8241fc42 868d5d48 6665a2a9 00000000 volsnap!VspWorkerThread+0x83
8b6a7dc0 82288efe 8a93493a 868f40e0 00000000 nt!PspSystemThreadStartup+0x9d
00000000 00000000 00000000 00000000 00000000 nt!KiThreadStartup+0x16


SYMBOL_STACK_INDEX: 0

SYMBOL_NAME: volsnap!VspWriteVolumePhase35+12

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: volsnap

IMAGE_NAME: volsnap.sys

DEBUG_FLR_IMAGE_TIMESTAMP: 49e01f09

STACK_COMMAND: .cxr 0xffffffff8b6a795c ; kb

FAILURE_BUCKET_ID: 0x7E_volsnap!VspWriteVolumePhase35+12

BUCKET_ID: 0x7E_volsnap!VspWriteVolumePhase35+12

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

Hey folks. The first PS3 I ever obtained to use was from Japan (off of eBay, stupid me). I never used a voltage transformer (which I should have, so just in case you plan on getting one from there) which eventually damaged the motherboard. Now I sent Sony Japan an email about this and they did reply.

I've also contacted and shipped the console to a third party repair people but they said it had to be about $500 for a new motherboard.

So folks anyone got a solution? I'm not worried, to be honest if there isn't a sensible solution. I do have an American PS3 I did but (although its not the fancy backwards compatible kind). So just for the hell of it I decided to ask here.

Well I was playing around with SMCoder and KHIIFM+ using my PC and I can skate in the canyon, without that annoying Terra, for absolutely no reason whatsoever.