BSOD Errors: 0x0000001E - 0x000000C1 - 0x00000024 And so on

[Baarup]

Hey guys.

I've recently bought a new computer, bought all parts myself.
And since i installed windows i've got tons of BSOD's ..

I've checked my memory with memtest, no errors there.

Can anyone please help?

Keyboard: Logitech G15
Mouse: Logitech MX518

 

[Arc]

Hello Baarup.

Intel(R) 8 Series/C220 Chipset Family SATA AHCI Controller driver is failing here.

fffff800`00b9bd78  fffff880`01370008Unable to load image \SystemRoot\system32\DRIVERS\iaStorA.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for [COLOR=Red]iaStorA.sys[/COLOR]
*** ERROR: Module load completed but symbols could not be loaded for [COLOR=Red]iaStorA.sys[/COLOR]
 iaStorA+0x7c008

I would suggest you to get rid of intel rapid storage. First uninstall it from Control Panel > Programs and Features. Then Uninstall the driver from device manager.

1. Right click on "my computer" icon and click "manage" on the context menu.
2. It will open the "computer management" window.
3. Select "Device Manager" in the left pane, It will list all the existing devices up.
4. Expand "IDE ATA/ATAPI controllers" by clicking on the triangle in front of it.
5. Select one Intel device item under it, right click, uninstall.
6. Continue the process for all Intel items under "IDE ATA/ATAPI controllers"
7. Now restart the computer. At restart, windows will auto configure the appropriate native system driver.

Update Intel(R) USB 3.0 eXtensible Host Controller Driver. Get it from https://downloadcenter.intel.com/default.aspx.

Update D-Link DWA-140 Wireless N USB Adapter(rev.B3) driver. Get it from D-Link | Support or MediaTek - Downloads Windows

I am seeing that you are using a BETA version of display driver. Any particular reason behind it?

Uninstall Gigabyte On-Off Charger. It is a must. You will loss nothing without it. Your cellphone will be smoothly charged even without it. It is causing issues here.

*** WARNING: Unable to verify timestamp for UsbCharger.sys
*** ERROR: Module load completed but symbols could not be loaded for[COLOR=Red] UsbCharger.sys[/COLOR]

Could not read faulting driver name
Probably caused by : [COLOR=Red]UsbCharger.sys [/COLOR]( UsbCharger+164d )

And, Disable USB Selective Suspend too.
USB Selective Suspend - Turn On or Off

Let us know the results when done.

 

[Baarup]

Now i've done all that.
D-Link DWA-140 - told me that i was already having the latest drivers?

Also removed the beta display driver, i did install that for checking if it could be the display drivers failing.

Got some more BSOD when i did all this, attached.
one error was with dxgmm1s.sys or something like that.

 

[Arc]

Post it following the Blue Screen of Death (BSOD) Posting Instructions.

 

[Baarup]

Post it following the Blue Screen of Death (BSOD) Posting Instructions.

Sorry, Done.

 

[Arc]

Post it following the Blue Screen of Death (BSOD) Posting Instructions.

Sorry, Done.

Where? Attach it in your next reply please.

 

[Baarup]

Weird :/
It should be in my first thread post, at the top.

But here it is.

 

[Baarup]

Uploaded.

 

[Arc]

It is still the D-Link DWA-140 Wireless N USB Adapter(rev.B3).

BugCheck 1E, {0, 0, 0, 0}

*** WARNING: Unable to verify timestamp for Dnetr28ux.sys
*** ERROR: Module load completed but symbols could not be loaded for Dnetr28ux.sys

Have you updated the driver as suggested earlier?

Update D-Link DWA-140 Wireless N USB Adapter(rev.B3) driver. Get it from D-Link | Support or MediaTek - Downloads Windows

Let us know.

 

[Baarup]

It is still the D-Link DWA-140 Wireless N USB Adapter(rev.B3).

BugCheck 1E, {0, 0, 0, 0}

*** WARNING: Unable to verify timestamp for Dnetr28ux.sys
*** ERROR: Module load completed but symbols could not be loaded for Dnetr28ux.sys

Have you updated the driver as suggested earlier?

Update D-Link DWA-140 Wireless N USB Adapter(rev.B3) driver. Get it from D-Link | Support or MediaTek - Downloads Windows

Let us know.

I did try to update it, but then i get the message its the current version.
So now i decided to run cable.

No other errors found?

 

[Arc]

See how old the driver is.

fffff880`09220000 fffff880`093b3000   Dnetr28ux T (no symbols)           
    Loaded symbol image file: Dnetr28ux.sys
    Image path: \SystemRoot\system32\DRIVERS\Dnetr28ux.sys
[COLOR=Red]    Image name: Dnetr28ux.sys
    Timestamp:        Thu Apr 28 11:48:18 2011[/COLOR] (4DB906AA)
    CheckSum:         00193FD2
    ImageSize:        00193000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4

If that is the latest one, you need to stop using that adapter and get a new one.

BTW, you want more errors? If so, ANOD Network Security Filter Driver is also failing.

fffff800`00b9b578  fffff880`03f7b9c2Unable to load image \SystemRoot\system32\DRIVERS\anodlwfx.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for [URL="http://www.carrona.org/drivers/driver.php?id=anodlwfx.sys"]anodlwfx.sys[/URL]
*** ERROR: Module load completed but symbols could not be loaded for [URL="http://www.carrona.org/drivers/driver.php?id=anodlwfx.sys"]anodlwfx.sys[/URL]
 anodlwfx+0x19c2

And that is too old.

fffff880`03f7a000 fffff880`03f83000   anodlwfx T (no symbols)           
    Loaded symbol image file: anodlwfx.sys
    Image path: \SystemRoot\system32\DRIVERS\anodlwfx.sys
[COLOR=Red]    Image name: anodlwfx.sys
    Timestamp:        Fri Mar 06 15:40:08 2009[/COLOR] (49B0F680)
    CheckSum:         0000A8C3
    ImageSize:        00009000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4

I would suggest to uninstall those.

Intel USB3 Drivers are failing, too.

fffff800`00b9c680  fffffa80`0ed28402
fffff800`00b9c688  fffff880`09056b36Unable to load image \SystemRoot\system32\DRIVERS\iusb3hub.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for iusb3hub.sys
*** ERROR: Module load completed but symbols could not be loaded for iusb3hub.sys
 iusb3hub+0x18b36
--------------------------------------------------------------------------------------------
fffff800`00b9bd30  fffff880`05589f60Unable to load image \SystemRoot\system32\DRIVERS\iusb3xhc.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for iusb3xhc.sys
*** ERROR: Module load completed but symbols could not be loaded for iusb3xhc.sys
 iusb3xhc+0x79f60

But those are not very old.

fffff880`05510000 fffff880`055d3000   iusb3xhc T (no symbols)           
    Loaded symbol image file: iusb3xhc.sys
    Image path: \SystemRoot\system32\DRIVERS\iusb3xhc.sys
[COLOR=Red]    Image name: iusb3xhc.sys
    Timestamp:        Fri Mar 29 18:06:19 2013[/COLOR] (51558AC3)
    CheckSum:         000C59AC
    ImageSize:        000C3000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4

So it seems to be the port error where the DLink adaptor is connected .... which is old. Still, dont take a chance ... search for updates in https://downloadcenter.intel.com/default.aspx

Got enough of errors? Happy now?

The process of troubleshooting is one by one ..... and the DLInk is the prima facie issue, which should be dealt with at first. So I wanted to concentrate on it only at first.

 

[Baarup]

I guess I'm just tired of my system failed when I just bought it. Sorry

I've uninstalled D-Link and ANOD now, got 3 BSOD in a row now, running on cable.
Thank you for all your help so far

 

[Arc]

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 the memtest results free from errors, 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. Post it following the Blue Screen of Death (BSOD) Posting Instructions.
__________________________________________________________________________
BSOD ANALYSIS:

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

Use !analyze -v to get detailed debugging information.

BugCheck 1A, {5002, fffff70001080000, 3283, 107137fffffffe}

Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+2983a )

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

0: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

MEMORY_MANAGEMENT (1a)
    # Any other values for parameter 1 must be individually examined.
Arguments:
Arg1: 0000000000005002, The subtype of the bugcheck.
Arg2: fffff70001080000
Arg3: 0000000000003283
Arg4: 00107137fffffffe

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

Use !analyze -v to get detailed debugging information.

BugCheck 50, {fffffa8604e6d798, 0, fffff80002c8e6eb, 5}


Could not read faulting driver name
Probably caused by : memory_corruption ( nt!MiDeleteAddressesInWorkingSet+27f )

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

7: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

PAGE_FAULT_IN_NONPAGED_AREA (50)
Invalid system memory was referenced.  This cannot be protected by try-except,
it must be protected by a Probe.  Typically the address is just plain bad or it
is pointing at freed memory.
Arguments:
Arg1: fffffa8604e6d798, memory referenced.
Arg2: 0000000000000000, value 0 = read operation, 1 = write operation.
Arg3: fffff80002c8e6eb, If non-zero, the instruction address which referenced the bad memory
    address.
Arg4: 0000000000000005, (reserved)

 

[Baarup]

I did leave memtest running for 20 passes, without any errors.
Then turning on Driver Verifier, to get a lot of bsods.

I hope these files tell you, more about what the problem is.

 

[Arc]

Five verifier enabled minidumps ... and 4 different situations.

BugCheck BE, {fffff8a016634774, a0d00003664dd321, fffff88008d6b0d0, c}

Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+44d06 )

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

BugCheck 4E, {2, 204eef, 42efff, 1240}

Probably caused by : dxgmms1.sys ( dxgmms1!VIDMM_GLOBAL::ReferenceDmaBuffer+1d9 )

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

BugCheck 4E, {2, 24595f, 42efff, 800}

Probably caused by : dxgmms1.sys ( dxgmms1!VIDMM_GLOBAL::ReferenceDmaBuffer+39b )

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

BugCheck C1, {180229f600000000, 1000, 0, 81}

Probably caused by : fileinfo.sys ( fileinfo!FIStreamGetInfo+11f )

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

BugCheck C1, {fffff98018dd6ee0, fffff98018dd60a9, ab0118, 23}

Probably caused by : memory_corruption ( nt!MiCheckSpecialPoolSlop+9a )

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

It cannot be a driver error. It is hardware error. Better you ask for RMA the computer/motherboard.

 

[Baarup]

Then i will ask them for RMA on my mobo, hope it is that one then

Also my onboard sound went off now, can only play if i enable surround, and can only plug it in as rear speakers now..

 

[Baarup]

So now i've got a new motherboard, i hoped it would help.
But no, i stille get some BSOD's, can it be my SSD?

Ty..

 

[Arc]

On what date have you changed the board?

Have you performed a clear reinstall on it?

It is showing a stop 0x3B, which is very common in nature, but very difficult to identify the source.

 

[Baarup]

I changed it yesterday, i've just updated firmware on ssd and my GPU drivers.
Should i do a clean install of windows now, with the new mobo? It's the same model.

I will look for that error if more bsod

 

[Arc]

I think it is better to go for a clean reinstall.