Bluescreens with Fresh Windows 7 Installation

Joselox

Distinguished
May 11, 2011
28
0
18,540
Hello,

I upgraded my PC and got a new Mobo+processor+ram.
I decided to go for a clean Windows 7 and I started getting blue screens before and after installing drivers for graphics and mobo.
I am using i7 4790k, asus z97-e, corsair 16gb ram (2 modules), 2 HDD, corsair 550W power supply.
I ran windows memory test and didn't show any errors.
I am going to now copy the result of the "whocrashed" app. to show you guys. It is long :)



System Information (local)
--------------------------------------------------------------------------------

Computer name: JOSELOX-PC
Windows version: Windows 7 Service Pack 1, 6.1, build: 7601
Windows dir: C:\Windows
Hardware: All Series, ASUS, ASUSTeK COMPUTER INC., Z97-E/USB 3.1
CPU: GenuineIntel Intel(R) Core(TM) i7-4790K CPU @ 4.00GHz Intel586, level: 6
8 logical processors, active mask: 255
RAM: 17115938816 bytes total

--------------------------------------------------------------------------------
Crash Dump Analysis
--------------------------------------------------------------------------------

Crash dump directory: C:\Windows\Minidump

Crash dumps are enabled on your computer.

On Wed 04-Oct-17 12:07:46 AM your computer crashed
crash dump file: C:\Windows\Minidump\100417-31106-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x6F980)
Bugcheck code: 0x4E (0x99, 0x3A55A8, 0x2, 0x3A64A7)
Error: PFN_LIST_CORRUPT
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 page frame number (PFN) list is corrupted.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem. 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 Wed 04-Oct-17 12:07:46 AM your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: ntkrnlmp.exe (nt!KeBugCheckEx+0x0)
Bugcheck code: 0x4E (0x99, 0x3A55A8, 0x2, 0x3A64A7)
Error: PFN_LIST_CORRUPT
Bug check description: This indicates that the page frame number (PFN) list is corrupted.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem. 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 03-Oct-17 9:03:13 PM your computer crashed
crash dump file: C:\Windows\Minidump\100317-14570-01.dmp
This was probably caused by the following module: nvlddmkm.sys (0xFFFFF8800F5069BB)
Bugcheck code: 0xD1 (0x53, 0xB, 0x0, 0xFFFFF8800F5069BB)
Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
file path: C:\Windows\system32\drivers\nvlddmkm.sys
product: NVIDIA Windows Kernel Mode Driver, Version 385.41
company: NVIDIA Corporation
description: NVIDIA Windows Kernel Mode Driver, Version 385.41
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.
A third party driver was identified as the probable root cause of this system error. It is suggested you look for an update for the following driver: nvlddmkm.sys (NVIDIA Windows Kernel Mode Driver, Version 385.41 , NVIDIA Corporation).
Google query: NVIDIA Corporation DRIVER_IRQL_NOT_LESS_OR_EQUAL

On Tue 03-Oct-17 4:59:28 PM your computer crashed
crash dump file: C:\Windows\Minidump\100317-25396-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x6F980)
Bugcheck code: 0x4E (0x99, 0x16B2FF, 0x2, 0x194EFE)
Error: PFN_LIST_CORRUPT
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 page frame number (PFN) list is corrupted.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem. 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 Sun 01-Oct-17 10:27:33 PM your computer crashed
crash dump file: C:\Windows\Minidump\100117-15272-01.dmp
This was probably caused by the following module: nvlddmkm.sys (0xFFFFF8800F2BE5C0)
Bugcheck code: 0xD1 (0x10E3A3E0, 0xB, 0x0, 0xFFFFF8800F2BE5C0)
Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
file path: C:\Windows\system32\drivers\nvlddmkm.sys
product: NVIDIA Windows Kernel Mode Driver, Version 385.41
company: NVIDIA Corporation
description: NVIDIA Windows Kernel Mode Driver, Version 385.41
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.
A third party driver was identified as the probable root cause of this system error. It is suggested you look for an update for the following driver: nvlddmkm.sys (NVIDIA Windows Kernel Mode Driver, Version 385.41 , NVIDIA Corporation).
Google query: NVIDIA Corporation DRIVER_IRQL_NOT_LESS_OR_EQUAL

--------------------------------------------------------------------------------
Conclusion
--------------------------------------------------------------------------------

5 crash dumps have been found and analyzed. A third party driver has been identified to be causing system crashes on your computer. It is strongly suggested that you check for updates for these drivers on their company websites. Click on the links below to search with Google for updates for these drivers:

nvlddmkm.sys (NVIDIA Windows Kernel Mode Driver, Version 385.41 , NVIDIA Corporation)

If no updates for these drivers are available, try searching with Google on the names of these drivers in combination with the errors that have been reported for these drivers. Include the brand and model name of your computer as well in the query. This often yields interesting results from discussions on the web by users who have been experiencing similar problems.

Read the topic general suggestions for troubleshooting system crashes for more information.

Note that it's not always possible to state with certainty whether a reported driver is responsible for crashing your system or that the root cause is in another module. Nonetheless it's suggested you look for updates for the products that these drivers belong to and regularly visit Windows update or enable automatic updates for Windows. In case a piece of malfunctioning hardware is causing trouble, a search with Google on the bug check errors together with the model name and brand of your computer may help you investigate this further.


Well, thats all.
Hope you can help.

Jose A. Mikulas
 

Joselox

Distinguished
May 11, 2011
28
0
18,540
Hello, thanks for the answer. Sorry for not replying, I was away for the weekend.
I reinstalled GPU (geforce drivers, right?) like you said.
Before running MemTest86 tonight, I took out one RAM from slot 3 and I had another error and now, I took slot 1 from the RAM to see what happens.

"On Mon 09-Oct-17 9:19:07 PM your computer crashed
crash dump file: C:\Windows\Minidump\100917-31559-01.dmp
This was probably caused by the following module: dxgmms1.sys (dxgmms1+0x20423)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF88004220423, 0xFFFFF8800CD91650, 0x0)
Error: SYSTEM_SERVICE_EXCEPTION
file path: C:\Windows\system32\drivers\dxgmms1.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: DirectX Graphics MMS
Bug check description: This indicates that an exception happened while executing a routine that transitions from non-privileged code to privileged code.
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"

I don't know if I can update chipset driver since I just installed windows and donwloaded those from asus for my Mobo (I will check now)

Meanwhile I can let you know that Google is doing crazy things like closing on its own and I cant open it again unless I restart. I close all chromes with the windows management and still cant open it again. Some times on youtube I will only see the video and anything else. Maybe this helps.
Games like League of legends keep giving me errors and shut down.

While I wait for your reply I will start a new windows install. All this GPU and drivers uninstall and install is harder than a fresh windows installation xD

I will check for your reply when I finish the install. Thanks!

Jose

PS: I have main HDD in sata 6gb port 1 and then dvd drive on port 2 and second sata HDD in port 3. Is this ok?
 
That error ( SYSTEM_SERVICE_EXCEPTION) related to corrupted device drivers or OS files, or damaged hard disk, or a variety of hardware. In your case, it maybe only for the GPU ( description: DirectX Graphics MMS). So try use onboard intel iGPU , remove the GPU, also plug in one stick RAM only. Then use DDU uninstall the GPU driver in safe mode, then switch to the NVIDIA GPU, after that reinstall the GPU driver. If the PC runs fine, then check the RAM one by one with MemTest86.

By the way, which GPU did you have?
 

Joselox

Distinguished
May 11, 2011
28
0
18,540


Just before reinstalling new Windows with my last attempt the PC seems to run fine. I tried the other ram stick and i reinstalled the chipset driver like you said and o played league of Legends for 2hs no problem. I Will keep you posted. I Will use it a lot today.
I use nvidia GeForce 750.
Thanks! Looks good for Now!!!
 

Joselox

Distinguished
May 11, 2011
28
0
18,540
Well, it was too good to be true. Computer just crashed and gave me this error:
Crash dump directory: C:\Windows\Minidump

Crash dumps are enabled on your computer.

On Fri 13-Oct-17 1:56:22 PM your computer crashed
crash dump file: C:\Windows\Minidump\101317-32931-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x70E00)
Bugcheck code: 0x50 (0xFFFFFAB00096C2C8, 0x0, 0xFFFFF80002F9F229, 0x5)
Error: PAGE_FAULT_IN_NONPAGED_AREA
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 invalid system memory has been referenced.
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 the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.
 
Because the other driver caused the problem, may try update all the driver, like audio, network, USB3.0 ( because you use win7), even the BIOS too.

Or try those methods from https://www.deskdecode.com/how-to-fix-page_fault_in_nonpaged_area-0x00000050/
 

Joselox

Distinguished
May 11, 2011
28
0
18,540
Hello again,
I did a clean Windows install TWICE and both times I was unable to install the usb drivers from Asus webpage. Now I installed Everest and it does not recognize my mobo. Is there a chance I got a fake or defective mobo? I bought is used. I can also not update bios with the EZ Update program from Asus.
I will post some pictures so you can see all the problems.
https://imgur.com/77rbdxD
https://imgur.com/a/lToj4
https://imgur.com/B8WStJS
https://imgur.com/UEjuvIl
https://imgur.com/JBDdSQm
 
From one picture, your MB had the 0402 version only, and you said your can't update the BIOS, it is strange, but you said you got it from someone else. So it may have the problem, then the previous owner may change the BIOS chipset.

Or if you want may try the DOS method by using the "BIOS-Utilities "
https://www.asus.com/us/Motherboards/Z97EUSB31/HelpDesk_Download/ but if you can return it to the seller, do it.

Also you had unknown device and PCI Simple Communications Controller in Device Manager, you need to install the intel Management Engine Interface driver.
 

Joselox

Distinguished
May 11, 2011
28
0
18,540


I already tried the Intel management engine interface and it sucks. I can not identify the correct one for me so I installed the Intel® Driver & Support Assistant and it wont find anything to install...
I have no idea what "8 Series Chipset-Based" mean and which one I have and I cant find it on the asus specifications for my motherboard. Sorry, this is pissing me off so much since I have spent more than 20hs with this crap.
I downloaded the DOS bios-utilities and when I run it from cmd dos it says it is not compatible with my x64 windows. Shall I try installing windows 32bits and try updating the bios from DOS? I ran DOS from windows cmd, not restarting.
Thanks for everything
 

Blackink

Distinguished
If it was me, I'd re-install Windows 7 again (sorry!), make sure you have the Ethernet drivers downloaded in case you need them, and then do all the Windows updates completely: check for updates, download, install, re-start, check for updates, download, install, re-start, etc....until ALL the windows 7 updates are installed.

DO NOT install any drivers from the Asus Installation CD.

Now run the PC the way you were and see if it Bluescreens. If not, your problem was something from the CD installation from ASUS (I've never used their CD for ANY drivers).
If it still blue screens, then your RAM or another component may be the problem and as others have mentioned in earlier posts, try the Memtest and then try one stick at a time.

Good Luck.....
 

Joselox

Distinguished
May 11, 2011
28
0
18,540

Believe it or not I tried that a few hours ago and the computer tilted (bad luck this time i guess, it never happened) I was about to do the same now but istalling fewer windows updates at a time.
I ran memtest and ram is fine so is HDD.
I only installed from webpage, not Asus CD.
I only installed ethernet drivers, and nvidia drivers right now.
I will install usb drivers (gave me errors) after all windows update and i will try all other asus updates after that too.

thanks for your help
 
For the intel IM driver, you need the IM for 9 Series Chipset-Based.

So you need to install the kb2685811 hot fix first, https://www.microsoft.com/en-us/download/details.aspx?id=38423&751be11f-ede8-5a0c-058c-2ee190a24fa6=True also need Microsoft* .NET framework 3.5 or higher. After that, do to the ASUS site to download and install the intel IM driver. Note: under the intel chipset driver tab. https://www.asus.com/us/Motherboards/Z97EUSB31/HelpDesk_Download/

May forget about the DOS method for updating the BIOS.
 

Joselox

Distinguished
May 11, 2011
28
0
18,540

Ok, I am done with all windows updates. When I went for the bb2685811 hotfix it said it was already installed. The same happened for the intel IM driver. I have a newer version now than the one from Asus.
The only problem I see is the "Other devices" "unknown device" driver missing under the Device Manager.
What could this be? Shall I try installing the USB driver from Asus?
 

Joselox

Distinguished
May 11, 2011
28
0
18,540
Well, here we go. While listening to music with 4 chrome windows open:

On Mon 10/23/2017 8:54:35 PM your computer crashed
crash dump file: C:\Windows\Minidump\102317-37658-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x70E00)
Bugcheck code: 0x50 (0xFFFFFA86014BAB9B, 0x0, 0xFFFFF80002EBFD85, 0x5)
Error: PAGE_FAULT_IN_NONPAGED_AREA
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 invalid system memory has been referenced.
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 the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.

I am so f@!#$ pissed right now...

I am reading some Toms Hardware posts about my error. I will try switching to my old rams and see if the problem goes away. These rams passed memtest, but who knows. I have been reading it could be over-speced timings for proper operation and many things
Here is a pic for the ram specs that the Mobo reads from Asus program:
https://imgur.com/Q9zgZqY
 
Your RAM is the Cl10, and the picture shows its timing is CL9, do you try use the intel XMP profile in the BIOS? Note: the RAM is 1600mhz with CL10.

The PAGE_FAULT_IN_NONPAGED_AREA maybe caused by RAM error or other driver. So try use the XMP profile, or manually set the RAM back to 1600mhz with Cl10.
 

Joselox

Distinguished
May 11, 2011
28
0
18,540


You are right, the RAM is CL10 and it shows CL9. I did not use intel XMP profile. Maybe previous owner.
If I want to do it manually, it has to be from the BIOS, right? Let me know, I will get right away with it! I never liked to overclock anyhing so I don't know how to do it. Tell me I can switch it from Bios and thats all I need, I will get right away with it!!!
 

Joselox

Distinguished
May 11, 2011
28
0
18,540
Ok, today I got an asnwer from Asus and they helped me updating the Bios. I also changed my RAM from Bios to "published profile" like you said with Intel XMP so now I am running on 10CL with both sticks and 1600.

Lets hope this helps!!! Otherwise, I got a friend who can help me diagnose my PC very cheap if this fails.
 

Joselox

Distinguished
May 11, 2011
28
0
18,540
Hello again,

So I updated the BIOS and problem solved. It could have been that or the XMP. I would guess it was the Bios update because Asus support told me that my processor was not supported by the old BIOS. Almost a week with no errors :)
I am so happy right now hahaha.

Thanks for everything!!! Problem solved!!!