Forthelove
New member
- Local time
- 2:47 AM
- Messages
- 14
A few days ago I booted up my HP Pavilion dv4-2049wm laptop. Windows update needed to reboot, due to my postponing it for a few days, so I let it reboot and I started getting blue screens.
After a few restarts (getting the BSOD every time), I booted into the last known good configuration. It booted up fine, but now I can no longer connect to my network (wired and wireless). It sees my wireless connection, but states "Limited Access."
Things I have tried:
Uninstalled/Updated network drivers from HP's site, specific to my laptop model.
Uninstalled all windows updates that were installed before BSOD
Flushed, registered, renewed dns via command prompt
Reset Winsock via command prompt
Tried a "clean" boot
Ran Windows Check Disk
Ran Windows Memory Tester (Unsure of exact name)
On the day of the crash I attempted to do a restore, but the earliest restore I could do was at the time of the windows update (same time as BSOD).
One thing I did notice is that the "Teredo Tunneling Pseudo_Interface" listed under network adapters is no longer there. Not sure what that might have to do with anything.
I ran this tool (Who Crashed/Crashdump) and here is my log:
--------------------------------------------------------------------------------
Conclusion
--------------------------------------------------------------------------------
On your computer a total of 26 crash dumps have been found. Only 21 could be analyzed. Only 15 are included in this report. 2 third party drivers have been identified to be causing system crashes on your computer. It is strongly suggested that you check for updates for these drivers on their company websites. Click on the links below to search with Google for updates for these drivers:
atikmpag.sys (AMD multi-vendor Miniport Driver, Advanced Micro Devices, Inc.)
athrx.sys (Atheros Extensible Wireless LAN device driver, Atheros Communications, Inc.)
If no updates for these drivers are available, try searching with Google on the names of these drivers in combination the errors that have been reported for these drivers and include the brand and model name of your computer as well in the query. This often yields interesting results from discussions from users who have been experiencing similar problems.
0
Any help would be greatly appreciated. I'm at a loss...no idea what to do.
Thanks
Justin
After a few restarts (getting the BSOD every time), I booted into the last known good configuration. It booted up fine, but now I can no longer connect to my network (wired and wireless). It sees my wireless connection, but states "Limited Access."
Things I have tried:
Uninstalled/Updated network drivers from HP's site, specific to my laptop model.
Uninstalled all windows updates that were installed before BSOD
Flushed, registered, renewed dns via command prompt
Reset Winsock via command prompt
Tried a "clean" boot
Ran Windows Check Disk
Ran Windows Memory Tester (Unsure of exact name)
On the day of the crash I attempted to do a restore, but the earliest restore I could do was at the time of the windows update (same time as BSOD).
One thing I did notice is that the "Teredo Tunneling Pseudo_Interface" listed under network adapters is no longer there. Not sure what that might have to do with anything.
I ran this tool (Who Crashed/Crashdump) and here is my log:
Code:
System Information (local)
--------------------------------------------------------------------------------
computer name: DECARO
windows version: Windows 7 , 6.1, build: 7600
windows dir: C:\Windows
CPU: AuthenticAMD AMD Turion™ II Ultra Dual-Core Mobile M620 AMD586, level: 16
2 logical processors, active mask: 3
RAM: 4022542336 total
VM: 2147352576, free: 1925451776
--------------------------------------------------------------------------------
Crash Dump Analysis
--------------------------------------------------------------------------------
Crash dump directory: C:\Windows\Minidump
Crash dumps are enabled on your computer.
On Mon 3/26/2012 4:04:01 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\032612-39312-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x70540)
Bugcheck code: 0xD1 (0x10, 0x2, 0x0, 0xFFFFF88001E895D6)
Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that a kernel-mode driver attempted to access pageable memory at a process IRQL that was too high.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time.
On Mon 3/26/2012 4:04:01 PM GMT your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: athrx.sys (athrx+0x4C0C7)
Bugcheck code: 0xD1 (0x10, 0x2, 0x0, 0xFFFFF88001E895D6)
Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
file path: C:\Windows\system32\drivers\athrx.sys
product: Driver for Atheros CB42/CB43/MB42/MB43 Network Adapter
company: Atheros Communications, Inc.
description: Atheros Extensible Wireless LAN device driver
Bug check description: This indicates that a kernel-mode driver attempted to access pageable memory at a process IRQL that was too high.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
A third party driver was identified as the probable root cause of this system error. It is suggested you look for an update for the following driver: athrx.sys (Atheros Extensible Wireless LAN device driver, Atheros Communications, Inc.).
Google query: athrx.sys Atheros Communications, Inc. DRIVER_IRQL_NOT_LESS_OR_EQUAL
On Mon 3/26/2012 3:56:41 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\032612-26629-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x70540)
Bugcheck code: 0xD1 (0x10, 0x2, 0x0, 0xFFFFF88001D205D6)
Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that a kernel-mode driver attempted to access pageable memory at a process IRQL that was too high.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time.
On Mon 3/19/2012 9:08:47 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\032112-31309-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x70540)
Bugcheck code: 0x9F (0x3, 0xFFFFFA800429F060, 0xFFFFF80000B9C518, 0xFFFFFA8005F2B340)
Error: DRIVER_POWER_STATE_FAILURE
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This bug check indicates that the driver is in an inconsistent or invalid power state.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time.
On Mon 3/12/2012 10:49:21 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\031212-32027-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x705C0)
Bugcheck code: 0x9F (0x3, 0xFFFFFA80042A0060, 0xFFFFF80000B9C518, 0xFFFFFA8005E8FA30)
Error: DRIVER_POWER_STATE_FAILURE
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This bug check indicates that the driver is in an inconsistent or invalid power state.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time.
On Sat 3/10/2012 8:54:04 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\031012-28516-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x705C0)
Bugcheck code: 0x9F (0x3, 0xFFFFFA8004294A20, 0xFFFFF80004C23518, 0xFFFFFA8004042B80)
Error: DRIVER_POWER_STATE_FAILURE
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This bug check indicates that the driver is in an inconsistent or invalid power state.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time.
On Fri 1/27/2012 8:16:44 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\012712-30030-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x705C0)
Bugcheck code: 0x9F (0x3, 0xFFFFFA800428F8D0, 0xFFFFF80004C25518, 0xFFFFFA800436D7D0)
Error: DRIVER_POWER_STATE_FAILURE
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This bug check indicates that the driver is in an inconsistent or invalid power state.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time.
On Wed 12/7/2011 11:02:30 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\120711-31418-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x705C0)
Bugcheck code: 0x7A (0xFFFFF6FB80000000, 0xFFFFFFFFC000000E, 0x3FC2B880, 0xFFFFF70000000388)
Error: KERNEL_DATA_INPAGE_ERROR
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This bug check indicates that the requested page of kernel data from the paging file could not be read into memory.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time.
On Tue 2/1/2011 11:10:44 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\020111-32011-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x70740)
Bugcheck code: 0x9F (0x3, 0xFFFFFA8004295060, 0xFFFFF80004817518, 0xFFFFFA8003A4DBC0)
Error: DRIVER_POWER_STATE_FAILURE
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This bug check indicates that the driver is in an inconsistent or invalid power state.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time.
On Fri 1/21/2011 7:21:45 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\012111-23556-01.dmp
This was probably caused by the following module: atikmpag.sys (atikmpag+0x6F30)
Bugcheck code: 0x116 (0xFFFFFA8004493010, 0xFFFFF88004359F30, 0xFFFFFFFFC0000001, 0x3)
Error: VIDEO_TDR_ERROR
file path: C:\Windows\system32\drivers\atikmpag.sys
product: AMD driver
company: Advanced Micro Devices, Inc.
description: AMD multi-vendor Miniport Driver
Bug check description: This indicates that an attempt to reset the display driver and recover from a timeout failed.
A third party driver was identified as the probable root cause of this system error. It is suggested you look for an update for the following driver: atikmpag.sys (AMD multi-vendor Miniport Driver, Advanced Micro Devices, Inc.).
Google query: atikmpag.sys Advanced Micro Devices, Inc. VIDEO_TDR_ERROR
On Fri 7/2/2010 8:59:18 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\070210-30342-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x70600)
Bugcheck code: 0xD1 (0x10, 0x2, 0x0, 0xFFFFF88001CF15D6)
Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that a kernel-mode driver attempted to access pageable memory at a process IRQL that was too high.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time.
On Fri 7/2/2010 2:04:35 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\070210-35693-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x70600)
Bugcheck code: 0x9F (0x3, 0xFFFFFA8004293A20, 0xFFFFF80000B9C518, 0xFFFFFA800EE34880)
Error: DRIVER_POWER_STATE_FAILURE
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This bug check indicates that the driver is in an inconsistent or invalid power state.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time.
On Sun 6/27/2010 11:37:35 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\062710-31340-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x70600)
Bugcheck code: 0x9F (0x3, 0xFFFFFA8004283060, 0xFFFFF80000B9C518, 0xFFFFFA80045D1BD0)
Error: DRIVER_POWER_STATE_FAILURE
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This bug check indicates that the driver is in an inconsistent or invalid power state.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time.
On Sun 6/27/2010 2:52:47 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\062710-28782-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x70600)
Bugcheck code: 0x9F (0x3, 0xFFFFFA8004285060, 0xFFFFF80000B9C518, 0xFFFFFA800A005BD0)
Error: DRIVER_POWER_STATE_FAILURE
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This bug check indicates that the driver is in an inconsistent or invalid power state.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time.
On Fri 6/25/2010 9:49:04 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\062610-27175-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x70600)
Bugcheck code: 0x9F (0x3, 0xFFFFFA80042C5060, 0xFFFFF80004875518, 0xFFFFFA8009200CF0)
Error: DRIVER_POWER_STATE_FAILURE
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This bug check indicates that the driver is in an inconsistent or invalid power state.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time.
The following dump files were found but could not be read. These files may be corrupt:
C:\Windows\Minidump\032612-39234-01.dmp
C:\Windows\Minidump\032612-39951-01.dmp
C:\Windows\Minidump\032612-40139-01.dmp
C:\Windows\Minidump\032612-40263-01.dmp
C:\Windows\Minidump\032612-41137-01.dmp--------------------------------------------------------------------------------
Conclusion
--------------------------------------------------------------------------------
On your computer a total of 26 crash dumps have been found. Only 21 could be analyzed. Only 15 are included in this report. 2 third party drivers have been identified to be causing system crashes on your computer. It is strongly suggested that you check for updates for these drivers on their company websites. Click on the links below to search with Google for updates for these drivers:
atikmpag.sys (AMD multi-vendor Miniport Driver, Advanced Micro Devices, Inc.)
athrx.sys (Atheros Extensible Wireless LAN device driver, Atheros Communications, Inc.)
If no updates for these drivers are available, try searching with Google on the names of these drivers in combination the errors that have been reported for these drivers and include the brand and model name of your computer as well in the query. This often yields interesting results from discussions from users who have been experiencing similar problems.
0
Any help would be greatly appreciated. I'm at a loss...no idea what to do.
Thanks
Justin
Last edited by a moderator:
My Computer
- OS
- Windows 7 Home Premium 64bit
