Sign-in / Sign-up
Your question

BSOD Page Fault In Nonpaged Area..

Tags:
  • Chrome
  • Blue Screen
  • RAM
  • Windows 7
Last response: in Windows 7
January 25, 2014 7:19:07 AM

Well, I don't really know why these BSOD's have started happening. I thought it was because my RAM was overclocked but I switched everything back to stock settings, still getting very random BSOD.

There is one trend though where I stress my pc with Passmark and then click on chrome, or another application, and boom, BSOD.

here's two dumps:

http://www.2shared.com/file/vyYts5_t/012414-16052-01.ht...

http://www.2shared.com/file/sKJsLLVy/012514-29920-01.ht...

the last one being the most recent.

More about : bsod page fault nonpaged area

a b $ Windows 7
January 25, 2014 8:24:48 AM

Can you upload it somewhere that doesn't require installing a downloader, try box.com or skydrive.
m
0
l
January 25, 2014 9:13:07 AM

I sent you a PM man.
m
0
l
Related resources
January 26, 2014 7:02:47 PM

You don't need a downloader anyways btw.
m
0
l
a b $ Windows 7
January 27, 2014 6:10:01 AM

Not trying to sound like a noob but I can't figure out how to download the file without it prompting for their B1 downloader.
m
0
l
January 27, 2014 7:47:59 AM

kawininjazx said:
Not trying to sound like a noob but I can't figure out how to download the file without it prompting for their B1 downloader.


It's cool dude, just check out the PM I sent ya. I uploaded it to Skydrive.

Usually I can just press download and it downloads the zip.
m
0
l
a c 296 $ Windows 7
January 27, 2014 8:21:05 AM

crash dump 1:

Windows 7 Kernel Version 7600 MP (6 procs) Free x64
Built by: 7600.17273.amd64fre.win7_gdr.130318-1532
System Uptime: 0 days 3:38:58.105

PROCESS_NAME: dwm.exe

BugCheck 50, {fffff900c2982d44, 0, fffff9600023d344, 0}
PAGE_FAULT_IN_NONPAGED_AREA (50)
Invalid system memory was referenced. This cannot be protected by try-except,
it must be protected by a Probe. Typically the address is just plain bad or it
is pointing at freed memory.
Arguments:
Arg1: fffff900c2982d44, memory referenced.
Arg2: 0000000000000000, value 0 = read operation, 1 = write operation.
Arg3: fffff9600023d344, If non-zero, the instruction address which referenced the bad memory
address.
Arg4: 0000000000000000, (reserved)

5: kd> k
Child-SP RetAddr Call Site
fffff880`08e97858 fffff800`02f4e694 nt!KeBugCheckEx
fffff880`08e97860 fffff800`02ecc96e nt! ?? ::FNODOBFM::`string'+0x41db7
fffff880`08e979c0 fffff960`0023d344 nt!KiPageFault+0x16e
fffff880`08e97b50 fffff960`00260749 win32k!GreSetRedirectionSurfaceSignaling+0x104
fffff880`08e97ba0 fffff800`02ecdad3 win32k!NtGdiHLSurfSetInformation+0x209
fffff880`08e97c20 000007fe`ff654efa nt!KiSystemServiceCopyEnd+0x13
00000000`0223f658 00000000`00000000 0x000007fe`ff654efa

This is a bugcheck in windows Desktop service manager

Recommend:
install the windows 7 service pack and updates. (this just has to have been fixed by now)

workaround would be to start cmd.exe as a admin
then turn off the service: Desktop window manager session manager, then config the service to be disabled
net.exe stop UxSms
sc.exe config uxsms start= disabled

here is info on what the service does:
http://en.wikipedia.org/wiki/Desktop_Window_Manager

Note: second crash dump was related to the same issue, most likely the same cause and solutions.
m
0
l
January 27, 2014 11:25:36 AM

johnbl said:
crash dump 1:

Windows 7 Kernel Version 7600 MP (6 procs) Free x64
Built by: 7600.17273.amd64fre.win7_gdr.130318-1532
System Uptime: 0 days 3:38:58.105

PROCESS_NAME: dwm.exe

BugCheck 50, {fffff900c2982d44, 0, fffff9600023d344, 0}
PAGE_FAULT_IN_NONPAGED_AREA (50)
Invalid system memory was referenced. This cannot be protected by try-except,
it must be protected by a Probe. Typically the address is just plain bad or it
is pointing at freed memory.
Arguments:
Arg1: fffff900c2982d44, memory referenced.
Arg2: 0000000000000000, value 0 = read operation, 1 = write operation.
Arg3: fffff9600023d344, If non-zero, the instruction address which referenced the bad memory
address.
Arg4: 0000000000000000, (reserved)

5: kd> k
Child-SP RetAddr Call Site
fffff880`08e97858 fffff800`02f4e694 nt!KeBugCheckEx
fffff880`08e97860 fffff800`02ecc96e nt! ?? ::FNODOBFM::`string'+0x41db7
fffff880`08e979c0 fffff960`0023d344 nt!KiPageFault+0x16e
fffff880`08e97b50 fffff960`00260749 win32k!GreSetRedirectionSurfaceSignaling+0x104
fffff880`08e97ba0 fffff800`02ecdad3 win32k!NtGdiHLSurfSetInformation+0x209
fffff880`08e97c20 000007fe`ff654efa nt!KiSystemServiceCopyEnd+0x13
00000000`0223f658 00000000`00000000 0x000007fe`ff654efa

This is a bugcheck in windows Desktop service manager

Recommend:
install the windows 7 service pack and updates. (this just has to have been fixed by now)

workaround would be to start cmd.exe as a admin
then turn off the service: Desktop window manager session manager, then config the service to be disabled
net.exe stop UxSms
sc.exe config uxsms start= disabled

here is info on what the service does:
http://en.wikipedia.org/wiki/Desktop_Window_Manager

Note: second crash dump was related to the same issue, most likely the same cause and solutions.


Thanks a lot my friend! I'm not completely stupid when it comes to computers, I've tried downloading the Windows Debugging tools myself but guess what? Every time I try to install, it says there has been a problem. I looked up a fix and it says the cause was because of a newer version of C++ 2010 already being installed. How lame. I don't really think that's the problem but whatever.

Btw, what do you mean by it has to have been fixed by now? On my part or theirs? My dad installed Windows 7 for me while I was at college because he put in my third harddrive (the other two were bad, no skitter, the other had TONS of bad sectors (no where near the normal amount)) and he installed the service packs and what not. I'm gonna try your work around. I will let you know if I have any BSOD's. These aren't CONSTANT but they do happen at random times and it's annoying.
m
0
l
a c 296 $ Windows 7
January 27, 2014 12:07:16 PM

-you have a old build of windows 7 without the service pack and updates. I think this would have been a bug in the old code that microsoft would have fixed a long time ago via a update.

metalhead0 said:
johnbl said:
crash dump 1:

Windows 7 Kernel Version 7600 MP (6 procs) Free x64
Built by: 7600.17273.amd64fre.win7_gdr.130318-1532
System Uptime: 0 days 3:38:58.105

PROCESS_NAME: dwm.exe

BugCheck 50, {fffff900c2982d44, 0, fffff9600023d344, 0}
PAGE_FAULT_IN_NONPAGED_AREA (50)
Invalid system memory was referenced. This cannot be protected by try-except,
it must be protected by a Probe. Typically the address is just plain bad or it
is pointing at freed memory.
Arguments:
Arg1: fffff900c2982d44, memory referenced.
Arg2: 0000000000000000, value 0 = read operation, 1 = write operation.
Arg3: fffff9600023d344, If non-zero, the instruction address which referenced the bad memory
address.
Arg4: 0000000000000000, (reserved)

5: kd> k
Child-SP RetAddr Call Site
fffff880`08e97858 fffff800`02f4e694 nt!KeBugCheckEx
fffff880`08e97860 fffff800`02ecc96e nt! ?? ::FNODOBFM::`string'+0x41db7
fffff880`08e979c0 fffff960`0023d344 nt!KiPageFault+0x16e
fffff880`08e97b50 fffff960`00260749 win32k!GreSetRedirectionSurfaceSignaling+0x104
fffff880`08e97ba0 fffff800`02ecdad3 win32k!NtGdiHLSurfSetInformation+0x209
fffff880`08e97c20 000007fe`ff654efa nt!KiSystemServiceCopyEnd+0x13
00000000`0223f658 00000000`00000000 0x000007fe`ff654efa

This is a bugcheck in windows Desktop service manager

Recommend:
install the windows 7 service pack and updates. (this just has to have been fixed by now)

workaround would be to start cmd.exe as a admin
then turn off the service: Desktop window manager session manager, then config the service to be disabled
net.exe stop UxSms
sc.exe config uxsms start= disabled

here is info on what the service does:
http://en.wikipedia.org/wiki/Desktop_Window_Manager

Note: second crash dump was related to the same issue, most likely the same cause and solutions.


Thanks a lot my friend! I'm not completely stupid when it comes to computers, I've tried downloading the Windows Debugging tools myself but guess what? Every time I try to install, it says there has been a problem. I looked up a fix and it says the cause was because of a newer version of C++ 2010 already being installed. How lame. I don't really think that's the problem but whatever.

Btw, what do you mean by it has to have been fixed by now? On my part or theirs? My dad installed Windows 7 for me while I was at college because he put in my third harddrive (the other two were bad, no skitter, the other had TONS of bad sectors (no where near the normal amount)) and he installed the service packs and what not. I'm gonna try your work around. I will let you know if I have any BSOD's. These aren't CONSTANT but they do happen at random times and it's annoying.


m
0
l
January 27, 2014 8:29:53 PM

johnbl said:
-you have a old build of windows 7 without the service pack and updates. I think this would have been a bug in the old code that microsoft would have fixed a long time ago via a update.


Honestly, not surprised because my dad is one of those guys that's like, "WELL IT WORKS." Then bitches because "I want the best" like seriously. Anyways, I'll look into updating and what not.

Also, I just checked out how many updates I have installed, I have 134. Are service packs included with the updates? I can't remember.
m
0
l