Windows 7 Win7 box crashing/locking up - BSOD

berryguru · Jul 29, 2010

I'm looking for some guidance on an issue with my Windows 7 box. My system is crashing once a week or a few times a month. I can't exactly pinpoint why, as the logs only show the crash after.

Logs indicate the following:
-------------------------------------------------------------------------------------
Level: Critical
Source: Kernal Power
Event ID: 41
User: System

The system has rebooted without cleanly shutting down first. This error could be caused if the system stopped responding, crashed, or lost power unexpectedly.
-------------------------------------------------------------------------------------
Level: Error
Source: Bug Check
Event ID: 1001
User: N/A

The computer has rebooted from a bugcheck. The bugcheck was: 0x0000007e (0xffffffffc0000005, 0xfffff80002a83324, 0xfffff880031c3e68, 0xfffff880031c36d0). A dump was saved in: C:\Windows\MEMORY.DMP. Report Id: 072710-17362-01.
-------------------------------------------------------------------------------------
I was thinking maybe my video cards were overheating. But they run between 59C - 62C. I'm running 3 120mm fans (2 in the front and 1 in the rear)

When I return to my machine I find it locked up at the screensaver. So I reboot the machine but it returns with a BSOD and attempts to do a memory dump. I'll have to reboot the machine 3 to 4 times before it will boot fully into Windows.

Machine Specs:
Processor: Intel Quad Q6700 @ 2.66GHz
Memory: 8GB DDR2 Corsair XMS
Video: Dual Nvidia GeForce 8600 GT
Hard Drive: 1 - 150GB Raptor, 2 - 500GB Seagate
Power Supply: Antec 650Watt

Any thoughts?

~berry

TorrentG · Jul 30, 2010

Since you're interested, here are your crash dumps in plain view. The first one has drivers shown. The other does not, because it would be redundant for me to list drivers in both. Fortunately for you, this is a rather easy one to solve.

Code:

Microsoft (R) Windows Debugger Version 6.12.0002.633 X86
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [E:\Temp\Rar$DI00.440\072710-17362-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*C:\SymCache*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...

TorrentG · Jul 29, 2010

Hey.

Please go to C:\Windows\Minidump

Copy and paste the files from there to any other folder. Then zip them. Attach the zip to a post using the paperclip above where you type, in advanced mode reply. We can have a look and fix this for you.

If there is no such folder or there are no files in it, then please follow this to set Windows and wait for the next crash to happen:

http://www.sevenforums.com/686577-post4.html

Athlonite · Jul 29, 2010

I was just reading about this same problem just yesterday and alot of people seam to think that old realtek drivers are most at fault for this and TorrentG also suggests that AVG is also an major cause of this fault aswell

berryguru · Jul 30, 2010

heya guys!

Thanks so much for the quick reply!

I've attached the files you mentioned. I zipped the last 2 .dmp files.

How are you guys opening these .dmp files? I'd like to take a look myself too. The resolution is starting to look promising!

Thanks again!

~berry

TorrentG · Jul 30, 2010

Since you're interested, here are your crash dumps in plain view. The first one has drivers shown. The other does not, because it would be redundant for me to list drivers in both. Fortunately for you, this is a rather easy one to solve.

Code:

Microsoft (R) Windows Debugger Version 6.12.0002.633 X86
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [E:\Temp\Rar$DI00.440\072710-17362-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*C:\SymCache*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`02a07000 PsLoadedModuleList = 0xfffff800`02c44e50
Debug session time: Tue Jul 27 10:26:06.243 2010 (UTC - 4:00)
System Uptime: 0 days 0:00:15.929
Loading Kernel Symbols
...............................................................
................................................................
.......
Loading User Symbols
Loading unloaded module list
....
Unable to load image \SystemRoot\system32\drivers\ftdibus.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for ftdibus.sys
*** ERROR: Module load completed but symbols could not be loaded for ftdibus.sys
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 1000007E, {ffffffffc0000005, fffff80002a83324, fffff880031c3e68, fffff880031c36d0}

Probably caused by : ftdibus.sys ( ftdibus+85fb )

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

1: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M (1000007e)
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.
Arguments:
Arg1: ffffffffc0000005, The exception code that was not handled
Arg2: fffff80002a83324, The address that the exception occurred at
Arg3: fffff880031c3e68, Exception Record Address
Arg4: fffff880031c36d0, Context Record Address

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!IofCallDriver+14
fffff800`02a83324 fe4a43          dec     byte ptr [rdx+43h]

EXCEPTION_RECORD:  fffff880031c3e68 -- (.exr 0xfffff880031c3e68)
ExceptionAddress: fffff80002a83324 (nt!IofCallDriver+0x0000000000000014)
   ExceptionCode: c0000005 (Access violation)
  ExceptionFlags: 00000000
NumberParameters: 2
   Parameter[0]: 0000000000000001
   Parameter[1]: 0000000000000043
Attempt to write to address 0000000000000043

CONTEXT:  fffff880031c36d0 -- (.cxr 0xfffff880031c36d0)
rax=0000000000000000 rbx=fffffa8015e00000 rcx=fffffa8008180050
rdx=0000000000000000 rsi=00000000fffff88a rdi=00000000fffff88a
rip=fffff80002a83324 rsp=fffff880031c40a0 rbp=fffffa8008180050
 r8=fffffa8008188e10  r9=fffff880009e6180 r10=fffffa8006a13430
r11=fffffa800817ae10 r12=0000000000000006 r13=0000000000000008
r14=fffffa8008180050 r15=0000000000000001
iopl=0         nv up ei pl zr na po nc
cs=0010  ss=0018  ds=002b  es=002b  fs=0053  gs=002b             efl=00010246
nt!IofCallDriver+0x14:
fffff800`02a83324 fe4a43          dec     byte ptr [rdx+43h] ds:002b:00000000`00000043=??
Resetting default scope

CUSTOMER_CRASH_COUNT:  1

PROCESS_NAME:  System

CURRENT_IRQL:  0

ERROR_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.

EXCEPTION_PARAMETER1:  0000000000000001

EXCEPTION_PARAMETER2:  0000000000000043

WRITE_ADDRESS: GetPointerFromAddress: unable to read from fffff80002caf0e0
 0000000000000043 

FOLLOWUP_IP: 
ftdibus+85fb
fffff880`04f925fb ??              ???

BUGCHECK_STR:  0x7E

DEFAULT_BUCKET_ID:  NULL_CLASS_PTR_DEREFERENCE

LAST_CONTROL_TRANSFER:  from fffff88004f925fb to fffff80002a83324

STACK_TEXT:  
fffff880`031c40a0 fffff880`04f925fb : fffffa80`15e00000 fffffa80`08180050 fffffa80`15e00000 fffff880`04b9a2d9 : nt!IofCallDriver+0x14
fffff880`031c40d0 fffffa80`15e00000 : fffffa80`08180050 fffffa80`15e00000 fffff880`04b9a2d9 fffffa80`15e00000 : ftdibus+0x85fb
fffff880`031c40d8 fffffa80`08180050 : fffffa80`15e00000 fffff880`04b9a2d9 fffffa80`15e00000 fffffa80`fffff88a : 0xfffffa80`15e00000
fffff880`031c40e0 fffffa80`15e00000 : fffff880`04b9a2d9 fffffa80`15e00000 fffffa80`fffff88a fffffa80`00000100 : 0xfffffa80`08180050
fffff880`031c40e8 fffff880`04b9a2d9 : fffffa80`15e00000 fffffa80`fffff88a fffffa80`00000100 fffff880`031c4120 : 0xfffffa80`15e00000
fffff880`031c40f0 fffff880`00000006 : fffffa80`08d171b0 ffff0000`07e52a78 fffffa80`08d5e790 00000000`00000006 : usbhub!UsbhFdoDeviceControl+0x1a5
fffff880`031c4150 fffffa80`08d171b0 : ffff0000`07e52a78 fffffa80`08d5e790 00000000`00000006 fffffa80`08d56410 : 0xfffff880`00000006
fffff880`031c4158 ffff0000`07e52a78 : fffffa80`08d5e790 00000000`00000006 fffffa80`08d56410 fffff880`04f928b7 : 0xfffffa80`08d171b0
fffff880`031c4160 fffffa80`08d5e790 : 00000000`00000006 fffffa80`08d56410 fffff880`04f928b7 fffffa80`08d171b0 : 0xffff0000`07e52a78
fffff880`031c4168 00000000`00000006 : fffffa80`08d56410 fffff880`04f928b7 fffffa80`08d171b0 fffffa80`08180050 : 0xfffffa80`08d5e790
fffff880`031c4170 fffffa80`08d56410 : fffff880`04f928b7 fffffa80`08d171b0 fffffa80`08180050 fffffa80`08d171b0 : 0x6
fffff880`031c4178 fffff880`04f928b7 : fffffa80`08d171b0 fffffa80`08180050 fffffa80`08d171b0 00000000`00000000 : 0xfffffa80`08d56410
fffff880`031c4180 fffffa80`08d171b0 : fffffa80`08180050 fffffa80`08d171b0 00000000`00000000 fffffa80`08d5e790 : ftdibus+0x88b7
fffff880`031c4188 fffffa80`08180050 : fffffa80`08d171b0 00000000`00000000 fffffa80`08d5e790 fffffa80`0000016d : 0xfffffa80`08d171b0
fffff880`031c4190 fffffa80`08d171b0 : 00000000`00000000 fffffa80`08d5e790 fffffa80`0000016d 00000000`00000000 : 0xfffffa80`08180050
fffff880`031c4198 00000000`00000000 : fffffa80`08d5e790 fffffa80`0000016d 00000000`00000000 fffff880`031c4208 : 0xfffffa80`08d171b0


SYMBOL_STACK_INDEX:  1

SYMBOL_NAME:  ftdibus+85fb

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: ftdibus

IMAGE_NAME:  ftdibus.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  46826082

STACK_COMMAND:  .cxr 0xfffff880031c36d0 ; kb

FAILURE_BUCKET_ID:  X64_0x7E_ftdibus+85fb

BUCKET_ID:  X64_0x7E_ftdibus+85fb

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

1: kd> lm tn 
start             end                 module name
fffff800`00bcd000 fffff800`00bd7000   kdcom    kdcom.dll    Mon Jul 13 21:31:07 2009 (4A5BDFDB)
fffff800`02a07000 fffff800`02fe3000   nt       ntkrnlmp.exe Sat Feb 27 02:55:23 2010 (4B88CFEB)
fffff800`02fe3000 fffff800`0302c000   hal      hal.dll      Mon Jul 13 21:27:36 2009 (4A5BDF08)
fffff880`00c00000 fffff880`00c5c000   volmgrx  volmgrx.sys  Mon Jul 13 19:20:33 2009 (4A5BC141)
fffff880`00c5c000 fffff880`00c6c000   PCIIDEX  PCIIDEX.SYS  Mon Jul 13 19:19:48 2009 (4A5BC114)
fffff880`00c6c000 fffff880`00c95000   nvraid   nvraid.sys   Wed May 20 02:39:40 2009 (4A13A5AC)
fffff880`00c95000 fffff880`00caf000   mountmgr mountmgr.sys Mon Jul 13 19:19:54 2009 (4A5BC11A)
fffff880`00caf000 fffff880`00cf3000   mcupdate_GenuineIntel mcupdate_GenuineIntel.dll Mon Jul 13 21:29:10 2009 (4A5BDF66)
fffff880`00cf3000 fffff880`00d07000   PSHED    PSHED.dll    Mon Jul 13 21:32:23 2009 (4A5BE027)
fffff880`00d07000 fffff880`00d65000   CLFS     CLFS.SYS     Mon Jul 13 19:19:57 2009 (4A5BC11D)
fffff880`00d65000 fffff880`00d98000   pci      pci.sys      Mon Jul 13 19:19:51 2009 (4A5BC117)
fffff880`00d98000 fffff880`00dad000   partmgr  partmgr.sys  Mon Jul 13 19:19:58 2009 (4A5BC11E)
fffff880`00dad000 fffff880`00db9000   BATTC    BATTC.SYS    Mon Jul 13 19:31:01 2009 (4A5BC3B5)
fffff880`00db9000 fffff880`00dce000   volmgr   volmgr.sys   Mon Jul 13 19:19:57 2009 (4A5BC11D)
fffff880`00dce000 fffff880`00dfe000   CLASSPNP CLASSPNP.SYS Mon Jul 13 19:19:58 2009 (4A5BC11E)
fffff880`00e00000 fffff880`00e09000   compbatt compbatt.sys Mon Jul 13 19:31:02 2009 (4A5BC3B6)
fffff880`00e09000 fffff880`00e10000   pciide   pciide.sys   Mon Jul 13 19:19:49 2009 (4A5BC115)
fffff880`00e11000 fffff880`00ed1000   CI       CI.dll       Mon Jul 13 21:32:13 2009 (4A5BE01D)
fffff880`00ed1000 fffff880`00f75000   Wdf01000 Wdf01000.sys Mon Jul 13 19:22:07 2009 (4A5BC19F)
fffff880`00f75000 fffff880`00f84000   WDFLDR   WDFLDR.SYS   Mon Jul 13 19:19:54 2009 (4A5BC11A)
fffff880`00f84000 fffff880`00fdb000   ACPI     ACPI.sys     Mon Jul 13 19:19:34 2009 (4A5BC106)
fffff880`00fdb000 fffff880`00fe4000   WMILIB   WMILIB.SYS   Mon Jul 13 19:19:51 2009 (4A5BC117)
fffff880`00fe4000 fffff880`00fee000   msisadrv msisadrv.sys Mon Jul 13 19:19:26 2009 (4A5BC0FE)
fffff880`00fee000 fffff880`00ffb000   vdrvroot vdrvroot.sys Mon Jul 13 20:01:31 2009 (4A5BCADB)
fffff880`01000000 fffff880`0105e000   msrpc    msrpc.sys    Mon Jul 13 19:21:32 2009 (4A5BC17C)
fffff880`0105e000 fffff880`0107c000   tdx      tdx.sys      Mon Jul 13 19:21:15 2009 (4A5BC16B)
fffff880`0107f000 fffff880`01088000   atapi    atapi.sys    Mon Jul 13 19:19:47 2009 (4A5BC113)
fffff880`01088000 fffff880`010b2000   ataport  ataport.SYS  Mon Jul 13 19:19:52 2009 (4A5BC118)
fffff880`010b2000 fffff880`010dd000   nvstor   nvstor.sys   Wed May 20 02:45:37 2009 (4A13A711)
fffff880`010dd000 fffff880`0113f000   storport storport.sys Mon Jul 13 20:01:18 2009 (4A5BCACE)
fffff880`0113f000 fffff880`0114a000   msahci   msahci.sys   Mon Jul 13 20:01:01 2009 (4A5BCABD)
fffff880`0114a000 fffff880`01155000   amdxata  amdxata.sys  Tue May 19 13:56:59 2009 (4A12F2EB)
fffff880`01155000 fffff880`011a1000   fltmgr   fltmgr.sys   Mon Jul 13 19:19:59 2009 (4A5BC11F)
fffff880`011a1000 fffff880`011b5000   fileinfo fileinfo.sys Mon Jul 13 19:34:25 2009 (4A5BC481)
fffff880`011b5000 fffff880`011da000   VIDEOPRT VIDEOPRT.SYS Mon Jul 13 19:38:51 2009 (4A5BC58B)
fffff880`011da000 fffff880`011eb000   Npfs     Npfs.SYS     Mon Jul 13 19:19:48 2009 (4A5BC114)
fffff880`011eb000 fffff880`011f8000   TDI      TDI.SYS      Mon Jul 13 19:21:18 2009 (4A5BC16E)
fffff880`01200000 fffff880`01209000   rdpencdd rdpencdd.sys Mon Jul 13 20:16:34 2009 (4A5BCE62)
fffff880`01209000 fffff880`01212000   rdprefmp rdprefmp.sys Mon Jul 13 20:16:35 2009 (4A5BCE63)
fffff880`01212000 fffff880`0121d000   Msfs     Msfs.SYS     Mon Jul 13 19:19:47 2009 (4A5BC113)
fffff880`0121d000 fffff880`013c0000   Ntfs     Ntfs.sys     Mon Jul 13 19:20:47 2009 (4A5BC14F)
fffff880`013c0000 fffff880`013da000   ksecdd   ksecdd.sys   Mon Jul 13 19:20:54 2009 (4A5BC156)
fffff880`013da000 fffff880`013e8000   vga      vga.sys      Mon Jul 13 19:38:47 2009 (4A5BC587)
fffff880`013e8000 fffff880`013f8000   watchdog watchdog.sys Mon Jul 13 19:37:35 2009 (4A5BC53F)
fffff880`01400000 fffff880`0142a000   cdrom    cdrom.sys    Mon Jul 13 19:19:54 2009 (4A5BC11A)
fffff880`0142a000 fffff880`01431000   Beep     Beep.SYS     Mon Jul 13 20:00:13 2009 (4A5BCA8D)
fffff880`01431000 fffff880`0143a000   RDPCDD   RDPCDD.sys   Mon Jul 13 20:16:34 2009 (4A5BCE62)
fffff880`0143d000 fffff880`014b0000   cng      cng.sys      Mon Jul 13 19:49:40 2009 (4A5BC814)
fffff880`014b0000 fffff880`014c1000   pcw      pcw.sys      Mon Jul 13 19:19:27 2009 (4A5BC0FF)
fffff880`014c1000 fffff880`014cb000   Fs_Rec   Fs_Rec.sys   Mon Jul 13 19:19:45 2009 (4A5BC111)
fffff880`014cb000 fffff880`015bd000   ndis     ndis.sys     Mon Jul 13 19:21:40 2009 (4A5BC184)
fffff880`01618000 fffff880`01621000   Null     Null.SYS     Mon Jul 13 19:19:37 2009 (4A5BC109)
fffff880`01622000 fffff880`01682000   NETIO    NETIO.SYS    Mon Jul 13 19:21:46 2009 (4A5BC18A)
fffff880`01682000 fffff880`016ad000   ksecpkg  ksecpkg.sys  Fri Dec 11 01:03:32 2009 (4B21E0B4)
fffff880`016ad000 fffff880`016f7000   fwpkclnt fwpkclnt.sys Mon Jul 13 19:21:08 2009 (4A5BC164)
fffff880`016f7000 fffff880`01707000   vmstorfl vmstorfl.sys Mon Jul 13 19:42:54 2009 (4A5BC67E)
fffff880`01707000 fffff880`01753000   volsnap  volsnap.sys  Mon Jul 13 19:20:08 2009 (4A5BC128)
fffff880`01753000 fffff880`0175b000   spldr    spldr.sys    Mon May 11 12:56:27 2009 (4A0858BB)
fffff880`0175b000 fffff880`01795000   rdyboost rdyboost.sys Mon Jul 13 19:34:34 2009 (4A5BC48A)
fffff880`01795000 fffff880`017a7000   mup      mup.sys      Mon Jul 13 19:23:45 2009 (4A5BC201)
fffff880`017a7000 fffff880`017b0000   hwpolicy hwpolicy.sys Mon Jul 13 19:19:22 2009 (4A5BC0FA)
fffff880`017b0000 fffff880`017ea000   fvevol   fvevol.sys   Mon Jul 13 19:22:15 2009 (4A5BC1A7)
fffff880`017ea000 fffff880`01800000   disk     disk.sys     Mon Jul 13 19:19:57 2009 (4A5BC11D)
fffff880`01802000 fffff880`019ff000   tcpip    tcpip.sys    Mon Jul 13 19:25:34 2009 (4A5BC26E)
fffff880`03e00000 fffff880`03e56180   vpcvmm   vpcvmm.sys   Tue Sep 22 21:32:38 2009 (4AB97AB6)
fffff880`03e57000 fffff880`03e6b000   termdd   termdd.sys   Mon Jul 13 20:16:36 2009 (4A5BCE64)
fffff880`03e6b000 fffff880`03ef5000   afd      afd.sys      Mon Jul 13 19:21:40 2009 (4A5BC184)
fffff880`03ef5000 fffff880`03f3a000   netbt    netbt.sys    Mon Jul 13 19:21:28 2009 (4A5BC178)
fffff880`03f3a000 fffff880`03f45000   ws2ifsl  ws2ifsl.sys  Mon Jul 13 20:10:33 2009 (4A5BCCF9)
fffff880`03f45000 fffff880`03f4e000   wfplwf   wfplwf.sys   Mon Jul 13 20:09:26 2009 (4A5BCCB6)
fffff880`03f4e000 fffff880`03f74000   pacer    pacer.sys    Mon Jul 13 20:09:41 2009 (4A5BCCC5)
fffff880`03f74000 fffff880`03f88000   vpcnfltr vpcnfltr.sys Tue Sep 22 21:32:30 2009 (4AB97AAE)
fffff880`03f88000 fffff880`03f97000   netbios  netbios.sys  Mon Jul 13 20:09:26 2009 (4A5BCCB6)
fffff880`03f97000 fffff880`03fb2000   wanarp   wanarp.sys   Mon Jul 13 20:10:21 2009 (4A5BCCED)
fffff880`03fb2000 fffff880`03fd3000   raspptp  raspptp.sys  Mon Jul 13 20:10:18 2009 (4A5BCCEA)
fffff880`03fd3000 fffff880`03fed000   rassstp  rassstp.sys  Mon Jul 13 20:10:25 2009 (4A5BCCF1)
fffff880`03fed000 fffff880`03ffc000   mouclass mouclass.sys Mon Jul 13 19:19:50 2009 (4A5BC116)
fffff880`04001000 fffff880`04052000   rdbss    rdbss.sys    Mon Jul 13 19:24:09 2009 (4A5BC219)
fffff880`04052000 fffff880`0405e000   nsiproxy nsiproxy.sys Mon Jul 13 19:21:02 2009 (4A5BC15E)
fffff880`0405e000 fffff880`04069000   mssmbios mssmbios.sys Mon Jul 13 19:31:10 2009 (4A5BC3BE)
fffff880`04069000 fffff880`04078000   discache discache.sys Mon Jul 13 19:37:18 2009 (4A5BC52E)
fffff880`04078000 fffff880`040fb000   csc      csc.sys      Mon Jul 13 19:24:26 2009 (4A5BC22A)
fffff880`040fb000 fffff880`04119000   dfsc     dfsc.sys     Mon Jul 13 19:23:44 2009 (4A5BC200)
fffff880`04119000 fffff880`0412a000   blbdrive blbdrive.sys Mon Jul 13 19:35:59 2009 (4A5BC4DF)
fffff880`0412a000 fffff880`04150000   tunnel   tunnel.sys   Mon Jul 13 20:09:37 2009 (4A5BCCC1)
fffff880`04150000 fffff880`04166000   intelppm intelppm.sys Mon Jul 13 19:19:25 2009 (4A5BC0FD)
fffff880`04166000 fffff880`041c9d80   nvm62x64 nvm62x64.sys Fri Oct 17 17:01:06 2008 (48F8FD12)
fffff880`041ca000 fffff880`041f9000   ndiswan  ndiswan.sys  Mon Jul 13 20:10:11 2009 (4A5BCCE3)
fffff880`04400000 fffff880`04456000   USBPORT  USBPORT.SYS  Mon Jul 13 20:06:31 2009 (4A5BCC07)
fffff880`04456000 fffff880`04457480   swenum   swenum.sys   Mon Jul 13 20:00:18 2009 (4A5BCA92)
fffff880`04458000 fffff880`0454c000   dxgkrnl  dxgkrnl.sys  Thu Oct 01 21:00:14 2009 (4AC5509E)
fffff880`0454c000 fffff880`04592000   dxgmms1  dxgmms1.sys  Mon Jul 13 19:38:32 2009 (4A5BC578)
fffff880`04592000 fffff880`045af000   serial   serial.sys   Mon Jul 13 20:00:40 2009 (4A5BCAA8)
fffff880`045af000 fffff880`045bb000   serenum  serenum.sys  Mon Jul 13 20:00:33 2009 (4A5BCAA1)
fffff880`045bb000 fffff880`045d8000   parport  parport.sys  Mon Jul 13 20:00:40 2009 (4A5BCAA8)
fffff880`045d8000 fffff880`045e3000   usbohci  usbohci.sys  Mon Jul 13 20:06:30 2009 (4A5BCC06)
fffff880`045e3000 fffff880`045f4000   usbehci  usbehci.sys  Mon Jul 13 20:06:30 2009 (4A5BCC06)
fffff880`045f4000 fffff880`04600000   ndistapi ndistapi.sys Mon Jul 13 20:10:00 2009 (4A5BCCD8)
fffff880`04a00000 fffff880`04a15000   NDProxy  NDProxy.SYS  Mon Jul 13 20:10:05 2009 (4A5BCCDD)
fffff880`04a15000 fffff880`04a71000   HdAudio  HdAudio.sys  Mon Jul 13 20:06:59 2009 (4A5BCC23)
fffff880`04a71000 fffff880`04aae000   portcls  portcls.sys  Mon Jul 13 20:06:27 2009 (4A5BCC03)
fffff880`04ac7000 fffff880`04b0a000   ks       ks.sys       Mon Jul 13 20:00:31 2009 (4A5BCA9F)
fffff880`04b0a000 fffff880`04b1c000   umbus    umbus.sys    Mon Jul 13 20:06:56 2009 (4A5BCC20)
fffff880`04b1c000 fffff880`04b39000   vpcusb   vpcusb.sys   Tue Sep 22 21:32:39 2009 (4AB97AB7)
fffff880`04b39000 fffff880`04b48000   usbrpm   usbrpm.sys   Mon Jul 13 20:35:14 2009 (4A5BD2C2)
fffff880`04b48000 fffff880`04b49f00   USBD     USBD.SYS     Mon Jul 13 20:06:23 2009 (4A5BCBFF)
fffff880`04b4a000 fffff880`04b52000   vmnetadapter vmnetadapter.sys Mon Aug 10 08:04:53 2009 (4A800CE5)
fffff880`04b52000 fffff880`04b5c000   VMNET    VMNET.SYS    Mon Aug 10 08:04:50 2009 (4A800CE2)
fffff880`04b5c000 fffff880`04b98000   vpchbus  vpchbus.sys  Tue Sep 22 21:32:32 2009 (4AB97AB0)
fffff880`04b98000 fffff880`04bf2000   usbhub   usbhub.sys   Mon Jul 13 20:07:09 2009 (4A5BCC2D)
fffff880`04ea8000 fffff880`04eca000   drmk     drmk.sys     Mon Jul 13 21:01:25 2009 (4A5BD8E5)
fffff880`04eca000 fffff880`04ecf200   ksthunk  ksthunk.sys  Mon Jul 13 20:00:19 2009 (4A5BCA93)
fffff880`04ed0000 fffff880`04ede000   crashdmp crashdmp.sys Mon Jul 13 20:01:01 2009 (4A5BCABD)
fffff880`04ede000 fffff880`04ee8000   dump_diskdump dump_diskdump.sys Mon Jul 13 20:01:00 2009 (4A5BCABC)
fffff880`04ee8000 fffff880`04f13000   dump_nvstor dump_nvstor.sys Wed May 20 02:45:37 2009 (4A13A711)
fffff880`04f13000 fffff880`04f26000   dump_dumpfve dump_dumpfve.sys Mon Jul 13 19:21:51 2009 (4A5BC18F)
fffff880`04f26000 fffff880`04f32000   Dxapi    Dxapi.sys    Mon Jul 13 19:38:28 2009 (4A5BC574)
fffff880`04f32000 fffff880`04f40000   hidusb   hidusb.sys   Mon Jul 13 20:06:22 2009 (4A5BCBFE)
fffff880`04f40000 fffff880`04f59000   HIDCLASS HIDCLASS.SYS Mon Jul 13 20:06:21 2009 (4A5BCBFD)
fffff880`04f59000 fffff880`04f61080   HIDPARSE HIDPARSE.SYS Mon Jul 13 20:06:17 2009 (4A5BCBF9)
fffff880`04f62000 fffff880`04f6d000   HidBatt  HidBatt.sys  Mon Jul 13 19:31:06 2009 (4A5BC3BA)
fffff880`04f6d000 fffff880`04f8a000   usbccgp  usbccgp.sys  Mon Jul 13 20:06:45 2009 (4A5BCC15)
fffff880`04f8a000 fffff880`04f98400   ftdibus  ftdibus.sys  Wed Jun 27 09:05:06 2007 (46826082)
fffff880`04f99000 fffff880`04fb0000   LEqdUsb  LEqdUsb.Sys  Wed Jun 17 12:49:54 2009 (4A391EB2)
fffff880`0fe00000 fffff880`0fe24000   rasl2tp  rasl2tp.sys  Mon Jul 13 20:10:11 2009 (4A5BCCE3)
fffff880`0fe24000 fffff880`0fe3f000   raspppoe raspppoe.sys Mon Jul 13 20:10:17 2009 (4A5BCCE9)
fffff880`0fe3f000 fffff880`0fe4a000   rdpbus   rdpbus.sys   Mon Jul 13 20:17:46 2009 (4A5BCEAA)
fffff880`0fe51000 fffff880`10b5ea00   nvlddmkm nvlddmkm.sys Fri Nov 20 22:40:46 2009 (4B07613E)
fffff880`10b5f000 fffff880`10b60180   nvBridge nvBridge.kmd Fri Nov 20 22:09:47 2009 (4B0759FB)
fffff880`10b61000 fffff880`10b9f000   1394ohci 1394ohci.sys Mon Jul 13 20:07:12 2009 (4A5BCC30)
fffff880`10b9f000 fffff880`10bc3000   HDAudBus HDAudBus.sys Mon Jul 13 20:06:13 2009 (4A5BCBF5)
fffff880`10bc3000 fffff880`10bd3000   CompositeBus CompositeBus.sys Mon Jul 13 20:00:33 2009 (4A5BCAA1)
fffff880`10bd3000 fffff880`10be9000   AgileVpn AgileVpn.sys Mon Jul 13 20:10:24 2009 (4A5BCCF0)
fffff880`10be9000 fffff880`10bf8000   kbdclass kbdclass.sys Mon Jul 13 19:19:50 2009 (4A5BC116)
fffff960`000f0000 fffff960`003ff000   win32k   win32k.sys   unavailable (00000000)

Unloaded modules:
fffff880`01600000 fffff880`0160e000   crashdmp.sys
    Timestamp: unavailable (00000000)
    Checksum:  00000000
    ImageSize:  0000E000
fffff880`0160e000 fffff880`01618000   dump_storpor
    Timestamp: unavailable (00000000)
    Checksum:  00000000
    ImageSize:  0000A000
fffff880`015bd000 fffff880`015e8000   dump_nvstor.
    Timestamp: unavailable (00000000)
    Checksum:  00000000
    ImageSize:  0002B000
fffff880`015e8000 fffff880`015fb000   dump_dumpfve
    Timestamp: unavailable (00000000)
    Checksum:  00000000
    ImageSize:  00013000

Code:

Microsoft (R) Windows Debugger Version 6.12.0002.633 X86
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [E:\Temp\Rar$DI00.737\072810-17612-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Invalid directory table base value 0x0
Symbol search path is: SRV*C:\SymCache*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`02a07000 PsLoadedModuleList = 0xfffff800`02c44e50
Debug session time: Wed Jul 28 22:03:51.009 2010 (UTC - 4:00)
System Uptime: 0 days 0:00:15.085
Loading Kernel Symbols
...................................................Unable to load image Unknown_Module_00000000`00000000, Win32 error 0n2
*** WARNING: Unable to verify timestamp for Unknown_Module_00000000`00000000
Unable to add module at 00000000`00000000

Loading User Symbols
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 7E, {ffffffffc0000005, fffff80002a83324, fffff880031c3e68, fffff880031c36d0}

Probably caused by : ntkrnlmp.exe ( nt!IofCallDriver+14 )

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

0: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

SYSTEM_THREAD_EXCEPTION_NOT_HANDLED (7e)
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.
Arguments:
Arg1: ffffffffc0000005, The exception code that was not handled
Arg2: fffff80002a83324, The address that the exception occurred at
Arg3: fffff880031c3e68, Exception Record Address
Arg4: fffff880031c36d0, Context Record Address

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!IofCallDriver+14
fffff800`02a83324 fe4a43          dec     byte ptr [rdx+43h]

EXCEPTION_RECORD:  fffff880031c3e68 -- (.exr 0xfffff880031c3e68)
Cannot read Exception record @ fffff880031c3e68

CONTEXT:  fffff880031c36d0 -- (.cxr 0xfffff880031c36d0)
Unable to read context, Win32 error 0n30

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

BUGCHECK_STR:  0x7E

CURRENT_IRQL:  0

LAST_CONTROL_TRANSFER:  from fffff80002a8513a to fffff880041cb9c2

STACK_TEXT:  
fffff800`00b9cc98 fffff800`02a8513a : 00000000`0027bcc4 fffffa80`081145d8 00000000`00000000 00000000`000003c6 : 0xfffff880`041cb9c2
fffff800`00b9cca0 fffff800`02a7fdcc : fffff800`02bf1e80 fffff800`00000000 00000000`00000000 fffff880`01092880 : nt!PoIdle+0x53a
fffff800`00b9cd80 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiIdleLoop+0x2c


FOLLOWUP_IP: 
nt!IofCallDriver+14
fffff800`02a83324 fe4a43          dec     byte ptr [rdx+43h]

SYMBOL_NAME:  nt!IofCallDriver+14

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nt

IMAGE_NAME:  ntkrnlmp.exe

DEBUG_FLR_IMAGE_TIMESTAMP:  4b88cfeb

STACK_COMMAND:  .cxr 0xfffff880031c36d0 ; kb

FAILURE_BUCKET_ID:  X64_0x7E_nt!IofCallDriver+14

BUCKET_ID:  X64_0x7E_nt!IofCallDriver+14

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

We use WinDBG to analyze.

Seems that the Liquid Pinnacle Edition driver is causing crashes. No surprise at all here based on the date:

Code:

ftdibus  ftdibus.sys  Wed Jun 27 09:05:06 2007

Please uninstall the software or update to a 2010 version.

-------

It's good practice to keep other updated drivers too. You can update your video card driver from the following link:

Code:

 nvlddmkm nvlddmkm.sys Fri Nov 20 22:40:46 2009

Link Removed - Invalid URL

This NVIDIA hardware firewall driver is old. Please update or uninstall it:

Code:

nvm62x64 nvm62x64.sys Fri Oct 17 17:01:06 2008

-----

Enjoy.

berryguru · Jul 30, 2010

Wow!!! That's an excellent find! Very impressed. I totally learned something tonight and how to troubleshoot in the future.

The ftdibus.sys is my USB to Serial adaptor. It's the far right one here SerialStuff.com all USB serial adapters and RS-232 RS-422 and RS-485 Stuff They only have XP/Vista 32/64-bit drivers for it, I believe I have the Vista 64bit drivers loaded. I don't see any supported drivers for Windows 7 64bit. I need the USB to Serial adaptor to connect to my Cisco lab devices. I'm astonished that this little device is crashing my system.

~berry

TorrentG · Jul 30, 2010

Ah, cool!

I may be able to find something for ya with a little more info.

In device manager, right click on it. Properties. Details tab. Change the dropdown to hardware ids. Copy/paste the results. If there's anything newer or more stable, I can find it like this.

berryguru · Jul 30, 2010

There she is - FTDIBUS\COMPORT&VID_0403&PID_6001

I've Googled for a different device to use, but looks like they don't have to many USB to Serial for Win7 x64.

~berry

TorrentG · Jul 30, 2010

One of the extremely rare instances that Google actually isn't your friend, lol!

Use only I.E. to access this page:

Microsoft Update Catalog

I think the one you want is at the top.

berryguru · Jul 30, 2010

Haha ...extremely rare instance! 8)

So I downloaded those drivers and believe it or not, when I attempted to install it said that 'Windows has determined the driver software for your device is up to date' What a stubborn device!!!

~berry

Super Sarge · Jul 30, 2010

I would definitely not use the NVIDIA Firewall, I am assuming it is in the BIOS, the one in in W7 is sufficient especially if you are behind a router

TorrentG · Jul 30, 2010

berryguru said:
Haha ...extremely rare instance! 8)

So I downloaded those drivers and believe it or not, when I attempted to install it said that 'Windows has determined the driver software for your device is up to date' What a stubborn device!!!

~berry

Install like this.

1) Extract the download to a folder on the pc.
2) Open device manager. Right click on the line for it. Update driver software. Browse my computer. Let me pick. Have disk. Browse.

Now find and double click on the .inf in the correct folder for x64 that you extracted. Hit ok. Hit next and it will install.

berryguru · Jul 30, 2010

Yup it worked! I was selecting one folder to deep during the install. I pulled it back one directory and it found the correct files.

So I've updated the USB to Serial adaptor drivers successfully and I've also updated the Nvidia drivers. So I'm looking good so far. Now for the Nvidia firewall I'm not finding any traces of it. I've attempted to simply unistall it, but I didn't see it listed. I've also done a search and I don't come up with anything. I don't recall ever installing or seeing anything in regards to an Nvidia firewall. Quite frankly I didn't even know they had one.

~berry

SerialStuff · Oct 12, 2010

This thread appeared in our site referrals, so I just thought I'd pop over and see what was up.
@berryguru We've changed our site design quite a bit since this was posted. The old layout is still visible at Link Removed
You say you bought the "far right one" on our front page, however this must be a mistake since the adapter in that position on our website is a Prolific based PL2303 adapter, and you were having issues with an FTDI driver. In either event I'm glad to see that you got the driver issue solved. For anyone else that has a similar issue with an FTDI based product under Windows 7 x64, please see their site for updated drivers: Virtual COM Port Drivers
FTDI Updates their drivers at least 4 times a year and was the first USB to Serial IC company to support 64bit Windows.
They also now offer an *.exe installer versus the old "zip file full of ini/inf files" approach, makes it much harder to make mistakes installing

To remove a driver in Windows Vista and 7, you can often uninstall it right from the Device Manager. Simply right-click the offending device and select uninstall. If no other attached device requires the same driver a "Delete the driver software for this device" checkbox should be shown on the proverbial "are you sure" dialog box. However, if the driver has a listing in the control panel ("Programs and Features" for 7/Vista Users) you should always try that option first.

As for the nVidia firewall, we have seen that here in the office a few times. It usually crops up when you are installing the nForce driver package for nVidia based motherboards. The driver installer tries to sneak it in, and if you let it it will often clash with the Windows Firewall, so we recommend to NOT install it and just stick to the Windows Firewall.

Seeing as this 3-ish month old thread (you guys don't have thread necro rules do you? Sorry, havnt read them all yet!) is getting enough traffic to show up in our referral logs, I have to shamelessly plug a coupon for you guys. Use code "windows7forums" at checkout to get $5 off any order over $20.

berryguru · Oct 30, 2010

Heya SerialStuff,

That's kind of cool how you came across this thread. I actually just popped on today because I'm starting to see BSOD's again. I'm not 100% sure it's caused by the FTDI driver again, but it's coming up in the minidumps. I'd like to post the minidump and see if somebody could take a look. I've opened the minidump using WinDbg ver6.12.0002.633 but there is a lot of data to decipher. I find it odd that the issue was resolved and the system was stable for months, and all of a sudden I'm getting BSOD's. I would assume if I wasn't have any problems with the FTDI driver, that nothing in regards to the FTDI driver would show up in the dumps.

~berry

TorrentG · Oct 30, 2010

Sure, post the crash dumps. I'll tell ya what's going on and how to fix them.

berryguru · Oct 30, 2010

View attachment 102310-15038-01.dmpI was hoping you were still around. I've actually been using the WinDbg tool quite a bit at the office, on some Server 2008 R2. But I'm a little confused on the output of this dump.

TorrentG · Oct 30, 2010

ASACPI ASACPI.sys Sun Mar 27 22:30:36 2005

nvm62x64 nvm62x64.sys Fri Oct 17 17:01:06 2008

Install my ATK attachment normally to update the first driver above.

For the other, extract the other attachment. Copy the .sys file from the extracted folder over C:\Windows\System32\drivers

-------

Must update this driver:

ftdibus ftdibus.sys Wed Jun 27 09:05:06 2007

http://www.ftdichip.com/FTDrivers.htm

Enjoy.

berryguru · Oct 30, 2010

Wow!! Okay you've got to tell me how you came about this solution. Because I'm just not seeing it in that dump. When you first start to run the dump, do you get the following:

Microsoft (R) Windows Debugger Version 6.12.0002.633 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.

Loading Dump File [D:\LogDUMPs\102310-15038-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*c:\symbols*Symbol information
Executable search path is:
Windows 7 Kernel Version 7600 MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Machine Name:
Kernel base = 0xfffff800`02c63000 PsLoadedModuleList = 0xfffff800`02ea0e50
Debug session time: Sat Oct 23 11:27:10.103 2010 (UTC - 7:00)
System Uptime: 0 days 0:00:15.788
Loading Kernel Symbols
...............................................................
................................................................
.........
Loading User Symbols
Loading unloaded module list
....
Unable to load image \SystemRoot\system32\drivers\ftdibus.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for ftdibus.sys
*** ERROR: Module load completed but symbols could not be loaded for ftdibus.sys
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 1000007E, {ffffffffc0000005, fffff80002cdf634, fffff880031b5e68, fffff880031b56d0}

Unable to load image \SystemRoot\system32\DRIVERS\usbhub.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for usbhub.sys
*** ERROR: Module load completed but symbols could not be loaded for usbhub.sys
Probably caused by : ftdibus.sys ( ftdibus+85fb )

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

Then you have to click the !analyze -v link?

TorrentG · Oct 30, 2010

Getting into dump analysis is a whole process.

Quickly though, in your particular crash, it clearly shows the cause and that's fairly rare:

"Probably caused by : ftdibus.sys ( ftdibus+85fb )"

You can type lmtn at them bottom then press enter to see the drivers.

Windows 7 Win7 box crashing/locking up - BSOD

New Member

Banned

New Member

New Member

Attachments

Banned

New Member

Banned

New Member

Banned

New Member

New Member

Banned

New Member

New Member

New Member

Banned

New Member

Banned

Attachments

New Member

Banned

Similar threads

Privacy & Transparency

Privacy & Transparency