Windows Vista DUMP DATA - Help Windows Vista

Opened log file 'c:\debuglog.txt'

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


Loading Dump File [C:\Windows\MEMORY.DMP]
Kernel Summary Dump File: Only kernel address space is available

Symbol search path is: SRV*c:\symbols*http://msdl.microsoft.com/download/symbols
Executable search path is: C:\Windows;C:\Windows\system32;C:\Windows\system32\drivers
Windows Vista Kernel Version 6000 UP Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 6000.16386.x86fre.vista_rtm.061101-2205
Kernel base = 0x81800000 PsLoadedModuleList = 0x81911db0
Debug session time: Fri Oct 12 20:36:37.220 2007 (GMT+5)
System Uptime: 0 days 0:00:55.892
Loading Kernel Symbols
...........................................................................................................................
Loading User Symbols
PEB is paged out (Peb.Ldr = 7ffd800c). Type ".hh dbgerr001" for details
Loading unloaded module list
...
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck A, {430, 2, 1, 81ba4e79}

Page 41e49 not present in the dump file. Type ".hh dbgerr004" for details
Page 422c9 not present in the dump file. Type ".hh dbgerr004" for details
Probably caused by : ntkrpamp.exe ( nt!KiTrap0E+2ac )

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

kd> !analyze -v;r;kv;lmtn;.logclose;q
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

IRQL_NOT_LESS_OR_EQUAL (a)
An attempt was made to access a pageable (or completely invalid) address at an
interrupt request level (IRQL) that is too high. This is usually
caused by drivers using improper addresses.
If a kernel debugger is available get the stack backtrace.
Arguments:
Arg1: 00000430, memory referenced
Arg2: 00000002, IRQL
Arg3: 00000001, bitfield :
bit 0 : value 0 = read operation, 1 = write operation
bit 3 : value 0 = not an execute operation, 1 = execute operation (only on chips which support this level of status)
Arg4: 81ba4e79, address which referenced memory

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

Page 41e49 not present in the dump file. Type ".hh dbgerr004" for details
Page 422c9 not present in the dump file. Type ".hh dbgerr004" for details

WRITE_ADDRESS: 00000430

CURRENT_IRQL: 2

FAULTING_IP:
hal!KeAcquireInStackQueuedSpinLockRaiseToSynch+19
81ba4e79 8711 xchg edx,dword ptr [ecx]

DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT

BUGCHECK_STR: 0xA

PROCESS_NAME: dllhost.exe

TRAP_FRAME: 946cbafc -- (.trap 0xffffffff946cbafc)
.trap 0xffffffff946cbafc
ErrCode = 00000002
eax=946cbb80 ebx=84fb5030 ecx=00000430 edx=946cbb80 esi=84fbb278 edi=000003fc
eip=81ba4e79 esp=946cbb70 ebp=946cbb8c iopl=0 nv up ei pl zr na pe nc
cs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000 efl=00010246
hal!KeAcquireInStackQueuedSpinLockRaiseToSynch+0x19:
81ba4e79 8711 xchg edx,dword ptr [ecx] ds:0023:00000430=????????
.trap
Resetting default scope

LAST_CONTROL_TRANSFER: from 81ba4e79 to 8188fc44

STACK_TEXT:
946cbafc 81ba4e79 badb0d00 946cbb80 81932300 nt!KiTrap0E+0x2ac
946cbb6c 81876a1b 946d79a4 84fbb278 00000000 hal!KeAcquireInStackQueuedSpinLockRaiseToSynch+0x19
946cbb8c 81794a22 000003fc 00000001 93876828 nt!ExAcquireResourceSharedLite+0x21
946cbba0 8179f30d 946d79a4 00000000 00000001 Ntfs!NtfsAcquireSharedVcb+0x22
946cbcf0 81712a79 946d79a4 84f84008 94edce31 Ntfs!NtfsCommonCleanup+0x12f
946cbd2c 81880278 946d7954 00000000 ffffffff Ntfs!NtfsCommonCleanupCallout+0x1d
946cbd2c 81880371 946d7954 00000000 ffffffff nt!KiSwapKernelStackAndExit+0x118
946d78ec 818b7efb 946d7954 81712a5c 946cc000 nt!KiSwitchKernelStackAndCallout+0x31
946d7938 81712af5 81712a5c 946d7954 00000000 nt!KeExpandKernelStackAndCalloutEx+0x1cc
946d7964 817a2cbe 946d79a4 84f84008 94ec09f9 Ntfs!NtfsCommonCleanupOnNewStack+0x30
946d7ae4 81827ecf 84678020 84f84008 84f84008 Ntfs!NtfsFsdCleanup+0x137
946d7afc 807b6a5c 84672d98 84f84008 00000000 nt!IofCallDriver+0x63
946d7b20 807b6c18 946d7b40 84672d98 00000000 fltmgr!FltpLegacyProcessingAfterPreCallbacksCompleted+0x22a
946d7b58 81827ecf 84672d98 84f84008 84f84018 fltmgr!FltpDispatch+0xc2
946d7b70 81994e9e 84fc9d90 82ecc1e0 00000001 nt!IofCallDriver+0x63
946d7bb4 819f3337 84fc9d90 84fbb278 00100020 nt!IopCloseFile+0x386
946d7c04 819f1728 84fc9d90 00ecc1e0 00100020 nt!ObpDecrementHandleCount+0x14c
946d7c50 81a7d589 9496e788 94998210 84fc9d90 nt!ObpCloseHandleTableEntry+0x23a
946d7c80 819f0f43 9496e788 946d7c94 84fc9d90 nt!ExSweepHandleTable+0x5f
946d7ca0 81a1bc2b 946dc644 84fb5290 84fb5030 nt!ObKillProcess+0x54
946d7d04 81a1ad38 00000000 00000000 84fb5030 nt!PspExitThread+0x5a1
946d7d24 81a1b223 84fb5030 00000000 00000001 nt!PspTerminateThreadByPointer+0x5b
946d7d54 8188c96a ffffffff 00000000 0018fd40 nt!NtTerminateProcess+0x1e0
946d7d54 76fe0f34 ffffffff 00000000 0018fd40 nt!KiFastCallEntry+0x12a
WARNING: Frame IP not in any known module. Following frames may be wrong.
0018fd40 00000000 00000000 00000000 00000000 0x76fe0f34


STACK_COMMAND: kb

FOLLOWUP_IP:
nt!KiTrap0E+2ac
8188fc44 833d648d928100 cmp dword ptr [nt!KiFreezeFlag (81928d64)],0

SYMBOL_STACK_INDEX: 0

SYMBOL_NAME: nt!KiTrap0E+2ac

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: nt

IMAGE_NAME: ntkrpamp.exe

DEBUG_FLR_IMAGE_TIMESTAMP: 4549ae00

FAILURE_BUCKET_ID: 0xA_W_nt!KiTrap0E+2ac

BUCKET_ID: 0xA_W_nt!KiTrap0E+2ac

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

eax=818f483c ebx=00000002 ecx=00000861 edx=819293dc esi=818f4820 edi=00000430
eip=8188fc44 esp=946cbae4 ebp=946cbafc iopl=0 nv up ei ng nz na pe nc
cs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000 efl=00000286
nt!KiTrap0E+0x2ac:
8188fc44 833d648d928100 cmp dword ptr [nt!KiFreezeFlag (81928d64)],0 ds:0023:81928d64=00000000
ChildEBP RetAddr Args to Child
946cbafc 81ba4e79 badb0d00 946cbb80 81932300 nt!KiTrap0E+0x2ac (FPO: [0,0] TrapFrame @ 946cbafc)
946cbb6c 81876a1b 946d79a4 84fbb278 00000000 hal!KeAcquireInStackQueuedSpinLockRaiseToSynch+0x19 (FPO: [0,0,0])
946cbb8c 81794a22 000003fc 00000001 93876828 nt!ExAcquireResourceSharedLite+0x21
946cbba0 8179f30d 946d79a4 00000000 00000001 Ntfs!NtfsAcquireSharedVcb+0x22 (FPO: [Non-Fpo])
946cbcf0 81712a79 946d79a4 84f84008 94edce31 Ntfs!NtfsCommonCleanup+0x12f (FPO: [Non-Fpo])
946cbd2c 81880278 946d7954 00000000 ffffffff Ntfs!NtfsCommonCleanupCallout+0x1d (FPO: [Non-Fpo])
946cbd2c 81880371 946d7954 00000000 ffffffff nt!KiSwapKernelStackAndExit+0x118 (FPO: [0,0] TrapFrame @ 946cbd44)
946d78ec 818b7efb 946d7954 81712a5c 946cc000 nt!KiSwitchKernelStackAndCallout+0x31
946d7938 81712af5 81712a5c 946d7954 00000000 nt!KeExpandKernelStackAndCalloutEx+0x1cc
946d7964 817a2cbe 946d79a4 84f84008 94ec09f9 Ntfs!NtfsCommonCleanupOnNewStack+0x30 (FPO: [Non-Fpo])
946d7ae4 81827ecf 84678020 84f84008 84f84008 Ntfs!NtfsFsdCleanup+0x137 (FPO: [Non-Fpo])
946d7afc 807b6a5c 84672d98 84f84008 00000000 nt!IofCallDriver+0x63
946d7b20 807b6c18 946d7b40 84672d98 00000000 fltmgr!FltpLegacyProcessingAfterPreCallbacksCompleted+0x22a (FPO: [Non-Fpo])
946d7b58 81827ecf 84672d98 84f84008 84f84018 fltmgr!FltpDispatch+0xc2 (FPO: [Non-Fpo])
946d7b70 81994e9e 84fc9d90 82ecc1e0 00000001 nt!IofCallDriver+0x63
946d7bb4 819f3337 84fc9d90 84fbb278 00100020 nt!IopCloseFile+0x386
946d7c04 819f1728 84fc9d90 00ecc1e0 00100020 nt!ObpDecrementHandleCount+0x14c
946d7c50 81a7d589 9496e788 94998210 84fc9d90 nt!ObpCloseHandleTableEntry+0x23a
946d7c80 819f0f43 9496e788 946d7c94 84fc9d90 nt!ExSweepHandleTable+0x5f
946d7ca0 81a1bc2b 946dc644 84fb5290 84fb5030 nt!ObKillProcess+0x54
start end module name
80203000 8020a000 pciide pciide.sys Fri Nov 17 11:51:26 2006 (455D54E6)
8020a000 80219000 volmgr volmgr.sys Thu Nov 02 14:21:44 2006 (4549B1A0)
80219000 80221000 msisadrv msisadrv.sys Thu Nov 02 14:05:08 2006 (4549ADBC)
80221000 8022a000 WMILIB WMILIB.SYS Thu Nov 02 14:24:53 2006 (4549B25D)
8022a000 8026d000 acpi acpi.sys Thu Nov 02 14:05:03 2006 (4549ADB7)
8026d000 8027a000 WDFLDR WDFLDR.SYS Thu Nov 02 14:24:05 2006 (4549B22D)
8027a000 802b5000 CLFS CLFS.SYS Thu Nov 02 14:00:52 2006 (4549ACBC)
802b5000 802bd000 BOOTVID BOOTVID.dll Thu Nov 02 15:09:29 2006 (4549BCD1)
802bd000 802c6000 PSHED PSHED.dll Thu Nov 02 15:12:51 2006 (4549BD9B)
802c6000 802ce000 kdcom kdcom.dll Thu Nov 02 15:12:20 2006 (4549BD7C)
80407000 8040f000 spldr spldr.sys Thu Oct 26 04:10:44 2006 (453FE7EC)
8040f000 80417000 atapi atapi.sys Fri Nov 17 11:51:20 2006 (455D54E0)
80417000 80461000 volmgrx volmgrx.sys Thu Nov 02 14:21:54 2006 (4549B1AA)
80461000 8046f000 PCIIDEX PCIIDEX.SYS Fri Nov 17 11:51:21 2006 (455D54E1)
8046f000 8047f000 mountmgr mountmgr.sys Thu Nov 02 14:21:06 2006 (4549B17A)
8047f000 804a4000 pci pci.sys Thu Nov 02 14:05:13 2006 (4549ADC1)
804a4000 8051f000 Wdf01000 Wdf01000.sys Thu Nov 02 14:24:18 2006 (4549B23A)
8051f000 80600000 CI CI.dll Thu Nov 02 15:12:45 2006 (4549BD95)
80603000 80639000 volsnap volsnap.sys Thu Nov 02 14:22:11 2006 (4549B1BB)
80639000 80672000 NETIO NETIO.SYS Thu Nov 02 14:28:01 2006 (4549B319)
80672000 8069d000 msrpc msrpc.sys Thu Nov 02 14:20:16 2006 (4549B148)
8069d000 807a1000 ndis ndis.sys Thu Nov 02 14:27:33 2006 (4549B2FD)
807a1000 807b1000 fileinfo fileinfo.sys Thu Nov 02 14:06:47 2006 (4549AE1F)
807b1000 807e2000 fltmgr fltmgr.sys Thu Nov 02 14:00:58 2006 (4549ACC2)
807e2000 80800000 ataport ataport.SYS Fri Nov 17 11:51:23 2006 (455D54E3)
81608000 81629000 CLASSPNP CLASSPNP.SYS Thu Nov 02 14:21:34 2006 (4549B196)
81629000 8163a000 disk disk.sys Thu Nov 02 14:21:40 2006 (4549B19C)
8163a000 8164b000 gagp30kx gagp30kx.sys Thu Nov 02 14:05:07 2006 (4549ADBB)
8164b000 81670000 ecache ecache.sys Thu Nov 02 14:22:42 2006 (4549B1DA)
81670000 8167f000 mup mup.sys Thu Nov 02 14:01:04 2006 (4549ACC8)
8167f000 8168e000 partmgr partmgr.sys Thu Nov 02 14:21:47 2006 (4549B1A3)
8168e000 816f8000 ksecdd ksecdd.sys Thu Nov 02 14:13:45 2006 (4549AFC1)
816f8000 81800000 Ntfs Ntfs.sys Thu Nov 02 14:01:39 2006 (4549ACEB)
81800000 81ba1000 nt ntkrpamp.exe Thu Nov 02 14:06:16 2006 (4549AE00)
81ba1000 81bd5000 hal halmacpi.dll Wed Dec 20 09:01:08 2006 (4588AE7C)
85e83000 85e92000 amdk8 amdk8.sys Thu Nov 02 14:00:18 2006 (4549AC9A)
85ff7000 86000000 crcdisk crcdisk.sys Thu Nov 02 14:22:27 2006 (4549B1CB)
86a25000 86a32000 crashdmp crashdmp.sys Thu Nov 02 14:21:36 2006 (4549B198)
86a33000 86a3e000 tunnel tunnel.sys Thu Nov 02 14:27:29 2006 (4549B2F9)
86a72000 86a7f000 watchdog watchdog.sys Thu Nov 02 14:07:44 2006 (4549AE58)
86aa2000 86aa3380 swenum swenum.sys Thu Nov 02 14:21:15 2006 (4549B183)
86b7c000 86b84000 dump_atapi dump_atapi.sys Fri Nov 17 11:51:20 2006 (455D54E0)
86bbc000 86bc4000 RDPCDD RDPCDD.sys Thu Nov 02 14:32:01 2006 (4549B409)
86bc4000 86bcc000 rdpencdd rdpencdd.sys Thu Nov 02 14:32:01 2006 (4549B409)
88612000 8861b000 Fs_Rec Fs_Rec.SYS Thu Nov 02 14:00:47 2006 (4549ACB7)
8861b000 88624000 rasacd rasacd.sys Thu Nov 02 14:28:13 2006 (4549B325)
8865a000 88663000 tunmp tunmp.sys Thu Nov 02 14:27:23 2006 (4549B2F3)
88697000 8869e000 Null Null.SYS Thu Nov 02 14:21:05 2006 (4549B179)
8869e000 886a5000 Beep Beep.SYS Thu Nov 02 14:21:03 2006 (4549B177)
886c1000 886c8000 parvdm parvdm.sys Thu Nov 02 14:21:23 2006 (4549B18B)
88720000 8872f280 ohci1394 ohci1394.sys Thu Nov 02 14:25:16 2006 (4549B274)
88770000 88780000 NDProxy NDProxy.SYS Thu Nov 02 14:28:08 2006 (4549B320)
88790000 887a0000 lltdio lltdio.sys Thu Nov 02 14:26:48 2006 (4549B2D0)
88a05000 88a26000 VIDEOPRT VIDEOPRT.SYS Thu Nov 02 14:24:07 2006 (4549B22F)
88a76000 88ab0000 sisgrp sisgrp.sys Fri Jul 09 00:25:55 2004 (40ED98BB)
88ab0000 88aba000 serenum serenum.sys Thu Nov 02 14:21:25 2006 (4549B18D)
88ac4000 88ad2000 usbehci usbehci.sys Thu Nov 02 14:25:04 2006 (4549B268)
88ad2000 88aea000 cdrom cdrom.sys Thu Nov 02 14:21:44 2006 (4549B1A0)
88aea000 88b04000 serial serial.sys Thu Nov 02 14:21:29 2006 (4549B191)
88b04000 88b1c000 parport parport.sys Thu Nov 02 14:21:29 2006 (4549B191)
88b1c000 88b27000 fdc fdc.sys Thu Nov 02 14:21:33 2006 (4549B195)
88b27000 88b32000 mouclass mouclass.sys Thu Nov 02 14:21:09 2006 (4549B17D)
88b32000 88b3d000 kbdclass kbdclass.sys Thu Nov 02 14:21:09 2006 (4549B17D)
88b3d000 88b50000 i8042prt i8042prt.sys Thu Nov 02 14:21:12 2006 (4549B180)
88b69000 88b74000 TDI TDI.SYS Thu Nov 02 14:28:46 2006 (4549B346)
88b74000 88b81080 1394BUS 1394BUS.SYS Thu Nov 02 14:25:12 2006 (4549B270)
88b82000 88b9fb80 SiSGbeXP SiSGbeXP.sys Fri Nov 05 08:59:29 2004 (418AF399)
89007000 89016000 raspppoe raspppoe.sys Thu Nov 02 14:28:12 2006 (4549B324)
89016000 89021000 ndistapi ndistapi.sys Thu Nov 02 14:28:07 2006 (4549B31F)
89021000 89038000 rasl2tp rasl2tp.sys Thu Nov 02 14:28:13 2006 (4549B325)
89038000 89063000 msiscsi msiscsi.sys Thu Nov 02 14:22:40 2006 (4549B1D8)
89063000 890a0000 USBPORT USBPORT.SYS Thu Nov 02 14:25:09 2006 (4549B26D)
890a0000 890aa000 usbohci usbohci.sys Thu Nov 02 14:25:05 2006 (4549B269)
890aa000 890b4000 mssmbios mssmbios.sys Thu Nov 02 14:05:13 2006 (4549ADC1)
890b4000 890be000 flpydisk flpydisk.sys Thu Nov 02 14:21:32 2006 (4549B194)
890be000 890c8000 nsiproxy nsiproxy.sys Thu Nov 02 14:27:30 2006 (4549B2FA)
890dc000 890e6000 secdrv secdrv.SYS Wed Sep 13 18:48:32 2006 (45080528)
890f0000 890fa000 Dxapi Dxapi.sys Thu Nov 02 14:08:17 2006 (4549AE79)
89140000 8914c000 vga vga.sys Thu Nov 02 14:23:56 2006 (4549B224)
89155000 89163000 Npfs Npfs.SYS Thu Nov 02 14:00:57 2006 (4549ACC1)
89163000 89172000 termdd termdd.sys Thu Nov 02 14:32:00 2006 (4549B408)
89172000 8917f000 umbus umbus.sys Thu Nov 02 14:25:24 2006 (4549B27C)
8917f000 8918a000 Msfs Msfs.SYS Thu Nov 02 14:00:56 2006 (4549ACC0)
8918a000 8919d000 raspptp raspptp.sys Thu Nov 02 14:28:14 2006 (4549B326)
8919d000 891c0000 ndiswan ndiswan.sys Thu Nov 02 14:28:13 2006 (4549B325)
891c0000 89200000 storport storport.sys Thu Nov 02 14:21:45 2006 (4549B1A1)
89404000 89412000 netbios netbios.sys Thu Nov 02 14:27:26 2006 (4549B2F6)
89412000 8942b000 fwpkclnt fwpkclnt.sys Thu Nov 02 14:27:26 2006 (4549B2F6)
8942b000 89436000 dump_dumpata dump_dumpata.sys Thu Nov 02 14:21:34 2006 (4549B196)
89499000 894a4000 tcpipreg tcpipreg.sys Thu Nov 02 14:27:46 2006 (4549B30A)
894fb000 8952f000 usbhub usbhub.sys Thu Nov 02 14:25:20 2006 (4549B278)
8954f000 89579000 ks ks.sys Thu Nov 02 14:21:18 2006 (4549B186)
89579000 89600000 rdpdr rdpdr.sys Thu Nov 02 14:32:58 2006 (4549B442)
8960d000 89624000 dfsc dfsc.sys Thu Nov 02 14:01:04 2006 (4549ACC8)
89624000 89637000 wanarp wanarp.sys Thu Nov 02 14:28:13 2006 (4549B325)
89637000 8964d000 pacer pacer.sys Thu Nov 02 14:27:33 2006 (4549B2FD)
8964d000 8967f000 netbt netbt.sys Thu Nov 02 14:27:18 2006 (4549B2EE)
8967f000 896c6000 afd afd.sys Thu Nov 02 14:28:41 2006 (4549B341)
896c6000 896da000 smb smb.sys Thu Nov 02 14:27:10 2006 (4549B2E6)
896fe000 89701080 srvkp srvkp.sys Fri Jul 09 01:07:31 2004 (40EDA27B)
8971a000 8972f000 tdx tdx.sys Thu Nov 02 14:27:34 2006 (4549B2FE)
8972f000 89800000 tcpip tcpip.sys Thu Nov 02 14:28:31 2006 (4549B337)
8c8ed000 8c8fc000 monitor monitor.sys Thu Nov 02 14:24:05 2006 (4549B22D)
8c8fc000 8c912000 cdfs cdfs.sys Thu Nov 02 14:00:50 2006 (4549ACBA)
8c972000 8c9c5000 csc csc.sys Thu Nov 02 14:01:36 2006 (4549ACE8)
8c9c5000 8ca00000 rdbss rdbss.sys Thu Nov 02 14:01:24 2006 (4549ACDC)
8fe00000 8ffff000 win32k win32k.sys Thu Nov 02 14:08:58 2006 (4549AEA2)
90c00000 90c09000 TSDDD TSDDD.dll Thu Nov 02 14:32:02 2006 (4549B40A)
90c10000 90d2d000 SiSGRV SiSGRV.dll Fri Jul 09 00:33:08 2004 (40ED9A6C)
90de0000 90df7000 dxg dxg.sys Thu Nov 02 14:08:17 2006 (4549AE79)
90ea5000 90ec0000 luafv luafv.sys Thu Nov 02 14:03:07 2006 (4549AD43)
9201e000 92031000 rspndr rspndr.sys Thu Nov 02 14:26:48 2006 (4549B2D0)
92621000 92633000 mrxsmb20 mrxsmb20.sys Thu Nov 02 14:01:16 2006 (4549ACD4)
92a54000 92b32000 peauth peauth.sys Mon Oct 23 14:25:32 2006 (453C8384)
92e71000 92e8c000 srvnet srvnet.sys Thu Nov 02 14:01:43 2006 (4549ACEF)
92ecc000 92f32000 HTTP HTTP.sys Thu Nov 02 14:27:06 2006 (4549B2E2)
92f72000 93000000 spsys spsys.sys Thu Oct 26 04:13:28 2006 (453FE890)
9342d000 93479000 srv srv.sys Thu Nov 02 14:01:55 2006 (4549ACFB)
93539000 9355d000 srv2 srv2.sys Thu Nov 02 14:01:46 2006 (4549ACF2)
9355d000 93596000 mrxsmb10 mrxsmb10.sys Thu Nov 02 14:01:25 2006 (4549ACDD)
93596000 935b4000 mrxsmb mrxsmb.sys Thu Nov 02 14:01:20 2006 (4549ACD8)
935b4000 935d3000 mrxdav mrxdav.sys Thu Nov 02 14:01:24 2006 (4549ACDC)
935d3000 935e7000 mpsdrv mpsdrv.sys Thu Nov 02 14:26:32 2006 (4549B2C0)
935e7000 93600000 bowser bowser.sys Thu Nov 02 14:01:11 2006 (4549ACCF)

Unloaded modules:
86a25000 86a32000 crashdmp.sys
Timestamp: unavailable (00000000)
Checksum: 00000000
86a1a000 86a25000 dump_ataport.sys
Timestamp: unavailable (00000000)
Checksum: 00000000
86b5c000 86b64000 dump_atapi.sys
Timestamp: unavailable (00000000)
Checksum: 00000000
Closing open log file c:\debuglog.txt

 

Hi and welcome to the BBS,
You need to provide more information. How often does it occur? When does it occur? Check more dump logs, check for any patterns (error codes, programs/files involved, etc). Is it a laptop or desktop computer? Did you install Vista yourself or did it come with the computer? Did you build the computer yourself?

Does the error message look like this:
*** STOP: 0x0000000A (parameter1, parameter2, parameter3, parameter4)
IRQL_NOT_LESS_OR_EQUAL
and if it happens to be related to hibernation/sleep:
http://support.microsoft.com/kb/941492/en-us

Matt

 

Hi mattman

Thank you for the reply. To answer your questions.

How often does it occur?

It occurs at random times and random situations. I had earlier Windows XP installed.
When does it occur?

It can happen anytime after booting, from 10 minutes to 3 hours

Check more dump logs, check for any patterns (error codes, programs/files involved, etc).

I couldn't get any pattern

Is it a laptop or desktop computer?

Desktop

Did you install Vista yourself or did it come with the computer?

Myself

Did you build the computer yourself?

Yes/No: Reason: Additional RAM and HDD were added many months ago. I had Windows XP running on the machine. It was doing fine. And then even Windows XP also started giving blue screens. Then I decided to upgrade to Vista.
I have two IDE HDD and one SATA. I suspected a SATA HDD problem and got it replaced. I replaced the SATA cable too. It didn't help.
Now I have disabled the SATA controller in the BIOS and installed Windows Vista on an IDE HDD.

Now I have a doubt, can IDE HDD cable cause problem any time?

 

Good info, thanks vrenjith. I am hoping I can help you further.

You upgraded from Win XP, but you were getting BSODs in Win XP as well. Basics, check if there is heat problem. Look under the fan on the CPU, are the fins of the heatsink free of dust?

If there is no consistent error message or pattern it may well be a hardware issue. First thing to check is the RAM. There are memory diagnostics in my signature.

Did you locate the memory you added in the location specified by the motherboard manufacturer? Check and try different combinations of your modules.

Drivers, start from the ground up. Whatever was causing the problem in Win XP may still causing the problem in Vista, did you check for updated Vista drivers for all of your drivers?
It may not be a driver problem, although, if Vista has installed drivers using information from the Win XP installation, it might.

Matt

 

Thank you Matt,

1)
After you pointed about the heat problem, I have started suspecting that.

2)
Regarding RAM, I did memory test many times and with different tools (I tried the memory test from Vista DVD also), and I could not locate any issue. All tools report success.

I have 1.5GB RAM, 1GB module and 512MB module. I get blue screen with all combinations (1GB alone, 512 alone, both together, swapped the slots).

I also got the 1GB module replaced from my Hardware vendor twice

3) Yes, I have used to Win XP drivers for my sound card (Philips) and the on board ethernet (SIS190). I don't remember whether I got a crash in Vista before I installed these drivers.

4) One additional observation that I have made here is given below.
When I had all there HDD connected and active, the blue screen that I used to get was mostly IRQL_NOT_LESS_OR_EQUAL.
Then, I suspected IDE problems, I disconnected all the IDE HDD and have just the SATA and Windows Vista.
The crash that happens now is showing two drivers, fltmgr.sys or tcpip.sys.
I read somewhere that fltmgr.sys could be infected. To check this I installed Live One Care and did a complete scan. But nothing detected.
Does this behaviour difference of crash mean something?


I will first check the heat problem and update here.

 

1) Check all the fans are spinning freely, including the graphics card fan which may be on the underside of the card and the fan in the power supply unit. Restricted air flow may be due to blocked intakes/exhausts. You can run with the side off the case and direct a desk fan onto the components. Is there good clearance at the back of the case for heated air to escape? If you have added components, the temperature inside the case will rise, you will need to add extra case fans accordingly.

2)

What might that be telling us Is it still the same brand and model? Major RAM manufacturers have a "comparator" that matches RAM with the motherboard.

3) When I built my Vista computer (February), there were no Vista drivers available at the motherboard manufacturer's website. I investigated exactly what hardware was on my motherboard and went to original chipset manufacturer's website to find the correct drivers. For example, I found that my motherboard chipset was a nVidia 570SLI, I went to nVidia and found the Vista drivers for it. Same for things like sound, which is Realtek HD Audio.

4)We don't want to concentrate on one dump log which may be different each time and tells you that it is probably not a software problem (different logs will probably identify a hardware problem). Watch for any consistencies in several logs. Those are MS files that you mention, first is the "Filter Manager" the other deals specifically with networking (internet?). If it keeps showing MS files in the dumps, we should look at a very "base" problem, not say, third party drivers.

Some other things to consider. The change from disconnecting the IDE drives, could it be from a drop in power consumption? If your system runs a generic/economy power supply, you may need it to have a power rating twice as high as you would expect.

Run Error Checking on each drive you have (you will need to reboot for the OS drive). I would include a surface scan.

Matt