2nd Harddrive problem

system · 2007-11-16T16:25:59.000Z

#5

AttachedDevice \FileSystem\Fastfat \Fat IRP_MJ_CREATE [F74721DE] fltMgr.sys
AttachedDevice \FileSystem\Fastfat \Fat IRP_MJ_CREATE_NAMED_PIPE [F74721DE] fltMgr.sys
AttachedDevice \FileSystem\Fastfat \Fat IRP_MJ_CLOSE [F7465F4C] fltMgr.sys
AttachedDevice \FileSystem\Fastfat \Fat IRP_MJ_READ [F7465F4C] fltMgr.sys
AttachedDevice \FileSystem\Fastfat \Fat IRP_MJ_WRITE [F7465F4C] fltMgr.sys
AttachedDevice \FileSystem\Fastfat \Fat IRP_MJ_QUERY_INFORMATION [F7465F4C] fltMgr.sys
AttachedDevice \FileSystem\Fastfat \Fat IRP_MJ_SET_INFORMATION [F7465F4C] fltMgr.sys
AttachedDevice \FileSystem\Fastfat \Fat IRP_MJ_QUERY_EA [F7465F4C] fltMgr.sys
AttachedDevice \FileSystem\Fastfat \Fat IRP_MJ_SET_EA [F7465F4C] fltMgr.sys
AttachedDevice \FileSystem\Fastfat \Fat IRP_MJ_FLUSH_BUFFERS [F7465F4C] fltMgr.sys
AttachedDevice \FileSystem\Fastfat \Fat IRP_MJ_QUERY_VOLUME_INFORMATION [F7465F4C] fltMgr.sys
AttachedDevice \FileSystem\Fastfat \Fat IRP_MJ_SET_VOLUME_INFORMATION [F7465F4C] fltMgr.sys
AttachedDevice \FileSystem\Fastfat \Fat IRP_MJ_DIRECTORY_CONTROL [F7465F4C] fltMgr.sys
AttachedDevice \FileSystem\Fastfat \Fat IRP_MJ_FILE_SYSTEM_CONTROL [F7472454] fltMgr.sys
AttachedDevice \FileSystem\Fastfat \Fat IRP_MJ_DEVICE_CONTROL [F7465F4C] fltMgr.sys
AttachedDevice \FileSystem\Fastfat \Fat IRP_MJ_INTERNAL_DEVICE_CONTROL [F7465F4C] fltMgr.sys
AttachedDevice \FileSystem\Fastfat \Fat IRP_MJ_SHUTDOWN [F7465F4C] fltMgr.sys
AttachedDevice \FileSystem\Fastfat \Fat IRP_MJ_LOCK_CONTROL [F7465F4C] fltMgr.sys
AttachedDevice \FileSystem\Fastfat \Fat IRP_MJ_CLEANUP [F7465F4C] fltMgr.sys
AttachedDevice \FileSystem\Fastfat \Fat IRP_MJ_CREATE_MAILSLOT [F74721DE] fltMgr.sys
AttachedDevice \FileSystem\Fastfat \Fat IRP_MJ_QUERY_SECURITY [F7465F4C] fltMgr.sys
AttachedDevice \FileSystem\Fastfat \Fat IRP_MJ_SET_SECURITY [F7465F4C] fltMgr.sys
AttachedDevice \FileSystem\Fastfat \Fat IRP_MJ_POWER [F7465F4C] fltMgr.sys
AttachedDevice \FileSystem\Fastfat \Fat IRP_MJ_SYSTEM_CONTROL [F7465F4C] fltMgr.sys
AttachedDevice \FileSystem\Fastfat \Fat IRP_MJ_DEVICE_CHANGE [F7465F4C] fltMgr.sys
AttachedDevice \FileSystem\Fastfat \Fat IRP_MJ_QUERY_QUOTA [F7465F4C] fltMgr.sys
AttachedDevice \FileSystem\Fastfat \Fat IRP_MJ_SET_QUOTA [F7465F4C] fltMgr.sys
AttachedDevice \FileSystem\Fastfat \Fat IRP_MJ_CREATE [A917C812] aswMon2.SYS
AttachedDevice \FileSystem\Fastfat \Fat IRP_MJ_CREATE_NAMED_PIPE [A917C812] aswMon2.SYS
AttachedDevice \FileSystem\Fastfat \Fat IRP_MJ_CLOSE [A917C812] aswMon2.SYS
AttachedDevice \FileSystem\Fastfat \Fat IRP_MJ_READ [A917C812] aswMon2.SYS
AttachedDevice \FileSystem\Fastfat \Fat IRP_MJ_WRITE [A917C812] aswMon2.SYS
AttachedDevice \FileSystem\Fastfat \Fat IRP_MJ_QUERY_INFORMATION [A917C812] aswMon2.SYS
AttachedDevice \FileSystem\Fastfat \Fat IRP_MJ_SET_INFORMATION [A917C812] aswMon2.SYS
AttachedDevice \FileSystem\Fastfat \Fat IRP_MJ_QUERY_EA [A917C812] aswMon2.SYS
AttachedDevice \FileSystem\Fastfat \Fat IRP_MJ_SET_EA [A917C812] aswMon2.SYS
AttachedDevice \FileSystem\Fastfat \Fat IRP_MJ_FLUSH_BUFFERS [A917C812] aswMon2.SYS
AttachedDevice \FileSystem\Fastfat \Fat IRP_MJ_QUERY_VOLUME_INFORMATION [A917C812] aswMon2.SYS
AttachedDevice \FileSystem\Fastfat \Fat IRP_MJ_SET_VOLUME_INFORMATION [A917C812] aswMon2.SYS
AttachedDevice \FileSystem\Fastfat \Fat IRP_MJ_DIRECTORY_CONTROL [A917C812] aswMon2.SYS
AttachedDevice \FileSystem\Fastfat \Fat IRP_MJ_FILE_SYSTEM_CONTROL [A917DF76] aswMon2.SYS
AttachedDevice \FileSystem\Fastfat \Fat IRP_MJ_DEVICE_CONTROL [A917C812] aswMon2.SYS
AttachedDevice \FileSystem\Fastfat \Fat IRP_MJ_INTERNAL_DEVICE_CONTROL [A917C812] aswMon2.SYS
AttachedDevice \FileSystem\Fastfat \Fat IRP_MJ_SHUTDOWN [A917C812] aswMon2.SYS
AttachedDevice \FileSystem\Fastfat \Fat IRP_MJ_LOCK_CONTROL [A917C812] aswMon2.SYS
AttachedDevice \FileSystem\Fastfat \Fat IRP_MJ_CLEANUP [A917C812] aswMon2.SYS
AttachedDevice \FileSystem\Fastfat \Fat IRP_MJ_CREATE_MAILSLOT [A917C812] aswMon2.SYS
AttachedDevice \FileSystem\Fastfat \Fat IRP_MJ_QUERY_SECURITY [A917C812] aswMon2.SYS
AttachedDevice \FileSystem\Fastfat \Fat IRP_MJ_SET_SECURITY [A917C812] aswMon2.SYS
AttachedDevice \FileSystem\Fastfat \Fat IRP_MJ_POWER [A917C812] aswMon2.SYS
AttachedDevice \FileSystem\Fastfat \Fat IRP_MJ_SYSTEM_CONTROL [A917C812] aswMon2.SYS
AttachedDevice \FileSystem\Fastfat \Fat IRP_MJ_DEVICE_CHANGE [A917C812] aswMon2.SYS
AttachedDevice \FileSystem\Fastfat \Fat IRP_MJ_QUERY_QUOTA [A917C812] aswMon2.SYS
AttachedDevice \FileSystem\Fastfat \Fat IRP_MJ_SET_QUOTA [A917C812] aswMon2.SYS

---- Registry - GMER 1.0.13 ----

Reg \Registry\USER\S-1-5-21-790525478-2025429265-839522115-1003\Software\Zepter Software\RegLib
Reg \Registry\USER\S-1-5-21-790525478-2025429265-839522115-1003\Software\Zepter Software\RegLib

---- EOF - GMER 1.0.13 ----

system · 2007-11-16T16:26:50.000Z

That’s it. Sorry if there was an easier way to do that !

Vlk · 2007-11-16T17:26:10.000Z

I see that you have ZoneAlarm, SpywareTerminator as well as CounterSpy installed on the machine. Maybe they’re just conflicting with each other.

Well, to be 100% sure, I’d actually need to have a lookg at the full dump (not just the process dump you already sent).

For instructions on how to create it and deliver it to us, please see: http://support.avast.com/index.php?_m=knowledgebase&_a=viewarticle&kbarticleid=71

Cheers
Vlk

system · 2007-11-16T17:49:39.000Z

Vlk post:20:

I see that you have ZoneAlarm, SpywareTerminator as well as CounterSpy installed on the machine. Maybe they’re just conflicting with each other.

Well, to be 100% sure, I’d actually need to have a lookg at the full dump (not just the process dump you already sent).

For instructions on how to create it and deliver it to us, please see: http://support.avast.com/index.php?_m=knowledgebase&_a=viewarticle&kbarticleid=71

Cheers
Vlk

Hi Vlk,

Obviously I can’t be certain, but since this problem only arose since approximately the time I fitted the new HDD, and I’ve been running those three together for a long time now with no problem, I’d be very surprised if it is a conflict. But then, what the hell do I know…

I’m following the instructions you posted, and will get back with the memory dump asap.

Many thanks

system · 2007-11-16T18:30:34.000Z

Ok, I’m doing something wrong, and I’m not sure what.

I did the regedit thing (see pic), then the ‘generate complete memory dump’ thing (it actually said ‘kernel memory dump’ which is what I assumed you wanted - see pic). I then rebooted.

I ran Avast until it froze. I then held down the right-hand Ctrl key and pressed scroll lock twice. Nothing happened.

Can you see what I’ve done wrong? Sorry.

igor0 · 2007-11-16T18:37:34.000Z

Actually, “Full memory dump” is what Vlk had on mind - even though maybe “Kernel memory dump” would be enough, don’t know.

What kind of keyboard do you have - PS/2 or USB?

system · 2007-11-16T18:40:34.000Z

The choice was either ‘none’, ‘small memory dump (64KB)’ or ‘kernel memory dump’

I’m using a USB keyboard (no PS/2 sockets on PC)

DavidR · 2007-11-16T18:46:34.000Z

Mine gives ‘Complete memory dump’ after the Kernel option in the drop down list.

system · 2007-11-16T18:56:14.000Z

Definitely not on mine.

I ran Avast again until it froze and tried the ctrl/scroll lock thing again. When scroll lock is pressed for the first time Avast pops up with “running test, do you really want to close this window”. The second scroll lock click removes this pop-up. As I said before, simply clicking on ‘stop’ to halt the scan doesn’t work, I just get an ‘egg-timer’.

igor0 · 2007-11-16T18:58:16.000Z

I guess it’s caused by the size of the swap file. The full dump is huge (as big as you RAM size), and it’s written in place of the swap file - so the swap must be at least that big for this option to be available.

Anyway, I’m afraid the manual bluescreen shortcut works only with PS/2 keyboard. The Microsoft Knowledgebase article has some instructions for USB keyboard as well (a different registry key):
http://support.microsoft.com/kb/244139

but it requires installation of an updated USB keyboard driver - and it speaks only about Windows 2003, so I’m really not sure if this would work on XP (and I don’t know if it’s a good idea to try…) :-\

system · 2007-11-16T19:13:35.000Z

To make sure that the feature is enabled on a computer that uses a USB keyboard, follow these steps: 1. Start Registry Editor.
2. Locate the following registry subkey:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\kbdhid\Parameters
3. Make sure that the following registry entry is enabled:
Name: CrashOnCtrlScroll
Data Type: REG_DWORD
Value: 1
4. Exit Registry Editor.

So just doing this by itself would be no good or could cause problems?

I’m not questioning you at all (although I’m about to ask a question, so I suppose I am really! ;D ) but if this started when the 2nd harddrive was put in, and I can temporarily stop the problem by disabling it, isn’t the problem for Avast being caused by something I’ve done with the HDD? Please accept my apologies in advance if you’re all now holding your heads in disbelief at the stupidity of this question! ;D

Vlk · 2007-11-16T20:39:42.000Z

So now I’m not quite sure if you have already followed the steps you yourself quoted in your previous post. And if you have, if you’re now able to invoke the blue screen by using the Ctrl + 2x ScrollLock key trick (make sure to reboot the system after making the registry change).

I'm not questioning you at all (although I'm about to ask a question, so I suppose I am really! ) but if this started when the 2nd harddrive was put in, and I can temporarily stop the problem by disabling it, isn't the problem for Avast being caused by something I've done with the HDD? Please accept my apologies in advance if you're all now holding your heads in disbelief at the stupidity of this question!

With all respect, I’m reluctant to make any conclusions until I actually see the dump.

Cheers
Vlk

system · 2007-11-16T21:49:33.000Z

No, I haven’t done it yet, I was asking if it was worth the risk or if you felt it was a waste of time even trying. I’m afraid I’ll be away from the PC for a couple of hours now, but I will do it as soon as I get back.

I’ll upload the dump if it works and let you know on here that I’ve succeeded. If you don’t hear from me for a long time, you’ll know I’m doing a reformat/fresh install!

system · 2007-11-17T00:18:03.000Z

I made the registry change, and I’m afraid it didn’t work.

system · 2007-11-17T02:12:16.000Z

;D ;D

I’ve got it to work (Avast scanning, that is)!! :o

I deleted the new HDD partition and reformatted it as a Dynamic Disk Simple Volume (rather than a Basic Volume).

I’ve now run a standard scan (no archive), just in order to do it quickly, and it went all the way through, with no freezing!!

I’ll try a thorough scan with achive tomorrow, but it’s looking good. I’m also able to context menu-scan the new HDD with no problem.

I just hope I don’t come back tomorrow with my tail between my legs…

system · 2007-11-17T10:56:27.000Z

Sorry if I’ve been a long time, but it’s taken a while to dry the tears and to make an attempt to remove the article that’s wedged itself between my legs…

As I said earlier, I deleted the new harddrive volume and reformatted it, this time as a Dynamic Simple Volume. I then rebooted and used the context menu to scan the new drive. It scanned it in about 2 seconds, as one would expect with nothing in it.

I ran a standard scan which completed with no problems. I then ran 2 thorough scans, one with archive scanning enabled, and both completed fine.

I then shut down the PC.

This morning all the old problems are back (both context menu and standard scan freeze).

Any thoughts?

igor0 · 2007-11-17T11:47:07.000Z

Thinking about it, there might be a simple workaround: go to avast! settings and enter the following path into the list of exclusions:
C:\System Volume Information\tracking.log

It won’t tell us where the problem is, so it’s hard to say whether the same problem appears with another file… but it might solve this particular problem (I hope?)

system · 2007-11-17T13:27:39.000Z

Thanks for your continued help, Igor.

I entered the path into the exclusion list and it stuck somewhere else this time (image 1). I shut down, restarted and ran 2 more scans, with it freezing both times I’m afraid (images 2 & 3).

system · 2007-11-17T18:56:39.000Z

Having got a bit fed up, I’ve now completely wiped the 2nd drive using Killdisk. It doesn’t show up in My Computer, and shows up in Disk Management as ‘not allocated’ and ‘not initialized’. When I open Disk management, the ‘Initialize and Convert Wizard’ opens.

With it in this state, Avast works perfectly.

Since my last post, I have also found that AdAware SE also freezes during scanning - it shows up in Task Manager as ‘not responding’ and then starts again, freezes again, and finally gets through the scan. I ran Kaspersky online scan, and this also froze! All other scanners work, I’ve run them all, and I’ve tried pretty-well every other program on the PC and nothing else seems affected.

Since wiping the drive has solved all the problems, I can only think that I’m doing something wrong when installing the HDD.

Any help anyone can give would be very much appreciated. I know this isn’t a general knowledge Forum, but I would very much like the 2nd drive, and certainly don’t want to be without Avast!

Thanks,

Graham.

system · 2007-11-18T07:08:05.000Z

Hello again and sorry for the delay.

IRQ and DMAs are commonly referred as “interruptions” and they’re the ‘bridge’ used by the operating system and software to directly ‘speak’ to hardware components installed in your PC.

For example, you may have a super fast DVD unit or Hard Drive, but if DMA is not activated -by these days that’s activated by default- you’ll never get the maximum performance from those devices because instead ‘talking’ directly to them, OS must use a walkaround thus making the whole process really slow. DMA stands for Direct Memory Address.

I tell you a little story to graphic this:
Some days ago I finally setted up my sister computer and until I finally managed to activate DMA support for the DVD recorder, uploading data to its HD was a painfull process. Every DVD took about 30 minutes or more (damn!!) to dump it’s data -pictures, music, videos- to the hard disk. When I finally managed to activate DMA support it took no more than 10 -often less- minutes to copy all the files. As you see, having a well tweaked PC really makes the difference.

For more info just check http://en.wikipedia.org/wiki/Direct_memory_access and http://en.wikipedia.org/wiki/IRQ

Best!

Announcements