Windows 7 Forums
Welcome to Windows 7 Forums. Our forum is dedicated to helping you find support and solutions for any problems regarding your Windows 7 PC be it Dell, HP, Acer, Asus or a custom build. We also provide an extensive Windows 7 tutorial section that covers a wide range of tips and tricks.



Windows 7: BSOD playing Heroes of Newerth error: Page fault in nonpaged area

08 Feb 2012   #1

Microsoft Windows 7 Home Premium 64-bit 7601 Multiprocessor Free Service Pack 1
 
 
BSOD playing Heroes of Newerth error: Page fault in nonpaged area

Hi there,

I just joined this forum (like many others) to get some expert help. Thanks in advance for taking your time as it is only with your generosity that we get solutions.

I am running a week old computer (self-built) with a week old Windows 7 Home Premium 64-bit Retail version (initial installation). I have attached the BSOD information required in the instructions given...

I got the BSOD error "Page fault in non paged area"
And the error reads as such:
Problem signature:
Problem Event Name: BlueScreen
OS Version: 6.1.7601.2.1.0.768.3
Locale ID: 1033

Additional information about the problem:
BCCode: 50
BCP1: FFFFFA8308CB5DA8
BCP2: 0000000000000000
BCP3: FFFFF80002E5442B
BCP4: 0000000000000005
OS Version: 6_1_7601
Service Pack: 1_0
Product: 768_1

Files that help describe the problem:
C:\Windows\Minidump\020812-10639-01.dmp
C:\Users\Eddie\AppData\Local\Temp\WER-19796-0.sysdata.xml

Read our privacy statement online:
Windows 7 Privacy Statement - Microsoft Windows

If the online privacy statement is not available, please read our privacy statement offline:
C:\Windows\system32\en-US\erofflps.txt

I appreciate any help you may give. Thanks again.

Cheers,
Eddie

My System SpecsSystem Spec
08 Feb 2012   #2
JMH

Win 7 Ultimate 64-bit. SP1.
 
 

* Kaspersky is a frequent cause of BSOD's.
I would remove and replace it with Microsoft Security Essentials AT LEAST TO TEST.

http://support.kaspersky.com/downloa...vremover10.zip

Microsoft Security Essentials - Free Antivirus for Windows


* Your crashes were caused by memory corruption/exception (probably a driver).
Please run these two tests to verify your memory and find which driver is causing the problem.

If you are overclocking anything reset to default before running these tests.
In other words STOP!!!

If you have raid > update its Driver.


Memtest.
Quote:
*Download a copy of Memtest86 and burn the ISO to a CD using Iso Recorder or another ISO burning program. Memtest86+ - Advanced Memory Diagnostic Tool

*Boot from the CD, and leave it running for at least 5 or 6 passes.

Just remember, any time Memtest reports errors, it can be either bad RAM or a bad motherboard slot.

Test the sticks individually, and if you find a good one, test it in all slots.

Any errors are indicative of a memory problem.

If a known good stick fails in a motherboard slot it is probably the slot.

RAM - Test with Memtest86+



Driver verifier

Quote:
Using Driver Verifier is an iffy proposition. Most times it'll crash and it'll tell you what the driver is. But sometimes it'll crash and won't tell you the driver. Other times it'll crash before you can log in to Windows. If you can't get to Safe Mode, then you'll have to resort to offline editing of the registry to disable Driver Verifier.

So, I'd suggest that you first backup your stuff and then make sure you've got access to another computer so you can contact us if problems arise. Then make a System Restore point (so you can restore the system using the Vista/Windows 7 Startup Repair feature).

Then, here's the procedure:
- Go to Start and type in "verifier" (without the quotes) and press Enter
- Select "Create custom settings (for code developers)" and click "Next"
- Select "Select individual settings from a full list" and click "Next"
- Select everything EXCEPT FOR "Special Pool", "Force Pending I/O Requests" and "Low Resource Simulation" and click "Next"
- Select "Select driver names from a list" and click "Next"
Then select all drivers NOT provided by Microsoft and click "Next"
- Select "Finish" on the next page.

Reboot the system and wait for it to crash to the Blue Screen.
Continue to use your system normally, and if you know what causes the crash, do that repeatedly.
The objective here is to get the system to crash because Driver Verifier is stressing the drivers out.
If it doesn't crash for you, then let it run for at least 36 hours of continuous operation.

Reboot into Windows (after the crash) and turn off Driver Verifier by going back in and selecting "Delete existing settings" on the first page, then locate and zip up the memory dump file and upload it with your next post.

If you can't get into Windows because it crashes too soon, try it in Safe Mode.
If you can't get into Safe Mode, try using System Restore from your installation DVD to set the system back to the previous restore point that you created.
Using Driver Verifier to identify issues with Windows drivers for advanced users
My System SpecsSystem Spec
27 Feb 2012   #3

Microsoft Windows 7 Home Premium 64-bit 7601 Multiprocessor Free Service Pack 1
 
 

Hey, thanks so much for your reply. I did the memtest...no dice (no errors).
Also took out the Kaspersky...
Do you have any other suggestions? Also, is there any other information that I can provide that may lead on to something? Thanks so much.
My System SpecsSystem Spec
.


27 Feb 2012   #4

Windows 7 Home Premium 64 Bit
 
 

Please provide the latest crash reports. They may reveal new information as to what is causing the crashes.
My System SpecsSystem Spec
27 Feb 2012   #5

Microsoft Windows 7 Home Premium 64-bit 7601 Multiprocessor Free Service Pack 1
 
 

Hey, here is the latest zip of all the information. Thanks again.
My System SpecsSystem Spec
27 Feb 2012   #6

Windows 7 Home Premium 64 Bit
 
 

Problem devices:
Code:
Not Available	USB\VID_0CF3&PID_3000\6&DF2EE03&0&7	The drivers for this device are not installed.
Ethernet Controller	PCI\VEN_8086&DEV_1503&SUBSYS_849C1043&REV_05\3&11583659&0&C8	The drivers for this device are not installed.


antivirus software:
Code:
avp.exe	c:\program files (x86)\kaspersky lab\kaspersky internet security 2012\avp.exe	1900	8	200	1380	2/27/2012 7:55 AM	12.0.0.374	197.55 KB (202,296 bytes)	4/25/2011 12:15 AM
avp.exe	c:\program files (x86)\kaspersky lab\kaspersky internet security 2012\avp.exe	2064	8	200	1380	2/27/2012 5:48 PM	12.0.0.374	197.55 KB (202,296 bytes)	4/25/2011 12:15 AM
klwtblfs.exe	c:\program files (x86)\kaspersky lab\kaspersky internet security 2012\x64\klwtblfs.exe	5580	8	200	1380	2/27/2012 5:48 PM	12.0.0.374	168.39 KB (172,432 bytes)	4/25/2011 12:14 AM


Code:
  1. Microsoft (R) Windows Debugger Version 6.12.0002.633 AMD64 Copyright (c) Microsoft Corporation. All rights reserved. Loading Dump File [D:\Kingston\BSODDmpFiles\pugmastaflex\Windows_NT6_BSOD_jcgriff2\022612-10062-01.dmp] Mini Kernel Dump File: Only registers and stack trace are available Symbol search path is: SRV*c:\symbols*http://msdl.microsoft.com/download/symbols Executable search path is: Windows 7 Kernel Version 7601 (Service Pack 1) MP (8 procs) Free x64 Product: WinNt, suite: TerminalServer SingleUserTS Personal Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506 Machine Name: Kernel base = 0xfffff800`02e4d000 PsLoadedModuleList = 0xfffff800`03092670 Debug session time: Sun Feb 26 21:25:42.284 2012 (UTC - 7:00) System Uptime: 0 days 6:11:28.111 Loading Kernel Symbols ............................................................... ................................................................ ........................... Loading User Symbols Loading unloaded module list ..... ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* Use !analyze -v to get detailed debugging information. BugCheck 1A, {5003, fffff70001080000, 4e9e, 4ea000009d45} Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+46f0d ) Followup: MachineOwner --------- 4: kd> !analyze -v ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* MEMORY_MANAGEMENT (1a) # Any other values for parameter 1 must be individually examined. Arguments: Arg1: 0000000000005003, The subtype of the bugcheck. Arg2: fffff70001080000 Arg3: 0000000000004e9e Arg4: 00004ea000009d45 Debugging Details: ------------------ BUGCHECK_STR: 0x1a_5003 CUSTOMER_CRASH_COUNT: 1 DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT PROCESS_NAME: avp.exe CURRENT_IRQL: 0 TRAP_FRAME: fffff8800483a580 -- (.trap 0xfffff8800483a580) NOTE: The trap frame does not contain all registers. Some register values may be zeroed or incorrect. rax=0000000000000000 rbx=0000000000000000 rcx=000000000f545000 rdx=000000000f550000 rsi=0000000000000000 rdi=0000000000000000 rip=fffff800031e05c6 rsp=fffff8800483a710 rbp=fffffa800eb634c0 r8=0000000000000000 r9=000000000f540000 r10=0000000000010000 r11=0000000000000006 r12=0000000000000000 r13=0000000000000000 r14=0000000000000000 r15=0000000000000000 iopl=0 nv up ei ng nz na po cy nt!ProbeForWrite+0x36: fffff800`031e05c6 0fb601 movzx eax,byte ptr [rcx] ds:00000000`0f545000=?? Resetting default scope LAST_CONTROL_TRANSFER: from fffff80002e5d74c to fffff80002ec9c40 STACK_TEXT: fffff880`0483a418 fffff800`02e5d74c : 00000000`0000001a 00000000`00005003 fffff700`01080000 00000000`00004e9e : nt!KeBugCheckEx fffff880`0483a420 fffff800`02ec7d6e : 00000000`00000000 00000000`0f545000 fffffa80`0e649700 00000000`00010000 : nt! ?? ::FNODOBFM::`string'+0x46f0d fffff880`0483a580 fffff800`031e05c6 : 00000000`0f530001 fffffa80`0cf8f870 fffff880`0483a808 00000000`00010000 : nt!KiPageFault+0x16e fffff880`0483a710 fffff880`0109c937 : 00000000`00000000 fffffa80`0eb634c0 00000000`00000203 fffff800`02ee94d3 : nt!ProbeForWrite+0x36 fffff880`0483a740 fffff880`010c289c : fffff880`0483a840 00000000`0f540001 fffffa80`1037e470 00000000`00000024 : fltmgr!FltpFilterMessage+0x77 fffff880`0483a790 fffff880`010c6ca2 : fffffa80`1037e470 00000000`1200e4e0 00000000`0f540000 fffff800`02ef27d6 : fltmgr!FltpMsgDeviceControl+0xdc fffff880`0483a7f0 fffff880`0109b99f : fffffa80`0cadb520 fffff880`0483ab60 fffffa80`0eb634c0 00000000`00000000 : fltmgr!FltpMsgDispatch+0xd2 fffff880`0483a870 fffff800`031e4a97 : fffffa80`0eb634c0 fffff880`0483ab60 fffffa80`1037e588 fffffa80`1037e470 : fltmgr! ?? ::FNODOBFM::`string'+0x2e80 fffff880`0483a8d0 fffff800`031e52f6 : 00000000`00000000 00000000`00000000 00000000`00000001 00000000`00000000 : nt!IopXxxControlFile+0x607 fffff880`0483aa00 fffff800`02ec8ed3 : ffffffff`ffffffff 00000000`1172e7f8 00000000`00000010 00000000`1172e7f0 : nt!NtDeviceIoControlFile+0x56 fffff880`0483aa70 00000000`74832e09 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13 00000000`1172f0f8 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x74832e09 STACK_COMMAND: kb FOLLOWUP_IP: nt! ?? ::FNODOBFM::`string'+46f0d fffff800`02e5d74c cc int 3 SYMBOL_STACK_INDEX: 1 SYMBOL_NAME: nt! ?? ::FNODOBFM::`string'+46f0d FOLLOWUP_NAME: MachineOwner MODULE_NAME: nt IMAGE_NAME: ntkrnlmp.exe DEBUG_FLR_IMAGE_TIMESTAMP: 4e02aaa3 FAILURE_BUCKET_ID: X64_0x1a_5003_nt!_??_::FNODOBFM::_string_+46f0d BUCKET_ID: X64_0x1a_5003_nt!_??_::FNODOBFM::_string_+46f0d Followup: MachineOwner ---------
  2. Loading Dump File [D:\Kingston\BSODDmpFiles\pugmastaflex\Windows_NT6_BSOD_jcgriff2\022512-9484-01.dmp] Mini Kernel Dump File: Only registers and stack trace are available Symbol search path is: SRV*c:\symbols*http://msdl.microsoft.com/download/symbols Executable search path is: Windows 7 Kernel Version 7601 (Service Pack 1) MP (8 procs) Free x64 Product: WinNt, suite: TerminalServer SingleUserTS Personal Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506 Machine Name: Kernel base = 0xfffff800`02e61000 PsLoadedModuleList = 0xfffff800`030a6670 Debug session time: Fri Feb 24 23:03:53.483 2012 (UTC - 7:00) System Uptime: 0 days 7:16:08.311 Loading Kernel Symbols ............................................................... ................................................................ ............................ Loading User Symbols Loading unloaded module list ..... ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* Use !analyze -v to get detailed debugging information. BugCheck 50, {fffff900c00df4b8, 0, fffff9600063dcd0, 0} Unable to load image \SystemRoot\System32\win32k.sys, Win32 error 0n2 *** WARNING: Unable to verify timestamp for win32k.sys *** ERROR: Module load completed but symbols could not be loaded for win32k.sys Could not read faulting driver name Probably caused by : cdd.dll ( cdd!CddBitmapHw::Release+b0 ) Followup: MachineOwner --------- 2: kd> !analyze -v ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* 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: fffff900c00df4b8, memory referenced. Arg2: 0000000000000000, value 0 = read operation, 1 = write operation. Arg3: fffff9600063dcd0, If non-zero, the instruction address which referenced the bad memory address. Arg4: 0000000000000000, (reserved) Debugging Details: ------------------ Could not read faulting driver name READ_ADDRESS: GetPointerFromAddress: unable to read from fffff80003110100 fffff900c00df4b8 FAULTING_IP: cdd!CddBitmapHw::Release+b0 fffff960`0063dcd0 488b9898140000 mov rbx,qword ptr [rax+1498h] MM_INTERNAL_CODE: 0 CUSTOMER_CRASH_COUNT: 1 DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT BUGCHECK_STR: 0x50 PROCESS_NAME: dwm.exe CURRENT_IRQL: 0 TRAP_FRAME: fffff880097a2640 -- (.trap 0xfffff880097a2640) NOTE: The trap frame does not contain all registers. Some register values may be zeroed or incorrect. rax=fffff900c00de020 rbx=0000000000000000 rcx=fffff900c4095030 rdx=fffffa80102c0b60 rsi=0000000000000000 rdi=0000000000000000 rip=fffff9600063dcd0 rsp=fffff880097a27d0 rbp=0000000000000001 r8=000000000000000b r9=fffff96000351c38 r10=0000000000000000 r11=fffff880097a28d0 r12=0000000000000000 r13=0000000000000000 r14=0000000000000000 r15=0000000000000000 iopl=0 nv up ei ng nz na pe nc cdd!CddBitmapHw::Release+0xb0: fffff960`0063dcd0 488b9898140000 mov rbx,qword ptr [rax+1498h] ds:0b60:fffff900`c00df4b8=???????????????? Resetting default scope LAST_CONTROL_TRANSFER: from fffff80002e899fc to fffff80002eddc40 STACK_TEXT: fffff880`097a24d8 fffff800`02e899fc : 00000000`00000050 fffff900`c00df4b8 00000000`00000000 fffff880`097a2640 : nt!KeBugCheckEx fffff880`097a24e0 fffff800`02edbd6e : 00000000`00000000 fffff900`c00df4b8 00000000`00000000 fffff900`c00c0010 : nt! ?? ::FNODOBFM::`string'+0x4611f fffff880`097a2640 fffff960`0063dcd0 : 00000000`00000000 fffff960`0022a810 00000000`00000000 00000000`00000000 : nt!KiPageFault+0x16e fffff880`097a27d0 fffff960`001664a0 : fffff900`c00c0010 fffff900`c00c0010 00000000`00000001 fffff900`c40b2670 : cdd!CddBitmapHw::Release+0xb0 fffff880`097a2810 fffff900`c00c0010 : fffff900`c00c0010 00000000`00000001 fffff900`c40b2670 00000000`00000001 : win32k+0xc64a0 fffff880`097a2818 fffff900`c00c0010 : 00000000`00000001 fffff900`c40b2670 00000000`00000001 00000000`03cb82d0 : 0xfffff900`c00c0010 fffff880`097a2820 00000000`00000001 : fffff900`c40b2670 00000000`00000001 00000000`03cb82d0 00000000`00000000 : 0xfffff900`c00c0010 fffff880`097a2828 fffff900`c40b2670 : 00000000`00000001 00000000`03cb82d0 00000000`00000000 00000000`00000000 : 0x1 fffff880`097a2830 00000000`00000001 : 00000000`03cb82d0 00000000`00000000 00000000`00000000 00000000`00000000 : 0xfffff900`c40b2670 fffff880`097a2838 00000000`03cb82d0 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x1 fffff880`097a2840 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x3cb82d0 STACK_COMMAND: kb FOLLOWUP_IP: cdd!CddBitmapHw::Release+b0 fffff960`0063dcd0 488b9898140000 mov rbx,qword ptr [rax+1498h] SYMBOL_STACK_INDEX: 3 SYMBOL_NAME: cdd!CddBitmapHw::Release+b0 FOLLOWUP_NAME: MachineOwner MODULE_NAME: cdd IMAGE_NAME: cdd.dll DEBUG_FLR_IMAGE_TIMESTAMP: 4ce7c546 FAILURE_BUCKET_ID: X64_0x50_cdd!CddBitmapHw::Release+b0 BUCKET_ID: X64_0x50_cdd!CddBitmapHw::Release+b0 Followup: MachineOwner ---------
  3. Loading Dump File [D:\Kingston\BSODDmpFiles\pugmastaflex\Windows_NT6_BSOD_jcgriff2\022012-9921-01.dmp] Mini Kernel Dump File: Only registers and stack trace are available Symbol search path is: SRV*c:\symbols*http://msdl.microsoft.com/download/symbols Executable search path is: Windows 7 Kernel Version 7601 (Service Pack 1) MP (8 procs) Free x64 Product: WinNt, suite: TerminalServer SingleUserTS Personal Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506 Machine Name: Kernel base = 0xfffff800`02e55000 PsLoadedModuleList = 0xfffff800`0309a670 Debug session time: Mon Feb 20 09:33:27.056 2012 (UTC - 7:00) System Uptime: 0 days 0:15:57.884 Loading Kernel Symbols ............................................................... ................................................................ ........................... Loading User Symbols Loading unloaded module list ..... ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* Use !analyze -v to get detailed debugging information. BugCheck 1A, {41790, fffffa800846bf40, ffff, 0} Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+36024 ) Followup: MachineOwner --------- 7: kd> !analyze -v ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* MEMORY_MANAGEMENT (1a) # Any other values for parameter 1 must be individually examined. Arguments: Arg1: 0000000000041790, The subtype of the bugcheck. Arg2: fffffa800846bf40 Arg3: 000000000000ffff Arg4: 0000000000000000 Debugging Details: ------------------ BUGCHECK_STR: 0x1a_41790 CUSTOMER_CRASH_COUNT: 1 DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT PROCESS_NAME: kldw.exe CURRENT_IRQL: 0 LAST_CONTROL_TRANSFER: from fffff80002f41150 to fffff80002ed1c40 STACK_TEXT: fffff880`099046e8 fffff800`02f41150 : 00000000`0000001a 00000000`00041790 fffffa80`0846bf40 00000000`0000ffff : nt!KeBugCheckEx fffff880`099046f0 fffff800`02f05569 : fffffa80`00000000 00000000`0161cfff fffffa80`00000000 fffff880`00961000 : nt! ?? ::FNODOBFM::`string'+0x36024 fffff880`099048b0 fffff800`031e9221 : fffffa80`0f7b5c10 00000000`00000000 fffffa80`10395f90 fffffa80`10395f90 : nt!MiRemoveMappedView+0xd9 fffff880`099049d0 fffff800`031e9623 : 0000007f`00000000 00000000`01530000 fffffa80`00000001 00000000`0008ec01 : nt!MiUnmapViewOfSection+0x1b1 fffff880`09904a90 fffff800`02ed0ed3 : 00000000`00000000 00000000`01530000 fffffa80`0f858540 00000000`00020238 : nt!NtUnmapViewOfSection+0x5f fffff880`09904ae0 00000000`773615ba : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13 00000000`0008e318 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x773615ba STACK_COMMAND: kb FOLLOWUP_IP: nt! ?? ::FNODOBFM::`string'+36024 fffff800`02f41150 cc int 3 SYMBOL_STACK_INDEX: 1 SYMBOL_NAME: nt! ?? ::FNODOBFM::`string'+36024 FOLLOWUP_NAME: MachineOwner MODULE_NAME: nt IMAGE_NAME: ntkrnlmp.exe DEBUG_FLR_IMAGE_TIMESTAMP: 4e02aaa3 FAILURE_BUCKET_ID: X64_0x1a_41790_nt!_??_::FNODOBFM::_string_+36024 BUCKET_ID: X64_0x1a_41790_nt!_??_::FNODOBFM::_string_+36024 Followup: MachineOwner ---------
  1. Caused by avp.exe: Kaspersky
  2. Possible causes are Memory problems... Graphics card memory problems... BIOS... Corrupted hard disk file system... Corrupted System Files... Missing Windows Updates... Drivers...
  3. Caused by kldw.exe: Kaspersky

You may need to run Memtest86+ again (we'll consider it after all Kaspersky remnants are gone), though I think it is fairly likely the crashes were caused by Kaspersky. Did you use the removal tool for Kaspersky lab products to remove the product?
My System SpecsSystem Spec
27 Feb 2012   #7

Microsoft Windows 7 Home Premium 64-bit 7601 Multiprocessor Free Service Pack 1
 
 

I just used the uninstall button. I will definitely get back to you tomorrow after using the remove kit. Do you have any suggestions for a preferred Anti-Virus (I do not mind the subscription ones) softwares that do not cause problems?

Thanks
My System SpecsSystem Spec
27 Feb 2012   #8

Windows 7 Home Premium 64 Bit
 
 

I use the Good and Free system security combination. I have not had any problems with it. I also use safe browsing techniques to avoid questionable websites, although WOT included in that security setup helps with this, as well.


Do you still need troubleshooting?
My System SpecsSystem Spec
19 Mar 2012   #9

Microsoft Windows 7 Home Premium 64-bit 7601 Multiprocessor Free Service Pack 1
 
 
Still BSODs

Actually, yes, I use that anti-virus now, Kaspersky is 100% gone...still getting BSODs...I will attach the zip files of the crashlogs when I get home. Thanks for following up. I feel really grateful for all the help.
My System SpecsSystem Spec
19 Mar 2012   #10

Windows 7 Home Premium 64 Bit
 
 

No problem. I'll keep an eye out for the crash reports.
My System SpecsSystem Spec
Reply

 BSOD playing Heroes of Newerth error: Page fault in nonpaged area





Thread Tools




Our Sites

Site Links

About Us

Find Us

Windows 7 Forums is an independent web site and has not been authorized, sponsored, or otherwise approved by Microsoft Corporation. "Windows 7" and related materials are trademarks of Microsoft Corp.

Designer Media Ltd

All times are GMT -5. The time now is 10:48 AM.
Twitter Facebook Google+



Windows 7 Forums

Seven Forums Android App Seven Forums IOS App
  

1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33