This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
![](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)
like the title I get a BSOD when running defrag. When i analyzed my disk it said that it was 4% fragmented so i ran the defrag and up popped my BSOD. I am switching to a ne HDD tomorow so i can see if that stops these BSODs from happening, but for now i am wondering what is causing the BSOD.
Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.
Sure. :)
There might have been other problems that needed fixing as above, but if you got rid of that j driver, that was definitely progress for sure.
Awesome about uninstalling Netgear stuff. I would have said that straight away, but hadn't realized it was actually installed. I thought the j driver was part of the simple driver installation you previously did and not from a full blown software install.
said that too soon.... :((((( minidump coming your way
There was no jumpstart wireless, but i uninstalled the netgear bloatware, deleted the jswpslwfx and now my system is running crash free :)
I believe that the problem was in the netgear software instead of a "jumpstarter wireless" but what do i know... anyway, thanks a lot for all of the help and i hope to never have another crash!!! If i do though, i know who the expert is :)
Same as I've said through the thread.
Must get rid of the jswpslwfx.sys by deleting - then reboot - then install latest Atheros in device manager.
Before rebooting, you can also look for jswpslwfx here in Regedit and delete the subkey:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services
Or I've found a post with a way that Auggy suggests to rid of jswpslwfx:
Open the Network and Sharing Center on the Taskbar > Change adapter settings > right-click the "Wireless Network Connection" > Properties > click on "Jumpstart Wireless Intermediate Driver" and select "Uninstall" > proceed with the uninstall
So i got WhoCrashed to help find out the problem and this is what it said. any suggestions on how to fix?
On Wed 6/13/2012 1:51:08 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\061212-27190-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7F1C0)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF80002CCF58D, 0xFFFFF88008FDEFE0, 0x0)
Error: SYSTEM_SERVICE_EXCEPTION
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 an exception happened while executing a routine that transitions from non-privileged code to privileged code.
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 6/13/2012 1:51:08 AM GMT your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: ntkrnlmp.exe (nt!KeBugCheckEx+0x0)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF80002CCF58D, 0xFFFFF88008FDEFE0, 0x0)
Error: SYSTEM_SERVICE_EXCEPTION
Bug check description: This indicates that an exception happened while executing a routine that transitions from non-privileged code to privileged code.
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 6/11/2012 1:37:33 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\061112-10951-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7F1C0)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF80002D4338F, 0xFFFFF88003BDCB50, 0x0)
Error: SYSTEM_SERVICE_EXCEPTION
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 an exception happened while executing a routine that transitions from non-privileged code to privileged code.
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/8/2012 6:21:53 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\061012-12776-01.dmp
This was probably caused by the following module: ntfs.sys (Ntfs+0x5A88)
Bugcheck code: 0x24 (0x1904FB, 0xFFFFF880031930B8, 0xFFFFF88003192910, 0xFFFFF80002CE2F95)
Error: NTFS_FILE_SYSTEM
file path: C:\Windows\system32\drivers\ntfs.sys
product: MicrosoftÆ WindowsÆ Operating System
company: Microsoft Corporation
description: NT File System Driver
Bug check description: This indicates a problem occurred in the NTFS file system.
The crash took place in a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system which cannot be identified at this time.
On Thu 6/7/2012 10:16:19 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\060712-28719-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x415B2)
Bugcheck code: 0x1000007E (0xFFFFFFFFC0000005, 0xFFFFF80002C455B2, 0xFFFFF880031FC7D8, 0xFFFFF880031FC030)
Error: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M
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 system thread generated an exception which the error handler did not catch.
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 Thu 6/7/2012 8:48:47 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\060712-14508-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0xB7612)
Bugcheck code: 0x1000007E (0xFFFFFFFFC0000005, 0xFFFFF80002CC3612, 0xFFFFF8800350F7D8, 0xFFFFF8800350F030)
Error: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M
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 system thread generated an exception which the error handler did not catch.
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 Thu 6/7/2012 8:11:00 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\060712-15412-01.dmp
This was probably caused by the following module: athurx.sys (athurx+0x23E9E)
Bugcheck code: 0x1000007E (0xFFFFFFFFC0000005, 0xFFFFF8800243DE9E, 0xFFFFF88005A354F8, 0xFFFFF88005A34D50)
Error: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M
file path: C:\Windows\system32\drivers\athurx.sys
product: Driver for Atheros UB91/UB93 Network Adapter
company: Atheros Communications, Inc.
description: Atheros Extensible Wireless LAN device driver
Bug check description: This indicates that a system thread generated an exception which the error handler did not catch.
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: athurx.sys (Atheros Extensible Wireless LAN device driver, Atheros Communications, Inc.).
Google query: athurx.sys Atheros Communications, Inc. SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M
On Thu 6/7/2012 7:42:59 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\060712-24804-01.dmp
This was probably caused by the following module: wdf01000.sys (Wdf01000+0x1C66F)
Bugcheck code: 0x1000007E (0xFFFFFFFFC0000005, 0xFFFFF88000F1466F, 0xFFFFF88002858358, 0xFFFFF88002857BB0)
Error: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M
file path: C:\Windows\system32\drivers\wdf01000.sys
product: MicrosoftÆ WindowsÆ Operating System
company: Microsoft Corporation
description: Kernel Mode Driver Framework Runtime
Bug check description: This indicates that a system thread generated an exception which the error handler did not catch.
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 a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system which cannot be identified at this time.
On Thu 6/7/2012 5:11:49 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\060712-27830-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7F190)
Bugcheck code: 0x1E (0x0, 0x0, 0x0, 0x0)
Error: KMODE_EXCEPTION_NOT_HANDLED
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 program generated an exception which the error handler did not catch.
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 Thu 6/7/2012 9:10:52 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\060712-25911-01.dmp
This was probably caused by the following module: ntfs.sys (Ntfs+0x5A88)
Bugcheck code: 0x24 (0x1904FB, 0xFFFFF8800318C5A8, 0xFFFFF8800318BE00, 0xFFFFF80002C5C1A8)
Error: NTFS_FILE_SYSTEM
file path: C:\Windows\system32\drivers\ntfs.sys
product: MicrosoftÆ WindowsÆ Operating System
company: Microsoft Corporation
description: NT File System Driver
Bug check description: This indicates a problem occurred in the NTFS file system.
The crash took place in a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system which cannot be identified at this time.
On Thu 6/7/2012 8:54:21 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\060712-28236-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7F190)
Bugcheck code: 0x1E (0x0, 0x0, 0x0, 0x0)
Error: KMODE_EXCEPTION_NOT_HANDLED
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 program generated an exception which the error handler did not catch.
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 Thu 6/7/2012 5:13:38 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\060712-31637-01.dmp
This was probably caused by the following module: wdf01000.sys (Wdf01000+0x35156)
Bugcheck code: 0x1000007E (0xFFFFFFFFC0000005, 0xFFFFF88000E5E156, 0xFFFFF88003D6A1E8, 0xFFFFF88003D69A40)
Error: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M
file path: C:\Windows\system32\drivers\wdf01000.sys
product: MicrosoftÆ WindowsÆ Operating System
company: Microsoft Corporation
description: Kernel Mode Driver Framework Runtime
Bug check description: This indicates that a system thread generated an exception which the error handler did not catch.
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 a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system which cannot be identified at this time.
On Thu 5/24/2012 6:16:39 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\060212-18298-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0xF8AED)
Bugcheck code: 0x1000007E (0xFFFFFFFFC0000005, 0xFFFFF80002D00AED, 0xFFFFF88003316788, 0xFFFFF88003315FE0)
Error: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M
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 system thread generated an exception which the error handler did not catch.
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 5/6/2012 3:39:58 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\050512-17378-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7CC40)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF80002C85C0E, 0xFFFFF88007FFBFE0, 0x0)
Error: SYSTEM_SERVICE_EXCEPTION
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 an exception happened while executing a routine that transitions from non-privileged code to privileged code.
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 5/5/2012 12:37:43 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\050412-22869-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7CC40)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF80002C9D52C, 0xFFFFF88008381EE0, 0x0)
Error: SYSTEM_SERVICE_EXCEPTION
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 an exception happened while executing a routine that transitions from non-privileged code to privileged code.
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.
