Return of Random BSOD

G

George634

New member
Local time
9:49 PM
Messages
6
Three weks ago I performed the recommended updates and thought my BSODs were cured. However, they continue at a lessened frequency. Past recommendation was to update the AE1000 driver. The most recent Win 7 driver is installed. See atttached files for current machine status. The dump files include the previous as well as the new files.
Again, thank you for your help.
George
 

My Computer

Computer Manufacturer/Model Number
HP p6516f
OS
Win 7 Home Premium 64 bit
CPU
AMD Athlon IIx4 630
Motherboard
2A92 1.01
Memory
6 GB
Graphics Card(s)
RS880
Monitor(s) Displays
HP 2010i
Hard Drives
WDC WD10EADS-65P6B0 SCSI (931 GB)
Crashes are still being caused by your Linksys adapter.

Start off by disabling automatic driver install
http://www.sevenforums.com/drivers/82054-turn-off-windows-7-automatic-driver-installation.html

Next, go into device manager and uninstall the device. Choose the option to remove the drivers if given one. After it is removed reboot the computer and when you boot back up install the drivers you downloaded from the Linksys site.

If this doesn't solve the problem then you most likely have a bad adapter.

BSOD BUGCHECK SUMMARY
Code: 
[font=lucida console]
Built by: 7601.17592.amd64fre.win7sp1_gdr.110408-1631
Debug session time: Thu May 26 16:19:32.969 2011 (UTC - 4:00)
System Uptime: 0 days 3:10:05.686
*** WARNING: Unable to verify timestamp for ae1000w7.sys
*** ERROR: Module load completed but symbols could not be loaded for ae1000w7.sys
Probably caused by : ae1000w7.sys
BUGCHECK_STR:  0x9F
PROCESS_NAME:  System
FAILURE_BUCKET_ID:  X64_0x9F_3_IMAGE_ae1000w7.sys
BiosReleaseDate = 09/07/2010
SystemManufacturer = Hewlett-Packard
SystemProductName = p6516f
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7601.17592.amd64fre.win7sp1_gdr.110408-1631
Debug session time: Tue May 17 12:52:10.699 2011 (UTC - 4:00)
System Uptime: 0 days 1:29:06.425
*** WARNING: Unable to verify timestamp for ae1000w7.sys
*** ERROR: Module load completed but symbols could not be loaded for ae1000w7.sys
Probably caused by : ae1000w7.sys
BUGCHECK_STR:  0x9F
PROCESS_NAME:  System
FAILURE_BUCKET_ID:  X64_0x9F_3_IMAGE_ae1000w7.sys
BiosReleaseDate = 09/07/2010
SystemManufacturer = Hewlett-Packard
SystemProductName = p6516f
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7601.17514.amd64fre.win7sp1_rtm.101119-1850
Debug session time: Tue May 10 17:03:34.609 2011 (UTC - 4:00)
System Uptime: 0 days 22:54:07.183
*** WARNING: Unable to verify timestamp for ae1000w7.sys
*** ERROR: Module load completed but symbols could not be loaded for ae1000w7.sys
Probably caused by : ae1000w7.sys
BUGCHECK_STR:  0x9F
PROCESS_NAME:  System
FAILURE_BUCKET_ID:  X64_0x9F_3_IMAGE_ae1000w7.sys
BiosReleaseDate = 09/07/2010
SystemManufacturer = Hewlett-Packard
SystemProductName = p6516f
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7601.17514.amd64fre.win7sp1_rtm.101119-1850
Debug session time: Tue May  3 00:48:37.530 2011 (UTC - 4:00)
System Uptime: 0 days 0:56:23.888
*** WARNING: Unable to verify timestamp for ae1000w7.sys
*** ERROR: Module load completed but symbols could not be loaded for ae1000w7.sys
Probably caused by : ae1000w7.sys
BUGCHECK_STR:  0x9F
PROCESS_NAME:  System
FAILURE_BUCKET_ID:  X64_0x9F_3_IMAGE_ae1000w7.sys
BiosReleaseDate = 09/07/2010
SystemManufacturer = Hewlett-Packard
SystemProductName = p6516f
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7601.17514.amd64fre.win7sp1_rtm.101119-1850
Debug session time: Mon May  2 23:08:35.965 2011 (UTC - 4:00)
System Uptime: 0 days 6:09:51.697
*** WARNING: Unable to verify timestamp for ae1000w7.sys
*** ERROR: Module load completed but symbols could not be loaded for ae1000w7.sys
Probably caused by : ae1000w7.sys
BUGCHECK_STR:  0x9F
PROCESS_NAME:  System
FAILURE_BUCKET_ID:  X64_0x9F_3_IMAGE_ae1000w7.sys
BiosReleaseDate = 09/07/2010
SystemManufacturer = Hewlett-Packard
SystemProductName = p6516f
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7601.17514.amd64fre.win7sp1_rtm.101119-1850
Debug session time: Mon May  2 16:08:52.424 2011 (UTC - 4:00)
System Uptime: 0 days 2:21:37.767
*** WARNING: Unable to verify timestamp for ae1000w7.sys
*** ERROR: Module load completed but symbols could not be loaded for ae1000w7.sys
Probably caused by : ae1000w7.sys
BUGCHECK_STR:  0x9F
PROCESS_NAME:  System
FAILURE_BUCKET_ID:  X64_0x9F_3_IMAGE_ae1000w7.sys
BiosReleaseDate = 09/07/2010
SystemManufacturer = Hewlett-Packard
SystemProductName = p6516f
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7601.17514.amd64fre.win7sp1_rtm.101119-1850
Debug session time: Mon May  2 02:41:14.586 2011 (UTC - 4:00)
System Uptime: 0 days 1:04:36.944
*** WARNING: Unable to verify timestamp for ae1000w7.sys
*** ERROR: Module load completed but symbols could not be loaded for ae1000w7.sys
Probably caused by : ae1000w7.sys
BUGCHECK_STR:  0x9F
PROCESS_NAME:  System
FAILURE_BUCKET_ID:  X64_0x9F_3_IMAGE_ae1000w7.sys
BiosReleaseDate = 09/07/2010
SystemManufacturer = Hewlett-Packard
SystemProductName = p6516f
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7601.17514.amd64fre.win7sp1_rtm.101119-1850
Debug session time: Mon May  2 01:00:26.225 2011 (UTC - 4:00)
System Uptime: 0 days 0:51:36.957
*** WARNING: Unable to verify timestamp for ae1000w7.sys
*** ERROR: Module load completed but symbols could not be loaded for ae1000w7.sys
Probably caused by : ae1000w7.sys
BUGCHECK_STR:  0x9F
PROCESS_NAME:  System
FAILURE_BUCKET_ID:  X64_0x9F_3_IMAGE_ae1000w7.sys
BiosReleaseDate = 04/12/2010
SystemManufacturer = Hewlett-Packard
SystemProductName = p6516f
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7601.17514.amd64fre.win7sp1_rtm.101119-1850
Debug session time: Sun May  1 21:21:36.639 2011 (UTC - 4:00)
System Uptime: 0 days 2:00:06.372
*** WARNING: Unable to verify timestamp for ae1000w7.sys
*** ERROR: Module load completed but symbols could not be loaded for ae1000w7.sys
Probably caused by : ae1000w7.sys
BUGCHECK_STR:  0x9F
PROCESS_NAME:  System
FAILURE_BUCKET_ID:  X64_0x9F_3_IMAGE_ae1000w7.sys
BiosReleaseDate = 04/12/2010
SystemManufacturer = Hewlett-Packard
SystemProductName = p6516f
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7601.17514.amd64fre.win7sp1_rtm.101119-1850
Debug session time: Sun May  1 13:36:44.969 2011 (UTC - 4:00)
System Uptime: 0 days 2:02:54.229
*** WARNING: Unable to verify timestamp for ae1000w7.sys
*** ERROR: Module load completed but symbols could not be loaded for ae1000w7.sys
Probably caused by : ae1000w7.sys
BUGCHECK_STR:  0x9F
PROCESS_NAME:  System
FAILURE_BUCKET_ID:  X64_0x9F_3_IMAGE_ae1000w7.sys
BiosReleaseDate = 04/12/2010
SystemManufacturer = Hewlett-Packard
SystemProductName = p6516f
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7601.17514.amd64fre.win7sp1_rtm.101119-1850
Debug session time: Sat Apr 30 18:01:31.838 2011 (UTC - 4:00)
System Uptime: 2 days 11:41:38.196
*** WARNING: Unable to verify timestamp for ae1000w7.sys
*** ERROR: Module load completed but symbols could not be loaded for ae1000w7.sys
Probably caused by : ae1000w7.sys
BUGCHECK_STR:  0x9F
PROCESS_NAME:  System
FAILURE_BUCKET_ID:  X64_0x9F_3_IMAGE_ae1000w7.sys
BiosReleaseDate = 04/12/2010
SystemManufacturer = Hewlett-Packard
SystemProductName = p6516f
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
  
[/font]
 

My Computer

Computer Manufacturer/Model Number
Self Built
OS
Windows 7 Home Premium 64bit
CPU
Intel Core i5-2500 @ 3.8GHz
Motherboard
MSI P67A-GD65
Memory
G.SKILL Ripjaws Series 8GB (2 x 4GB) DDR3 1600
Graphics Card(s)
NVIDIA GTX 550Ti
Sound Card
On Board
Monitor(s) Displays
ASUS 23"
Hard Drives
OCZ Vertex 3 VTX3-25SAT3-60G
Keyboard
Wireless
Mouse
Wireless
Completed the tasks. However, when I rebooted the driver was automatically installed. I presume it was the one I doenloaded. Had one crash already. Only happens when the computer is in standby due to inactivity. I have never had one while actively using the unit.
 

My Computer

Computer Manufacturer/Model Number
HP p6516f
OS
Win 7 Home Premium 64 bit
CPU
AMD Athlon IIx4 630
Motherboard
2A92 1.01
Memory
6 GB
Graphics Card(s)
RS880
Monitor(s) Displays
HP 2010i
Hard Drives
WDC WD10EADS-65P6B0 SCSI (931 GB)
George634 said:
Completed the tasks. However, when I rebooted the driver was automatically installed. I presume it was the one I doenloaded. Had one crash already. Only happens when the computer is in standby due to inactivity. I have never had one while actively using the unit.
Click to expand...

No. If the driver was reinstalled automatically then it was the Windows driver. Sometimes installing a 3rd party driver on top of a windows driver can cause issues.

Try this guide to disable automatic driver install
How to Turn off Windows 7 Automatic Driver Installation
 

My Computer

Computer Manufacturer/Model Number
Self Built
OS
Windows 7 Home Premium 64bit
CPU
Intel Core i5-2500 @ 3.8GHz
Motherboard
MSI P67A-GD65
Memory
G.SKILL Ripjaws Series 8GB (2 x 4GB) DDR3 1600
Graphics Card(s)
NVIDIA GTX 550Ti
Sound Card
On Board
Monitor(s) Displays
ASUS 23"
Hard Drives
OCZ Vertex 3 VTX3-25SAT3-60G
Keyboard
Wireless
Mouse
Wireless
You must log in or register to reply here.

Similar threads

Frequent random BSOD CRITICAL_OBJECT_TERMINATION by ntoskrnl.exe
Replies
3
Views
738
torchwood
torchwood
Solved Return of the BSOD: STOP 0x*00000000000A
Replies
5
Views
2K
ICIT2LOL
ICIT2LOL
Need help with constant, random BSOD
Replies
8
Views
1K
willyj73
W
Recent Spate of Random BSODs - Error Code 0x0000004a in ntoskrnl.exe
Replies
8
Views
2K
axe0
A
Periods of random BSOD
Replies
1
Views
1K
Ludwig
L
Back
Top