I get a Blue Screen when running defrag

Anonymous
2012-06-07T09:21:27+00:00

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.

Windows for home | Previous Windows versions | Apps

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.

0 comments

61 answers

Sort by: Newest
Most helpful Newest Oldest
  1. Anonymous
    2012-06-13T02:40:59+00:00

    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.

    Was this answer helpful?

    0 comments
  2. Anonymous
    2012-06-11T03:48:36+00:00

    when i click join network, my normal network shows up as: Nativewifi Default Profile

    Was this answer helpful?

    0 comments
  3. Anonymous
    2012-06-11T03:47:05+00:00

    ok chkdsk is running now and I still cannot connect to the web on my PC. i think the Jswpslwfx.sys is/or contains the program that runs my netgear web adapter

    Was this answer helpful?

    0 comments
  4. Anonymous
    2012-06-11T02:51:39+00:00

    This latest crash had nothing to do with the wireless, although unfortunately, jswpslwfx jswpslwfx.sys Thu May 15 06:28:50 2008 (482C1062) is still present.

    The actual wireless driver is updated though, to 2011.

    This crash was a 0x24 NTFS file system related crash.

    Visit your motherboard site and download/install the latest AMD chipset driver package to install:

    amdxata  amdxata.sys  Fri Mar 19 12:18:18 2010 (4BA3A3CA)

    It may or may not update the above driver. If it doesn't, then it is likely not an issue.

    After you do that, open an elevated command prompt and run this command for every hard drive partition on the system:

    chkdsk /r C:

    For D partition, it would be -

    chkdsk /r D:

    so on and so on until they are all completed.

    This wireless related driver also needs to be removed:

    scmndisp scmndisp.sys Wed Jan 17 02:48:03 2007 (45ADD4B3)

    Recomend to rename it to .bak, rename jswpslwfx.sys to .bak

    Reboot and then install the latest Atheros driver again.

    Was this answer helpful?

    0 comments
  5. Anonymous
    2012-06-11T02:38:26+00:00

    ok i tried that and it still wont connect to the net. (sorry i was gone for a long weekend mountainbiking). swhile i was away my comp BSOD'd again and this is the minidump:

    https://skydrive.live.com/redir?resid=E82D099599B1CE45!333&authkey=!AFw7ZwmFbMCTab8

    Was this answer helpful?

    0 comments