BSOD: PAGE_FAULT_IN_NONPAGED_AREA (50), arg4:0000000000000002

Greetings and Salutations;

Scratching my head. Never in all the 25+ years of building pc's have I ever had this many BSOD's. RANDOM. RE-SET, RE-IMAGED, RE-INSTALLED WINDOWS SO MANY TIMES. Now I know why I don't this for a living anymore.

I have installed windbg from sdk. I have saved off many memory.dmp files. This one attached is most recent. I did a initial look, using !thread and "dps limit base" to try and isolate error. Not able to isolate to a drivers error.
I dont think it is a PEBKAC (problem exist between keyboard and chair) error.

any assistance would be much appreciated.
Attachment 227241

Hello and welcome to TenForums

You are right it is not evident from the crash dumps whether a non-Microsoft driver is involved.

In these situations we usually assess if the variety of different bugchecks indicate possible hardware problems or we pursue the driver route by using driver verifier.

Code:

2019-03-13T16:23:24.457		The computer has rebooted from a bugcheck.  The bugcheck was: 0x00000050 (0xffff860a5cdcd166, 0x0000000000000000, 0xfffff802788c71cc, 0x0000000000000002). A dump was saved in: C:\WINDOWS\MEMORY.DMP. Report Id: 39b7e4b4-5b92-4360-a332-c396b4f6228c.
2019-03-13T16:34:55.070		The computer has rebooted from a bugcheck.  The bugcheck was: 0x0000003b (0x0000000080000003, 0xfffff80452431af1, 0xffffb385e80e1220, 0x0000000000000000). A dump was saved in: C:\WINDOWS\MEMORY.DMP. Report Id: 45e4c5b6-d03a-449d-836f-897ed3a41634.
2019-03-13T17:21:11.030		The computer has rebooted from a bugcheck.  The bugcheck was: 0x00000050 (0xffffc7094a8ef30c, 0x0000000000000000, 0xfffff8037957da51, 0x0000000000000002). A dump was saved in: C:\WINDOWS\MEMORY.DMP. Report Id: 0cb293b1-ed47-4c16-a99a-6cf9d0d88337.
2019-03-13T18:35:02.120		The computer has rebooted from a bugcheck.  The bugcheck was: 0x000000d1 (0x000000000000000f, 0x0000000000000002, 0x0000000000000000, 0xfffff8075402ec0b). A dump was saved in: C:\WINDOWS\MEMORY.DMP. Report Id: 176592c1-e479-46b6-82c7-b95f45c16fc0.
2019-03-13T19:36:18.531		The computer has rebooted from a bugcheck.  The bugcheck was: 0x00000050 (0xffffc8035872d2cc, 0x0000000000000000, 0xfffff8063161aa51, 0x0000000000000002). A dump was saved in: C:\WINDOWS\MEMORY.DMP. Report Id: 3492a188-6c7e-4f02-a472-4bf100eb00c5.

Based on the above I would not be too sure which way to go so I'd advise running driver verifier for about 48h to see if it throws up any drivers that are not functioning correctly. Follow the tutorial below.

Diagnostic Test

 DRIVER VERIFIER

   Warning

Please make a backup of your important files and get your rescue media or create one.
Please create a restore point.

Please read and run driver verifier.

If you suspect a driver is causing a problem but do not have a clear idea which one it is then Driver Verifier stresses your drivers and will crash your pc if any driver fails due to a violation.

Driver verifier should be performed for a max of 48 hours, or until you have a bluescreen, whichever comes first.

If driver verifier has found a violation and you can't get back into windows normally, try to boot into safe mode and reset driver verifier from within safe mode, or in the troubleshooting options open command prompt and type verifier /reset.

   Note

Your system will act very sluggishly while driver verifier is enabled, this is normal as your drivers will be being subjected to heavy testing in order to make them crash.

thank you for the reply Phil. I will get that setup and running.

When checking e-mail this morning I got this new one. Havent seen this in all the trials and tribulations of trying to get this system into a stable state.Attachment 227260

JUST GOT THIS RIGHT AFTER I POSTED PRIOR. So frustrating. I didnt even have time to run windbg.








Attachment 227262

iqvw64e.sys is listed as an Intel Corporation Network Adapter Diagnostic Driver.

This looks like something you could either remove or try to update. Unless you are using it I would remove it.

The most recent crash (Page Fault in nonPaged Area) still does not show any driver.

Thanks Phil. I didnt search for the file and what it was part of. still trying to review last bsod in memory.dmp in windbg.

Iqvw64e.sys file information

The process known as Intel® Network Adapter Diagnostic Driver belongs to software Intel® iQVW64.SYS or Intel® Network Connections by Intel (Intel | Data Center Solutions, IoT, and PC Innovation).

uninstalled Intel® Network Connections.

Thanks Again.

Greetings;

Trying to follow through on instruction for driver verifier. another BSOD.

Attachment 227269

while sitting idle and with the firefox web browser open to Ten Forums. RANDOM CRASH. no other apps open.

I am really hoping that by posting these in sequential order that people can have a place to goto so they dont have to go through this (insert fun word(s) here).

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) A driver has inadvertently or deliberately modified critical kernel code
or data. See http://www.microsoft.com/whdc/driver...tPatching.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) A hardware corruption occurred, e.g. failing RAM holding kernel code or data.
Arguments:
Arg1: a39fe96472c8d738, Reserved
Arg2: b3b6f5eac54714b6, Reserved
Arg3: fffff8016d6e8c48, Failure type dependent information
Arg4: 0000000000000001, Type of corrupted region, can be

web site listed is "Not Found", imagine that ...

Attachment 227291

I am really trying to get driver verifier re-search done so I comprehend what I am doing and will execute asap.

another one. I am gonna stop posting.Attachment 227297Attachment 227300

I got 3 more after this post. PAGE_FAULT_IN_NONPAGED_AREA.

Ok, this is starting to look a lot like hardware failure.

I suspect your RAM might be faulty. Please run your machine with one of the RAM modules removed, this will reduce your memory to 8GB but it will be enough to test. Check to see if the BSODs continue. Then swap modules over and see if the other is causing BSODs. In this way you can tell if one of the modules is faulty. If so you will need to replace the RAM. I recommend that you replace them both with a matched pair.

Tracking down hardware faults is tricky so it might not be as simple as this but let's take it a step at a time.