Here are some specs:

System Manufacturer BIOSTAR Group
Model TA770E3
Total amount of system memory 4.00 GB RAM
System type 64-bit operating system
Number of processor cores 4

Storage
Total size of hard disk(s) 466 GB
Disk partition (C 355 GB Free (466 GB Total)
Media drive (D CD/DVD

Graphics
Display adapter type Radeon X1600 Series (Microsoft Corporation - WDDM)
Total available graphics memory 2047 MB
Dedicated graphics memory 256 MB
Dedicated system memory 0 MB
Shared system memory 1791 MB
Display adapter driver version 8.56.1.15
Primary monitor resolution 1280x1024
DirectX version DirectX 9.0 or better

Network
Network Adapter Realtek PCIe GBE Family Controller
Network Adapter Virtual Machine Network Services Driver




By the way i went to download the VM driver but it was just a text file which said if i want the driver download virtual pc 07, but i already have that installed. So im confused about that.

Ok so I have now done all the installtions aside from the VM ones.

What is the next step you would like me to take. Or is it vital for these VM drivers to be updated.

VM not vital

We can wait for another BSOD or get more aggressive now. If you want to get more aggressive run driver verifier

Beyond that, please run Verifier with these settings:

Reboot the system and wait for it to crash to the Blue Screen. Continue to use your system normally, and if you know what causes the crash, do that repeatedly. The objective here is to get the system to crash because Driver Verifier is stressing the drivers out. If it doesn't crash for you, then let it run for at least 36 hours of continuous operation (an estimate on my part).

Reboot into Windows (after the crash) and turn off Driver Verifier by going back in and selecting "Delete existing settings" on the first page, then locate and zip up the memory dump file and upload it with your next post.

If you can't get into Windows because it crashes too soon, try it in Safe Mode.
If you can't get into Safe Mode, try using System Restore from your installation DVD to set the system back to the previous restore point that you created.

If that doesn't work, post back and we'll have to see about fixing the registry entry off-line:

Code:

Delete these registry keys (works in XP, Vista, Win7):
        HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Session Manager\Memory Management\VerifyDrivers
        HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Session Manager\Memory Management\VerifyDriverLevel

Using Driver Verifier to identify issues with Windows drivers for advanced users

Ok. Im not sure about getting aggresive because I dont really have access to another PC at the moment as im at University.

I just completed the SFC scan and it complete saying windows rescource protection did not find any integrity violations.

How about doing what you mentioned in your first post:

USBHUB.sys. Your USB hub is causing a driver timeout. You may have to many devices (unpowered) on the usb chain etc.
Re-install the USB driver and run a system file check

Can you guide me step by step in how to do this because I think this is where the problem is.

Looks like I didnt need to force anything as i just got another BSOD.

The dump file is attached!

Hi Sun-head

Same USBHUB, same old drivers. BIOS64.sys (2003)

That bios64 file may be the reason that you keep crashing. It is from 7 years before win 7 was released and so cannot know how to function in win 7.

See pic


Ken J

Hi.

I followed the online manual and it said update the bios i had to use the bios utility on the website. So I completed that and when it rebooted it Blue Screened so im attaching the dump for that. After that blue screen, which was a different one to previous ones, I restarted the machine again and it loaded up fine.

Anyway here is the dump. How can you check is the BIOS64 has been updated or not.

This crash was caused by your AVG remove it and replace it with Microsoft Security essentials

Code:

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


Loading Dump File [C:\Users\K\Desktop\New folder (5)\011411-35833-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;srv*e:\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.16617.amd64fre.win7_gdr.100618-1621
Machine Name:
Kernel base = 0xfffff800`01c5b000 PsLoadedModuleList = 0xfffff800`01e98e50
Debug session time: Fri Jan 14 07:51:50.778 2011 (GMT-5)
System Uptime: 0 days 0:00:31.761
Loading Kernel Symbols
...............................................................
................................................................
...........
Loading User Symbols
Loading unloaded module list
....
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 1000007E, {ffffffffc0000005, fffff88001060141, fffff88001faa968, fffff88001faa1d0}

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

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

2: 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: fffff88001060141, The address that the exception occurred at
Arg3: fffff88001faa968, Exception Record Address
Arg4: fffff88001faa1d0, 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: 
fltmgr!TreeUnlinkMulti+51
fffff880`01060141 488b4620        mov     rax,qword ptr [rsi+20h]

EXCEPTION_RECORD:  fffff88001faa968 -- (.exr 0xfffff88001faa968)
ExceptionAddress: fffff88001060141 (fltmgr!TreeUnlinkMulti+0x0000000000000051)
   ExceptionCode: c0000005 (Access violation)
  ExceptionFlags: 00000000
NumberParameters: 2
   Parameter[0]: 0000000000000000
   Parameter[1]: ffffffffffffffff
Attempt to read from address ffffffffffffffff

CONTEXT:  fffff88001faa1d0 -- (.cxr 0xfffff88001faa1d0)
rax=ff0c67c2ff0c67c2 rbx=0000000000000000 rcx=fffffa80057ed308
rdx=fffffa8005ad0650 rsi=ff0d68c3ff0d68c3 rdi=0000000000000000
rip=fffff88001060141 rsp=fffff88001faaba0 rbp=fffffa80057ed308
 r8=ffffffffffffffff  r9=ffffffffffffffff r10=0000000000000050
r11=0000000000000001 r12=fffffa8005ad0650 r13=fffffa8004759684
r14=0000000000004000 r15=0000000000000000
iopl=0         nv up ei ng nz na po nc
cs=0010  ss=0000  ds=002b  es=002b  fs=0053  gs=002b             efl=00010286
fltmgr!TreeUnlinkMulti+0x51:
fffff880`01060141 488b4620        mov     rax,qword ptr [rsi+20h] ds:002b:ff0d68c3`ff0d68e3=????????????????
Resetting default scope

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

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:  0000000000000000

EXCEPTION_PARAMETER2:  ffffffffffffffff

READ_ADDRESS: GetPointerFromAddress: unable to read from fffff80001f030e0
 ffffffffffffffff 

FOLLOWUP_IP: 
avgmfx64+13ea
fffff880`0197e3ea ??              ???

BUGCHECK_STR:  0x7E

LAST_CONTROL_TRANSFER:  from fffff8800105d460 to fffff88001060141

STACK_TEXT:  
fffff880`01faaba0 fffff880`0105d460 : fffffa80`05a5b010 fffffa80`05ad0650 fffffa80`05a5b010 fffff800`01fe1196 : fltmgr!TreeUnlinkMulti+0x51
fffff880`01faabf0 fffff880`0105dbe9 : fffff880`01fa8000 00000000`00000702 fffffa80`0428dd00 fffffa80`055d4500 : fltmgr!FltpPerformPreCallbacks+0x730
fffff880`01faacf0 fffff880`0105c6c7 : fffffa80`05a41ab0 fffffa80`0428dde0 fffffa80`04067e40 00000000`00000000 : fltmgr!FltpPassThrough+0x2d9
fffff880`01faad70 fffff800`01fe178e : fffffa80`05ad0650 fffffa80`04202820 00000000`00000000 fffffa80`0428dde0 : fltmgr!FltpDispatch+0xb7
fffff880`01faadd0 fffff800`01cd08b4 : fffffa80`05ac0f00 fffff8a0`01c2be40 fffffa80`036d8210 fffff8a0`01c2be40 : nt!IopDeleteFile+0x11e
fffff880`01faae60 fffff880`0197e3ea : fffff8a0`01c2be40 fffffa80`05ac0f00 00000000`00000000 fffffa80`05ac0a00 : nt!ObfDereferenceObject+0xd4
fffff880`01faaec0 fffff8a0`01c2be40 : fffffa80`05ac0f00 00000000`00000000 fffffa80`05ac0a00 fffff880`01e5c180 : avgmfx64+0x13ea
fffff880`01faaec8 fffffa80`05ac0f00 : 00000000`00000000 fffffa80`05ac0a00 fffff880`01e5c180 00000000`00000000 : 0xfffff8a0`01c2be40
fffff880`01faaed0 00000000`00000000 : fffffa80`05ac0a00 fffff880`01e5c180 00000000`00000000 00000000`00000000 : 0xfffffa80`05ac0f00


SYMBOL_STACK_INDEX:  6

SYMBOL_NAME:  avgmfx64+13ea

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: avgmfx64

IMAGE_NAME:  avgmfx64.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  4c858c0a

STACK_COMMAND:  .cxr 0xfffff88001faa1d0 ; kb

FAILURE_BUCKET_ID:  X64_0x7E_avgmfx64+13ea

BUCKET_ID:  X64_0x7E_avgmfx64+13ea

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

AVG - Download tools

http://www.microsoft.com/security_essentials/


And yes the BIOS64.sys is still the same (2003)


Ken J

Damn.

Well How can I change this damn BIOS64.sys. Basically in the file you told me to download of their site before, i found a folder inside packages called Drivers, but the has 3 sub folder all of which have many sub folders.


So when in go into drivers folder, there are then 3 folders:

WDM
SBDrv
Display

Inside WDM there are these folders:

TVW_HSUSB
RIO
AVS_T200
AVS_HSUSB

Some of these also have subfolders aswell

Inside SBDrv you find:

SB7xx
SB6xx
Filter

Again these have sub folders

Finally Display:

W76A_INF
W7_INF

I dont have a clue where to find this driver or a installation for it!

I was wondering if you could dowload the same file you told me to get of this same link BIOSTAR :: TA770E3 :: Driver . Then you can look through the sub folders and check which driver i require to install. Also when i went on the support page for biostar, i did a scan which they provided and ive put the results in a word document for you. Hope it may help.

I am curious. Have you removed AVG and replaced it with MSE?

No not yet reason why is because i just bought a license a few months back. But I cant see why it needs to be replaced for this BIOS64.sys to be updated.

It doesnt but we dont "know" that the BIOS64.sys is the "sole" cause. It may be the interaction between them.

We just suggest, you need to decide what is right for you.

I understand.

I was wondering then remember when you said this:

USBHUB.sys. Your USB hub is causing a driver timeout. You may have to many devices (unpowered) on the usb chain etc.

Re-install the USB driver and run a system file check



Could you guide me step by step on how to do this, If this doesnt work then Im gonna have to consider your option on replacing AVG.

Thanks Again

Just had another Blue Screen. Mouse stopped working, looked at the bottom of it and the red light was off. Tried takin the usb out and plugging it in again. Mouse still wouldnt work, 30 seconds later BSOD. This leads me to think that the problem is with something USB related. Here are the dump files