Solved Random BSOD error

[Goliath1000]

I kept having random BSODs at random times, doing different thing, including doing nothing, laptop would BSOD. Ran WhoCrashed and report is as follows:
Crash Dump Analysis
--------------------------------------------------------------------------------

Crash dump directory: C:\Windows\Minidump

Crash dumps are enabled on your computer.

On Mon 21/10/2013 3:00:24 PM GMT your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: Unknown (0xFFFFF880033F1640)
Bugcheck code: 0x109 (0xA3A039D8A1A88782, 0xB3B7465EF426C4CC, 0xFFFFF880033F1640, 0x3)
Error: CRITICAL_STRUCTURE_CORRUPTION
Bug check description: This indicates that the kernel has detected critical kernel code or data corruption.
This might be a case of memory corruption. More often memory corruption happens because of software errors in buggy drivers, not because of faulty RAM modules.
A third party driver was identified as the probable root cause of this system error.
Google query: CRITICAL_STRUCTURE_CORRUPTION



On Fri 18/10/2013 3:09:39 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\101813-34803-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x75BC0)
Bugcheck code: 0x109 (0xA3A039D8A11A75C7, 0xB3B7465EF398B321, 0xFFFFF880033F1640, 0x3)
Error: CRITICAL_STRUCTURE_CORRUPTION
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 the kernel has detected critical kernel code or data corruption.
This might be a case of memory corruption. More often memory corruption happens because of software errors in buggy drivers, not because of faulty RAM modules.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.



On Tue 15/10/2013 8:22:49 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\101513-40856-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x75BC0)
Bugcheck code: 0x109 (0xA3A039D8A2A8B6D4, 0xB3B7465EF526F29E, 0xFFFFF8800334D640, 0x3)
Error: CRITICAL_STRUCTURE_CORRUPTION
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 the kernel has detected critical kernel code or data corruption.
This might be a case of memory corruption. More often memory corruption happens because of software errors in buggy drivers, not because of faulty RAM modules.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.



On Sat 12/10/2013 1:49:29 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\101213-34803-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x75BC0)
Bugcheck code: 0x109 (0xA3A039D8A21BF5D8, 0xB3B7465EF49A31A2, 0xFFFFF8800334D640, 0x3)
Error: CRITICAL_STRUCTURE_CORRUPTION
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 the kernel has detected critical kernel code or data corruption.
This might be a case of memory corruption. More often memory corruption happens because of software errors in buggy drivers, not because of faulty RAM modules.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.



On Fri 11/10/2013 10:57:38 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\101113-29140-01.dmp
This was probably caused by the following module: netio.sys (0xFFFFF88001ACB6FD)
Bugcheck code: 0xD1 (0x28, 0x2, 0x0, 0xFFFFF88001ACB6FD)
Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
file path: C:\Windows\system32\drivers\netio.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Network I/O Subsystem
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 a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system that cannot be identified at this time.



On Fri 4/10/2013 11:52:07 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\100413-33992-01.dmp
This was probably caused by the following module: netio.sys (0xFFFFF880018106FD)
Bugcheck code: 0xD1 (0x28, 0x2, 0x0, 0xFFFFF880018106FD)
Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
file path: C:\Windows\system32\drivers\netio.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Network I/O Subsystem
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 a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system that cannot be identified at this time.



On Fri 4/10/2013 10:26:22 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\100413-22354-01.dmp
This was probably caused by the following module: netio.sys (0xFFFFF880019AE6FD)
Bugcheck code: 0xD1 (0x28, 0x2, 0x0, 0xFFFFF880019AE6FD)
Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
file path: C:\Windows\system32\drivers\netio.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Network I/O Subsystem
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 a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system that cannot be identified at this time.



On Fri 4/10/2013 9:50:29 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\100413-24726-01.dmp
This was probably caused by the following module: netio.sys (0xFFFFF88001AA96FD)
Bugcheck code: 0xD1 (0x28, 0x2, 0x0, 0xFFFFF88001AA96FD)
Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
file path: C:\Windows\system32\drivers\netio.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Network I/O Subsystem
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 a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system that cannot be identified at this time.



On Fri 4/10/2013 8:58:55 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\100413-25334-01.dmp
This was probably caused by the following module: netio.sys (0xFFFFF88001A106FD)
Bugcheck code: 0xD1 (0x28, 0x2, 0x0, 0xFFFFF88001A106FD)
Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
file path: C:\Windows\system32\drivers\netio.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Network I/O Subsystem
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 a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system that cannot be identified at this time.



On Mon 30/9/2013 11:57:25 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\093013-23790-01.dmp
This was probably caused by the following module: netio.sys (0xFFFFF88001B766FD)
Bugcheck code: 0xD1 (0x28, 0x2, 0x0, 0xFFFFF88001B766FD)
Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
file path: C:\Windows\system32\drivers\netio.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Network I/O Subsystem
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 a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system that cannot be identified at this time.



On Sat 28/9/2013 2:04:27 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\092813-142397-01.dmp
This was probably caused by the following module: netio.sys (0xFFFFF8800198A6FD)
Bugcheck code: 0xD1 (0x28, 0x2, 0x0, 0xFFFFF8800198A6FD)
Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
file path: C:\Windows\system32\drivers\netio.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Network I/O Subsystem
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 a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system that cannot be identified at this time.



On Wed 25/9/2013 7:11:03 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\092513-225374-01.dmp
This was probably caused by the following module: netio.sys (0xFFFFF88001A246FD)
Bugcheck code: 0xD1 (0x28, 0x2, 0x0, 0xFFFFF88001A246FD)
Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
file path: C:\Windows\system32\drivers\netio.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Network I/O Subsystem
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 a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system that cannot be identified at this time.



On Mon 2/9/2013 9:09:10 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\090213-37596-01.dmp
This was probably caused by the following module: netio.sys (0xFFFFF880019286FD)
Bugcheck code: 0xD1 (0x28, 0x2, 0x0, 0xFFFFF880019286FD)
Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
file path: C:\Windows\system32\drivers\netio.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Network I/O Subsystem
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 a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system that cannot be identified at this time.



On Fri 31/5/2013 3:04:08 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\053113-24476-01.dmp
This was probably caused by the following module: netio.sys (0xFFFFF880018106FD)
Bugcheck code: 0xD1 (0x28, 0x2, 0x0, 0xFFFFF880018106FD)
Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
file path: C:\Windows\system32\drivers\netio.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Network I/O Subsystem
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 a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system that cannot be identified at this time.



On Wed 29/5/2013 6:53:47 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\052913-35006-01.dmp
This was probably caused by the following module: netio.sys (0xFFFFF88001A106FD)
Bugcheck code: 0xD1 (0x28, 0x2, 0x0, 0xFFFFF88001A106FD)
Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
file path: C:\Windows\system32\drivers\netio.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Network I/O Subsystem
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 a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system that cannot be identified at this time.



.rar file attached with SF files inside.
Please help asap, need my laptop in top working condition!
Thanks in advance for your help

 

[Arc]

04/10/2013 onwards, the BSODs are stop 0x109.

earlier, the BSODs are stop 0xD1, caused by network drivers.

For the stop 0xD1 BSODs, I would suggest you to download and install Drivers for Atheros AR9485WB and Windows 7.

A stop 0x109 is a comparatively vast bugcheck. As a first attempt, you may plan to update your BIOS to Version 211 dated 2012.12.05; available in ASUSTeK Computer Inc. -Support- Drivers and Download K55VM (you should use the Windows BIOS Flash Utility by ASUS (available in the same page) to do it.

Also,
Test your RAM modules for possible errors.
How to Test and Diagnose RAM Issues with Memtest86+
Run memtest for at least 8 passes, preferably overnight.
If it start showing errors/red lines, stop testing. A single error is enough to determine that something is going bad there.

Let us know the results.

 

[Goliath1000]

Great news:

1. Updated Aetheros successfully
2. Updated BIOS successfully
3. Will be running Memtest tonight, will post results here.

Thanks for your help.

Edited:

Ran Memtest last night, about 4 passes, 0 errors, will run it again this weekend when there is more time.
Thanks very much for your help Arc

 

[Goliath1000]

Bad news,

My laptop just crashed again today, after two days of silence. I have updated BIOS and Aetheros, what else do I need to do?


Attached are files.

 

[Arc]

*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

CRITICAL_STRUCTURE_CORRUPTION (109)
This bugcheck is generated when the kernel detects that critical kernel code or
data have been corrupted. There are generally three causes for a corruption:
1) [COLOR=Red]A driver has inadvertently or deliberately modified critical kernel code
 or data.[/COLOR] See http://www.microsoft.com/whdc/driver/kernel/64bitPatching.mspx
2) A developer attempted to set a normal kernel breakpoint using a kernel
 debugger that was not attached when the system was booted. Normal breakpoints,
 "bp", can only be set if the debugger is attached at boot time. Hardware
 breakpoints, "ba", can be set at any time.
3) [COLOR=Red]A hardware corruption occurred, e.g. failing RAM holding kernel code or data.[/COLOR]
Arguments:

Your crash dumps are not showing any finite probable cause.

Test your RAM modules for possible errors.
How to Test and Diagnose RAM Issues with Memtest86+
Run memtest for at least 8 passes, preferably overnight.

If it start showing errors/red lines, stop testing. A single error is enough to determine that something is going bad there.
If memtest reports no error, enable Driver Verifier to monitor the drivers.
Driver Verifier - Enable and Disable
Run Driver Verifier for 24 hours or the occurrence of the next crash, whichever is earlier.

   Information

Why Driver Verifier:
It puts a stress on the drivers, ans so it makes the unstable drivers crash. Hopefully the driver that crashes is recorded in the memory dump.

How Can we know that DV is enabled:
It will make the system bit of slow, laggy.

   Warning

Before enabling DV, make it sure that you have earlier System restore points made in your computer. You can check it easily by using CCleaner looking at Tools > System Restore.

If there is no points, make a System Restore Point manually before enabling DV.

   Tip

• If you fail to get on the Desktop because of DV, Boot into Advanced Boot Options > Safe mode. Disable DV there. Now boot normally again, and try following the instruction of enabling DV again.
• If you cannot boot in Safe mode too, do a System Restore to a point you made earlier.

Let us know the results, with the subsequent crash dumps, if any.

 

[Goliath1000]

Hey arc,

So far no crashes 3 days from the last crash. Ran Memtest 7 passes no errors.

 

[Arc]

Good news.

If it crashes again, post the crash data.

 

[Goliath1000]

Bad news. Crashed again. Seems to be the jinx whenever I put this thread as solved. Could it be my torrent, Tixati?
Also btw, I cant seem to windows update Intel Corporation - Graphics Adapter WDDM1.1, Graphics Adapter WDDM1.3 - Intel (R) HD Graphics 4000. Is there any solution that you might have for this? Attached is crash data.

 

[Arc]

Read the post #5 for one more time?

 

[Goliath1000]

Will do the driver verifier tonight onwards, if I shut down my computer will it still be counted within the 24 hours or is the 24 hours only running time?

 

[Goliath1000]

Ok system immediately crashed upon restart with DV. Turned it off in Safe Mode cos could not get into normal windows. Attached is crash report. Hopefully the cause is stated in there.

 

[Arc]

The verifier enabled minidump blames to the display driver.

BugCheck C4, {f6, b8, fffffa800d4fc060, fffff8800f4cfbbd}

*** WARNING: Unable to verify timestamp for nvlddmkm.sys
*** ERROR: Module load completed but symbols could not be loaded for nvlddmkm.sys
Probably caused by : nvlddmkm.sys ( nvlddmkm+9abbd )

Followup: MachineOwner
---------

Install the NVIDIA DRIVERS 314.22WHQL only.

• Uninstall All nvidia items in Control Panel > Programs and features
  • 3D Vision Control Driver
  • 3D Vision Driver
  • Graphics Driver
  • HD Audio Driver
  • PhysX
  • nvidia Update
  (Are you using nvidia chipset drivers? If so, dont uninstall anything other than those are listed).
• Now follow Drivers - Clean Left over Files after Uninstalling
• Download 314.22 WHQL. While installing, Select Custom (Advanced) install. In the next page, follow this settings:
  
  

Now, you need to continue with verifier. Do the regular network related functions that you do with verifier on. Notice if it crashes or not.

 

[Goliath1000]

Crashed again after verifier, heres the reports.

 

[Arc]

Both the BSODs are the same ....

BugCheck D1, {28, 2, 0, fffff880018106fd}

[COLOR=Red]Probably caused by : NETIO.SYS [/COLOR]( NETIO!RtlCopyBufferToMdl+1d )

Followup: MachineOwner
---------

They indicates to the same thing .... Qualcomm Atheros AR9485WB-EG Wireless Network Adapter.

fffff880`037926c8  fffff880`06834499Unable to load image \SystemRoot\system32\DRIVERS\athrx.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for athrx.sys
[COLOR=Red]*** ERROR: Module load completed but symbols could not be loaded for athrx.sys[/COLOR]
 athrx+0x34499

Whereas the driver is almost up-to-date.

fffff880`06800000 fffff880`06bfb000   athrx    T (no symbols)           
    Loaded symbol image file: athrx.sys
    Image path: \SystemRoot\system32\DRIVERS\athrx.sys
[COLOR=Red]    Image name: athrx.sys
    Timestamp:        Tue Jun 25 11:26:14 2013[/COLOR] (51C930FE)
    CheckSum:         003D0EBA
    ImageSize:        003FB000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4

So it may be something else causing some stress on it. Still you try to install it: Drivers for Atheros AR9485WB and Windows 7

And Free up the startup. Windows does not need any other program to auto start with it, but the auto start programs often conflicts and causes various problems including BSODs.

1. Click on the Start button
2. Type “msconfig (without quotes), click the resulting link. It will open the System Configuration window.
3. Select the “Startup” tab.
4. Deselect all items other than the antivirus.
5. Apply > OK
6. Accept then restart.

Let us know the results.

 

[Goliath1000]

Could it be due to my torrent that could be overloading the wireless?

 

[Arc]

Could it be due to my torrent that could be overloading the wireless?

Well, sometimes torrents can cause it. You update your client. And uninstall other web helper like programs if you have installed.