Have you run the Windows 7 Upgrade Advisor? http://www.google.com/url?sa=t&sourc...VHyEPZ-QyeM05A
Install and run it to make sure that all of your hardware is compatible with Windows 7. If not that, it's most likely an out-of-place driver. We'll cross that bridge when we come to it.
I'm suspicious of rams (2x1 gb 800 mhz kingston). How can I test them?
Mine has done this the past 3 days in a row. Only once a day but crashes and then dumps to memory. Not sure what changed and what is causing the problems.
Please any advice would be great.
-Grant
Could you please upload the actual dmp files for us?
Copy the files from C:\Windows\Minidump to the desktop. Select all of them, and right-click>send to>compressed folder.
On your next post, in the editing bar, you will see a paperclip icon. Click on that, and upload the zip folder.
Here is the DT diags that you mentioned in another post. Not sure if this is the same information or not.
Nope, we need the actual dmp files. If you like, you can also use the SF Diagnostic Tool to help you gather the dmps.
Here you go. Let me know if you need anything else.
It looks as if your USB to Serial port driver is causing the issue. I suggest removing it, and see what happens.
Code:Microsoft (R) Windows Debugger Version 6.11.0001.404 AMD64 Copyright (c) Microsoft Corporation. All rights reserved. Loading Dump File [C:\Users\Jonathan\Desktop\041710-32229-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 (2 procs) Free x64 Product: WinNt, suite: TerminalServer SingleUserTS Built by: 7600.16539.amd64fre.win7_gdr.100226-1909 Machine Name: Kernel base = 0xfffff800`02c5b000 PsLoadedModuleList = 0xfffff800`02e98e50 Debug session time: Sat Apr 17 11:57:29.613 2010 (GMT-4) System Uptime: 2 days 11:35:54.564 Loading Kernel Symbols ............................................................... ................................................................ ................................................................ .............. Loading User Symbols Loading unloaded module list ................................................. ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* Use !analyze -v to get detailed debugging information. BugCheck 44, {fffffa8008443330, eae, 0, 0} Unable to load image \SystemRoot\system32\DRIVERS\ser2pl64.sys, Win32 error 0n2 *** WARNING: Unable to verify timestamp for ser2pl64.sys *** ERROR: Module load completed but symbols could not be loaded for ser2pl64.sys Probably caused by : ser2pl64.sys ( ser2pl64+7a71 ) Followup: MachineOwner --------- 0: kd> !analyze -v ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* MULTIPLE_IRP_COMPLETE_REQUESTS (44) A driver has requested that an IRP be completed (IoCompleteRequest()), but the packet has already been completed. This is a tough bug to find because the easiest case, a driver actually attempted to complete its own packet twice, is generally not what happened. Rather, two separate drivers each believe that they own the packet, and each attempts to complete it. The first actually works, and the second fails. Tracking down which drivers in the system actually did this is difficult, generally because the trails of the first driver have been covered by the second. However, the driver stack for the current request can be found by examining the DeviceObject fields in each of the stack locations. Arguments: Arg1: fffffa8008443330, Address of the IRP Arg2: 0000000000000eae Arg3: 0000000000000000 Arg4: 0000000000000000 Debugging Details: ------------------ IRP_ADDRESS: fffffa8008443330 CUSTOMER_CRASH_COUNT: 1 DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT BUGCHECK_STR: 0x44 PROCESS_NAME: System CURRENT_IRQL: 2 DEVICE_OBJECT: fffffa80073da070 LAST_CONTROL_TRANSFER: from fffff80002cb5235 to fffff80002ccb600 STACK_TEXT: fffff800`00b9c1d8 fffff800`02cb5235 : 00000000`00000044 fffffa80`08443330 00000000`00000eae 00000000`00000000 : nt!KeBugCheckEx fffff800`00b9c1e0 fffff880`00e31a52 : 00000000`00000000 fffffa80`03fb5260 00000000`00000001 00000000`00000000 : nt! ?? ::FNODOBFM::`string'+0x3ecbe fffff800`00b9c2c0 fffff880`00e2213e : fffffa80`08443330 fffff800`00000001 00000000`00000002 fffffa80`08443330 : Wdf01000!FxRequest::CompleteInternal+0x646 fffff800`00b9c370 fffff880`05941a71 : fffffa80`0ae23400 fffffa80`0b48d5c0 fffffa80`0ae23400 0000057f`f4b72a38 : Wdf01000!imp_WdfRequestCompleteWithInformation+0x1aa fffff800`00b9c3e0 fffffa80`0ae23400 : fffffa80`0b48d5c0 fffffa80`0ae23400 0000057f`f4b72a38 fffffa80`0ae23390 : ser2pl64+0x7a71 fffff800`00b9c3e8 fffffa80`0b48d5c0 : fffffa80`0ae23400 0000057f`f4b72a38 fffffa80`0ae23390 fffff880`05941b61 : 0xfffffa80`0ae23400 fffff800`00b9c3f0 fffffa80`0ae23400 : 0000057f`f4b72a38 fffffa80`0ae23390 fffff880`05941b61 fffffa80`0b48d750 : 0xfffffa80`0b48d5c0 fffff800`00b9c3f8 0000057f`f4b72a38 : fffffa80`0ae23390 fffff880`05941b61 fffffa80`0b48d750 00000000`00000000 : 0xfffffa80`0ae23400 fffff800`00b9c400 fffffa80`0ae23390 : fffff880`05941b61 fffffa80`0b48d750 00000000`00000000 fffffa80`0ae23400 : 0x57f`f4b72a38 fffff800`00b9c408 fffff880`05941b61 : fffffa80`0b48d750 00000000`00000000 fffffa80`0ae23400 fffffa80`08850cc0 : 0xfffffa80`0ae23390 fffff800`00b9c410 fffffa80`0b48d750 : 00000000`00000000 fffffa80`0ae23400 fffffa80`08850cc0 fffffa80`0ae23390 : ser2pl64+0x7b61 fffff800`00b9c418 00000000`00000000 : fffffa80`0ae23400 fffffa80`08850cc0 fffffa80`0ae23390 fffffa80`0757b5e8 : 0xfffffa80`0b48d750 STACK_COMMAND: kb FOLLOWUP_IP: ser2pl64+7a71 fffff880`05941a71 ?? ??? SYMBOL_STACK_INDEX: 4 SYMBOL_NAME: ser2pl64+7a71 FOLLOWUP_NAME: MachineOwner MODULE_NAME: ser2pl64 IMAGE_NAME: ser2pl64.sys DEBUG_FLR_IMAGE_TIMESTAMP: 4a604108 FAILURE_BUCKET_ID: X64_0x44_ser2pl64+7a71 BUCKET_ID: X64_0x44_ser2pl64+7a71 Followup: MachineOwner ---------
Quote