Solved your computer crashed

[nickestrand]

Hello,

My computer is now 6 months old, and i had this Blue screen problem from the beginng.

It can be inside gamez, on firefox surfing the webb, watching movies etc.
First i notised it when i had shut down my computer! i had to power of the psu or i got the Blue screen before i could log in to windows.

i removed my memmorys and tested them induvidual in 1 slott and i gott massiv fails on one of them in memtest86 so i removed it and only use the good one.

tht solved the blue screen starting up windows!

but i still have these crashes inside windows now and then

[FONT=Segoe UI, Arial]On Wed 2011-08-31 11:29:21 GMT your computer crashed
crash dump file: C:\Windows\Minidump\083111-38157-01.dmp
This was probably caused by the following module: [FONT=Segoe UI, Arial]ntoskrnl.exe[/FONT] (nt+0x71F00)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF80002C5B7C0, 0xFFFFF88003037070, 0x0)
Error: [FONT=Segoe UI, Arial]SYSTEM_SERVICE_EXCEPTION[/FONT]
file path: C:\Windows\system32\ntoskrnl.exe
product: [FONT=Segoe UI, Arial]Microsoft® Windows® Operating System[/FONT]
company: [FONT=Segoe UI, Arial]Microsoft Corporation[/FONT]
description: NT Kernel & System
Bug check description: This indicates that an exception happened while executing a routine that transitions from non-privileged code to privileged code.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time. [/FONT]


[FONT=Segoe UI, Arial]On Mon 2011-08-29 17:07:47 GMT your computer crashed
crash dump file: C:\Windows\Minidump\082911-32588-01.dmp
This was probably caused by the following module: [FONT=Segoe UI, Arial]ntoskrnl.exe[/FONT] (nt+0x71F00)
Bugcheck code: 0x50 (0xFFFFFFFF80048B70, 0x1, 0xFFFFF80002E0590D, 0x5)
Error: [FONT=Segoe UI, Arial]PAGE_FAULT_IN_NONPAGED_AREA[/FONT]
file path: C:\Windows\system32\ntoskrnl.exe
product: [FONT=Segoe UI, Arial]Microsoft® Windows® Operating System[/FONT]
company: [FONT=Segoe UI, Arial]Microsoft Corporation[/FONT]
description: NT Kernel & System
Bug check description: This indicates that invalid system memory has been referenced.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time.
[/FONT]

[FONT=Segoe UI, Arial]On Fri 2011-08-26 21:29:36 GMT your computer crashed
crash dump file: C:\Windows\Minidump\082611-31527-01.dmp
This was probably caused by the following module: [FONT=Segoe UI, Arial]ntoskrnl.exe[/FONT] (nt+0x71F00)
Bugcheck code: 0x50 (0xFFFFF87FF95A48C0, 0x0, 0xFFFFF80002C9A324, 0x5)
Error: [FONT=Segoe UI, Arial]PAGE_FAULT_IN_NONPAGED_AREA[/FONT]
file path: C:\Windows\system32\ntoskrnl.exe
product: [FONT=Segoe UI, Arial]Microsoft® Windows® Operating System[/FONT]
company: [FONT=Segoe UI, Arial]Microsoft Corporation[/FONT]
description: NT Kernel & System
Bug check description: This indicates that invalid system memory has been referenced.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time.
[/FONT]

[FONT=Segoe UI, Arial]On Fri 2011-08-26 21:26:03 GMT your computer crashed
crash dump file: C:\Windows\Minidump\082611-31325-01.dmp
This was probably caused by the following module: [FONT=Segoe UI, Arial]ntoskrnl.exe[/FONT] (nt+0x71F00)
Bugcheck code: 0xC0000221 (0xFFFFF8A0002A7150, 0x0, 0x0, 0x0)
Error: [FONT=Segoe UI, Arial]STATUS_IMAGE_CHECKSUM_MISMATCH[/FONT]
file path: C:\Windows\system32\ntoskrnl.exe
product: [FONT=Segoe UI, Arial]Microsoft® Windows® Operating System[/FONT]
company: [FONT=Segoe UI, Arial]Microsoft Corporation[/FONT]
description: NT Kernel & System
Bug check description: This indicates that a driver or a system DLL has been corrupted.
This might be a case of memory corruption. More often memory corruption happens because of software errors in buggy drivers, not because of faulty RAM modules. There is a possibility this problem was caused by a virus or other malware.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time.
[/FONT]

 

[yowanvista]

You have old drivers on your system

Update the Silicon Image drivers
Silicon Image - Support

SiWinAcc.sys        fffff880`01148000    fffff880`01152000    0x0000a000    0x41868d31    01/11/2004 23:23:29      
SiRemFil.sys        fffff880`01967000    fffff880`0196f000    0x00008000    0x4536a8b7    19/10/2006 02:20:39                
Si3114r5.sys        fffff880`00c2a000    fffff880`00c7d000    0x00053000    0x4926648d    21/11/2008 11:34:37

Run SFC http://www.sevenforums.com/tutorials/1538-sfc-scannow-command-system-file-checker.html

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

PAGE_FAULT_IN_NONPAGED_AREA (50)
Invalid system memory was referenced.  This cannot be protected by try-except,
it must be protected by a Probe.  Typically the address is just plain bad or it
is pointing at freed memory.
Arguments:
Arg1: ffffffff80048b70, memory referenced.
Arg2: 0000000000000001, value 0 = read operation, 1 = write operation.
Arg3: fffff80002e0590d, If non-zero, the instruction address which referenced the bad memory
    address.
Arg4: 0000000000000005, (reserved)

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


Could not read faulting driver name

WRITE_ADDRESS: GetPointerFromAddress: unable to read from fffff80002f090e0
 ffffffff80048b70 

FAULTING_IP: 
nt!ExAllocatePoolWithTag+53d
fffff800`02e0590d 48895808        mov     qword ptr [rax+8],rbx

MM_INTERNAL_CODE:  5

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

BUGCHECK_STR:  0x50

PROCESS_NAME:  AvastSvc.exe

CURRENT_IRQL:  0

TRAP_FRAME:  fffff8800b7e7470 -- (.trap 0xfffff8800b7e7470)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=ffffffff80048b68 rbx=0000000000000000 rcx=fffff8a000284870
rdx=0000000000000001 rsi=0000000000000000 rdi=0000000000000000
rip=fffff80002e0590d rsp=fffff8800b7e7600 rbp=fffffa8001825140
 r8=0000000000000001  r9=fffffa80018252b0 r10=fffffa8001825148
r11=0000000000000001 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei pl zr na po nc
nt!ExAllocatePoolWithTag+0x53d:
fffff800`02e0590d 48895808        mov     qword ptr [rax+8],rbx ds:ffffffff`80048b70=????????????????
Resetting default scope

LAST_CONTROL_TRANSFER:  from fffff80002d50b91 to fffff80002cd2f00

STACK_TEXT:  
fffff880`0b7e7308 fffff800`02d50b91 : 00000000`00000050 ffffffff`80048b70 00000000`00000001 fffff880`0b7e7470 : nt!KeBugCheckEx
fffff880`0b7e7310 fffff800`02cd0fee : 00000000`00000001 fffffa80`018252b0 00000000`275f6000 fffff8a0`00000000 : nt! ?? ::FNODOBFM::`string'+0x40f5b
fffff880`0b7e7470 fffff800`02e0590d : 00000000`00000000 fffff880`00000000 00000000`00000001 fffffa80`021c8760 : nt!KiPageFault+0x16e
fffff880`0b7e7600 fffff800`02cf8f3a : fffff880`00000001 fffffa80`04e07b00 fffff880`0b7e7840 fffffa80`00000000 : nt!ExAllocatePoolWithTag+0x53d
fffff880`0b7e76f0 fffff880`012e67c9 : fffffa80`04e07b00 fffffa80`03e8cbd0 fffffa80`043c9e40 fffff8a0`09b035c0 : nt!RtlInsertElementGenericTableFullAvl+0x4a
fffff880`0b7e7730 fffff880`012ef380 : fffffa80`043c9e40 fffffa80`03651180 fffff880`0b7e7918 00210000`0001b1f5 : Ntfs!NtfsCreateFcb+0x211
fffff880`0b7e7810 fffff880`012d6d7f : fffffa80`043c9e40 fffffa80`043c9e40 fffff8a0`03b53801 00000000`00000000 : Ntfs!NtfsCreateNewFile+0x4a0
fffff880`0b7e7b50 fffff880`0123fc0d : fffffa80`043c9e40 fffffa80`03e8cbd0 fffff880`0301b3d0 fffffa80`04a21000 : Ntfs!NtfsCommonCreate+0xecf
fffff880`0b7e7d30 fffff800`02ccad87 : fffff880`0301b340 00000000`00000000 00000000`7efd5000 00000000`19d1fcc4 : Ntfs!NtfsCommonCreateCallout+0x1d
fffff880`0b7e7d60 fffff800`02ccad41 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KySwitchKernelStackCallout+0x27
fffff880`0301b210 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSwitchKernelStackContinue


STACK_COMMAND:  kb

FOLLOWUP_IP: 
nt!ExAllocatePoolWithTag+53d
fffff800`02e0590d 48895808        mov     qword ptr [rax+8],rbx

SYMBOL_STACK_INDEX:  3

SYMBOL_NAME:  nt!ExAllocatePoolWithTag+53d

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nt

IMAGE_NAME:  ntkrnlmp.exe

DEBUG_FLR_IMAGE_TIMESTAMP:  4a5bc600

FAILURE_BUCKET_ID:  X64_0x50_nt!ExAllocatePoolWithTag+53d

BUCKET_ID:  X64_0x50_nt!ExAllocatePoolWithTag+53d

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

 

[nickestrand]

Hey,

Thanks for that fast answer, i use to have this raid controller card installed but i removed it 5 days ago. i think i have uninstalled the drivers for it now.

i hope this will make a diffrens

Thanks.