Sign in with
Sign up | Sign in
Your question

Blue screen of death win7 64bit ultimate

Last response: in Windows 7
Share
August 1, 2012 2:01:26 PM


Sir i have
intel motherboard and processor i7, 2600k, 3.40ghz,
4 gb ram, kingston ddr3
1gb ddr5 inno 3d, nvidia geforce gts 450 card
500gb and 1 tera HDk

i tried to sove this error fault in non page area some thing like tht in blue screen,
i tried to fix it up,
by: scndsk my all drives, any errors were fixed but no bad sectors found
running memtest, it was ok
and, changing slots of Ram, puting it in 1 ,thn in 2 and like that
but no gain no improvement

then i scaned alll my drives by bootscan and normal scan by new and updated avast antivirus 7

i tried reinsatalling windows many time and after completing windows start scaningg by avast

but my windows and sysytem
with in two days sarted showing blue screeen , and once it shows blue screenn fault in non page are, then it starts coming more frequently like more than thrice a day, and some time after 15 min gap.

kindly do tell me the solution....thanks i also treid updating everythng and pluged inalll devices again and propelty. thnks
when windows open the following error displayed. but in blue screen its wtitten Page Fault In Non Paged Area.



Problem signature:
Problem Event Name: BlueScreen
OS Version: 6.1.7600.2.0.0.256.1
Locale ID: 1033

Additional information about the problem:
BCCode: 50
BCP1: FFFFF8A009766000
BCP2: 0000000000000000
BCP3: FFFFF80003339079
BCP4: 0000000000000000
OS Version: 6_1_7600
Service Pack: 0_0
Product: 256_1

Files that help describe the problem:
C:\Windows\Minidump\080112-16957-01.dmp
C:\Users\Sayen\AppData\Local\Temp\WER-41948-0.sysdata.xml

Read our privacy statement online:
http://go.microsoft.com/fwlink/?linkid=104288&clcid=0x0...

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

More about : blue screen death win7 64bit ultimate

August 1, 2012 2:20:44 PM

Download WHOCRASHED HERE and report back.
m
0
l
August 1, 2012 3:15:06 PM

starting windown opening browser and opening ur mail and downloading file u mentioned...costs me 3 time crash bsods. :(  am so fed up... well i will be replying soon
m
0
l
Related resources
August 1, 2012 3:36:01 PM

What board do you have?

Also try running Windows memory diagnostics.
m
0
l
August 1, 2012 3:59:20 PM


--------------------------------------------------------------------------------
Welcome to WhoCrashed (HOME EDITION) v 3.06
--------------------------------------------------------------------------------

This program checks for drivers which have been crashing your computer. If your computer has displayed a blue screen of death, suddenly rebooted or shut down then this program will help you find the root cause and possibly a solution.

Whenever a computer suddenly reboots without displaying any notice or blue screen of death, the first thing that is often thought about is a hardware failure. In reality, on Windows most crashes are caused by malfunctioning device drivers and kernel modules. In case of a kernel error, many computers do not show a blue screen unless they are configured for this. Instead these systems suddenly reboot without any notice.

This program will analyze your crash dumps with the single click of a button. It will tell you what drivers are likely to be responsible for crashing your computer. If will report a conclusion which offers suggestions on how to proceed in any situation while the analysis report will display internet links which will help you further troubleshoot any detected problems.


To obtain technical support visit www.resplendence.com/support

Click here to check if you have the latest version or if an update is available.

Just click the Analyze button for a comprehensible report ...



--------------------------------------------------------------------------------
Home Edition Notice
--------------------------------------------------------------------------------

This version of WhoCrashed is free for use at home only. If you would like to use this software at work or in a commercial environment you should get the professional edition of WhoCrashed which also allows analysis of crashdumps on remote drives and computers on the network and offers a range of additional features.

Click here for more information on the professional edition.
Click here to buy the the professional edition of WhoCrashed.



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

computer name: SAYEN-PC
windows version: Windows 7 , 6.1, build: 7600
windows dir: C:\Windows
CPU: GenuineIntel Intel(R) Core(TM) i7-2600K CPU @ 3.40GHz Intel586, level: 6
8 logical processors, active mask: 255
RAM: 4271267840 total
VM: 2147352576, free: 1999609856



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

Crash dump directory: C:\Windows\Minidump

Crash dumps are enabled on your computer.


On Wed 8/1/2012 3:56:30 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\080112-28314-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x71F00)
Bugcheck code: 0x50 (0xFFFFF8A0095F6000, 0x0, 0xFFFFF80003349079, 0x0)
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 which cannot be identified at this time.


On Wed 8/1/2012 3:56:30 PM GMT your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: aswsnx.sys (aswSnx+0x22760)
Bugcheck code: 0x50 (0xFFFFF8A0095F6000, 0x0, 0xFFFFF80003349079, 0x0)
Error: PAGE_FAULT_IN_NONPAGED_AREA
file path: C:\Windows\system32\drivers\aswsnx.sys
product: avast! Antivirus System
company: AVAST Software
description: avast! Virtualization Driver
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.
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: aswsnx.sys (avast! Virtualization Driver, AVAST Software).
Google query: aswsnx.sys AVAST Software PAGE_FAULT_IN_NONPAGED_AREA




On Wed 8/1/2012 3:48:48 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\080112-26473-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x71F00)
Bugcheck code: 0x50 (0xFFFFF8A009566000, 0x0, 0xFFFFF80003399079, 0x0)
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 which cannot be identified at this time.


On Wed 8/1/2012 3:30:46 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\080112-16208-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x71F00)
Bugcheck code: 0x50 (0xFFFFF8A009566000, 0x0, 0xFFFFF8000334F079, 0x0)
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 which cannot be identified at this time.


On Wed 8/1/2012 3:23:23 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\080112-15927-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x71F00)
Bugcheck code: 0x50 (0xFFFFF8A0099F6000, 0x0, 0xFFFFF80003395079, 0x0)
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 which cannot be identified at this time.


On Wed 8/1/2012 3:09:42 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\080112-21013-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x71F00)
Bugcheck code: 0x50 (0xFFFFF8A0093F6000, 0x0, 0xFFFFF80003389079, 0x0)
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 which cannot be identified at this time.


On Wed 8/1/2012 3:02:30 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\080112-16801-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x71F00)
Bugcheck code: 0x50 (0xFFFFF8A00C166000, 0x0, 0xFFFFF80003347079, 0x0)
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 which cannot be identified at this time.


On Wed 8/1/2012 2:55:27 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\080112-16957-02.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x71F00)
Bugcheck code: 0x50 (0xFFFFF8A009366000, 0x0, 0xFFFFF80003339079, 0x0)
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 which cannot be identified at this time.


On Wed 8/1/2012 1:47:47 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\080112-21746-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x71F00)
Bugcheck code: 0x50 (0xFFFFF8A00A566000, 0x0, 0xFFFFF80003337079, 0x0)
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 which cannot be identified at this time.


On Wed 8/1/2012 1:40:36 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\080112-16957-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x71F00)
Bugcheck code: 0x50 (0xFFFFF8A009766000, 0x0, 0xFFFFF80003339079, 0x0)
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 which cannot be identified at this time.


On Wed 8/1/2012 1:33:38 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\080112-15771-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x71F00)
Bugcheck code: 0x50 (0xFFFFF8A009566000, 0x0, 0xFFFFF80003397079, 0x0)
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 which cannot be identified at this time.


On Wed 8/1/2012 8:20:02 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\080112-16411-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x71F00)
Bugcheck code: 0x50 (0xFFFFF8A00A566000, 0x0, 0xFFFFF8000333B079, 0x0)
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 which cannot be identified at this time.


On Wed 8/1/2012 8:13:11 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\080112-15943-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x71F00)
Bugcheck code: 0x50 (0xFFFFF8A0093F6000, 0x0, 0xFFFFF8000334A079, 0x0)
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 which cannot be identified at this time.


On Wed 8/1/2012 2:51:21 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\080112-25974-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x71F00)
Bugcheck code: 0x50 (0xFFFFF8A0049F6000, 0x0, 0xFFFFF8000334A079, 0x0)
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 which cannot be identified at this time.


On Wed 8/1/2012 2:43:26 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\080112-25521-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x71F00)
Bugcheck code: 0x50 (0xFFFFF8A0037F6000, 0x0, 0xFFFFF80003355079, 0x0)
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 which cannot be identified at this time.



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

27 crash dumps have been found and analyzed. Only 15 are included in this report. 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:

aswsnx.sys (avast! Virtualization Driver, AVAST Software)

If no updates for these drivers are available, try searching with Google on the names of these drivers in combination the errors that have been reported for these drivers and include the brand and model name of your computer as well in the query. This often yields interesting results from discussions from 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 actually 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.




m
0
l
August 1, 2012 4:05:19 PM

one thing i want to mention more is
once blue screen with same error occured
when i newly installed window and windwo 7 64 bit ultimate opens for first time with in few minutes it gve ths error bsod crash up occured. even i didnt installed any 2nd or thrd prty drivers. jz windows was installed. thnkx.
m
0
l
August 1, 2012 4:24:31 PM

memroy diagnostic test was ok...no error
m
0
l
August 1, 2012 5:18:53 PM

Uninstall Avast and use Microsoft Security Essentials.

32 bit: HERE

64 bit: HERE


Also update your version of Windows (Service Pack1)

Done doing this and download and install CCleaner HERE and clean up your system..

Further: have you disabled pagefile?
m
0
l
August 1, 2012 5:30:05 PM

iftikharchughtai said:
no need of re installing windows


Go into the Control Panel and run Windows update after doing the above listed things.
m
0
l
a b $ Windows 7
August 1, 2012 5:32:32 PM

The above poster wants to ensure you have SP1 installed for Win7. So if you hit windows update, you should get all the updates. (EDIT, beat to it :)  )

I have not used Windows memory diagnostics, but have used memtest86+ in the past.

May be worth trying that. Burn the ISO image to CD/DVD. Not just burning the file, windows should be able to open its own burning software when you open the ISO file. Memtest is best run over night if you can.

http://www.memtest.org/#downiso

It may not hurt to run a hard drive scan as well. HD Tune(the free non Pro) has a good HDD test(Error scan).

http://www.hdtune.com/download.html

You are not getting the standard BSOD's for driver issues at all. If the system is too unstable, test the drives on another system.
m
0
l
August 1, 2012 5:35:34 PM

i also had rtestd memtest u r sayngg same results.

@Russk1
i have already installed security essentials avast and this was working jointly
m
0
l
August 1, 2012 5:42:09 PM

can i do this all in safemode with networking,
updating and installing ccinstaller
because in normal mode bsod will crash system
m
0
l
August 1, 2012 5:46:00 PM

iftikharchughtai said:
i also had rtestd memtest u r sayngg same results.

@Russk1
i have already installed security essentials avast and this was working jointly


Whocrashed indicated "Avast" as the culprit for the crashes. Toss "Avast" and keep Security Essentials...two AV's with "real time"
protection is a recipe for disaster.

Quote:
--------------------------------------------------------------------------------
Conclusion
--------------------------------------------------------------------------------

27 crash dumps have been found and analyzed. Only 15 are included in this report. 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:

aswsnx.sys (avast! Virtualization Driver, AVAST Software)

m
0
l
!