Hi, My PC started having daily random BSOD, causing the computer to restart at least twice a day. I have uploaded my mini dump files from the last few crashes to Sky Drive. Ran memory test, and no issues found. I replaced my RAM several months ago, as I was having BSOD failures it the memory was suspected. This is new RAM, and the issues started to happen on a regular basis when installed the latest updates, including SP1 about 2/3 weeks ago. Any help would be much appreciated! OS - Windows 7 Ultimate 64bit PC - HP Pavilion RAM - 4gb http://cid-9f34d7c6a45c7c90.skydrive.live.com/redir.aspx?resid=9F34D7C6A45C7C90!108

Since you mention the issue start to occurs after you install the updates, in that case have you try uninstalling the recent update and see how it goes? Lastly if you could provide us the exact model of the HP Pavilion, that would helps

No, I haven't tried to restoring to an earlier state, but will give it a shot. My model number for the HP Pavilion is a6357c.Mohammd Shafaqat

Hi, From the first dump file, I notice Bug Check 0x3B: SYSTEM_SERVICE_EXCEPTION This indicates that an exception happened while executing a routine that transitions from non-privileged code to privileged code. From the second dump file, I notice Bug Check 0x24: NTFS_FILE_SYSTEM This indicates a problem occurred in ntfs.sys, the driver file that allows the system to read and write to NTFS drives. From the third and fourth dump files, I notice Bug Check 0x1E: KMODE_EXCEPTION_NOT_HANDLED This indicates that a kernel-mode program generated an exception which the error handler did not catch. I suggest referring to the following methods to testing the BSOD. 1. If you are running any gadgets, please disable them or uninstall them. 2. Regarding the NTFS drive issue, please run Chkdsk /f /r from an elevated command. 3. Go to update BIOS and drivers from manufacture's site. http://h10025.www1.hp.com/ewfrf/wc/softwareCategory?os=4063&lc=en&cc=us&dlc=en&sw_lang=&product=3658915#N152 Note: I cannot find any device driver with Windows 7 64-bit for your computer model. If the computer is not compatible with Windows 7 64-bit or its SP1, it could lead to hardware issue. You should confirm HP with this. 4. Also, go to Safe Mode and check if the issue persists. Best Regards, NikiPlease remember to click "Mark as Answer" on the post that helps you, and to click "Unmark as Answer" if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.

******************************************************************************* * * * 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: fffff96000177cf1, Address of the exception record for the exception that caused the bugcheck Arg3: fffff88008b28110, Address of the context record for the exception that caused the bugcheck Arg4: 0000000000000000, zero. Debugging Details: ------------------ EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at "0x%08lx" referenced memory at "0x%08lx". The memory could not be "%s". FAULTING_IP: win32k!FindTimer+59 fffff960`00177cf1 4c396b28 cmp qword ptr [rbx+28h],r13 CONTEXT: fffff88008b28110 -- (.cxr 0xfffff88008b28110) rax=0000000000005332 rbx=004c011f005233af rcx=fffff960003a10e0 rdx=0000000000005332 rsi=0000000000000000 rdi=0000000000000000 rip=fffff96000177cf1 rsp=fffff88008b28af0 rbp=004c011f0052341f r8=0000000000000000 r9=0000000000000000 r10=fffff900c1d3cc30 r11=fffff900c1d3cc30 r12=fffff960003a14d0 r13=fffff900c0618dc0 r14=0000000000000000 r15=0000000000000000 iopl=0 nv up ei pl nz na pe cy cs=0010 ss=0018 ds=002b es=002b fs=0053 gs=002b efl=00010203 win32k!FindTimer+0x59: fffff960`00177cf1 4c396b28 cmp qword ptr [rbx+28h],r13 ds:002b:004c011f`005233d7=???????????????? Resetting default scope CUSTOMER_CRASH_COUNT: 1 DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT BUGCHECK_STR: 0x3B PROCESS_NAME: sidebar.exe CURRENT_IRQL: 0 LAST_CONTROL_TRANSFER: from fffff96000177e32 to fffff96000177cf1 STACK_TEXT: fffff880`08b28af0 fffff960`00177e32 : fffff900`c0618dc0 00000000`00005332 00000000`00005332 00000000`0000492c : win32k!FindTimer+0x59 fffff880`08b28b40 fffff960`00143fa8 : fffff900`c0618dc0 00000000`00005332 00000000`0000492c 00000000`00000000 : win32k!InternalSetTimer+0x9a fffff880`08b28bb0 fffff960`00143f1e : 00000000`00000000 00000000`00000000 00000000`0000492c fffff800`02eea453 : win32k!SetTimer+0x5c fffff880`08b28bf0 fffff800`02e9d8d3 : fffffa80`03bc7b60 fffff880`08b28ca0 00000000`00000001 00000000`00000020 : win32k!NtUserSetTimer+0x7e fffff880`08b28c20 00000000`76c7693a : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13 00000000`032ce218 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x76c7693a FOLLOWUP_IP: win32k!FindTimer+59 fffff960`00177cf1 4c396b28 cmp qword ptr [rbx+28h],r13 SYMBOL_STACK_INDEX: 0 SYMBOL_NAME: win32k!FindTimer+59 FOLLOWUP_NAME: MachineOwner MODULE_NAME: win32k IMAGE_NAME: win32k.sys DEBUG_FLR_IMAGE_TIMESTAMP: 4d6f104c STACK_COMMAND: .cxr 0xfffff88008b28110 ; kb FAILURE_BUCKET_ID: X64_0x3B_win32k!FindTimer+59 BUCKET_ID: X64_0x3B_win32k!FindTimer+59 _________________________________________________________________________________________________________ Bug CHeck 0x3B: http://msdn.microsoft.com/en-us/library/ff558949(VS.85).aspx Update your graphic card driver. ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* NTFS_FILE_SYSTEM (24) If you see NtfsExceptionFilter on the stack then the 2nd and 3rd parameters are the exception record and context record. Do a .cxr on the 3rd parameter and then kb to obtain a more informative stack trace. Arguments: Arg1: 00000000001904fb Arg2: fffff8800bd9e1d8 Arg3: fffff8800bd9da30 Arg4: fffff880012352b5 Debugging Details: ------------------ EXCEPTION_RECORD: fffff8800bd9e1d8 -- (.exr 0xfffff8800bd9e1d8) ExceptionAddress: fffff880012352b5 (Ntfs!NtfsAcquireExclusiveFcb+0x0000000000000065) ExceptionCode: c0000005 (Access violation) ExceptionFlags: 00000000 NumberParameters: 2 Parameter[0]: 0000000000000000 Parameter[1]: 0000000000000058 Attempt to read from address 0000000000000058 CONTEXT: fffff8800bd9da30 -- (.cxr 0xfffff8800bd9da30) rax=000000000000ff7b rbx=fffff8a01eba8670 rcx=0000000000000000 rdx=fffff8a01eba8601 rsi=0000000000000000 rdi=0000000000000001 rip=fffff880012352b5 rsp=fffff8800bd9e410 rbp=fffffa8008d4acb0 r8=0000000000000000 r9=0000000000000001 r10=fffff8800bd9e4f0 r11=0000000000000000 r12=0000000000000000 r13=00000000c00000d8 r14=0000000000000702 r15=fffffa8004201180 iopl=0 nv up ei pl nz na pe nc cs=0010 ss=0018 ds=002b es=002b fs=0053 gs=002b efl=00010202 Ntfs!NtfsAcquireExclusiveFcb+0x65: fffff880`012352b5 488b4958 mov rcx,qword ptr [rcx+58h] ds:002b:00000000`00000058=???????????????? Resetting default scope CUSTOMER_CRASH_COUNT: 1 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_CODE: (NTSTATUS) 0xc0000005 - The instruction at "0x%08lx" referenced memory at "0x%08lx". The memory could not be "%s". EXCEPTION_PARAMETER1: 0000000000000000 EXCEPTION_PARAMETER2: 0000000000000058 READ_ADDRESS: GetPointerFromAddress: unable to read from fffff800030bf0e8 0000000000000058 FOLLOWUP_IP: Ntfs!NtfsAcquireExclusiveFcb+65 fffff880`012352b5 488b4958 mov rcx,qword ptr [rcx+58h] FAULTING_IP: Ntfs!NtfsAcquireExclusiveFcb+65 fffff880`012352b5 488b4958 mov rcx,qword ptr [rcx+58h] BUGCHECK_STR: 0x24 DEFAULT_BUCKET_ID: NULL_CLASS_PTR_DEREFERENCE LAST_CONTROL_TRANSFER: from fffff880012a13a4 to fffff880012352b5 STACK_TEXT: fffff880`0bd9e410 fffff880`012a13a4 : 00000000`00000000 fffff880`0bd9e720 00000000`00000001 fffffa80`08d4acb0 : Ntfs!NtfsAcquireExclusiveFcb+0x65 fffff880`0bd9e460 fffff880`012a9fad : fffffa80`08d4acb0 fffffa80`04201180 00000000`00100001 00000000`00000000 : Ntfs!NtfsFlushVolume+0x188 fffff880`0bd9e590 fffff880`012aa6b4 : fffffa80`08d4acb0 fffffa80`03a59c10 fffffa80`039cb4d0 00000000`00000000 : Ntfs!NtfsCommonFlushBuffers+0x459 fffff880`0bd9e670 fffff880`0119fbcf : fffffa80`03a59fb0 fffffa80`03a59c10 fffffa80`08d4acb0 fffff880`0bd9e698 : Ntfs!NtfsFsdFlushBuffers+0x104 fffff880`0bd9e6e0 fffff880`0119e6df : fffffa80`0435d3e0 00000000`00000000 fffffa80`0435d300 fffffa80`03a59c10 : fltmgr!FltpLegacyProcessingAfterPreCallbacksCompleted+0x24f fffff880`0bd9e770 fffff800`0319671b : 00000000`00000002 fffffa80`039cb4d0 00000000`00000000 fffffa80`03a59c10 : fltmgr!FltpDispatch+0xcf fffff880`0bd9e7d0 fffff800`0312d871 : fffffa80`03a59c10 fffffa80`06a90480 fffffa80`039cb4d0 fffff880`009ea180 : nt!IopSynchronousServiceTail+0xfb fffff880`0bd9e840 fffff800`02e8d8d3 : fffffa80`06a90480 fffffa80`0366d5f0 fffffa80`0435d3e0 fffffa80`039cb4d0 : nt!NtFlushBuffersFile+0x171 fffff880`0bd9e8d0 fffff800`02e89e70 : fffff800`030cd96d fffff8a0`0222a060 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13 fffff880`0bd9ea68 fffff800`030cd96d : fffff8a0`0222a060 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiServiceLinkage fffff880`0bd9ea70 fffff800`0312bcce : 00000000`00000000 fffffa80`06a90480 00000000`00000080 00000000`00000001 : nt!PopFlushVolumeWorker+0x1bd fffff880`0bd9ed40 fffff800`02e7ffe6 : fffff880`009ea180 fffffa80`06a90480 fffff880`009f4f40 00000000`00000202 : nt!PspSystemThreadStartup+0x5a fffff880`0bd9ed80 00000000`00000000 : fffff880`0bd9f000 fffff880`0bd99000 fffff880`0bd9d5d0 00000000`00000000 : nt!KxStartSystemThread+0x16 SYMBOL_STACK_INDEX: 0 SYMBOL_NAME: Ntfs!NtfsAcquireExclusiveFcb+65 FOLLOWUP_NAME: MachineOwner MODULE_NAME: Ntfs IMAGE_NAME: Ntfs.sys DEBUG_FLR_IMAGE_TIMESTAMP: 4ce792f9 STACK_COMMAND: .cxr 0xfffff8800bd9da30 ; kb FAILURE_BUCKET_ID: X64_0x24_Ntfs!NtfsAcquireExclusiveFcb+65 BUCKET_ID: X64_0x24_Ntfs!NtfsAcquireExclusiveFcb+65 Followup: MachineOwner --------- ________________________________________________________ Run chkdsk /r /f ******************************************************************************* * * * 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: 0000000000000000, The exception code that was not handled Arg2: 0000000000000000, The address that the exception occurred at Arg3: 0000000000000000, Parameter 0 of the exception Arg4: 0000000000000000, Parameter 1 of the exception Debugging Details: ------------------ EXCEPTION_CODE: (Win32) 0 (0) - The operation completed successfully. FAULTING_IP: +345952f0153dfdc 00000000`00000000 ?? ??? EXCEPTION_PARAMETER1: 0000000000000000 EXCEPTION_PARAMETER2: 0000000000000000 CUSTOMER_CRASH_COUNT: 1 DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT BUGCHECK_STR: 0x1E PROCESS_NAME: System CURRENT_IRQL: 2 EXCEPTION_RECORD: fffff800044c82c8 -- (.exr 0xfffff800044c82c8) ExceptionAddress: fffff80002ee8549 (nt!KiInsertTimerTable+0x0000000000000189) ExceptionCode: c0000005 (Access violation) ExceptionFlags: 00000000 NumberParameters: 2 Parameter[0]: 0000000000000000 Parameter[1]: ffffffffffffffff Attempt to read from address ffffffffffffffff TRAP_FRAME: fffff800044c8370 -- (.trap 0xfffff800044c8370) NOTE: The trap frame does not contain all registers. Some register values may be zeroed or incorrect. rax=0000000040c30089 rbx=0000000000000000 rcx=fffff8000304ee80 rdx=fffffa80066e4c70 rsi=0000000000000000 rdi=0000000000000000 rip=fffff80002ee8549 rsp=fffff800044c8500 rbp=0000000000000000 r8=0000800200000000 r9=00000000000000c3 r10=fffff8000304ee80 r11=fffff8800141d700 r12=0000000000000000 r13=0000000000000000 r14=0000000000000000 r15=0000000000000000 iopl=0 nv up ei pl nz na po nc nt!KiInsertTimerTable+0x189: fffff800`02ee8549 410fb74002 movzx eax,word ptr [r8+2] ds:0089:00008002`00000002=???? Resetting default scope LAST_CONTROL_TRANSFER: from fffff80002ed3ffe to fffff80002edc610 STACK_TEXT: fffff800`044c73a8 fffff800`02ed3ffe : fffffa80`07c563d0 fffff880`016f4750 fffff800`044c7b20 fffff800`02f082a0 : nt!KeBugCheck fffff800`044c73b0 fffff800`02f07f6d : fffff800`030e3a10 fffff800`0301fc78 fffff800`02e5c000 fffff800`044c82c8 : nt!KiKernelCalloutExceptionHandler+0xe fffff800`044c73e0 fffff800`02f06d45 : fffff800`030230fc fffff800`044c7458 fffff800`044c82c8 fffff800`02e5c000 : nt!RtlpExecuteHandlerForException+0xd fffff800`044c7410 fffff800`02f17dc1 : fffff800`044c82c8 fffff800`044c7b20 fffff800`00000000 fffff800`02e5c000 : nt!RtlDispatchException+0x415 fffff800`044c7af0 fffff800`02edbcc2 : fffff800`044c82c8 fffffa80`066e4c70 fffff800`044c8370 00008002`00000000 : nt!KiDispatchException+0x135 fffff800`044c8190 fffff800`02eda5ca : 00000000`00000000 00000000`05311c9a fffff800`0304ee80 fffff800`02e1ab7f : nt!KiExceptionDispatch+0xc2 fffff800`044c8370 fffff800`02ee8549 : fffffa80`04ac6000 ffffffff`fffdb610 fffff800`03051080 fffff800`0305ccc0 : nt!KiGeneralProtectionFault+0x10a fffff800`044c8500 fffff800`02ee505a : ffffffff`fff85ee0 fffff800`02ee8062 fffff800`044c8600 00000000`00000001 : nt!KiInsertTimerTable+0x189 fffff800`044c8560 fffff800`02ee7ead : fffffa80`066e4c70 fffffa80`06847308 fffffa80`06847308 00000000`00000000 : nt!KiTimerWaitTest+0x15a fffff800`044c85e0 fffff800`02ee7dee : 00000032`b3a81188 fffff800`044c8c58 00000000`00154cc0 fffff800`03052a88 : nt!KiProcessExpiredTimerList+0x6d fffff800`044c8c30 fffff800`02ee7bd7 : 00000080`6c06bbc3 00000080`00154cc0 00000080`6c06bbd8 00000000`000000c0 : nt!KiTimerExpiration+0x1be fffff800`044c8cd0 fffff800`02ed436a : fffff800`0304ee80 fffff800`0305ccc0 00000000`00000000 fffff880`04402db0 : nt!KiRetireDpcList+0x277 fffff800`044c8d80 00000000`00000000 : fffff800`044c9000 fffff800`044c3000 fffff800`044c8d40 00000000`00000000 : nt!KiIdleLoop+0x5a STACK_COMMAND: kb FOLLOWUP_IP: nt!KiKernelCalloutExceptionHandler+e fffff800`02ed3ffe 90 nop SYMBOL_STACK_INDEX: 1 SYMBOL_NAME: nt!KiKernelCalloutExceptionHandler+e FOLLOWUP_NAME: MachineOwner MODULE_NAME: nt IMAGE_NAME: ntkrnlmp.exe DEBUG_FLR_IMAGE_TIMESTAMP: 4ce7951a FAILURE_BUCKET_ID: X64_0x1E_nt!KiKernelCalloutExceptionHandler+e BUCKET_ID: X64_0x1E_nt!KiKernelCalloutExceptionHandler+e Followup: MachineOwner --------- ____________________________________________________________ Bug Check Code 0x1E: http://msdn.microsoft.com/en-us/library/ff557408(v=VS.85).aspx Try to upload a kernel/full dump for more information ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* Use !analyze -v to get detailed debugging information. BugCheck 1E, {0, 0, 0, 0} Unable to load image \SystemRoot\system32\DRIVERS\xchalVx64.sys, Win32 error 0n2 *** WARNING: Unable to verify timestamp for xchalVx64.sys *** ERROR: Module load completed but symbols could not be loaded for xchalVx64.sys Probably caused by : xchalVx64.sys ( xchalVx64+fcce ) Followup: MachineOwner --------- 1: 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: 0000000000000000, The exception code that was not handled Arg2: 0000000000000000, The address that the exception occurred at Arg3: 0000000000000000, Parameter 0 of the exception Arg4: 0000000000000000, Parameter 1 of the exception Debugging Details: ------------------ EXCEPTION_CODE: (Win32) 0 (0) - The operation completed successfully. FAULTING_IP: +345952f018bdfdc 00000000`00000000 ?? ??? EXCEPTION_PARAMETER1: 0000000000000000 EXCEPTION_PARAMETER2: 0000000000000000 CUSTOMER_CRASH_COUNT: 1 DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT BUGCHECK_STR: 0x1E PROCESS_NAME: System CURRENT_IRQL: 2 EXCEPTION_RECORD: fffff8800311b898 -- (.exr 0xfffff8800311b898) ExceptionAddress: fffff80002ee1116 (nt!KeReleaseSpinLock+0x0000000000000026) ExceptionCode: c0000096 ExceptionFlags: 00000000 NumberParameters: 0 TRAP_FRAME: fffff8800311b940 -- (.trap 0xfffff8800311b940) NOTE: The trap frame does not contain all registers. Some register values may be zeroed or incorrect. rax=0000000000000000 rbx=0000000000000000 rcx=fffffa8004b3c834 rdx=fffffa8004f1ce80 rsi=0000000000000000 rdi=0000000000000000 rip=fffff80002ee1116 rsp=fffff8800311bad0 rbp=fffffa8004bd8248 r8=fffff88006e00000 r9=0000000000000000 r10=0000000000000000 r11=0000000000000080 r12=0000000000000000 r13=0000000000000000 r14=0000000000000000 r15=0000000000000000 iopl=0 nv up ei pl zr na po nc nt!KeReleaseSpinLock+0x26: fffff800`02ee1116 450f22c3 mov cr8,r11 Resetting default scope LAST_CONTROL_TRANSFER: from fffff80002ecdffe to fffff80002ed6610 STACK_TEXT: fffff880`0311a978 fffff800`02ecdffe : 00000000`00000020 fffffa80`080b8d90 fffff880`0311b0f0 fffff800`02f022a0 : nt!KeBugCheck fffff880`0311a980 fffff800`02f01f6d : fffff800`030dda10 fffff800`03019c78 fffff800`02e56000 fffff880`0311b898 : nt!KiKernelCalloutExceptionHandler+0xe fffff880`0311a9b0 fffff800`02f00d45 : fffff800`0301d0fc fffff880`0311aa28 fffff880`0311b898 fffff800`02e56000 : nt!RtlpExecuteHandlerForException+0xd fffff880`0311a9e0 fffff800`02f11dc1 : fffff880`0311b898 fffff880`0311b0f0 fffff880`00000000 00000000`00000000 : nt!RtlDispatchException+0x415 fffff880`0311b0c0 fffff800`02ed5cc2 : fffff880`0311b898 fffffa80`04b3c000 fffff880`0311b940 fffffa80`04f1ce98 : nt!KiDispatchException+0x135 fffff880`0311b760 fffff800`02ed45ca : fffffa80`04ae61a0 00000000`00000002 00000000`00000001 fffffa80`03a73950 : nt!KiExceptionDispatch+0xc2 fffff880`0311b940 fffff800`02ee1116 : 00000000`00000000 fffff880`0311bb80 00000000`00004380 00000000`00000001 : nt!KiGeneralProtectionFault+0x10a fffff880`0311bad0 fffff880`04c16cce : fffffa80`04f1ce98 fffff880`0311bb80 00000000`ffffffff fffffa80`04b3c000 : nt!KeReleaseSpinLock+0x26 fffff880`0311bb00 fffffa80`04f1ce98 : fffff880`0311bb80 00000000`ffffffff fffffa80`04b3c000 fffffa80`04bd52e0 : xchalVx64+0xfcce fffff880`0311bb08 fffff880`0311bb80 : 00000000`ffffffff fffffa80`04b3c000 fffffa80`04bd52e0 fffff880`04c29209 : 0xfffffa80`04f1ce98 fffff880`0311bb10 00000000`ffffffff : fffffa80`04b3c000 fffffa80`04bd52e0 fffff880`04c29209 fffffa80`03ef9e84 : 0xfffff880`0311bb80 fffff880`0311bb18 fffffa80`04b3c000 : fffffa80`04bd52e0 fffff880`04c29209 fffffa80`03ef9e84 fffffa80`04bd8248 : 0xffffffff fffff880`0311bb20 fffffa80`04bd52e0 : fffff880`04c29209 fffffa80`03ef9e84 fffffa80`04bd8248 fffffa80`04bdafe8 : 0xfffffa80`04b3c000 fffff880`0311bb28 fffff880`04c29209 : fffffa80`03ef9e84 fffffa80`04bd8248 fffffa80`04bdafe8 fffffa80`03ef9e84 : 0xfffffa80`04bd52e0 fffff880`0311bb30 fffffa80`03ef9e84 : fffffa80`04bd8248 fffffa80`04bdafe8 fffffa80`03ef9e84 fffffa80`04b3c000 : xchalVx64+0x22209 fffff880`0311bb38 fffffa80`04bd8248 : fffffa80`04bdafe8 fffffa80`03ef9e84 fffffa80`04b3c000 00000000`00000000 : 0xfffffa80`03ef9e84 fffff880`0311bb40 fffffa80`04bdafe8 : fffffa80`03ef9e84 fffffa80`04b3c000 00000000`00000000 fffffa80`04b3c000 : 0xfffffa80`04bd8248 fffff880`0311bb48 fffffa80`03ef9e84 : fffffa80`04b3c000 00000000`00000000 fffffa80`04b3c000 fffffa80`04bd52e0 : 0xfffffa80`04bdafe8 fffff880`0311bb50 fffffa80`04b3c000 : 00000000`00000000 fffffa80`04b3c000 fffffa80`04bd52e0 fffffa80`04bdafe8 : 0xfffffa80`03ef9e84 fffff880`0311bb58 00000000`00000000 : fffffa80`04b3c000 fffffa80`04bd52e0 fffffa80`04bdafe8 fffffa80`03ef9ef5 : 0xfffffa80`04b3c000 STACK_COMMAND: kb FOLLOWUP_IP: xchalVx64+fcce fffff880`04c16cce ?? ??? SYMBOL_STACK_INDEX: 8 SYMBOL_NAME: xchalVx64+fcce FOLLOWUP_NAME: MachineOwner MODULE_NAME: xchalVx64 IMAGE_NAME: xchalVx64.sys DEBUG_FLR_IMAGE_TIMESTAMP: 48ce2536 FAILURE_BUCKET_ID: X64_0x1E_xchalVx64+fcce BUCKET_ID: X64_0x1E_xchalVx64+fcce Followup: MachineOwner _________________________________ The BSOD was caused by xchalVx64. It belongs to ViXS SCode Support Library (x64). Update it or uninstall it. This posting is provided "AS IS" with no warranties or guarantees , and confers no rights. Microsoft Student Partner Microsoft Certified Professional Microsoft Certified Systems Administrator: Security Microsoft Certified Systems Engineer: Security Microsoft Certified Technology Specialist: Windows Server 2008 Active Directory, Configuration Microsoft Certified Technology Specialist: Windows Server 2008 Network Infrastructure, Configuration Microsoft Certified Technology Specialist: Windows Server 2008 Applications Infrastructure, Configuration

Only ViXs hardware I have is the TV tuner card that came with the PC. How do I unstall the support library? I can't upload the Memory.dmp, it is 93MB compressed and SkyDrive allows only 50MB files. I can upload some more mini dumps if that helps. I uninstalled SP1, that do anything. I did notice a pattern with the crashes, they happen when the computer comes out of Sleep and/or hibernate mode. Never has happened on me while using the PC. I use the PC as my media center PC and it is on most of the day as it pumps media to my Xbox. Will run checkdsk tonight see if anything is found. Lastly, HP doesn't allow you to get updates for BIOS unless you are on the original OS that came on the computer (Vista in my case) or you upgrade thru them. :(Mohammd Shafaqat