- Type2 Board Vendor Name 1 Type2 Board Product Name1 update#
- Type2 Board Vendor Name 1 Type2 Board Product Name1 driver#
- Type2 Board Vendor Name 1 Type2 Board Product Name1 windows#
On Mon 23:21:45 your computer crashed or a problem was reportedĬrash dump file: C:\Windows\Minidump\061515-28812-01.dmp This problem might also be caused because of overheating (thermal issue). This may be because of a hardware issue such as faulty RAM, overheating (thermal issue) or because of a buggy driver. This might be a case of memory corruption. This was probably caused by the following module: ntoskrnl.exe (nt+0x14E8A0)īugcheck code: 0x19 (0x3, 0xFFFFE000AB1137D0, 0xFFFFE000A74A96F0, 0xFFFFE000AB1137D0)īug check description: This indicates that a pool header is corrupt.
On Sat 17:13:18 your computer crashed or a problem was reportedĬrash dump file: C:\Windows\Minidump\122615-22562-01.dmp This bug check can also occur because of overheated CPUs (thermal issue).
Type2 Board Vendor Name 1 Type2 Board Product Name1 driver#
This could be caused by either a non-responding driver or non-responding hardware. This was probably caused by the following module: ntoskrnl.exe (nt+0x14E3A0)īugcheck code: 0x133 (0x1, 0x1E00, 0x0, 0x0)īug check description: The DPC watchdog detected a prolonged run time at an IRQL of DISPATCH_LEVEL or above. On Sun 13:43:03 your computer crashed or a problem was reportedĬrash dump file: C:\Windows\Minidump\052216-23687-01.dmp This was probably caused by the following module: netwbw02.sys (0xFFFFF8000C79D47F)īugcheck code: 0xD1 (0x28, 0x2, 0x0, 0xFFFFF8000C79D47F) On Wed 10:34:50 your computer crashed or a problem was reportedĬrash dump file: C:\Windows\Minidump\030117-27546-01.dmp This was probably caused by the following module: ntoskrnl.exe (nt+0x14DBA0)īugcheck code: 0x139 (0x3, 0xFFFFD00021078EB0, 0xFFFFD00021078E08, 0x0) On Fri 09:27:57 your computer crashed or a problem was reportedĬrash dump file: C:\Windows\Minidump\112417-33031-01.dmp Google query: netwbw02.sys Intel Corporation DRIVER_IRQL_NOT_LESS_OR_EQUAL It means that a crash dump file was properly written out.
This bug check belongs to the crash dump test that you have performed with WhoCrashed or other software. This was probably caused by the following module: netwbw02.sys (0xFFFFF800510BDF61)īugcheck code: 0xD1 (0x8, 0x2, 0x1, 0xFFFFF800510BDF61)īug check description: This indicates that a kernel-mode driver attempted to access pageable memory at a process IRQL that was too high. On Mon 09:19:37 your computer crashed or a problem was reportedĬrash dump file: C:\Windows\Minidump\121117-29031-01.dmp Google query: netwbw02.sys Intel Corporation KERNEL_SECURITY_CHECK_FAILURE
Type2 Board Vendor Name 1 Type2 Board Product Name1 update#
It is suggested you look for an update for the following driver: netwbw02.sys (Intel® Wireless WiFi Link Driver, Intel Corporation). Product: Intel® Wireless WiFi Link Adapterĭescription: Intel® Wireless WiFi Link DriverĪ third party driver was identified as the probable root cause of this system error. This was probably caused by the following module: netwbw02.sys (NETwbw02+0x1B1671)įile path: C:\Windows\system32\drivers\netwbw02.sys Possibly this problem is caused by another driver that cannot be identified at this time.
Type2 Board Vendor Name 1 Type2 Board Product Name1 windows#
The crash took place in the Windows kernel.
Product: Microsoft® Windows® Operating Systemīug check description: The kernel has detected the corruption of a critical data structure. This was probably caused by the following module: ntoskrnl.exe (nt+0x154EA0)īugcheck code: 0x139 (0x3, 0xFFFFD000FA461DA0, 0xFFFFD000FA461CF8, 0x0)įile path: C:\Windows\system32\ntoskrnl.exe On Tue 08:54:42 your computer crashed or a problem was reportedĬrash dump file: C:\Windows\Minidump\013018-32921-01.dmp Hardware: SATELLITE L50-B, TOSHIBA, Type2 - Board Vendor Name1, Type2 - Board Product Name1ĬPU: GenuineIntel Intel(R) Core(TM) i5-4200U CPU 1.60GHz Intel586, level: 6Ĭrash dumps are enabled on your computer. Windows version: Windows 8.1, 6.3, build: 9600 J'ai téléchargé whocrashed sur la page du lien et ai lancé une analyse.