hi! my computer randomly reboots,I have analyzed the minidump files , but Im not sure what the problem seems to be.I think it has something to to with the memory. I have the latest drivers and I have reinstalled many times. below is 2 of my minidump files. Would be grateful if someone could have a look. /regards Peter **************** Debugging Details: ------------------ ***** Kernel symbols are WRONG. Please fix symbols to do analysis. EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - Instruktionen p "0x%08lx" refererade till minnet p "0x%08lx". Det gick inte att utf ra en minnes tgärd. F ljande fel returnerades: The memory could not be "%s". FAULTING_IP: nt+c590f 8059990f 8b37 mov esi,[edi] TRAP_FRAME: b24ddacc -- (.trap ffffffffb24ddacc) ErrCode = 00000000 eax=81a9b438 ebx=000011f4 ecx=000011a8 edx=00000013 esi=0000c6f3 edi=0000123c eip=8059990f esp=b24ddb40 ebp=b24ddb64 iopl=0 nv up ei pl nz na po nc cs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000 efl=00010206 nt+0xc590f: 8059990f 8b37 mov esi,[edi] ds:0023:0000123c=???????? Resetting default scope DEFAULT_BUCKET_ID: DRIVER_FAULT BUGCHECK_STR: 0x8E LAST_CONTROL_TRANSFER: from 8059a178 to 8059990f STACK_TEXT: WARNING: Stack unwind information not available. Following frames may be wrong. b24ddb64 8059a178 000011a8 b24ddb8c 0000004c nt+0xc590f b24ddbd8 80596c27 00000000 b24ddc18 00000040 nt+0xc6178 b24ddc2c 80553f0d 00000000 00000000 00000001 nt+0xc2c27 b24ddca8 80554688 0372ec60 00000003 0372ec38 nt+0x7ff0d b24ddcf0 80556b3c 0372ec60 00000003 0372ec38 nt+0x80688 b24ddd30 8052d571 0372ec60 00000003 0372ec38 nt+0x82b3c b24ddd64 ffffffff b27b1d8c 805aca20 00000000 nt+0x59571 804d6da8 00000000 00000000 00000000 00000000 0xffffffff FOLLOWUP_IP: nt+c590f 8059990f 8b37 mov esi,[edi] FOLLOWUP_NAME: MachineOwner SYMBOL_NAME: nt+c590f IMAGE_NAME: Unknown_Image DEBUG_FLR_IMAGE_TIMESTAMP: 0 STACK_COMMAND: .trap ffffffffb24ddacc ; kb BUCKET_ID: WRONG_SYMBOLS MODULE_NAME: Unknown_Module Followup: MachineOwner --------- Another one ***************************** 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. An exception code of 0x80000002 (STATUS_DATATYPE_MISALIGNMENT) indicates that an unaligned data reference was encountered. The trap frame will supply additional information. Arguments: Arg1: c000001d, The exception code that was not handled Arg2: b2f41c17, The address that the exception occurred at Arg3: 80539144, Trap Frame Arg4: 00000000 Debugging Details: ------------------ ***** Kernel symbols are WRONG. Please fix symbols to do analysis. EXCEPTION_CODE: (NTSTATUS) 0xc000001d - {UNDANTAG} Ogiltig instruktion Ett f rs k gjordes att utf ra en ogiltig instruktion. FAULTING_IP: netbt+c17 b2f41c17 ffff ??? TRAP_FRAME: 80539144 -- (.trap ffffffff80539144) ErrCode = 00000000 eax=80539224 ebx=81caa468 ecx=81cdf008 edx=00000040 esi=81d02300 edi=81cdf008 eip=b2f41c17 esp=805391b8 ebp=805391d0 iopl=0 nv dn ei pl nz na pe nc cs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000 efl=00010602 netbt+0xc17: b2f41c17 ffff ??? Resetting default scope DEFAULT_BUCKET_ID: DRIVER_FAULT BUGCHECK_STR: 0x8E LAST_CONTROL_TRANSFER: from b2f6da57 to b2f41c17 STACK_TEXT: WARNING: Stack unwind information not available. Following frames may be wrong. 805391d0 b2f6da57 00000040 81caa402 c00000b6 netbt+0xc17 8053922c b2f69d3e 81caa468 00001050 80539330 tcpip+0x7a57 805392ac b2f67685 00000000 ba00a8c0 ae00a8c0 tcpip+0x3d3e 805392f8 b2f672f8 b2f699f5 81e06d18 00000000 tcpip+0x1685 805393a0 b2f673b0 81e06d18 81e03a20 81d622f0 tcpip+0x12f8 805393e0 b2f7d90c 00000000 81e13270 81c2f898 tcpip+0x13b0 80539410 f83d9565 81d1b640 81e13270 81c2f898 tcpip+0x1790c 80539444 f8096f58 81ddf718 81e13270 00000000 NDIS+0x20565 80539484 f83d94c9 81e173e8 81e13270 81c2f898 psched+0x7f58 805394b8 f880f6fd 81e07168 81e13270 81c2f898 NDIS+0x204c9 000005ee 00000000 00000000 00000000 00000000 RTL8139+0x6fd FAILED_INSTRUCTION_ADDRESS: netbt+c17 b2f41c17 ffff ??? FOLLOWUP_IP: netbt+c17 b2f41c17 ffff ??? FOLLOWUP_NAME: MachineOwner SYMBOL_NAME: netbt+c17 IMAGE_NAME: Unknown_Image DEBUG_FLR_IMAGE_TIMESTAMP: 0 STACK_COMMAND: .trap ffffffff80539144 ; kb BUCKET_ID: WRONG_SYMBOLS MODULE_NAME: Unknown_Module Followup: MachineOwner ---------

If it is doing it after it has been on for awhile I would suggest making sure there is no dust on the cooling fans and around the air intake areas. Sounds like the processor may be overheating and shutting things down. Clean things up and give it a try. Mine was doing that last week, once I cleaned the dust out it hasn't rebooted since .