BSOD when changing windows

N

Nemanja_Wap

Member
Hi! For the last couple of days I'm getting a BSOD when changing between Opera and World of Tanks (for example). I have a bluescreenview and i will copy the results after the text. I'm using Windows 7 Ultimate x64. My components are: AMD Athlon X2 280, Nvidia GeForce 210, 4 Gb of DDR2 ram... I searched forums with paremeters from bluescreenview and with name of driver that causes BSOD. I have tried many solutions, but it still apears. I appreciate any kind of help!

==================================================
Dump File : 052816-12433-01.dmp
Crash Time : 28.5.2016 0:55:10
Bug Check String : PAGE_FAULT_IN_NONPAGED_AREA
Bug Check Code : 0x00000050
Parameter 1 : fffff900`c1f74190
Parameter 2 : 00000000`00000000
Parameter 3 : fffff960`002ec69d
Parameter 4 : 00000000`00000000
Caused By Driver : win32k.sys
Caused By Address : win32k.sys+c40d1
File Description : Multi-User Win32 Driver
Product Name : Microsoft® Windows® Operating System
Company : Microsoft Corporation
File Version : 6.1.7600.16385 (win7_rtm.090713-1255)
Processor : x64
Crash Address : ntoskrnl.exe+71f00
Stack Address 1 :
Stack Address 2 :
Stack Address 3 :
Computer Name :
Full Path : C:\Windows\Minidump\052816-12433-01.dmp
Processors Count : 2
Major Version : 15
Minor Version : 7600
Dump File Size : 288.592
Dump File Time : 28.5.2016 0:56:27
==================================================

==================================================
Dump File : 052716-13088-01.dmp
Crash Time : 27.5.2016 23:48:30
Bug Check String : PAGE_FAULT_IN_NONPAGED_AREA
Bug Check Code : 0x00000050
Parameter 1 : fffff900`c1c18770
Parameter 2 : 00000000`00000000
Parameter 3 : fffff960`00686d15
Parameter 4 : 00000000`00000000
Caused By Driver : win32k.sys
Caused By Address : win32k.sys+c40d1
File Description : Multi-User Win32 Driver
Product Name : Microsoft® Windows® Operating System
Company : Microsoft Corporation
File Version : 6.1.7600.16385 (win7_rtm.090713-1255)
Processor : x64
Crash Address : ntoskrnl.exe+71f00
Stack Address 1 :
Stack Address 2 :
Stack Address 3 :
Computer Name :
Full Path : C:\Windows\Minidump\052716-13088-01.dmp
Processors Count : 2
Major Version : 15
Minor Version : 7600
Dump File Size : 291.504
Dump File Time : 27.5.2016 23:49:20
==================================================

==================================================
Dump File : 052716-14164-01.dmp
Crash Time : 27.5.2016 21:29:05
Bug Check String : PAGE_FAULT_IN_NONPAGED_AREA
Bug Check Code : 0x00000050
Parameter 1 : fffff900`c298b770
Parameter 2 : 00000000`00000000
Parameter 3 : fffff960`00626d15
Parameter 4 : 00000000`00000000
Caused By Driver : ntoskrnl.exe
Caused By Address : ntoskrnl.exe+71f00
File Description : NT Kernel & System
Product Name : Microsoft® Windows® Operating System
Company : Microsoft Corporation
File Version : 6.1.7600.16385 (win7_rtm.090713-1255)
Processor : x64
Crash Address : ntoskrnl.exe+71f00
Stack Address 1 :
Stack Address 2 :
Stack Address 3 :
Computer Name :
Full Path : C:\Windows\Minidump\052716-14164-01.dmp
Processors Count : 2
Major Version : 15
Minor Version : 7600
Dump File Size : 291.560
Dump File Time : 27.5.2016 21:30:31
==================================================

==================================================
Dump File : 052616-17425-01.dmp
Crash Time : 26.5.2016 22:58:43
Bug Check String : SYSTEM_SERVICE_EXCEPTION
Bug Check Code : 0x0000003b
Parameter 1 : 00000000`c0000005
Parameter 2 : fffff960`006a6d15
Parameter 3 : fffff880`073d3110
Parameter 4 : 00000000`00000000
Caused By Driver : cdd.dll
Caused By Address : cdd.dll+6d15
File Description : Canonical Display Driver
Product Name : Microsoft® Windows® Operating System
Company : Microsoft Corporation
File Version : 6.1.7600.16385 (win7_rtm.090713-1255)
Processor : x64
Crash Address : ntoskrnl.exe+71f00
Stack Address 1 :
Stack Address 2 :
Stack Address 3 :
Computer Name :
Full Path : C:\Windows\Minidump\052616-17425-01.dmp
Processors Count : 2
Major Version : 15
Minor Version : 7600
Dump File Size : 291.552
Dump File Time : 26.5.2016 22:59:38
==================================================

==================================================
Dump File : 052516-11247-01.dmp
Crash Time : 25.5.2016 23:54:56
Bug Check String : SYSTEM_SERVICE_EXCEPTION
Bug Check Code : 0x0000003b
Parameter 1 : 00000000`c0000005
Parameter 2 : fffff800`02e9601e
Parameter 3 : fffff880`072540e0
Parameter 4 : 00000000`00000000
Caused By Driver : ntoskrnl.exe
Caused By Address : ntoskrnl.exe+71f00
File Description : NT Kernel & System
Product Name : Microsoft® Windows® Operating System
Company : Microsoft Corporation
File Version : 6.1.7600.16385 (win7_rtm.090713-1255)
Processor : x64
Crash Address : ntoskrnl.exe+71f00
Stack Address 1 :
Stack Address 2 :
Stack Address 3 :
Computer Name :
Full Path : C:\Windows\Minidump\052516-11247-01.dmp
Processors Count : 2
Major Version : 15
Minor Version : 7600
Dump File Size : 291.552
Dump File Time : 25.5.2016 23:55:44
==================================================

==================================================
Dump File : 052516-12760-01.dmp
Crash Time : 25.5.2016 22:49:58
Bug Check String : PAGE_FAULT_IN_NONPAGED_AREA
Bug Check Code : 0x00000050
Parameter 1 : fffff900`c25d3770
Parameter 2 : 00000000`00000000
Parameter 3 : fffff960`006b6d15
Parameter 4 : 00000000`00000000
Caused By Driver : dxgkrnl.sys
Caused By Address : dxgkrnl.sys+378d2
File Description : DirectX Graphics Kernel
Product Name : Microsoft® Windows® Operating System
Company : Microsoft Corporation
File Version : 6.1.7600.16385 (win7_rtm.090713-1255)
Processor : x64
Crash Address : ntoskrnl.exe+71f00
Stack Address 1 :
Stack Address 2 :
Stack Address 3 :
Computer Name :
Full Path : C:\Windows\Minidump\052516-12760-01.dmp
Processors Count : 2
Major Version : 15
Minor Version : 7600
Dump File Size : 291.552
Dump File Time : 25.5.2016 22:50:48
==================================================
 
ubuysa

ubuysa

The BSOD Doctor
That BSOD happens because a program (or Windows) referenced a byte of memory that was not assigned to it or which it's not permitted to access. In all your examples all the useful information we can gather from the BSOD data is that in each case it was a memory read operation (the memory addresses in the other parameters don't help unless we have a memory dump).

You start by saying "...for the last couple of days...", so what happened two days ago? If something was working before and now it's not then something has changed. What changed two days ago?

Have you installed recent Windows updates, driver updates, software updates, new hardware, new software, have you made configuration changes, registry changes, are you using software in new ways, exploiting new features, etc. etc. If you can figure out what changed two days ago you'll be halfway home.

One of the first things I'd be doing is to disconnect all external devices except for the keyboard and mouse and see whether it will BSOD then. If it does I'd ensure that all the latest Windows updates are applied (including recommended updates) and that all drivers are fully up to date and properly installed. Use ONLY drivers from PCS or the hardware manufacturer's website, do NOT use a third party driver search and install tool.

I'd also download Memtest (from http://memtest.org) and leave Memtest running at least overnight (24 hours would be better) to check that you don't have a flaky RAM card.

If it were mine I'd even take a full disk image of the system drive (so you have an easy way back to where you are now) - I'd use Macrium Reflect for that - and do a clean install of Windows 7 and all the latest drivers. Then test it thoroughly without installing any other software or hardware to see whether it BSODs in that clean state. That will help you decide whether it's a software issue (which is the most likely) or a hardware issue.
 
Last edited:
N

Nemanja_Wap

Member
ubuysa said:
That BSOD happens because a program (or Windows) referenced a byte of memory that was not assigned to it or which it's not permitted to access. In all your examples all the useful information we can gather from the BSOD data is that in each case it was a memory read operation (the memory addresses in the other parameters don't help unless we have a memory dump).

You start by saying "...for the last couple of days...", so what happened two days ago? If something was working before and now it's not then something has changed. What changed two days ago?

Have you installed recent Windows updates, driver updates, software updates, new hardware, new software, have you made configuration changes, registry changes, are you using software in new ways, exploiting new features, etc. etc. If you can figure out what changed two days ago you'll be halfway home.

One of the first things I'd be doing is to disconnect all external devices except for the keyboard and mouse and see whether it will BSOD then. If it does I'd ensure that all the latest Windows updates are applied (including recommended updates) and that all drivers are fully up to date and properly installed. Use ONLY drivers from PCS or the hardware manufacturer's website, do NOT use a third party driver search and install tool.

I'd also download Memtest (from http://memtest.org) and leave Memtest running at least overnight (24 hours would be better) to check that you don't have a flaky RAM card.

If it were mine I'd even take a full disk image of the system drive (so you have an easy way back to where you are now) - I'd use Macrium Reflect for that - and do a clean install of Windows 7 and all the latest drivers. Then test it thoroughly without installing any other software or hardware to see whether it BSODs in that clean state. That will help you decide whether it's a software issue (which is the most likely) or a hardware issue.
Click to expand...

For the last two days i was evoiding sudden graphic changes that caused BSOD (example: when I'm playing WOT I don't minimize it often). It happenes mostly when I try to bring WOT up again in full screen. I don't know which external device could cause BSOD, I have camera, microphone, printer, sensor for remote and that's all. I have not instaled any updates and the automatic ones are off. I have tried instaling latest display drivers and it happens again. Now I will try putting other graphic card (same as mine, but it's ASUS) and see will it repeat. I already tried instaling other version of Windows 7 Ultimate x64, and ofter some time it started again. Than you for your answer, I will definitely try your methods!
 
N

Nemanja_Wap

Member
For the last two days I was avoiding sudden graphic changes that usually trigger BSOD. Almost everytime it happend when I was trying to bring minimized full screen aplications back up. Sometimes it goes normal. I don't know which external device could trigger it. I have web cam, microphone, printer, sensor for remote and that kind of stuff. I have tried instaling other drivers (all from manufacturer's website) and same again. A few months ago I even instaled other version of Windows 7 Ultimate x64 and after some time same. Now I want to try putting other graphics card (I borrowed it form friend). It has similar strenght as mine, but it's from ASUS. Thank you for the answer, I will definitely try your methods!
 
N

Nemanja_Wap

Member
Again BSOD... This time it was in screen saver and I moved mouse to wake it.
==================================================
Dump File : 053016-12948-01.dmp
Crash Time : 30.5.2016 19:28:02
Bug Check String : SYSTEM_SERVICE_EXCEPTION
Bug Check Code : 0x0000003b
Parameter 1 : 00000000`c0000005
Parameter 2 : fffff960`00174283
Parameter 3 : fffff880`064d2060
Parameter 4 : 00000000`00000000
Caused By Driver : win32k.sys
Caused By Address : win32k.sys+c4283
File Description : Multi-User Win32 Driver
Product Name : Microsoft® Windows® Operating System
Company : Microsoft Corporation
File Version : 6.1.7600.16385 (win7_rtm.090713-1255)
Processor : x64
Crash Address : ntoskrnl.exe+71f00
Stack Address 1 :
Stack Address 2 :
Stack Address 3 :
Computer Name :
Full Path : C:\Windows\Minidump\053016-12948-01.dmp
Processors Count : 2
Major Version : 15
Minor Version : 7600
Dump File Size : 291.496
Dump File Time : 30.5.2016 19:28:53
==================================================
 
ubuysa

ubuysa

The BSOD Doctor
Nemanja_Wap said:
Memtest was running for 16 hours and found no erors... I'dont know what can I do next.
Click to expand...

Take a disk image of your system drive (so you have a way back) and do a clean reinstall of Windows and drivers. Install nothing else at that point just see whether it will BSOD. If it does it's mots likely hardware.
 
ubuysa

ubuysa

The BSOD Doctor
Nemanja_Wap said:
If i instal nothing else i will no BSOD for shure. Because it happens when I switch between aplications.
Click to expand...

Then you have a software issue, quite possibly caused by the applications themselves.

My best advice would be for you to reinstall Windows and the drivers and then install your third party apps one at a time, testing fully after each install until you find the issue.

There really is no magic bullet here and no short cuts. It may be that your system has become unstable because of repeated installs/uninstalls or config changes etc. In a situation like yours where there is no obvious way forward a clean reinstall of Windows and drivers, followed by a careful and progressive reinstall of third party applications is the only way to get to the bottom of this.

You might well find that a clean reinstall of everything solves the problem.
 
N

Nemanja_Wap

Member
I will do that. It's been a long time since I reinstaled some apps. Thank you sir, if you ever visit Belgrade, you have a drink from me ;)
 
You must log in or register to reply here.
Top