Solved BSOD every boot - PAGE_FAULT_IN_NONPAGED_AREA (ntoskrnl.exe)

[DisksInSpace]

Hello 7forums, this is my first post. I read the posting guidelines, hope I've got in most of what is needed below.

Since last friday on the 26th of october my computer is blue screening every time I use it. The computer BSODs immediatelly after the Windows loading screen on 100 % of all boots.

Before that, it has been working fine for 1.5 years with the occational blue screen, but nothing that did not go away immediatelly on a subsequent boot and did not return for multiple days or weeks.

The error message is PAGE_FAULT_IN_NONPAGED_AREA. No dll is mentioned anywhere on the blue screen.

I have not installed any new hardware recently. I used it fine 2 hours before it stopped working, and before that multiple weeks without any changes to HW.

Here is what I have done so far to try to resolve the problem.

* Booting in safe mode fails with BSOD, same thing with 'last known good config'
* Tried to repair windows. Repair fails on 'repair boot' with another BSOD "verification of KnownDLL failed". After reboot again I'm back to PAGE_FAULT... BSOD again.
* Viewed the minidump files in BlueScreenViewer. The last one with the same message that looks relevant does NOT seem to have a driver on the call stack, there is only ntoskrnl.exe.
* I've run checkdisk from repair cmd-line, no reported errors on any disks and all files seem to be there fine.
* I've removed all 4 memory sticks and tried rebooting with only one of them in the motherboard on boot, regardless of which are there still the same BOSD.
* I've run memory test twice from my F12 boot menu, no reported errors with all 4 sticks connected.
* I have 2 graphics cards. I've tried to boot with just one of them, but regardless of which one is in the motherboard I still get the same BSOD behavior.
* I've tried getting rid of dust inside my box and rebooting, no change in result.
* Read somewhere that running sfc /scannow may help, but that command fails with a message about there being is a pending repair that needs reboot first, but reboot/repair fails as mentioned above.
* Booting from my Windows install DVD does not change anything either

All this is done with no other peripherals connected to the computer except monitor, keyboard and mouse.

When my computer BSODs now no new minidump files seem to be created anymore. It does say on BSOD screen that it is creating a dump file, but when I check in Windows/Minidumps from subsequent repair boot+cmd console, its just the same ones there as before and no new dumps.

I have not tried to reinstall Windows since I feel it is likely this is a hardware problem and that a OS-reinstall would be a big pain to go through (lost files, lots of time, etc) and likely not make any difference anyway. I guess it is possible that windows repair actually fixed something and then just failed to complete, but I find that rather unlikely under the circumstances. But it's hard to be certain, obviously.


My conclusions are this
- It seems unlikely this is a faulty driver, hard drive, memory stick or graphics card.
- The most likely problem is faulty motherboard, if it is not that it might perhaps be the CPU
- I read somewhere that PSU problem could cause this BSOD error, but it seems unlikely to me in this case
- It is unlikely that re installing Windows would fix this

What do you guys think, am I drawing the right conclusions here?

BSOD minidumps are attached. Computer specs as below


Motherboard
Gigabyte GA-990FXA-UD7, Socket-AM3+, ATX, 990FX+SB950, DDR3, 6xPCIe(2.0)x16, CFX&SLI, SATA 6Gb/s, USB 3.0, FW

CPU
AMD Phenom II X6 1100T Black Edition, Socket-AM3, Six Core, 3,3GHZ/3,7GHz Turbo, 9MB, 125W, Boxed

CPU Cooler
Noctua NH-U12P SE2, Socket 775/1155/1156/1366, AM2/AM2+/AM3, 1300 RPM, 92,3 m³/h, 19,8 dBA

Graphics card

(in CrossFire mode) 2* XFX Radeon HD 6970 2GB GDDR5, PCI-Express 2.1, 2xDVI, HDMI, 2xmini-DisplayPort, 880MHz,

PSU
Corsair TX V2 850W PSU, ATX 12V V2.3, 80 Plus Bronze, Standard. 4x 6+2-pin PCIe, 8x SATA, 140mm Fan

SSD (boot disk)
Corsair SSD Force Series™ 3, 60GB, SATA 6 Gb/s (SATA3.0), 550MB/490MB/s read/write, SandForce® SF-2200

Disk (w/ Windows)
Western Digital Caviar® Green™ 2TB, SATA 3Gb/sec, RPM = IntelliPower, 64MB

OS
Microsoft Windows 7 Home Premium, x64, English, Full, DVD

 

[Arc]

Welcome aboard.

It is caused by Wisair WSR Host Wire Adapter Driver.

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

Use !analyze -v to get detailed debugging information.

BugCheck 1000007E, {ffffffffc0000005, fffff880088ed35e, fffff880143cc9e8, fffff880143cc240}
[COLOR=Red]
Probably caused by : WSR_HWA.SYS [/COLOR]( WSR_HWA+5b35e )

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

And it is very old.

 lmvm WSR_HWA
start             end                 module name
fffff880`08892000 fffff880`0897c000   WSR_HWA  T (no symbols)           
    Loaded symbol image file: WSR_HWA.SYS
    Image path: \SystemRoot\system32\DRIVERS\WSR_HWA.SYS
   [COLOR=Red] Image name: WSR_HWA.SYS
    Timestamp:        Mon May 10 15:08:36 2010 [/COLOR](4BE7D41C)
    CheckSum:         000E8826
    ImageSize:        000EA000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4

Update it from Welcome to Wisair.

Also, disable USB selective suspense.
http://www.sevenforums.com/tutorials/147369-usb-selective-suspend-turn-off.html

Let us know the results.

Edit: Uninstall Norton, Norton 360 and all Symentec products using Norton Removal Tool and use Microsoft Security Essentials.

 

[DisksInSpace]

Thanks for responding,


Yes ONE of the minidumps contains that driver. However, it seems unlikely to me it can be causing the following

Safe mode boot fails w/ BSOD
Windows repair fails w/ BSOD
Boot Windows in last known config fails w/ BSOD

And how am I supposed to update a driver if I cant even start Windows in any way? If there is a way, pls let me know

Im sure it has caused BSODs, but there must be another root cause for the above

 

[Arc]

If you are failing to boot at all (I dont know how did you collect the dumps in that situation) follow it.

• Scan with http://www.sevenforums.com/tutorials/166445-windows-defender-offline.html
• http://www.sevenforums.com/tutorials/219533-troubleshooting-windows-7-failure-boot.html
• Remove all but one ram stick and all graphics cards.

Thanks for responding,
Yes ONE of the minidumps contains that driver. However, it seems unlikely to me it can be causing the following

Lol .... ONE+ONE= ONE ?
View attachment 239773

Have you seen the rest part of my first post ? is there any other info?

 

[DisksInSpace]

How I got the dumps is explained in my first post. I got them out by starting windows repair mode (which becomes an option after a failed boot), then at the end of repair (which finds no problem) there is an 'Advanced' option. From the menu that comes after that there is an option to start a command prompt. From here I copied the dump files with the copy command to a USB stick. It seems that whoever built the repair included some form of USB disk drivers, thank god.

About booting with only one memory stick and excluding faulty graphics card, I have already done that. This is also explained in my original post.

What good is having posting guidelines if some people don't even bother reading whats in the posts, just because there are attachments? LOL indeed

Sure, I realize a lot of people ask a lot of strange and retarded stuff in forums like these

I'll check out the links

 

[DisksInSpace]

Also, disable USB selective suspense.

Edit: Uninstall Norton, Norton 360 and all Symentec products using Norton Removal Tool and use Microsoft Security Essentials.

Disabling USB selective suspense, seems to require windows to actually start first. Same with Ms Security essentials.

Ill see what I can do with the other link about troubleshooting Win7 failure to start

 

[Arc]

After checking 100+ threads a day, there is a very minimum time in hand for rants.

Sorry I lack time here.

 

[DisksInSpace]

I have built this computer myself. There is no vendor I can point to and say this is your problem. If there was I would not be asking here. This is my problem, and that's fine.

No, I dont "enjoy" BSODs. They have been very rare until recently, as explained. Unless you have a good deal of experience, I feel they are not exactly easy to trouble shoot and deal with. Now the situation has changed and I am forced to learn. If you want to judge me for that, go ahead.

And to be clear, yes I've already talked to multiple vendors and nobody seems to provide a BSOD problem solving service even if I would be willing to pay for it, so I have no choice here except figuring this out on my own.

That is why I am here, to learn how to fix this. After first trying everything I could think of before asking for help.

As an update, I've tried bootrec now and no improvement. Safe mode just results in an immediate reboot now. I still cant find a way to start windows in any mode other than repair which still can not complete.

My next step will likely be to attempt a clean windows re install. If that does not work, I think I will send the motherboard back to the vendor I bought it from so they can do a HW analysis on it. This they say they will do.

 

[DisksInSpace]

Clean windows install fixed this issue.

Thank you for your help