New Comp, worked fine till Upgrades, now BSODs constantly. 0x0000009f

[legendor]

Hello I recently acquired a Dell Inspiron M5040. It came stock with

AMD E-450 APU with Raedon(tm) HD graphics 1.65GHz
4gb of DDR3 RAM

I upgraded the hard drive inside, and switched to an Intel 540 series 120gb SSD. I used a 40 dollar cable and CD to transfer the OS and drivers and such to the new SSD from the old HD.
Then I noticed I started getting BSODs, not being able to log off, shutdown, or restart. I had 4-5 crashes and minidumps, but then last night after another crash, only that crash remained in my minidump folder...weird. I tried using SF diagnostic tool, and it crashed every time after event logs success. Here is the folder I get when running SF diagnostic, grab all.

Using BlueScreenView, I attributed the bug check string to be DRIVER POWER STATE FAILURE, with code 0x0000009f. The filename that is showing red is ntoskrnl.exe. In the previous errors I had the past couple days, there was also a atkimdag error file? Please PLEASE HELP! I spent a lot of money on this computer and it is such a pain to be constantly trying to fix this issue!!! Thank you!

 

[Arc]

Hello legendor.

Uninstall McAfee Using McAfee Removal Tool.
Use Microsoft Security Essentials as your antivirus with windows inbuilt firewall, and free MBAM as the on demand scanner.

Download and install those, and then run full system scans with both of them, one by one.

update the network driver. Broadcom 802.11g Network Adapter - Dell Wireless 1390 WLAN Mini-Card
First, download the network card driver from manufactuer's/Dell's website.
Then reinstall the driver:

1. Click the Start Button, type "devmgmt.msc" (without quotation marks) in the Start Menu Search box and press Enter.
2. Double click to expand "Network adaptors".
3. Right click your network card and click Uninstall.
4. Check "Delete driver software for this device" check box, click OK.
5. Restart the computer
6. If windows does not auto configure the appropriate drivers at startup, install the downloaded one manually.

Let us know the results.

 

[legendor]

Uninstalled McAfee, ran the MSE quick scan (oops) and it came clean...Malware Bytes full scan clean. Trying to find correct driver. I found a download from Cnet .com a folder called 80211g? is this correct driveR?I found the correct driver from Dell. I deleted my current one andn successfully followed the steps for reinstallation. How do i test to see if it works. Also mentionable, windows update was failing and crashing constantly throughout the BS errors. I guess I will try to install and download windows update?

 

[Arc]

Try installing windows updates again ..... let us know if it is working now or not.

 

[legendor]

It is working!!!! Thank you so much you have made my holidays!!! I know that's dumb sounding but this has really been on my nerves lately. Any idea as to what went wrong??? Thanks again Arc

 

[Arc]

It is working!!!! Thank you so much you have made my holidays!!! I know that's dumb sounding but this has really been on my nerves lately. Any idea as to what went wrong??? Thanks again Arc

You are most welcome I am happy that I could help.

The problem was McAfee. You know how it attempts to protect you from internet threats? By disabling network As it is not there anymore, the problem is over.

If you think that you are really out of the issues, you may mark this thread as solved, by clicking the green button.

 

[legendor]

Bsod

Just recieved this BSOD while watching a movie on VLC media player. Nirsoft attributes it to 0x000000044 error code, MULTIPLE_IRP_COMPLETE_REQUESTS.

 

[Arc]

Sorry for the late reply.

It says it is a stop 0x44.

[COLOR=Red]BugCheck 44[/COLOR], {fffffa8009a52600, 1d7b, 0, 0}

*** WARNING: Unable to verify timestamp for amd_xata.sys
*** ERROR: Module load completed but symbols could not be loaded for amd_xata.sys
[COLOR=Red]Probably caused by : amd_xata.sys[/COLOR] ( amd_xata+2f01 )

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

It is a difficult situation to handle. Usually it is two different drivers who think they own the request packet, and both attempt to complete it. The first request successes, but the second one fails. It turns into a stop 0x44. Here it is to search for the device object fields of the failing driver, but in this situation, no information is available.

cmd  flg cl Device   File     Completion-Context
 [  f, 0]   0  0 fffffa800713c9c0 00000000 fffff8800114fec4-fffffa800749c220    
[COLOR=Red]          fffffa800713c9c0: Could not read device object or _DEVICE_OBJECT not found
    amd_xata[/COLOR]
            Args: 00000000 00000000 00000000 fffffa800713cb10
>[  0, 0]   0  0 fffffa8007140040 00000000 00000000-00000000    
          [COLOR=Red]Cannot read _DRIVER_OBJECT at fffffa8007137630[/COLOR]

            Args: 00000000 00000000 00000000 00000000
IO verifier information:
[COLOR=Red]No information available - the verifier is probably disabled[/COLOR]

I am suggesting you to do two things. First you update AMD Stor Filter Driver from http://support.amd.com/us/Pages/AMDSupportHub.aspx, and if then the issue persists, enable Driver verifier.
Driver Verifier - Enable and Disable

Let us know the results.

 

[legendor]

performed the required steps, computer freezes without bluescreen error showing.. i have to hard boot it with power button because nothing responds. My minidump folder now has a lock on it too

 

[Vir Gnarus]

Check the properties window of your Minidump folder and see if you somehow lost rights to it. Try to regain both ownership and viewing rights of the folder under the Security tab. If the details on the folder are showing up erroneous/empty (like security tab) then the folder is corrupt. Try deleting it and remaking it. If you can't even do that for some reason, then most likely you have a drive problem corrupting the filesystem (try doing CHKDSK /R).

When you said you followed the steps, did you also attempt to turn on Driver Verifier as well?

 

[legendor]

Yes, the minidump properties tab goes haywire whenever I try to open the security tab.. It only started happening after I followed the steps to turn on Driver Verifier. I will try to regain rights to the folder, if that doesn't work I'll try deleting/remaking, then CHKDSK /R

edit1: security tab opens now, and it shows that I have all permissions allowed throughout the system, user and admin settings...I am going to try to turn off Driver Verifier to see if my minidump folder is back with its contents. Computer is noticeably laggy during system processes sometimes, a lot more than ever before.

 

[legendor]

Computer is now slower than a 4 year old computer with lower specs... Tab switching in Firefox and Chrome is so laggy, and this translates to my programs/multitasking...Please help . I haven't BSOD since last time, but I feel that something somebody made me do in the previous posts has messed up my laptop. If there is anything I should try please let me know!

I feel like it is a driver problem... All of this started when I installed my new SSD. Thanks :/

 

[Arc]

Check it, do you have Driver verifier enabled by any chance till now? If so, disable it, now!

Driver Verifier - Enable and Disable.

 

[legendor]

Just clicked delete existing settings, and it said no changes made..:/

 

[Arc]

Scan the system for possible virus infection.

• Anti-rootkit utility TDSSKiller
• Windows Defender Offline

Stress test the CPU.
Hardware - Stress Test With Prime95

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.

 

[legendor]

TDSSkiller came back clean. Windows defender seemed to be a bit unnecessarily complicated, so is it possible to just run a malwarebytes scan?

edit: sorry for the atrocious grammar

 

[Vir Gnarus]

It's evident: replace your new drive. If you are getting instability issues as soon as you installed new hardware, that new hardware is bad. The file corruptions displayed previously show that, amongst other things.

Btw, I looked up the drive name, and I don't see an Intel 540 series anywhere. I see a 520 series and an 840, but no 540.

 

[legendor]

argh...I'm sorry it is a 520 series. I really don't understand how this happened...It's really irritating to spend a lot of money on a product and then have issues that are undiagnosable...I am not willing to give up though...Will try to keep updated. Thank you :/

 

[Vir Gnarus]

I think I see the problem then. This is a Sandforce controller drive. Sandforce controller drives are notorious for being very unstable and are wrecked with problems top-to-bottom. Same goes for OCZ drives. I would recommend avoiding Sandforce drives in the future unless you wish to gamble on it. You should RMA your drive if possible and either receive a refund on it to put towards a more stable item like a Samsung or Crucial, or try your luck by getting it replaced. You may need to have it replaced a couple times before you end up getting one that is somewhat stable.

 

[legendor]

There must be something I can do -.- Why would they sell these drives if they are 'wrecked with problems'... I don't understand how a drive can be so horrible