Ive been geting BSOD ever since I bought this computer

S

Skudz

New member
Local time
9:05 PM
Messages
2
I bought this computer brand new and within the first 20 minutes on being turned on for the first time it got the Blue screen. I thought I fixed it a few times because it seems to not happen for weeks then it will happen rapidly. It happend 8 times within today. I attached my mini dump file. Any help?
 

My Computer My Computer

At a glance

Widows 7
OS
Widows 7
Skudz said:
I bought this computer brand new and within the first 20 minutes on being turned on for the first time it got the Blue screen. I thought I fixed it a few times because it seems to not happen for weeks then it will happen rapidly. It happend 8 times within today. I attached my mini dump file. Any help?
Click to expand...



This crash was caused by hardware, probably memory. I would download memtestx86 and run it for at least 5 passes

Let us know if you need help


Ken

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


Loading Dump File [C:\Users\K\Desktop\042110-17706-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*F:\symbols*http://msdl.microsoft.com/download/symbols
Executable search path is: 
Windows 7 Kernel Version 7600 UP Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 7600.20655.amd64fre.win7_ldr.100226-1909
Machine Name:
Kernel base = 0xfffff800`02a03000 PsLoadedModuleList = 0xfffff800`02c3be50
Debug session time: Wed Apr 21 09:35:34.435 2010 (GMT-4)
System Uptime: 0 days 0:22:26.480
Loading Kernel Symbols
...............................................................
................................................................
...................
Loading User Symbols
Loading unloaded module list
......
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 24, {1904fb, fffff880027102a8, fffff8800270fb10, fffff80002a56c32}

Probably caused by : hardware ( Ntfs!NtfsDeleteAllocationFromRecord+1b4 )

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

kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        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: fffff880027102a8
Arg3: fffff8800270fb10
Arg4: fffff80002a56c32

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


EXCEPTION_RECORD:  fffff880027102a8 -- (.exr 0xfffff880027102a8)
ExceptionAddress: fffff80002a56c32 (nt!CcFlushCache+0x00000000000001c2)
   ExceptionCode: c0000005 (Access violation)
  ExceptionFlags: 00000000
NumberParameters: 2
   Parameter[0]: 0000000000000000
   Parameter[1]: 0000000000000001
Attempt to read from address 0000000000000001

CONTEXT:  fffff8800270fb10 -- (.cxr 0xfffff8800270fb10)
rax=0000000000000001 rbx=fffffa8005f0e3d8 rcx=0000000000000000
rdx=fffffa8001c1e780 rsi=0000000000000001 rdi=fffffa8001756cc0
rip=fffff80002a56c32 rsp=fffff880027104e0 rbp=fffff88002710650
 r8=0000000000000000  r9=0000000000000000 r10=0000000000000000
r11=fffff880027103b0 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei ng nz na po nc
cs=0010  ss=0018  ds=002b  es=002b  fs=0053  gs=002b             efl=00010286
nt!CcFlushCache+0x1c2:
fffff800`02a56c32 8406            test    byte ptr [rsi],al ds:002b:00000000`00000001=??
Resetting default scope

CUSTOMER_CRASH_COUNT:  1

PROCESS_NAME:  ccSvcHst.exe

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:  0000000000000001

READ_ADDRESS: GetPointerFromAddress: unable to read from fffff80002ca60e0
 0000000000000001 

FOLLOWUP_IP: 
Ntfs!NtfsDeleteAllocationFromRecord+1b4
fffff880`012a0924 395c2470        cmp     dword ptr [rsp+70h],ebx

FAULTING_IP: 
nt!CcFlushCache+1c2
fffff800`02a56c32 8406            test    byte ptr [rsi],al

BUGCHECK_STR:  0x24

DEFAULT_BUCKET_ID:  NULL_CLASS_PTR_DEREFERENCE

MISALIGNED_IP: 
nt!CcFlushCache+1c2
fffff800`02a56c32 8406            test    byte ptr [rsi],al

LAST_CONTROL_TRANSFER:  from fffff880012a0924 to fffff80002a56c32

STACK_TEXT:  
fffff880`027104e0 fffff880`012a0924 : fffffa80`05f0e3d8 fffff8a0`00000000 00000000`00000000 fffff880`00002000 : nt!CcFlushCache+0x1c2
fffff880`027105e0 fffff880`012ad212 : fffff880`068ba730 00000000`00000001 fffff980`01b46dc8 00000000`0000b601 : Ntfs!NtfsDeleteAllocationFromRecord+0x1b4
fffff880`027106a0 fffff880`012c7aa5 : fffff880`068ba730 fffff8a0`0998b680 fffff8a0`09ad2140 fffff880`0271099c : Ntfs!NtfsDeleteFile+0x346
fffff880`02710920 fffff880`01234aa9 : fffffa80`017fba40 fffffa80`01d29c10 fffff880`068ba690 fffffa80`01c1e780 : Ntfs!NtfsCommonCleanup+0x2472
fffff880`02710d30 fffff800`02a63787 : fffff880`068ba690 00000000`00000000 00000000`7ef17000 00000000`08f6ff34 : Ntfs!NtfsCommonCleanupCallout+0x19
fffff880`02710d60 fffff800`02a63741 : 00000000`00000000 fffffa80`01c1e780 fffff880`02711000 fffff800`02a7b20a : nt!KySwitchKernelStackCallout+0x27
fffff880`068ba560 fffff800`02a7b20a : fffff880`068ba594 fffffa80`01c1e780 00000000`00000000 00000000`00000000 : nt!KiSwitchKernelStackContinue
fffff880`068ba580 fffff880`01234662 : fffff880`01234a90 fffff880`068ba690 fffff880`068ba900 00000000`00000000 : nt!KeExpandKernelStackAndCalloutEx+0x29a
fffff880`068ba660 fffff880`012d6244 : fffff880`068ba730 fffff880`068ba730 fffff880`068ba730 fffff8a0`00e57d98 : Ntfs!NtfsCommonCleanupOnNewStack+0x42
fffff880`068ba6d0 fffff880`010c223f : fffff880`068ba730 fffffa80`01d29c10 fffffa80`01d29fb0 fffffa80`01ce0bb0 : Ntfs!NtfsFsdCleanup+0x144
fffff880`068ba940 fffff880`010c06df : fffffa80`025d3040 00000000`00000000 fffffa80`01f84400 fffffa80`01d29c10 : fltmgr!FltpLegacyProcessingAfterPreCallbacksCompleted+0x24f
fffff880`068ba9d0 fffff800`02d8591f : fffffa80`01d29c10 fffffa80`04f89b30 00000000`00000000 fffffa80`01887b60 : fltmgr!FltpDispatch+0xcf
fffff880`068baa30 fffff800`02d6b594 : 00000000`00000000 fffffa80`04f89b30 fffffa80`01d20101 fffffa80`01887b60 : nt!IopCloseFile+0x11f
fffff880`068baac0 fffff800`02d85411 : fffffa80`04f89b30 fffffa80`00000001 fffff8a0`012b8e30 00000000`00000000 : nt!ObpDecrementHandleCount+0xb4
fffff880`068bab40 fffff800`02d85324 : 00000000`00001e1c fffffa80`04f89b30 fffff8a0`012b8e30 00000000`00001e1c : nt!ObpCloseHandleTableEntry+0xb1
fffff880`068babd0 fffff800`02a6ab53 : fffffa80`01c1e780 fffff880`068baca0 00000000`7ef26000 00000000`00000105 : nt!ObpCloseHandle+0x94
fffff880`068bac20 00000000`76f5ffaa : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
00000000`0845e808 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x76f5ffaa


SYMBOL_STACK_INDEX:  1

SYMBOL_NAME:  Ntfs!NtfsDeleteAllocationFromRecord+1b4

FOLLOWUP_NAME:  MachineOwner

IMAGE_NAME:  hardware

DEBUG_FLR_IMAGE_TIMESTAMP:  0

STACK_COMMAND:  .cxr 0xfffff8800270fb10 ; kb

MODULE_NAME: hardware

FAILURE_BUCKET_ID:  X64_IP_MISALIGNED

BUCKET_ID:  X64_IP_MISALIGNED

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

My Computer My Computer

At a glance

Win 8 Release candidate 8400[email protected]4 gigsNvidia 9600M
Computer Manufacturer/Model Number
HP Pavillion dv-7 1005 Tx
OS
Win 8 Release candidate 8400
CPU
[email protected]
Memory
4 gigs
Graphics Card(s)
Nvidia 9600M
Sound Card
HD built-in
Monitor(s) Displays
17" Wxga
Screen Resolution
1440x900
Cooling
none
Internet Speed
45Mb down 5Mb up
zigzag3143 said:
Skudz said:
I bought this computer brand new and within the first 20 minutes on being turned on for the first time it got the Blue screen. I thought I fixed it a few times because it seems to not happen for weeks then it will happen rapidly. It happend 8 times within today. I attached my mini dump file. Any help?
Click to expand...



This crash was caused by hardware, probably memory. I would download memtestx86 and run it for at least 5 passes

Let us know if you need help


Ken

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


Loading Dump File [C:\Users\K\Desktop\042110-17706-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*F:\symbols*http://msdl.microsoft.com/download/symbols
Executable search path is: 
Windows 7 Kernel Version 7600 UP Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 7600.20655.amd64fre.win7_ldr.100226-1909
Machine Name:
Kernel base = 0xfffff800`02a03000 PsLoadedModuleList = 0xfffff800`02c3be50
Debug session time: Wed Apr 21 09:35:34.435 2010 (GMT-4)
System Uptime: 0 days 0:22:26.480
Loading Kernel Symbols
...............................................................
................................................................
...................
Loading User Symbols
Loading unloaded module list
......
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 24, {1904fb, fffff880027102a8, fffff8800270fb10, fffff80002a56c32}

Probably caused by : hardware ( Ntfs!NtfsDeleteAllocationFromRecord+1b4 )

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

kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        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: fffff880027102a8
Arg3: fffff8800270fb10
Arg4: fffff80002a56c32

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


EXCEPTION_RECORD:  fffff880027102a8 -- (.exr 0xfffff880027102a8)
ExceptionAddress: fffff80002a56c32 (nt!CcFlushCache+0x00000000000001c2)
   ExceptionCode: c0000005 (Access violation)
  ExceptionFlags: 00000000
NumberParameters: 2
   Parameter[0]: 0000000000000000
   Parameter[1]: 0000000000000001
Attempt to read from address 0000000000000001

CONTEXT:  fffff8800270fb10 -- (.cxr 0xfffff8800270fb10)
rax=0000000000000001 rbx=fffffa8005f0e3d8 rcx=0000000000000000
rdx=fffffa8001c1e780 rsi=0000000000000001 rdi=fffffa8001756cc0
rip=fffff80002a56c32 rsp=fffff880027104e0 rbp=fffff88002710650
 r8=0000000000000000  r9=0000000000000000 r10=0000000000000000
r11=fffff880027103b0 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei ng nz na po nc
cs=0010  ss=0018  ds=002b  es=002b  fs=0053  gs=002b             efl=00010286
nt!CcFlushCache+0x1c2:
fffff800`02a56c32 8406            test    byte ptr [rsi],al ds:002b:00000000`00000001=??
Resetting default scope

CUSTOMER_CRASH_COUNT:  1

PROCESS_NAME:  ccSvcHst.exe

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:  0000000000000001

READ_ADDRESS: GetPointerFromAddress: unable to read from fffff80002ca60e0
 0000000000000001 

FOLLOWUP_IP: 
Ntfs!NtfsDeleteAllocationFromRecord+1b4
fffff880`012a0924 395c2470        cmp     dword ptr [rsp+70h],ebx

FAULTING_IP: 
nt!CcFlushCache+1c2
fffff800`02a56c32 8406            test    byte ptr [rsi],al

BUGCHECK_STR:  0x24

DEFAULT_BUCKET_ID:  NULL_CLASS_PTR_DEREFERENCE

MISALIGNED_IP: 
nt!CcFlushCache+1c2
fffff800`02a56c32 8406            test    byte ptr [rsi],al

LAST_CONTROL_TRANSFER:  from fffff880012a0924 to fffff80002a56c32

STACK_TEXT:  
fffff880`027104e0 fffff880`012a0924 : fffffa80`05f0e3d8 fffff8a0`00000000 00000000`00000000 fffff880`00002000 : nt!CcFlushCache+0x1c2
fffff880`027105e0 fffff880`012ad212 : fffff880`068ba730 00000000`00000001 fffff980`01b46dc8 00000000`0000b601 : Ntfs!NtfsDeleteAllocationFromRecord+0x1b4
fffff880`027106a0 fffff880`012c7aa5 : fffff880`068ba730 fffff8a0`0998b680 fffff8a0`09ad2140 fffff880`0271099c : Ntfs!NtfsDeleteFile+0x346
fffff880`02710920 fffff880`01234aa9 : fffffa80`017fba40 fffffa80`01d29c10 fffff880`068ba690 fffffa80`01c1e780 : Ntfs!NtfsCommonCleanup+0x2472
fffff880`02710d30 fffff800`02a63787 : fffff880`068ba690 00000000`00000000 00000000`7ef17000 00000000`08f6ff34 : Ntfs!NtfsCommonCleanupCallout+0x19
fffff880`02710d60 fffff800`02a63741 : 00000000`00000000 fffffa80`01c1e780 fffff880`02711000 fffff800`02a7b20a : nt!KySwitchKernelStackCallout+0x27
fffff880`068ba560 fffff800`02a7b20a : fffff880`068ba594 fffffa80`01c1e780 00000000`00000000 00000000`00000000 : nt!KiSwitchKernelStackContinue
fffff880`068ba580 fffff880`01234662 : fffff880`01234a90 fffff880`068ba690 fffff880`068ba900 00000000`00000000 : nt!KeExpandKernelStackAndCalloutEx+0x29a
fffff880`068ba660 fffff880`012d6244 : fffff880`068ba730 fffff880`068ba730 fffff880`068ba730 fffff8a0`00e57d98 : Ntfs!NtfsCommonCleanupOnNewStack+0x42
fffff880`068ba6d0 fffff880`010c223f : fffff880`068ba730 fffffa80`01d29c10 fffffa80`01d29fb0 fffffa80`01ce0bb0 : Ntfs!NtfsFsdCleanup+0x144
fffff880`068ba940 fffff880`010c06df : fffffa80`025d3040 00000000`00000000 fffffa80`01f84400 fffffa80`01d29c10 : fltmgr!FltpLegacyProcessingAfterPreCallbacksCompleted+0x24f
fffff880`068ba9d0 fffff800`02d8591f : fffffa80`01d29c10 fffffa80`04f89b30 00000000`00000000 fffffa80`01887b60 : fltmgr!FltpDispatch+0xcf
fffff880`068baa30 fffff800`02d6b594 : 00000000`00000000 fffffa80`04f89b30 fffffa80`01d20101 fffffa80`01887b60 : nt!IopCloseFile+0x11f
fffff880`068baac0 fffff800`02d85411 : fffffa80`04f89b30 fffffa80`00000001 fffff8a0`012b8e30 00000000`00000000 : nt!ObpDecrementHandleCount+0xb4
fffff880`068bab40 fffff800`02d85324 : 00000000`00001e1c fffffa80`04f89b30 fffff8a0`012b8e30 00000000`00001e1c : nt!ObpCloseHandleTableEntry+0xb1
fffff880`068babd0 fffff800`02a6ab53 : fffffa80`01c1e780 fffff880`068baca0 00000000`7ef26000 00000000`00000105 : nt!ObpCloseHandle+0x94
fffff880`068bac20 00000000`76f5ffaa : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
00000000`0845e808 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x76f5ffaa


SYMBOL_STACK_INDEX:  1

SYMBOL_NAME:  Ntfs!NtfsDeleteAllocationFromRecord+1b4

FOLLOWUP_NAME:  MachineOwner

IMAGE_NAME:  hardware

DEBUG_FLR_IMAGE_TIMESTAMP:  0

STACK_COMMAND:  .cxr 0xfffff8800270fb10 ; kb

MODULE_NAME: hardware

FAILURE_BUCKET_ID:  X64_IP_MISALIGNED

BUCKET_ID:  X64_IP_MISALIGNED

Followup: MachineOwner
---------
Click to expand...


Well I downloaded Memtest and let it run over 500% and it still came back with nothin. Any other suggestions?
 

My Computer My Computer

At a glance

Widows 7
OS
Widows 7
You must log in or register to reply here.

Similar threads

Blue screen of death - no downloads or changes to computer recently
Replies
17
Views
32K
CHRISX
C
Solved I know I’m late to the party but FOUR questions about Windows 7 & 10
Replies
3
Views
7K
SIW2
SIW2
BSOD resets since last month, sudden increase today
Replies
1
Views
2K
Churys
C
BSOD STOP D1 - pci.sys
2
Replies
39
Views
34K
wither 2
W
BSOD STOP 0xc9
Replies
3
Views
996
martinlest
M
Back
Top