hola como estas?
gracias por la imagen pero lamentablemente no nos dice mucho :S
nos podrias ayudar con un poco de historia
desde cuando empezo el error?
instalaste alguna aplicacion en esas fechas?
saludos cordiales
hola jesus, baja el whocrashed es free
en mi caso me pasa lo mismo y me dijo que el problema estaba en que el antivirus no era del todo compatible asi que lo voy a desinstalar, les dejo el reporte!
System Information (local)
computer name: PITT-PC
windows version: Windows 8 , 6.2, build: 9200
windows dir: C:\WINDOWS
CPU: AuthenticAMD AMD Athlon(tm) II X2 250 Processor AMD586, level: 16
2 logical processors, active mask: 3
RAM: 1878249472 total
VM: 2147352576, free: 1925185536
*** * Crash Dump Analysis*
Crash dump directory: C:\WINDOWS\Minidump
Crash dumps are enabled on your computer.
On Tue 22/01/2013 0:46:39 GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\012113-25974-01.dmp
This was probably caused by the following module:
aswnet.sys (0xFFFFF8800384A3AA)
Bugcheck code: 0xD1 (0x38, 0x2, 0x0, 0xFFFFF8800384A3AA)
Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
file path: C:\WINDOWS\system32\drivers\aswnet.sys
product: Avast Firewall
company: AVAST Software
description: AVAST Firewall Core 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: aswnet.sys (AVAST Firewall Core Driver, AVAST Software).
Google query: AVAST Software DRIVER_IRQL_NOT_LESS_OR_EQUAL
On Tue 22/01/2013 0:46:39 GMT your computer crashed
crash dump file: C:\WINDOWS\memory.dmp
This was probably caused by the following module:
aswnet.sys (aswnet+0x313AA)
Bugcheck code: 0xD1 (0x38, 0x2, 0x0, 0xFFFFF8800384A3AA)
Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
file path: C:\WINDOWS\system32\drivers\aswnet.sys
product: Avast Firewall
company: AVAST Software
description: AVAST Firewall Core 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: aswnet.sys (AVAST Firewall Core Driver, AVAST Software).
Google query: AVAST Software DRIVER_IRQL_NOT_LESS_OR_EQUAL
On Tue 22/01/2013 0:17:27 GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\012113-24601-01.dmp
This was probably caused by the following module:
aswnet.sys (0xFFFFF88003A543AA)
Bugcheck code: 0xD1 (0x38, 0x2, 0x0, 0xFFFFF88003A543AA)
Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
file path: C:\WINDOWS\system32\drivers\aswnet.sys
product: Avast Firewall
company: AVAST Software
description: AVAST Firewall Core 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: aswnet.sys (AVAST Firewall Core Driver, AVAST Software).
Google query: AVAST Software DRIVER_IRQL_NOT_LESS_OR_EQUAL
*** * Conclusion*
3 crash dumps have been found and analyzed. A third party driver has 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:
aswnet.sys (AVAST Firewall Core Driver, AVAST Software)
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.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(128, 8%, 22%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EA%3C/text%3E%3C/svg%3E)
