hi there.
yea im just gonna wait till the new bored arrives. lucky im not paying for the bored its just for testing, well as soon as i get it im gonna reinstall win 7 and test everything.
will post updates as i go.
thanks again for your help
hi there me again.
well i got the new motherbored and replaced it. pc seems to be running alot faster and smoother.
i didnt reinstall windows i just kept it all the same. the main bored is the same as the other one.
so after running it for some time i got a BSOD again.
here is the info hopefully this points to somthing..
any suggestions, i thinking of reloding windows but just wanna know what was the cause of this BSOD.
anyways thanks for the help
Your Serial and USB drivers are out of date:Your RAID drivers are also pre-Windows 7 RTM:Code:BrFiltLo Brother USB Mass-Stora Kernel 2006/08/07 03:51:06 AM BrFiltUp Brother USB Mass-Stora Kernel 2006/08/07 03:51:02 AM Brserid Brother MFC Serial Por Kernel 2006/08/07 03:51:11 AM BrSerWdm Brother WDM Serial dri Kernel 2006/08/07 03:51:05 AM BrUsbMdm Brother MFC USB Fax On Kernel 2006/08/07 03:51:00 AM BrUsbSer Brother MFC USB Serial Kernel 2006/08/09 02:11:02 PMpPlease update those drivers. If the crashes persist, please enable driver verifier: Using Driver Verifier to identify issues with DriversCode:SiSRaid2 SiSRaid2 Kernel 2008/09/24 08:28:20 PM SiSRaid4 SiSRaid4 Kernel 2008/10/01 11:56:04 PM
Code:Microsoft (R) Windows Debugger Version 6.12.0002.633 AMD64 Copyright (c) Microsoft Corporation. All rights reserved. Loading Dump File [C:\Users\Jonathan\AppData\Local\Temp\Temp3_Seven Forums.zip\Seven Forums\062710-22588-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 7 Kernel Version 7600 MP (4 procs) Free x64 Product: WinNt, suite: TerminalServer SingleUserTS Built by: 7600.16539.amd64fre.win7_gdr.100226-1909 Machine Name: Kernel base = 0xfffff800`02c4e000 PsLoadedModuleList = 0xfffff800`02e8be50 Debug session time: Sat Jun 26 18:04:42.269 2010 (UTC - 4:00) System Uptime: 0 days 3:30:50.768 Loading Kernel Symbols ............................................................... ................................................................ ..................... Loading User Symbols Loading unloaded module list .... ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* Use !analyze -v to get detailed debugging information. BugCheck 3B, {c0000005, fffff80002c91603, fffff88006e4d0c0, 0} Probably caused by : memory_corruption ( nt!MmCleanProcessAddressSpace+f7 ) Followup: MachineOwner --------- 3: kd> !analyze -v ******************************************************************************* * * * 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: fffff80002c91603, Address of the instruction which caused the bugcheck Arg3: fffff88006e4d0c0, 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: nt!MmCleanProcessAddressSpace+f7 fffff800`02c91603 498b442420 mov rax,qword ptr [r12+20h] CONTEXT: fffff88006e4d0c0 -- (.cxr 0xfffff88006e4d0c0) rax=fffffa800a1a8d00 rbx=ffffffffffffffff rcx=fffff880033d5d00 rdx=8000000000000000 rsi=fffffa8006ceb060 rdi=fffffa800aaff370 rip=fffff80002c91603 rsp=fffff88006e4da90 rbp=0000000000000001 r8=0007ffffffffffff r9=0000000000000090 r10=fffff80002c4e000 r11=00000000000006e3 r12=0000000000000000 r13=0000000000000001 r14=0000000000037fff r15=0000000000000001 iopl=0 nv up ei pl nz na po nc cs=0010 ss=0018 ds=002b es=002b fs=0053 gs=002b efl=00010206 nt!MmCleanProcessAddressSpace+0xf7: fffff800`02c91603 498b442420 mov rax,qword ptr [r12+20h] ds:002b:00000000`00000020=???????????????? Resetting default scope CUSTOMER_CRASH_COUNT: 1 DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT BUGCHECK_STR: 0x3B PROCESS_NAME: firefox.exe CURRENT_IRQL: 0 LAST_CONTROL_TRANSFER: from fffff80002fa4c4f to fffff80002c91603 STACK_TEXT: fffff880`06e4da90 fffff800`02fa4c4f : fffff8a0`0b4f8a10 00000000`00000001 00000000`00000000 fffffa80`0aaff370 : nt!MmCleanProcessAddressSpace+0xf7 fffff880`06e4dae0 fffff800`02f7c6eb : 00000000`00000000 00000000`00000001 00000000`7efdb000 00000000`00000000 : nt!PspExitThread+0x92f fffff880`06e4dba0 fffff800`02cbd853 : fffffa80`06ceb060 00000000`00000000 00000000`7efdb001 fffffa80`0aaff370 : nt!NtTerminateProcess+0x25b fffff880`06e4dc20 00000000`76d6017a : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13 00000000`001cdf08 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x76d6017a FOLLOWUP_IP: nt!MmCleanProcessAddressSpace+f7 fffff800`02c91603 498b442420 mov rax,qword ptr [r12+20h] SYMBOL_STACK_INDEX: 0 SYMBOL_NAME: nt!MmCleanProcessAddressSpace+f7 FOLLOWUP_NAME: MachineOwner MODULE_NAME: nt DEBUG_FLR_IMAGE_TIMESTAMP: 4b88cfeb STACK_COMMAND: .cxr 0xfffff88006e4d0c0 ; kb IMAGE_NAME: memory_corruption FAILURE_BUCKET_ID: X64_0x3B_nt!MmCleanProcessAddressSpace+f7 BUCKET_ID: X64_0x3B_nt!MmCleanProcessAddressSpace+f7 Followup: MachineOwner ---------
Hey, I read your original posts and just wanted to share an experience regarding memory.
I recently added memory to an old machine and started seeing problems. I did not correlate the two for several days. The problem was not obvious until it hung in SETUP mode.
Then, I pulled the new memory and my machine started working fine again. The problem stems from the memory maker did not correctly detecting my motherboard and causing the wrong memory to be purchased. The problem was such that I crashed occasionally and sometimes often, but not consistently.
Scrutenize your memory compatibility on any upgrade on an older PC. The same could be said for other system components.
thanks for the reply Jonathan_King,
in regards to the drivers that are out dated, i dont know where to find other drivers, the ones im using i installed from MSI, the latest 64bit drivers they got.
anyways here are a few more dump files.
im getting to the point i dont know what else to do, iv replace everything except the prossesor and power surply.
Last edited by Nightfox; 08 Jul 2010 at 10:27.
It appears that you are running RAID.
Do you know what it is? If not, read this article: RAID - Wikipedia, the free encyclopedia
Basically, it is multiple hard drives functioning as a single one, for backup or performance reasons.
Please disconnect one drive...leave only one attached. Set your SATA setting in your BIOS to "AHCI" or "non-RAID", which is the same as "IDE".
Your mouse drivers appear to be out of date. Do you have a standard mouse you can use instead? If not, please update the drivers for it....Summary of the Dumps:Code:Alpham164.sys Mon Jul 23 03:57:03 2007 Alpham264.sys Tue Mar 20 05:51:03 2007Code:Built by: 7600.16539.amd64fre.win7_gdr.100226-1909 Debug session time: Mon Jun 28 13:00:39.515 2010 (UTC - 4:00) System Uptime: 0 days 0:00:11.013 BugCheck 1000007E, {ffffffffc0000005, fffff80002c86786, fffff880037168a8, fffff88003716110} Probably caused by : memory_corruption ( nt!MiProcessWorkingSets+c6 ) PROCESS_NAME: System BUGCHECK_STR: 0x7E จจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจ Built by: 7600.16539.amd64fre.win7_gdr.100226-1909 Debug session time: Sat Jun 26 18:04:42.269 2010 (UTC - 4:00) System Uptime: 0 days 3:30:50.768 BugCheck 3B, {c0000005, fffff80002c91603, fffff88006e4d0c0, 0} Probably caused by : memory_corruption ( nt!MmCleanProcessAddressSpace+f7 ) BUGCHECK_STR: 0x3B PROCESS_NAME: firefox.exe จจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจ Built by: 7600.16539.amd64fre.win7_gdr.100226-1909 Debug session time: Mon Jul 5 12:15:58.797 2010 (UTC - 4:00) System Uptime: 0 days 0:05:23.296 BugCheck 3B, {c0000005, fffff80002c7f90b, fffff8800a333e60, 0} Probably caused by : ntkrnlmp.exe ( nt!ExQueryPoolUsage+e0 ) BUGCHECK_STR: 0x3B PROCESS_NAME: svchost.exe จจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจ Built by: 7600.16539.amd64fre.win7_gdr.100226-1909 Debug session time: Mon Jul 5 12:09:51.926 2010 (UTC - 4:00) System Uptime: 0 days 0:38:06.050 BugCheck 3B, {c0000005, fffff88004832537, fffff8800aa1fa90, 0} Probably caused by : dxgmms1.sys ( dxgmms1!VIDMM_SEGMENT::TrimAllProcesses+10b ) BUGCHECK_STR: 0x3B PROCESS_NAME: Wow.exe จจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจ Built by: 7600.16539.amd64fre.win7_gdr.100226-1909 Debug session time: Sat Jul 3 10:02:09.621 2010 (UTC - 4:00) System Uptime: 0 days 1:37:15.119 BugCheck 1A, {5003, fffff70001080000, 5b8a, 5b8c00009714} Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+21b86 ) BUGCHECK_STR: 0x1a_5003 PROCESS_NAME: svchost.exe จจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจ Built by: 7600.16539.amd64fre.win7_gdr.100226-1909 Debug session time: Tue Jun 29 12:19:06.674 2010 (UTC - 4:00) System Uptime: 0 days 0:55:32.798 *** WARNING: Unable to verify timestamp for iaStor.sys *** ERROR: Module load completed but symbols could not be loaded for iaStor.sys BugCheck 1000007E, {ffffffffc0000005, fffff880014e33c2, fffff88003b477a8, fffff88003b47010} Probably caused by : iaStor.sys ( iaStor+6c3c2 ) PROCESS_NAME: System BUGCHECK_STR: 0x7E จจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจ
hi Jonathan
yea i am using raid, been using it all along, got 2 160 gig drives in raid.
im gonna be rather sad if thats the problem!
the mouse is a gamining mouse but i havent installed the drivers i let win 7 detect them.
You may consider installing the mouse drivers from the manufacturer, instead of generic Windows drivers.
I can understand about the RAID. Let's just break the array temporarily. If it turns out that the mouse drivers are the problem, go ahead and restore it, and see what happens.
hey guys,
its been a while since i posted anything here,
i managed to get the box stable for some time by replacing main bored a few times as well as mem. now after a few months of stability i wanted to go back to win 7 64bit and so i did. im now on the 64bit and the pc was running well for a few days, today i got 2 BSOD so now im thinking this ant hardware ( well at least i hope)
can you check the bumps and see if anything seems off
thanks
installed who crashed and got the following,
On Wed 2011/11/02 07:55:32 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\110211-21840-01.dmp
This was probably caused by the following module: tcpip.sys (tcpip+0x5DF1A)
Bugcheck code: 0x1E (0x0, 0x0, 0x0, 0x0)
Error: KMODE_EXCEPTION_NOT_HANDLED
file path: C:\Windows\system32\drivers\tcpip.sys
product: Microsoftฎ Windowsฎ Operating System
company: Microsoft Corporation
description: TCP/IP Driver
Bug check description: This indicates that a kernel-mode program generated an exception which the error handler did not catch.
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 a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system which cannot be identified at this time.
On Wed 2011/11/02 07:55:32 PM GMT your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: lachesis.sys (Lachesis+0xF44)
Bugcheck code: 0x1E (0x0, 0x0, 0x0, 0x0)
Error: KMODE_EXCEPTION_NOT_HANDLED
file path: C:\Windows\system32\drivers\lachesis.sys
product: Lachesis USB Optical Mouse
company: Razer (Asia-Pacific) Pte Ltd
description: Lachesis USB Optical Mouse Driver
Bug check description: This indicates that a kernel-mode program generated an exception which the error handler did not catch.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
A third party driver was identified as the probable root cause of this system error. It is suggested you look for an update for the following driver: lachesis.sys (Lachesis USB Optical Mouse Driver, Razer (Asia-Pacific) Pte Ltd).
Google query: lachesis.sys Razer (Asia-Pacific) Pte Ltd KMODE_EXCEPTION_NOT_HANDLED
On Wed 2011/11/02 07:09:17 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\110211-30560-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7CC40)
Bugcheck code: 0xA (0x42, 0x2, 0x1, 0xFFFFF80002AB763C)
Error: IRQL_NOT_LESS_OR_EQUAL
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoftฎ Windowsฎ Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that Microsoft Windows or a kernel-mode driver accessed paged memory at DISPATCH_LEVEL or above.
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.
so im guessing my mouse driver for the lachesis.sys error. so gonna install the latest ones i can find. as to the tcpip.sys that looks like networks so gonna install latest network drives.
now the ntoskrnl.exe that i dont know what it is, so any advice plz??
Quote