parishpete
New Member
- Joined
- Sep 30, 2010
- Messages
- 204
- Thread Author
-
- #1
Microsoft Windows 7 Home Premium
Version 6.1.7600 Build 7600
Asus M4N78 motherboard
Nvidia Geforce 9500GT
2 x Seagate ST3500418AS 500Gb disks striping RAID
1 1Tb Freeagent Pro ESATA
LITE-ON DVDRW SOHW-1693S ATA Device
Optiarc DVD RW AD-7241S SCSI CdRom Device
System Type X86-based PC
Processor AMD Phenom(tm) II X4 955 Processor, 3200 Mhz, 4 Core(s), 4 Logical Processor(s)
BIOS Version/Date American Megatrends Inc. 1103, 28/04/2010 updated today
SMBIOS Version 2.5
Hardware Abstraction Layer Version = "6.1.7600.16385"
Installed Physical Memory (RAM) 4.00 GB
Total Physical Memory 3.25 GB
Available Physical Memory 1.91 GB
Total Virtual Memory 6.50 GB
Available Virtual Memory 5.04 GB
Page File Space 3.25 GB
My PC was bespoke built 11 months ago by a local shop which unfortunately went bust a month later after 15 years of trading. It is the fourth they had built for me and the other three have all been superb.
I have suffered a BSOD at power up several times each week since it was a fortnight old. It was built into an existing case and save for the front USB port, the Lite-on DVD and the case fans, the rest was new. Though the keyboard & mouse have only just been updated a month ago.
The First BSOD came after connecting a rear USB port from the old case so I removed it but I think it was a red herring.
In the new build I installed all my software and only some Bluetooth drivers showed up as unsigned. These I later uninstalled in case they were the culprits. No change.
The BSOD’s continued, culminating in Win7 declaring itself non-genuine which even Microsoft could not sort out and required a clean install last May. It has done it again once since May but that was overcome by re-entering the key.
Following rebuild I put the software back in stages (all regular stuff; Office 2007, Photoshop Elements, Powerdirector, Itunes. No games or suchlike. The BSOD’s continue to this day.
Very occasionally, perhaps twice since May, a BSOD has occurred while running an application but otherwise once up and running it behaves perfectly.
I sense that since there have been a number of auto disk scans, that the striping RAID array on one of the 2 Disks is at fault. I know that Nvidia chipset and Raid drivers are up to date and the Bios is fully up to date as of today.
The minidump files and driver & system data are attached. All help gratefully received
Pete
Version 6.1.7600 Build 7600
Asus M4N78 motherboard
Nvidia Geforce 9500GT
2 x Seagate ST3500418AS 500Gb disks striping RAID
1 1Tb Freeagent Pro ESATA
LITE-ON DVDRW SOHW-1693S ATA Device
Optiarc DVD RW AD-7241S SCSI CdRom Device
System Type X86-based PC
Processor AMD Phenom(tm) II X4 955 Processor, 3200 Mhz, 4 Core(s), 4 Logical Processor(s)
BIOS Version/Date American Megatrends Inc. 1103, 28/04/2010 updated today
SMBIOS Version 2.5
Hardware Abstraction Layer Version = "6.1.7600.16385"
Installed Physical Memory (RAM) 4.00 GB
Total Physical Memory 3.25 GB
Available Physical Memory 1.91 GB
Total Virtual Memory 6.50 GB
Available Virtual Memory 5.04 GB
Page File Space 3.25 GB
My PC was bespoke built 11 months ago by a local shop which unfortunately went bust a month later after 15 years of trading. It is the fourth they had built for me and the other three have all been superb.
I have suffered a BSOD at power up several times each week since it was a fortnight old. It was built into an existing case and save for the front USB port, the Lite-on DVD and the case fans, the rest was new. Though the keyboard & mouse have only just been updated a month ago.
The First BSOD came after connecting a rear USB port from the old case so I removed it but I think it was a red herring.
In the new build I installed all my software and only some Bluetooth drivers showed up as unsigned. These I later uninstalled in case they were the culprits. No change.
The BSOD’s continued, culminating in Win7 declaring itself non-genuine which even Microsoft could not sort out and required a clean install last May. It has done it again once since May but that was overcome by re-entering the key.
Following rebuild I put the software back in stages (all regular stuff; Office 2007, Photoshop Elements, Powerdirector, Itunes. No games or suchlike. The BSOD’s continue to this day.
Very occasionally, perhaps twice since May, a BSOD has occurred while running an application but otherwise once up and running it behaves perfectly.
I sense that since there have been a number of auto disk scans, that the striping RAID array on one of the 2 Disks is at fault. I know that Nvidia chipset and Raid drivers are up to date and the Bios is fully up to date as of today.
The minidump files and driver & system data are attached. All help gratefully received
Pete
Solution
Wow! Bsod machine you have there! haha Welcome!
Let's move on to fixing this, shall we?
First and foremost: Uninstall the AVG in safe mode with this tool:
AV Uninstallers - Windows 7 Forums
Reboot and install MSE to replace it.
-----------------
Your Broadcom Bluetooth drivers are too old. They must be updated:
btwrchid btwrchid.sys Mon Feb 26 00:08:38 2007
btwaudio btwaudio.sys Mon Feb 26 00:07:42 2007
btwavdt btwavdt.sys Mon Feb 26 00:06:24 2007
----------
Your Logitech QuickCam drivers are too old and must be updated:
LVUSBSta LVUSBSta.sys Fri May 11 19:40:49 2007
Link Removed
--------------
This ATK0110 driver is so old from 2004 that it will drive any Win7 PC bonkers. Install this to update it...
Let's move on to fixing this, shall we?
First and foremost: Uninstall the AVG in safe mode with this tool:
AV Uninstallers - Windows 7 Forums
Reboot and install MSE to replace it.
-----------------
Your Broadcom Bluetooth drivers are too old. They must be updated:
btwrchid btwrchid.sys Mon Feb 26 00:08:38 2007
btwaudio btwaudio.sys Mon Feb 26 00:07:42 2007
btwavdt btwavdt.sys Mon Feb 26 00:06:24 2007
----------
Your Logitech QuickCam drivers are too old and must be updated:
LVUSBSta LVUSBSta.sys Fri May 11 19:40:49 2007
Link Removed
--------------
This ATK0110 driver is so old from 2004 that it will drive any Win7 PC bonkers. Install this to update it...
Wow! Bsod machine you have there! haha Welcome!
Let's move on to fixing this, shall we?
First and foremost: Uninstall the AVG in safe mode with this tool:
AV Uninstallers - Windows 7 Forums
Reboot and install MSE to replace it.
-----------------
Your Broadcom Bluetooth drivers are too old. They must be updated:
btwrchid btwrchid.sys Mon Feb 26 00:08:38 2007
btwaudio btwaudio.sys Mon Feb 26 00:07:42 2007
btwavdt btwavdt.sys Mon Feb 26 00:06:24 2007
----------
Your Logitech QuickCam drivers are too old and must be updated:
LVUSBSta LVUSBSta.sys Fri May 11 19:40:49 2007
Link Removed
--------------
This ATK0110 driver is so old from 2004 that it will drive any Win7 PC bonkers. Install this to update it:
Link Removed - Invalid URL
------------
These drivers are too old and must be removed. Navigate to C:\Windows\System32\drivers and delete it then reboot:
StarOpen StarOpen.SYS Tue Jun 27 15:15:56 2006
PxHelp20 PxHelp20.sys Mon Apr 25 15:48:02 2005
Run Ccleaner to clean the registry after.
-------------
If you follow this well, your pc will be fine. Enjoy!
Please keep us updated and/or post new crash dumps so I can see what you may have missed. Good luck with it.
You'd also do well to update your NVIDIA nForce chipset drivers for your motherboard:
Link Removed - Invalid URL
Let's move on to fixing this, shall we?
First and foremost: Uninstall the AVG in safe mode with this tool:
AV Uninstallers - Windows 7 Forums
Reboot and install MSE to replace it.
-----------------
Your Broadcom Bluetooth drivers are too old. They must be updated:
btwrchid btwrchid.sys Mon Feb 26 00:08:38 2007
btwaudio btwaudio.sys Mon Feb 26 00:07:42 2007
btwavdt btwavdt.sys Mon Feb 26 00:06:24 2007
----------
Your Logitech QuickCam drivers are too old and must be updated:
LVUSBSta LVUSBSta.sys Fri May 11 19:40:49 2007
Link Removed
--------------
This ATK0110 driver is so old from 2004 that it will drive any Win7 PC bonkers. Install this to update it:
Link Removed - Invalid URL
------------
These drivers are too old and must be removed. Navigate to C:\Windows\System32\drivers and delete it then reboot:
StarOpen StarOpen.SYS Tue Jun 27 15:15:56 2006
PxHelp20 PxHelp20.sys Mon Apr 25 15:48:02 2005
Run Ccleaner to clean the registry after.
-------------
If you follow this well, your pc will be fine. Enjoy!
Please keep us updated and/or post new crash dumps so I can see what you may have missed. Good luck with it.
You'd also do well to update your NVIDIA nForce chipset drivers for your motherboard:
Link Removed - Invalid URL
Last edited:
parishpete
New Member
- Joined
- Sep 30, 2010
- Messages
- 204
- Thread Author
-
- #3
Torrent
Thanks for the speedy response, my data must have made your eyes pop out!
I take it you don't rate AVG too highly. It runs ok on my other win7 machine which is really well behaved. I'll pull it out anyway.
The Broadcoms can go, I don't use the dongle now that I have the logitech blutooth keyboard. Its dongle handles all BT peripherals.
Clearly the BIOS update I just perfomed did nothing a subsequent restart ended in BSOD!
Will let you know
thanks again
Pete
Will update the rest and hold my breath
Thanks for the speedy response, my data must have made your eyes pop out!
I take it you don't rate AVG too highly. It runs ok on my other win7 machine which is really well behaved. I'll pull it out anyway.
The Broadcoms can go, I don't use the dongle now that I have the logitech blutooth keyboard. Its dongle handles all BT peripherals.
Clearly the BIOS update I just perfomed did nothing a subsequent restart ended in BSOD!
Will let you know
thanks again
Pete
Will update the rest and hold my breath
You're welcome. Ya, last year, 3 out of every 4 machines I would look at with bsod, AVG was the culprit (and it slows down machines unnecessarily.)
They've gotten better but any machine with bsods, that's the first things I say to get rid of.
Cool....awaiting good news after some time that no further bsods happened or a new crash dump.
They've gotten better but any machine with bsods, that's the first things I say to get rid of.
Cool....awaiting good news after some time that no further bsods happened or a new crash dump.
parishpete
New Member
- Joined
- Sep 30, 2010
- Messages
- 204
- Thread Author
-
- #5
whilst on the subject of drivers, my new Logitech MX5500 keyboard and mouse works at the welcome screen but having logged on I assume takes forever to load the user defined info and is inoperable until that info is loaded.
If I get a BSOD followed by the standard start windows in safe/normal mode etc, I can't select a mode from the keyboard.
Any clues?
Pete
If I get a BSOD followed by the standard start windows in safe/normal mode etc, I can't select a mode from the keyboard.
Any clues?
Pete
Hmmm, not really. You could make sure you have the latest drivers for them too, from Logitech's site at the above link.
Other than that, by time we're through, you aren't going to be having bsod issues any longer, so it won't be an issue.
Other than that, by time we're through, you aren't going to be having bsod issues any longer, so it won't be an issue.
parishpete
New Member
- Joined
- Sep 30, 2010
- Messages
- 204
- Thread Author
-
- #7
Thanks
If it's still a pain I'll talk to Logitech. The drivers are 3 weeks old.
I'll get under the bonnet first thing in morning and keep my fingers crossed
Pete
If it's still a pain I'll talk to Logitech. The drivers are 3 weeks old.
I'll get under the bonnet first thing in morning and keep my fingers crossed
Pete
parishpete
New Member
- Joined
- Sep 30, 2010
- Messages
- 204
- Thread Author
-
- #8
Update
Torrent
The day started with a BSOD but as usual just the one.
have done all alterations as suggested.
The bluetooth drivers were the most up to date but since the device isn't used I have removed them
The same is true of the logitech quick cam. I will plug it in and see if it pulls up generic MS drivers.
The ATK installer gave no messages and flashed through quickly, so I don't know whether it worked or not. A new driver list is attached.
New chipset drivers were available as were video card drivers.
Now I just have sit back and cross my fingers! Should know what's what in a few days.
Many thanks for your help
Pete
Torrent
The day started with a BSOD but as usual just the one.
have done all alterations as suggested.
The bluetooth drivers were the most up to date but since the device isn't used I have removed them
The same is true of the logitech quick cam. I will plug it in and see if it pulls up generic MS drivers.
The ATK installer gave no messages and flashed through quickly, so I don't know whether it worked or not. A new driver list is attached.
New chipset drivers were available as were video card drivers.
Now I just have sit back and cross my fingers! Should know what's what in a few days.
Many thanks for your help
Pete
Attachments
parishpete
New Member
- Joined
- Sep 30, 2010
- Messages
- 204
- Thread Author
-
- #9
Hi Torrent, not out of the woods yet.
For an acid test, I powered down, unplugged from the mains, drank coffee, read the paper.
Powered up, logged on, and waited... windows hung. No sidebar gadgets, no keybord or mouse. waited 10 mins and reset.
came back up, BSOD, came back up ok.
Event log says staropen & pxhelp drivers failed to load. Had run Cclean. perhaps there is more to do. Kernel power 41 also showed up again.
Files attached
Thanks
Pete
For an acid test, I powered down, unplugged from the mains, drank coffee, read the paper.
Powered up, logged on, and waited... windows hung. No sidebar gadgets, no keybord or mouse. waited 10 mins and reset.
came back up, BSOD, came back up ok.
Event log says staropen & pxhelp drivers failed to load. Had run Cclean. perhaps there is more to do. Kernel power 41 also showed up again.
Files attached
Thanks
Pete
cybercore
New Member
- Joined
- Jul 7, 2009
- Messages
- 15,641
100210-16754-01.dmp
MEMORY_MANAGEMENT (1a)
nt!
Update the drivers, follow my links or check at your PC brand manufacturer's support site:
AsIO.sys Mon Dec 17 11:10:20 2007
ASUS Probe
Link Removed
lvpopflt.sys Sat May 12 02:35:49 2007
lvuvc.sys Sat May 12 02:38:36 2007
LVUSBSta.sys Sat May 12 02:40:49 2007
Logitech QuickCam
Link Removed
nvsmu.sys Mon Jun 29 10:36:34 2009
nvmf6232.sys Fri Jul 31 02:47:55 2009
nvraid.sys Wed May 20 09:43:36 2009
nvstor.sys Wed May 20 09:44:09 2009
nvrd32.sys Wed Aug 05 03:28:19 2009
nvstor32.sys Wed Aug 05 03:27:05 2009
nForce Drivers
Drivers - Download NVIDIA Drivers
I would also run memtest overnight:
RAM - Test with Memtest86+ - Windows 7 Forums
MEMORY_MANAGEMENT (1a)
nt!
Update the drivers, follow my links or check at your PC brand manufacturer's support site:
AsIO.sys Mon Dec 17 11:10:20 2007
ASUS Probe
Link Removed
lvpopflt.sys Sat May 12 02:35:49 2007
lvuvc.sys Sat May 12 02:38:36 2007
LVUSBSta.sys Sat May 12 02:40:49 2007
Logitech QuickCam
Link Removed
nvsmu.sys Mon Jun 29 10:36:34 2009
nvmf6232.sys Fri Jul 31 02:47:55 2009
nvraid.sys Wed May 20 09:43:36 2009
nvstor.sys Wed May 20 09:44:09 2009
nvrd32.sys Wed Aug 05 03:28:19 2009
nvstor32.sys Wed Aug 05 03:27:05 2009
nForce Drivers
Drivers - Download NVIDIA Drivers
I would also run memtest overnight:
RAM - Test with Memtest86+ - Windows 7 Forums
Code:
Microsoft (R) Windows Debugger Version 6.11.0001.404 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [F:\a\Minidump\100210-16754-01.dmp]
Windows 7 Kernel Version 7600 MP (4 procs) Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 7600.16617.x86fre.win7_gdr.100618-1621
MEMORY_MANAGEMENT (1a)
# Any other values for parameter 1 must be individually examined.
Arguments:
Arg1: 00041289, The subtype of the bugcheck.
Arg2: 18068001
Arg3: 000002b0
Arg4: 1807de05
Debugging Details:
------------------
BUGCHECK_STR: 0x1a_41289
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
PROCESS_NAME: GoogleUpdate.e
CURRENT_IRQL: 0
LAST_CONTROL_TRANSFER: from 82cb4826 to 82d1ad10
STACK_TEXT:
a12efbc4 82cb4826 0000001a 00041289 18068001 nt!KeBugCheckEx+0x1e
a12efbec 82cea51f c0c611a0 c00c0340 350ff025 nt!MiLocateWsle+0xc1
a12efc10 82cebe7a a12efc98 87af5358 876a9d40 nt!MiGetPageProtection+0x107
a12efc3c 82ce3968 18068000 876a93e0 876a9d40 nt!MiQueryAddressState+0x353
a12efc78 82eb7605 18068000 876a93e0 94bf40eb nt!MiQueryAddressSpan+0x7e
a12efd14 82c8144a ffffffff 18051000 00000000 nt!NtQueryVirtualMemory+0x572
a12efd14 77a964f4 ffffffff 18051000 00000000 nt!KiFastCallEntry+0x12a
WARNING: Frame IP not in any known module. Following frames may be wrong.
0012fbbc 00000000 00000000 00000000 00000000 0x77a964f4
STACK_COMMAND: kb
FOLLOWUP_IP:
nt!MiLocateWsle+c1
82cb4826 cc int 3
SYMBOL_STACK_INDEX: 1
SYMBOL_NAME: nt!MiLocateWsle+c1
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: nt
DEBUG_FLR_IMAGE_TIMESTAMP: 4c1c3fac
IMAGE_NAME: memory_corruption
FAILURE_BUCKET_ID: 0x1a_41289_nt!MiLocateWsle+c1
BUCKET_ID: 0x1a_41289_nt!MiLocateWsle+c1
Followup: MachineOwner
---------
start end module name
80b9c000 80ba4000 kdcom kdcom.dll Tue Jul 14 04:08:58 2009 (4A5BDAAA)
82c07000 82c3e000 hal halmacpi.dll Tue Jul 14 02:11:03 2009 (4A5BBF07)
82c3e000 8304e000 nt ntkrpamp.exe Sat Jun 19 06:55:24 2010 (4C1C3FAC)
83207000 83212000 mcupdate_AuthenticAMD mcupdate_AuthenticAMD.dll Tue Jul 14 02:13:13 2009 (4A5BBF89)
83212000 83223000 PSHED PSHED.dll Tue Jul 14 04:09:36 2009 (4A5BDAD0)
83223000 8322b000 BOOTVID BOOTVID.dll Tue Jul 14 04:04:34 2009 (4A5BD9A2)
8322b000 8326d000 CLFS CLFS.SYS Tue Jul 14 02:11:10 2009 (4A5BBF0E)
8326d000 83318000 CI CI.dll Tue Jul 14 04:09:28 2009 (4A5BDAC8)
83318000 83389000 Wdf01000 Wdf01000.sys Tue Jul 14 02:11:36 2009 (4A5BBF28)
83389000 83397000 WDFLDR WDFLDR.SYS Tue Jul 14 02:11:25 2009 (4A5BBF1D)
83397000 833df000 ACPI ACPI.sys Tue Jul 14 02:11:11 2009 (4A5BBF0F)
833df000 833e8000 WMILIB WMILIB.SYS Tue Jul 14 02:11:22 2009 (4A5BBF1A)
833e8000 833f0000 msisadrv msisadrv.sys Tue Jul 14 02:11:09 2009 (4A5BBF0D)
8b809000 8b833000 pci pci.sys Tue Jul 14 02:11:16 2009 (4A5BBF14)
8b833000 8b83e000 vdrvroot vdrvroot.sys Tue Jul 14 02:46:19 2009 (4A5BC74B)
8b83e000 8b84f000 partmgr partmgr.sys Tue Jul 14 02:11:35 2009 (4A5BBF27)
8b84f000 8b85f000 volmgr volmgr.sys Tue Jul 14 02:11:25 2009 (4A5BBF1D)
8b85f000 8b8aa000 volmgrx volmgrx.sys Tue Jul 14 02:11:41 2009 (4A5BBF2D)
8b8aa000 8b8c9000 nvraid nvraid.sys Wed May 20 09:43:36 2009 (4A13A698)
8b8c9000 8b8ee000 CLASSPNP CLASSPNP.SYS Tue Jul 14 02:11:20 2009 (4A5BBF18)
8b8ee000 8b8f5000 pciide pciide.sys Tue Jul 14 02:11:19 2009 (4A5BBF17)
8b8f5000 8b903000 PCIIDEX PCIIDEX.SYS Tue Jul 14 02:11:15 2009 (4A5BBF13)
8b903000 8b96e000 nvrd32 nvrd32.sys Wed Aug 05 03:28:19 2009 (4A78D223)
8b96e000 8b984000 mountmgr mountmgr.sys Tue Jul 14 02:11:27 2009 (4A5BBF1F)
8b984000 8b98d000 atapi atapi.sys Tue Jul 14 02:11:15 2009 (4A5BBF13)
8b98d000 8b9b0000 ataport ataport.SYS Tue Jul 14 02:11:18 2009 (4A5BBF16)
8b9b0000 8b9d5000 nvstor nvstor.sys Wed May 20 09:44:09 2009 (4A13A6B9)
8b9d5000 8b9ee000 bowser bowser.sys Tue Jul 14 02:14:21 2009 (4A5BBFCD)
8b9ee000 8ba00000 mpsdrv mpsdrv.sys Tue Jul 14 02:52:52 2009 (4A5BC8D4)
8ba10000 8ba57000 storport storport.sys Tue Jul 14 02:45:58 2009 (4A5BC736)
8ba57000 8ba8e000 nvstor32 nvstor32.sys Wed Aug 05 03:27:05 2009 (4A78D1D9)
8ba8e000 8ba97000 amdxata amdxata.sys Tue May 19 20:57:35 2009 (4A12F30F)
8ba97000 8bacb000 fltmgr fltmgr.sys Tue Jul 14 02:11:13 2009 (4A5BBF11)
8bacb000 8badc000 fileinfo fileinfo.sys Tue Jul 14 02:21:51 2009 (4A5BC18F)
8badc000 8bb93000 ndis ndis.sys Tue Jul 14 02:12:24 2009 (4A5BBF58)
8bb93000 8bbd1000 NETIO NETIO.SYS Tue Jul 14 02:12:35 2009 (4A5BBF63)
8bbd1000 8bbf6000 ksecpkg ksecpkg.sys Fri Dec 11 06:04:22 2009 (4B21C4C6)
8bc00000 8bc0e000 pcw pcw.sys Tue Jul 14 02:11:10 2009 (4A5BBF0E)
8bc0e000 8bc17000 Fs_Rec Fs_Rec.sys Tue Jul 14 02:11:14 2009 (4A5BBF12)
8bc17000 8bc27000 mup mup.sys Tue Jul 14 02:14:14 2009 (4A5BBFC6)
8bc2a000 8bd59000 Ntfs Ntfs.sys Tue Jul 14 02:12:05 2009 (4A5BBF45)
8bd59000 8bd84000 msrpc msrpc.sys Tue Jul 14 02:11:59 2009 (4A5BBF3F)
8bd84000 8bd97000 ksecdd ksecdd.sys Tue Jul 14 02:11:56 2009 (4A5BBF3C)
8bd97000 8bdf4000 cng cng.sys Tue Jul 14 02:32:55 2009 (4A5BC427)
8be00000 8be08000 hwpolicy hwpolicy.sys Tue Jul 14 02:11:01 2009 (4A5BBF05)
8be0f000 8bf58000 tcpip tcpip.sys Mon Jun 14 06:36:59 2010 (4C15A3DB)
8bf58000 8bf89000 fwpkclnt fwpkclnt.sys Tue Jul 14 02:12:03 2009 (4A5BBF43)
8bf89000 8bfc8000 volsnap volsnap.sys Tue Jul 14 02:11:34 2009 (4A5BBF26)
8bfc8000 8bfd0000 spldr spldr.sys Mon May 11 19:13:47 2009 (4A084EBB)
8bfd0000 8bffd000 rdyboost rdyboost.sys Tue Jul 14 02:22:02 2009 (4A5BC19A)
8c000000 8c010000 lltdio lltdio.sys Tue Jul 14 02:53:18 2009 (4A5BC8EE)
8c010000 8c023000 rspndr rspndr.sys Tue Jul 14 02:53:20 2009 (4A5BC8F0)
8c026000 8c058000 fvevol fvevol.sys Sat Sep 26 05:24:21 2009 (4ABD7B55)
8c058000 8c069000 disk disk.sys Tue Jul 14 02:11:28 2009 (4A5BBF20)
8c069000 8c0ee000 HTTP HTTP.sys Tue Jul 14 02:12:53 2009 (4A5BBF75)
8c0ee000 8c10f000 srvnet srvnet.sys Tue Jun 22 05:47:09 2010 (4C20242D)
8c117000 8c136000 cdrom cdrom.sys Tue Jul 14 02:11:24 2009 (4A5BBF1C)
8c136000 8c159000 MpFilter MpFilter.sys Sat Mar 20 06:03:26 2010 (4BA4490E)
8c159000 8c160000 Null Null.SYS Tue Jul 14 02:11:12 2009 (4A5BBF10)
8c160000 8c167000 Beep Beep.SYS Tue Jul 14 02:45:00 2009 (4A5BC6FC)
8c167000 8c173000 vga vga.sys Tue Jul 14 02:25:50 2009 (4A5BC27E)
8c173000 8c194000 VIDEOPRT VIDEOPRT.SYS Tue Jul 14 02:25:49 2009 (4A5BC27D)
8c194000 8c1a1000 watchdog watchdog.sys Tue Jul 14 02:24:10 2009 (4A5BC21A)
8c1a1000 8c1a9000 RDPCDD RDPCDD.sys Tue Jul 14 03:01:40 2009 (4A5BCAE4)
8c1a9000 8c1b1000 rdpencdd rdpencdd.sys Tue Jul 14 03:01:39 2009 (4A5BCAE3)
8c1b1000 8c1b9000 rdprefmp rdprefmp.sys Tue Jul 14 03:01:41 2009 (4A5BCAE5)
8c1b9000 8c1c4000 Msfs Msfs.SYS Tue Jul 14 02:11:26 2009 (4A5BBF1E)
8c1c4000 8c1d2000 Npfs Npfs.SYS Tue Jul 14 02:11:31 2009 (4A5BBF23)
8c1d2000 8c1e9000 tdx tdx.sys Tue Jul 14 02:12:10 2009 (4A5BBF4A)
8c1e9000 8c1f4000 TDI TDI.SYS Tue Jul 14 02:12:12 2009 (4A5BBF4C)
8c1f4000 8c1ff000 hidusb hidusb.sys Tue Jul 14 02:51:04 2009 (4A5BC868)
8e600000 8e606480 HIDPARSE HIDPARSE.SYS Tue Jul 14 02:50:59 2009 (4A5BC863)
8e60a000 8e7dd580 lvpopflt lvpopflt.sys Sat May 12 02:35:49 2007 (4644FDD5)
8e7de000 8e7f1b00 usbaudio usbaudio.sys Tue Jul 14 02:51:23 2009 (4A5BC87B)
8e7f2000 8e7fd000 monitor monitor.sys Tue Jul 14 02:25:58 2009 (4A5BC286)
91600000 91609000 nvsmu nvsmu.sys Mon Jun 29 10:36:34 2009 (4A486F02)
91609000 91613000 usbohci usbohci.sys Tue Jul 14 02:51:14 2009 (4A5BC872)
91613000 9161e000 mouhid mouhid.sys Tue Jul 14 02:45:08 2009 (4A5BC704)
91621000 91653000 netbt netbt.sys Tue Jul 14 02:12:18 2009 (4A5BBF52)
91653000 916ad000 afd afd.sys Tue Jul 14 02:12:34 2009 (4A5BBF62)
916ad000 916b4000 wfplwf wfplwf.sys Tue Jul 14 02:53:51 2009 (4A5BC90F)
916b4000 916d3000 pacer pacer.sys Tue Jul 14 02:53:58 2009 (4A5BC916)
916d3000 916e1000 netbios netbios.sys Tue Jul 14 02:53:54 2009 (4A5BC912)
916e1000 916fb000 serial serial.sys Tue Jul 14 02:45:33 2009 (4A5BC71D)
916fb000 9170e000 wanarp wanarp.sys Tue Jul 14 02:55:02 2009 (4A5BC956)
9170e000 9171e000 termdd termdd.sys Tue Jul 14 03:01:35 2009 (4A5BCADF)
9171e000 9175f000 rdbss rdbss.sys Tue Jul 14 02:14:26 2009 (4A5BBFD2)
9175f000 91769000 nsiproxy nsiproxy.sys Tue Jul 14 02:12:08 2009 (4A5BBF48)
91769000 91773000 mssmbios mssmbios.sys Tue Jul 14 02:19:25 2009 (4A5BC0FD)
91773000 9177f000 discache discache.sys Tue Jul 14 02:24:04 2009 (4A5BC214)
9177f000 91797000 dfsc dfsc.sys Tue Jul 14 02:14:16 2009 (4A5BBFC8)
91797000 917a5000 blbdrive blbdrive.sys Tue Jul 14 02:23:04 2009 (4A5BC1D8)
917a5000 917a6440 AsIO AsIO.sys Mon Dec 17 11:10:20 2007 (47663CFC)
917a7000 917c8000 tunnel tunnel.sys Tue Jul 14 02:54:03 2009 (4A5BC91B)
917c8000 917d9000 amdppm amdppm.sys Tue Jul 14 02:11:03 2009 (4A5BBF07)
917d9000 917f1000 parport parport.sys Tue Jul 14 02:45:34 2009 (4A5BC71E)
917f1000 917f26c0 ASACPI ASACPI.sys Wed May 13 14:11:32 2009 (4A0AAAE4)
917f3000 917fd000 serenum serenum.sys Tue Jul 14 02:45:27 2009 (4A5BC717)
91804000 9184f000 USBPORT USBPORT.SYS Tue Jul 14 02:51:13 2009 (4A5BC871)
9184f000 9185e000 usbehci usbehci.sys Sat Oct 24 06:58:55 2009 (4AE27B7F)
9185e000 9187d000 HDAudBus HDAudBus.sys Tue Jul 14 02:50:55 2009 (4A5BC85F)
9187d000 918c1880 nvmf6232 nvmf6232.sys Fri Jul 31 02:47:55 2009 (4A72312B)
918c2000 918d9000 raspptp raspptp.sys Tue Jul 14 02:54:47 2009 (4A5BC947)
918d9000 918f0000 rassstp rassstp.sys Tue Jul 14 02:54:57 2009 (4A5BC951)
918f0000 918fd000 mouclass mouclass.sys Tue Jul 14 02:11:15 2009 (4A5BBF13)
918fd000 91931000 ks ks.sys Thu Mar 04 05:57:52 2010 (4B8F2FC0)
91931000 9193f000 umbus umbus.sys Tue Jul 14 02:51:38 2009 (4A5BC88A)
9193f000 91983000 usbhub usbhub.sys Sat Oct 24 07:00:05 2009 (4AE27BC5)
91983000 91994000 NDProxy NDProxy.SYS Tue Jul 14 02:54:27 2009 (4A5BC933)
9199d000 919ed000 HdAudio HdAudio.sys Tue Jul 14 02:51:46 2009 (4A5BC892)
919ed000 919f9000 kbdhid kbdhid.sys Tue Jul 14 02:45:09 2009 (4A5BC705)
94200000 9421a000 WudfPf WudfPf.sys Tue Jul 14 02:50:13 2009 (4A5BC835)
9421a000 94221d80 LHidFilt LHidFilt.Sys Thu Mar 18 10:50:19 2010 (4BA1E94B)
94222000 94229780 LMouFilt LMouFilt.Sys Thu Mar 18 10:50:27 2010 (4BA1E953)
9422b000 9425a000 portcls portcls.sys Tue Jul 14 02:51:00 2009 (4A5BC864)
9425a000 94273000 drmk drmk.sys Tue Jul 14 03:36:05 2009 (4A5BD2F5)
94273000 9427d000 Dxapi Dxapi.sys Tue Jul 14 02:25:25 2009 (4A5BC265)
9427d000 9428a000 crashdmp crashdmp.sys Tue Jul 14 02:45:50 2009 (4A5BC72E)
9428a000 942f5000 dump_nvrd32 dump_nvrd32.sys Wed Aug 05 03:28:19 2009 (4A78D223)
942f5000 9431a000 dump_CLASSPNP dump_CLASSPNP.SYS Tue Jul 14 02:11:20 2009 (4A5BBF18)
9431a000 9432b000 dump_dumpfve dump_dumpfve.sys Tue Jul 14 02:12:47 2009 (4A5BBF6F)
9432b000 94342000 usbccgp usbccgp.sys Tue Jul 14 02:51:31 2009 (4A5BC883)
94342000 94343700 USBD USBD.SYS Tue Jul 14 02:51:05 2009 (4A5BC869)
94344000 9434c880 LVUSBSta LVUSBSta.sys Sat May 12 02:40:49 2007 (4644FF01)
9434d000 943b1000 bthport bthport.sys Tue Jul 14 02:51:30 2009 (4A5BC882)
943b1000 943cc000 luafv luafv.sys Tue Jul 14 02:15:44 2009 (4A5BC020)
943cc000 943e7000 hidbth hidbth.sys Tue Jul 14 02:51:33 2009 (4A5BC885)
943e7000 943fa000 HIDCLASS HIDCLASS.SYS Tue Jul 14 02:51:01 2009 (4A5BC865)
94600000 9461b000 bthpan bthpan.sys Tue Jul 14 02:51:43 2009 (4A5BC88F)
9461b000 9462d000 bthmodem bthmodem.sys Tue Jul 14 02:51:34 2009 (4A5BC886)
9462e000 94996880 lvuvc lvuvc.sys Sat May 12 02:38:36 2007 (4644FE7C)
94997000 949ae000 USBSTOR USBSTOR.SYS Tue Jul 14 02:51:19 2009 (4A5BC877)
949ae000 949c0000 BTHUSB BTHUSB.sys Tue Jul 14 02:51:36 2009 (4A5BC888)
949c0000 949e4000 rfcomm rfcomm.sys Tue Jul 14 02:51:41 2009 (4A5BC88D)
949e4000 949f1000 BthEnum BthEnum.sys Tue Jul 14 02:51:35 2009 (4A5BC887)
949f1000 949fe000 modem modem.sys Tue Jul 14 02:55:24 2009 (4A5BC96C)
94a00000 94a18000 raspppoe raspppoe.sys Tue Jul 14 02:54:53 2009 (4A5BC94D)
94a18000 94a25000 kbdclass kbdclass.sys Tue Jul 14 02:11:15 2009 (4A5BBF13)
94a25000 94a26380 swenum swenum.sys Tue Jul 14 02:45:08 2009 (4A5BC704)
94a28000 954a5dc0 nvlddmkm nvlddmkm.sys Sat Jul 10 00:15:14 2010 (4C379162)
954a6000 954a7040 nvBridge nvBridge.kmd Sat Jul 10 00:10:11 2010 (4C379033)
954a8000 9555f000 dxgkrnl dxgkrnl.sys Fri Oct 02 03:48:33 2009 (4AC54DE1)
9555f000 95598000 dxgmms1 dxgmms1.sys Tue Jul 14 02:25:25 2009 (4A5BC265)
95598000 955a5000 CompositeBus CompositeBus.sys Tue Jul 14 02:45:26 2009 (4A5BC716)
955a5000 955b7000 AgileVpn AgileVpn.sys Tue Jul 14 02:55:00 2009 (4A5BC954)
955b7000 955cf000 rasl2tp rasl2tp.sys Tue Jul 14 02:54:33 2009 (4A5BC939)
955cf000 955da000 ndistapi ndistapi.sys Tue Jul 14 02:54:24 2009 (4A5BC930)
955da000 955fc000 ndiswan ndiswan.sys Tue Jul 14 02:54:34 2009 (4A5BC93A)
99030000 9927a000 win32k win32k.sys Sat Jun 19 07:06:50 2010 (4C1C425A)
99290000 99299000 TSDDD TSDDD.dll Tue Jul 14 03:01:40 2009 (4A5BCAE4)
992c0000 992de000 cdd cdd.dll unavailable (00000000)
9cc00000 9cc0d000 tcpipreg tcpipreg.sys Tue Jul 14 02:54:14 2009 (4A5BC926)
9cc0d000 9cc2d480 WUDFRd WUDFRd.sys Tue Jul 14 02:50:44 2009 (4A5BC854)
9cc32000 9cc55000 mrxsmb mrxsmb.sys Sat Feb 27 09:32:02 2010 (4B88CA72)
9cc55000 9cc90000 mrxsmb10 mrxsmb10.sys Sat Feb 27 09:32:21 2010 (4B88CA85)
9cc90000 9ccab000 mrxsmb20 mrxsmb20.sys Sat Feb 27 09:32:11 2010 (4B88CA7B)
9ccab000 9ccfa000 srv2 srv2.sys Tue Jun 22 05:47:19 2010 (4C202437)
9ccfa000 9cd4b000 srv srv.sys Tue Jun 22 05:47:32 2010 (4C202444)
9cd4b000 9cd53e00 MpNWMon MpNWMon.sys Sat Mar 20 06:03:24 2010 (4BA4490C)
9cd54000 9cd5b000 parvdm parvdm.sys Tue Jul 14 02:45:29 2009 (4A5BC719)
9cd5b000 9cdf2000 peauth peauth.sys Tue Jul 14 03:35:44 2009 (4A5BD2E0)
9cdf2000 9cdfc000 secdrv secdrv.SYS Wed Sep 13 16:18:32 2006 (45080528)
parishpete
New Member
- Joined
- Sep 30, 2010
- Messages
- 204
- Thread Author
-
- #11
Hi Cybercore,
Thanks for your response there are a few things I don't understand:
Asio.sys. I've downloded the latest drivers from Asus yesterday:
Bios, Bios utilities & Chipset. Audio i did just now. I haven't done utilities or other downloads. I held off utilities because it ATK110 which Torrent gave me a seperate link to.
Can you confirm which set of downloads contains it please.
I took out logitech cam drivers and allowed Win7 to search. No Logitech software is installed and the drivers listed are those found by Win 7. They may be old but they are the newest available for the cam.
The Nforce drivers must be part of the chipset as some of these look like storage drivers. Nvidia storage was updated yesterday as part of the chipset but those you refer to could be under 'other' downloads. There are some RAID drivers there. I have just downloaded them but they are the same age.
Many thanks
Pete
What are they drivers for?
I ran Memtest 3 times during the last month for 24+ hours at a time. no error reported.
Thanks for your response there are a few things I don't understand:
Asio.sys. I've downloded the latest drivers from Asus yesterday:
Bios, Bios utilities & Chipset. Audio i did just now. I haven't done utilities or other downloads. I held off utilities because it ATK110 which Torrent gave me a seperate link to.
Can you confirm which set of downloads contains it please.
I took out logitech cam drivers and allowed Win7 to search. No Logitech software is installed and the drivers listed are those found by Win 7. They may be old but they are the newest available for the cam.
The Nforce drivers must be part of the chipset as some of these look like storage drivers. Nvidia storage was updated yesterday as part of the chipset but those you refer to could be under 'other' downloads. There are some RAID drivers there. I have just downloaded them but they are the same age.
Many thanks
Pete
What are they drivers for?
I ran Memtest 3 times during the last month for 24+ hours at a time. no error reported.
parishpete
New Member
- Joined
- Sep 30, 2010
- Messages
- 204
- Thread Author
-
- #12
Hi
I just found Aiso.sys is part of Asus Probe. The latest download is the same age.
The drivers for my 2 dvd drives seem to have corrupted or disappeared in the melee. Windows refuses to update or roll back because they present. any clues..
Many thanks
Pete
I just found Aiso.sys is part of Asus Probe. The latest download is the same age.
The drivers for my 2 dvd drives seem to have corrupted or disappeared in the melee. Windows refuses to update or roll back because they present. any clues..
Many thanks
Pete
cybercore
New Member
- Joined
- Jul 7, 2009
- Messages
- 15,641
If there's nothing newer than 2007 drivers for the Quick cam, then disconnect it and then uninstall it from your system for the period of troubleshooting. Old drivers often cause blue screens.
What do you mean by this:
Attach any new crash dumps.
What do you mean by this:
The drivers for my 2 dvd drives seem to have corrupted or disappeared in the melee.
Attach any new crash dumps.
cybercore
New Member
- Joined
- Jul 7, 2009
- Messages
- 15,641
Ok, but this was the last month. If you don't want to do it again, at least run the memory diagnostic tool:I ran Memtest 3 times during the last month for 24+ hours at a time. no error reported.
Diagnosing memory problems on your computer
Use system recovery options to diagnose memory in Windows 7?
parishpete
New Member
- Joined
- Sep 30, 2010
- Messages
- 204
- Thread Author
-
- #15
Ignore the ROM driver issue it has been put right.
When I said memtest 3 times in the last month I should have added the last test was for 36 hours only 6 days ago and came up clean. Ive just run the diagnostic you suggested and that came up clean too.
Will uninstall the cam. however this link says it's OK: Windows 7 Compatibility for Logitech Quickcam Pro 5000 Webcam: Logitech. Drivers, Updates, Downloads
I just let windows install it like any other USB kit. without OEM software
Any further advice on the Asus/Nvidia drivers? All that I can find are old but supposedly current.
Have attached up to the minute data
Kind regards
Pete
When I said memtest 3 times in the last month I should have added the last test was for 36 hours only 6 days ago and came up clean. Ive just run the diagnostic you suggested and that came up clean too.
Will uninstall the cam. however this link says it's OK: Windows 7 Compatibility for Logitech Quickcam Pro 5000 Webcam: Logitech. Drivers, Updates, Downloads
I just let windows install it like any other USB kit. without OEM software
Any further advice on the Asus/Nvidia drivers? All that I can find are old but supposedly current.
Have attached up to the minute data
Kind regards
Pete
Update Logitech drivers for everything you have from them (camera, keyboard, mouse, anything else I've missed):
LVUSBSta LVUSBSta.sys Fri May 11 19:40:49 2007
lvuvc lvuvc.sys Fri May 11 19:38:36 2007
LHidFilt LHidFilt.Sys Wed Jun 17 12:49:04 2009
LMouFilt LMouFilt.Sys Wed Jun 17 12:49:08 2009
lvpopflt lvpopflt.sys Fri May 11 19:35:49 2007
lvuvc lvuvc.sys Fri May 11 19:38:36 2007
Link Removed
Run this command from an elevated command prompt:
chkdsk /r
LVUSBSta LVUSBSta.sys Fri May 11 19:40:49 2007
lvuvc lvuvc.sys Fri May 11 19:38:36 2007
LHidFilt LHidFilt.Sys Wed Jun 17 12:49:04 2009
LMouFilt LMouFilt.Sys Wed Jun 17 12:49:08 2009
lvpopflt lvpopflt.sys Fri May 11 19:35:49 2007
lvuvc lvuvc.sys Fri May 11 19:38:36 2007
Link Removed
Run this command from an elevated command prompt:
chkdsk /r
Last edited:
parishpete
New Member
- Joined
- Sep 30, 2010
- Messages
- 204
- Thread Author
-
- #17
Thanks Torrent,
Some of the files are for the quickcam, some for MX5500 keyboard & mouse
I unstalled the drivers for the cam just before your message followed by a restart but
lvpopflt.sys
LVUSBSta.sys
lvuvc.sys Fri May 11 19:38:36 2007
are still on board
Is it safe to simply find and delete them?
With regard to MX5500 drivers I spoke to logitech this morning re my slow loading issue (The keyboard & mouse don't work until windows has fully loaded)and they told me to re-install the earlier software. It was complete nonsense and made no difference. I have emailed them and await their further instruction. I'll leave the drivers be for the moment. It may not help but the BSOD has been around 10 months longer than the keyboard & mouse.
Finally what's and "elevated" command prompt? I'm familiar with chkdsk and its switches
regards
pete
Some of the files are for the quickcam, some for MX5500 keyboard & mouse
I unstalled the drivers for the cam just before your message followed by a restart but
lvpopflt.sys
LVUSBSta.sys
lvuvc.sys Fri May 11 19:38:36 2007
are still on board
Is it safe to simply find and delete them?
With regard to MX5500 drivers I spoke to logitech this morning re my slow loading issue (The keyboard & mouse don't work until windows has fully loaded)and they told me to re-install the earlier software. It was complete nonsense and made no difference. I have emailed them and await their further instruction. I'll leave the drivers be for the moment. It may not help but the BSOD has been around 10 months longer than the keyboard & mouse.
Finally what's and "elevated" command prompt? I'm familiar with chkdsk and its switches
regards
pete
Yeah, please don't receive advice from elsewhere while I'm helping you. Believe me when I tell you, anything else than what I say will always take you in the wrong direction, like Logitech did.
Elevated means to run as administrator. You can right click the shortcut and choose "run as administrator".
Yes, if you've removed the camera from the system, you can delete those 2 driver files, reboot, then run Ccleaner to clean the registry.
They're in C:\Windows\System32\drivers
There isn't an update for them though, for the camera?
Elevated means to run as administrator. You can right click the shortcut and choose "run as administrator".
Yes, if you've removed the camera from the system, you can delete those 2 driver files, reboot, then run Ccleaner to clean the registry.
They're in C:\Windows\System32\drivers
There isn't an update for them though, for the camera?
parishpete
New Member
- Joined
- Sep 30, 2010
- Messages
- 204
- Thread Author
-
- #19
Thanks Torrent,
The logitech site only gives drivers for quickcam pro 5000 up to Vista. MS Win 7 compatibility says the cam is ok, I assume on generic drivers, though it failed to load other than those in my driver list. I'll leave it off for the moment.
The keyboard and mouse issue shouldn't be related they are less than a month old. but I'll put back the latest issue of setpoint.
I'll delete the leftover cam drivers and see what happens over the next few days.
I'm still not clear about the Nforce drivers your fellow member referred to. The motherboard drivers should all be current now.
regards
pete
The logitech site only gives drivers for quickcam pro 5000 up to Vista. MS Win 7 compatibility says the cam is ok, I assume on generic drivers, though it failed to load other than those in my driver list. I'll leave it off for the moment.
The keyboard and mouse issue shouldn't be related they are less than a month old. but I'll put back the latest issue of setpoint.
I'll delete the leftover cam drivers and see what happens over the next few days.
I'm still not clear about the Nforce drivers your fellow member referred to. The motherboard drivers should all be current now.
regards
pete
Yeah, Cybercore knows well too. I've been teaching him and he's learned an extremely large amount of knowledge in a very short time. Excellent.
Run that checkdisk command I've shown above. The latest crash you posted was involving the file system NTFS, as it was a 0x24 crash.
On Windows 7, you really don't want any older drivers than July 2009, with a certain special exception here or there.
When machines crash like yours, it's very important to have all peripheral drivers as new as possible, like we've been doing. Hopefully now that drivers are updated/removed, and the bad sector scan runs on the hard drive, crashes will no longer take place. If they do, please post and we will be sure to pick out anything further that may need attention.
Run that checkdisk command I've shown above. The latest crash you posted was involving the file system NTFS, as it was a 0x24 crash.
On Windows 7, you really don't want any older drivers than July 2009, with a certain special exception here or there.
When machines crash like yours, it's very important to have all peripheral drivers as new as possible, like we've been doing. Hopefully now that drivers are updated/removed, and the bad sector scan runs on the hard drive, crashes will no longer take place. If they do, please post and we will be sure to pick out anything further that may need attention.