Solved Bsod page_fault_in_nonpaged_area

[easwar2641993]

That's right, it seems like this is a software issue. Have you run the Upgrade Advisor?

Free Download PC Upgrade Advisor Windows 7 Hardware Programs Issues

Yes..I ran it..all are compatible and the only issue reported there is in 64bit,you need to custom install the windows or some thing like that.For graphics card,it is written that there is a need to install Windows Home Premium or something like that.
Today when I enabled verifier,I got bsod with code 0xc9 and parameter 1 was 0x0c.Because I reformatted the system without uploading dump files and I am sorry.
I wish to know what is PCI bridge in System Devices in Device Manager.And Intel (R) 4 Series Chipset PCI Express Root Port -2E31.Because both are sharing Memory address and IRQ respectively.I am not able to disable or update PCI Bridge driver and it is grayed out.But if I disable that PCI -E Root Port,the graphics driver wont work and system works in a resolution similar to that of in a safe mode.Any ideas?
Looks like a driver/software issue.

 

[DeanP]

What software do you install on Windows 7?

 

[easwar2641993]

That's right, it seems like this is a software issue. Have you run the Upgrade Advisor?

Free Download PC Upgrade Advisor Windows 7 Hardware Programs Issues

A new type of BSOD in Windows 7 with verifier enabled.
DRIVER_IRQ_NOT_LESS_NOT_EQUAL
0xd1

 

[Jonathan_King]

Thinking about this, it seems as if the motherboard is actually the cause. You are getting a strange hybrid of symptoms common to hardware and software causes, and based on what you said about that PCIe driver giving BSODs under driver verifier, I wonder if that is the cause.

Try installing updated chipset drivers: Intel® Driver Update Utility

...Summary of the dumps:

[font=lucida console]
Built by: 7601.17514.x86fre.win7sp1_rtm.101119-1850
Debug session time: Mon Feb 28 07:00:27.336 2011 (UTC - 5:00)
System Uptime: 0 days 0:00:06.130
Probably caused by : ntkrpamp.exe ( nt!KiTrap0E+2cf )
PROCESS_NAME:  System
BUGCHECK_STR:  DISABLED_INTERRUPT_FAULT
DEFAULT_BUCKET_ID:  VERIFIER_ENABLED_VISTA_MINIDUMP
FAILURE_BUCKET_ID:  DISABLED_INTERRUPT_FAULT_VRF_CODE_AV_BAD_IP_nt!KiTrap0E+2cf
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7601.17514.x86fre.win7sp1_rtm.101119-1850
Debug session time: Mon Feb 28 04:43:04.145 2011 (UTC - 5:00)
System Uptime: 0 days 0:00:07.940
*** WARNING: Unable to verify timestamp for nvlddmkm.sys
*** ERROR: Module load completed but symbols could not be loaded for nvlddmkm.sys
BUGCHECK_STR:  0xc9_c
DEFAULT_BUCKET_ID:  VERIFIER_ENABLED_VISTA_MINIDUMP
PROCESS_NAME:  System
FAILURE_BUCKET_ID:  0xc9_c_VRF_dxgkrnl!DpiQueryBusInterface+78
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7601.17514.x86fre.win7sp1_rtm.101119-1850
Debug session time: Mon Feb 28 04:31:47.938 2011 (UTC - 5:00)
System Uptime: 0 days 0:06:35.733
*** WARNING: Unable to verify timestamp for nvlddmkm.sys
*** ERROR: Module load completed but symbols could not be loaded for nvlddmkm.sys
Probably caused by : pci.sys ( pci!PciStallForPowerChange+78 )
DEFAULT_BUCKET_ID:  NULL_CLASS_PTR_DEREFERENCE
PROCESS_NAME:  System
BUGCHECK_STR:  0x7E
FAILURE_BUCKET_ID:  0x7E_VRF_pci!PciStallForPowerChange+78
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7601.17514.x86fre.win7sp1_rtm.101119-1850
Debug session time: Mon Feb 28 04:20:37.406 2011 (UTC - 5:00)
System Uptime: 0 days 0:00:12.091
BUGCHECK_STR:  0xc9_c
DEFAULT_BUCKET_ID:  VERIFIER_ENABLED_VISTA_MINIDUMP
PROCESS_NAME:  System
FAILURE_BUCKET_ID:  0xc9_c_VRF_nt!IovpCompleteRequest+3c
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7601.17514.x86fre.win7sp1_rtm.101119-1850
Debug session time: Mon Feb 28 04:10:23.244 2011 (UTC - 5:00)
System Uptime: 0 days 0:00:05.038
BUGCHECK_STR:  0xc9_c
DEFAULT_BUCKET_ID:  VERIFIER_ENABLED_VISTA_MINIDUMP
PROCESS_NAME:  System
FAILURE_BUCKET_ID:  0xc9_c_VRF_nt!IovpCompleteRequest+3c
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7601.17514.x86fre.win7sp1_rtm.101119-1850
Debug session time: Mon Feb 28 04:00:31.164 2011 (UTC - 5:00)
System Uptime: 0 days 0:00:05.959
BUGCHECK_STR:  0xc9_c
DEFAULT_BUCKET_ID:  VERIFIER_ENABLED_VISTA_MINIDUMP
PROCESS_NAME:  System
FAILURE_BUCKET_ID:  0xc9_c_VRF_nt!IovpCompleteRequest+3c
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
  
[/font]

 

[easwar2641993]

Thinking about this, it seems as if the motherboard is actually the cause. You are getting a strange hybrid of symptoms common to hardware and software causes, and based on what you said about that PCIe driver giving BSODs under driver verifier, I wonder if that is the cause.

Try installing updated chipset drivers: Intel® Driver Update Utility

...Summary of the dumps:

[FONT=lucida console]
Built by: 7601.17514.x86fre.win7sp1_rtm.101119-1850
Debug session time: Mon Feb 28 07:00:27.336 2011 (UTC - 5:00)
System Uptime: 0 days 0:00:06.130
Probably caused by : ntkrpamp.exe ( nt!KiTrap0E+2cf )
PROCESS_NAME:  System
BUGCHECK_STR:  DISABLED_INTERRUPT_FAULT
DEFAULT_BUCKET_ID:  VERIFIER_ENABLED_VISTA_MINIDUMP
FAILURE_BUCKET_ID:  DISABLED_INTERRUPT_FAULT_VRF_CODE_AV_BAD_IP_nt!KiTrap0E+2cf
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7601.17514.x86fre.win7sp1_rtm.101119-1850
Debug session time: Mon Feb 28 04:43:04.145 2011 (UTC - 5:00)
System Uptime: 0 days 0:00:07.940
*** WARNING: Unable to verify timestamp for nvlddmkm.sys
*** ERROR: Module load completed but symbols could not be loaded for nvlddmkm.sys
BUGCHECK_STR:  0xc9_c
DEFAULT_BUCKET_ID:  VERIFIER_ENABLED_VISTA_MINIDUMP
PROCESS_NAME:  System
FAILURE_BUCKET_ID:  0xc9_c_VRF_dxgkrnl!DpiQueryBusInterface+78
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7601.17514.x86fre.win7sp1_rtm.101119-1850
Debug session time: Mon Feb 28 04:31:47.938 2011 (UTC - 5:00)
System Uptime: 0 days 0:06:35.733
*** WARNING: Unable to verify timestamp for nvlddmkm.sys
*** ERROR: Module load completed but symbols could not be loaded for nvlddmkm.sys
Probably caused by : pci.sys ( pci!PciStallForPowerChange+78 )
DEFAULT_BUCKET_ID:  NULL_CLASS_PTR_DEREFERENCE
PROCESS_NAME:  System
BUGCHECK_STR:  0x7E
FAILURE_BUCKET_ID:  0x7E_VRF_pci!PciStallForPowerChange+78
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7601.17514.x86fre.win7sp1_rtm.101119-1850
Debug session time: Mon Feb 28 04:20:37.406 2011 (UTC - 5:00)
System Uptime: 0 days 0:00:12.091
BUGCHECK_STR:  0xc9_c
DEFAULT_BUCKET_ID:  VERIFIER_ENABLED_VISTA_MINIDUMP
PROCESS_NAME:  System
FAILURE_BUCKET_ID:  0xc9_c_VRF_nt!IovpCompleteRequest+3c
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7601.17514.x86fre.win7sp1_rtm.101119-1850
Debug session time: Mon Feb 28 04:10:23.244 2011 (UTC - 5:00)
System Uptime: 0 days 0:00:05.038
BUGCHECK_STR:  0xc9_c
DEFAULT_BUCKET_ID:  VERIFIER_ENABLED_VISTA_MINIDUMP
PROCESS_NAME:  System
FAILURE_BUCKET_ID:  0xc9_c_VRF_nt!IovpCompleteRequest+3c
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7601.17514.x86fre.win7sp1_rtm.101119-1850
Debug session time: Mon Feb 28 04:00:31.164 2011 (UTC - 5:00)
System Uptime: 0 days 0:00:05.959
BUGCHECK_STR:  0xc9_c
DEFAULT_BUCKET_ID:  VERIFIER_ENABLED_VISTA_MINIDUMP
PROCESS_NAME:  System
FAILURE_BUCKET_ID:  0xc9_c_VRF_nt!IovpCompleteRequest+3c
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
  
[/FONT]

I have installed the very latest version of chipset utility.When I contacted Intel for support for this they told that it must be the issue either with Windows 7 or DG41WV boards with GT 240 Graphics cards.They haven't tested the board with this card.But the main point is it is not showing any BSODs under verifier in Windows Vista and XP..And in Windows 7,the irq of that PCI-E is shown as 0xFFFFFFFE(-2), and while in windows Vista it is shown as the same but instead of -2,it is shown a long positive number.In XP,the irq is same as of the graphics card 16.Also in support of this,Intel told it should be issue of Windows 7.I have contacted Microsoft 2-3 weeks ago.Till now,no reply.

 

[usasma]

First, please excuse my questions as I've just come to this topic - and I have some serious eye problems so I've only been able to glance over all 105 posts.

You have instructed Driver Verifier to check all non-Microsoft drivers
Yet Microsoft drivers are showing up as the cause in the Driver Verifier enabled memory dumps.

This, to me, means that the 3rd party drivers aren't at fault.
If that's the case, the only things left are: Windows, compatibility issues, or hardware

Now, a discussion about Driver Verifier (DV).

DV is used to stress drivers and (hopefully) cause them to crash and spit out a BSOD error message that names the faulty driver. But driver developers don't have to follow Microsoft's rules for drivers development - so we can't assume that all drivers will react equally to DV.

In short, what if you have a driver that's not quite up to Microsoft's standards - but it works OK under normal circumstances? In that case, the driver can crash under Driver Verifier, but won't necessarily crash under normal usage.

So, use Driver Verifier if you're having crashes. Once you've finished with the crash diagnostics - turn Driver Verifier off.

I don't think that Windows is the issue.
But there are issues with Win7 that aren't present with the other OS's (in particular, I've seen RAM issues in the Asus P5 series of boards that can only be explained by that).

So, we're looking at how your system handles RAM
We're looking at your video card and it's drivers
We're looking at your power supply - and how well it provides power to the video card
and we're looking at the mobo/CPU in case of issues there.

FIRST
To test RAM, please run these two free tests according to the instructions:

Memory Diagnostics (read the instructions at the link)
Please run the test for a minimum of 7 passes.
and
Prime95 Setup:
- extract the contents of the zip file to a location of your choice
- double click on the executable file
- select "Just stress testing"
- select the "Blend" test. If you've already run MemTest overnight please run the "Small FFTs" test instead. (run all 3 if you find a problem and note how long it takes to error out with each)
- "Number of torture test threads to run" should equal the number of CPU's times 2 (if you're using hyperthreading).
The easiest way to figure this out is to go to Task Manager...Performance tab - and see the number of boxes under CPU Usage History
Then run the test for 6 to 24 hours - or until you get errors (whichever comes first).
This won't necessarily crash the system - but check the output in the test window for errors.
The Test selection box and the stress.txt file describes what components that the program stresses.
More details on the use of this test: Torture test your CPU with Prime95

[/QUOTE]

SECOND
Please visit here and download the latest nVidia drivers for your video card and OS (yours are about 6 months old): NVIDIA DRIVERS 266.58 WHQL
Ensure that your video card fan is operational, that the cooler is clear of dust/hairballs, and that the power plugs are firmly plugged in. Borrow another video card from the system that you used previously and try that in your system (to see if the BSOD's still occur with the new drivers).

Please run these free stress tests for the video cards:

FurMark download site: FurMark: VGA Stress Test, Graphics Card and GPU Stability Test, Burn-in Test, OpenGL Benchmark and GPU Temperature | oZone3D.Net
FurMark Setup:
- If you have more than one GPU, select Multi-GPU during setup
- In the Run mode box, select "Stability Test" and "Log GPU Temperature"
Click "Go" to start the test
- Run the test until the GPU temperature maxes out - or until you start having problems (whichever comes first).
NOTE: Set the alarm to go off at 90ºC. Then watch the system from that point on.
- Click "Quit" to exit

Two other video stress tests (may be more stressful than FurMark):
Video Memory stress Test - МИРNVIDIA / Утилиты / VMT
Artifact Locator - МИРNVIDIA / Утилиты / Artifact Locator
Sorry, but I don't read the language that this website is made in.

Another interesting test that just came to my attention: Download - OCCT Website english
USE AT YOUR OWN RISK - program doesn't have a whole bunch of safety features to protect you from yourself!

THIRD
For the PSU - Please disconnect (and remove) all non-essential devices. Disconnect any CD/DVD drives (both cables) any USB devices (leave the webcam/microphone connected if you use them with Yahoo), any spare fans (and use a house fan to cool the case off), disconnect both cables on any spare hard drives, remove any unneeded devices plugged into the motherboard (such as a 56K modem if not used). That will use less power - which should enable more power to go to the video card. If the PSU isn't powerful enough, it won't just slow down your video card - it will give you problems similar to what you've been experiencing.

FOURTH
Here is a DRAFT of a discussion about Prime95 - there are lot's of tests included here. Run as many as you can.

DRAFT Prime95 testing procedure
This is in case you are getting errors in Prime95 and want to nail down the cause

Run HDD diag and MemTest prior to Prime95

Run Blend test
Run Inplace Large FFT's test
Run Small FFT's test

Run CPU Stress Tests
- http://downloadcenter.intel.com/Detail_Desc.aspx?agr=Y&DwnldID=19182&lang=eng
- 7Byte : Hot CPU Tester Pro
- 7Byte : BurnIn64
- CPU Stress test - Overclock.net - Overclocking.net
- Fossil Free Online CPU Load or Stress Test.
- CPU Stability Test description, System Resources Tune-Up. Downloads List By All Time Popularity | PCWorld - PCWorld
- CPU Stress test - Overclock.net - Overclocking.net
- |MG| CPU Stability Test 6.0 Download
- LinX - A simple Linpack interface - XtremeSystems Forums

Run Video Stress Tests
- FurMark: VGA Stress Test, Graphics Card and GPU Stability Test, Burn-in Test, OpenGL Benchmark and GPU Temperature | oZone3D.Net
- МИРNVIDIA / Утилиты / VMT
- МИРNVIDIA / Утилиты / Artifact Locator

Swap RAM sticks around per Steps 7 through 10 of this link and run Prime95 (in Blend mode) on each stick/slot: Memory Diagnostics
This is because of issues found in this topic: http://www.sevenforums.com/crashes-debugging/124155-blue-screens-again-2.html#post1076674
************************
DISCUSSION:
Small FFT's test CPU cache and very little memory.
Large FFT's access' a lot of memory - but in-place option keeps it limited
Blend is not run in-place, so it cycles the tests through a lot of RAM

All tests stress the CPU
In-place large FFT's and Blend also test CPU/RAM interface (mobo in all but Athlon64 and Intel i-series)
- This would then be testing the memory controller onboard the CPU in the Athlon64 and i-series processors
In-place large FFT's stress CPU more than Blend
MemTest is better at testing RAM

Prime 95 tests 3 things:
- Memory
- CPU/RAM interface (mobo in all but Athlon64 and Intel i-series)
- CPU

FWIW - the distinction between RAM and different types of memory in the system is one that I've made. The documentation that I've read speaks of RAM issues and CPU cache - and doesn't mention the other aspects. BUT, this is just speculation on my part, so we'll have to see how it works for us.
Link to explanation about i-series CPU/RAM interface: Intel Core - Wikipedia, the free encyclopedia

Common features of all Nehalem based processors include an integrated DDR3 memory controller as well as QuickPath Interconnect or PCI Express and Direct Media Interface on the processor replacing the aging quad-pumped Front Side Bus used in all earlier Core processors.

Post back the results of each test as they complete - and we'll move on from there.

 

[easwar2641993]

First, please excuse my questions as I've just come to this topic - and I have some serious eye problems so I've only been able to glance over all 105 posts.

You have instructed Driver Verifier to check all non-Microsoft drivers
Yet Microsoft drivers are showing up as the cause in the Driver Verifier enabled memory dumps.

This, to me, means that the 3rd party drivers aren't at fault.
If that's the case, the only things left are: Windows, compatibility issues, or hardware

Now, a discussion about Driver Verifier (DV).

DV is used to stress drivers and (hopefully) cause them to crash and spit out a BSOD error message that names the faulty driver. But driver developers don't have to follow Microsoft's rules for drivers development - so we can't assume that all drivers will react equally to DV.

In short, what if you have a driver that's not quite up to Microsoft's standards - but it works OK under normal circumstances? In that case, the driver can crash under Driver Verifier, but won't necessarily crash under normal usage.

So, use Driver Verifier if you're having crashes. Once you've finished with the crash diagnostics - turn Driver Verifier off.

I don't think that Windows is the issue.
But there are issues with Win7 that aren't present with the other OS's (in particular, I've seen RAM issues in the Asus P5 series of boards that can only be explained by that).

So, we're looking at how your system handles RAM
We're looking at your video card and it's drivers
We're looking at your power supply - and how well it provides power to the video card
and we're looking at the mobo/CPU in case of issues there.

FIRST
To test RAM, please run these two free tests according to the instructions:

Memory Diagnostics (read the instructions at the link)
Please run the test for a minimum of 7 passes.
and
Prime95 Setup:
- extract the contents of the zip file to a location of your choice
- double click on the executable file
- select "Just stress testing"
- select the "Blend" test. If you've already run MemTest overnight please run the "Small FFTs" test instead. (run all 3 if you find a problem and note how long it takes to error out with each)
- "Number of torture test threads to run" should equal the number of CPU's times 2 (if you're using hyperthreading).
The easiest way to figure this out is to go to Task Manager...Performance tab - and see the number of boxes under CPU Usage History
Then run the test for 6 to 24 hours - or until you get errors (whichever comes first).
This won't necessarily crash the system - but check the output in the test window for errors.
The Test selection box and the stress.txt file describes what components that the program stresses.
More details on the use of this test: Torture test your CPU with Prime95

SECOND
Please visit here and download the latest nVidia drivers for your video card and OS (yours are about 6 months old): NVIDIA DRIVERS 266.58 WHQL
Ensure that your video card fan is operational, that the cooler is clear of dust/hairballs, and that the power plugs are firmly plugged in. Borrow another video card from the system that you used previously and try that in your system (to see if the BSOD's still occur with the new drivers).

Please run these free stress tests for the video cards:
THIRD
For the PSU - Please disconnect (and remove) all non-essential devices. Disconnect any CD/DVD drives (both cables) any USB devices (leave the webcam/microphone connected if you use them with Yahoo), any spare fans (and use a house fan to cool the case off), disconnect both cables on any spare hard drives, remove any unneeded devices plugged into the motherboard (such as a 56K modem if not used). That will use less power - which should enable more power to go to the video card. If the PSU isn't powerful enough, it won't just slow down your video card - it will give you problems similar to what you've been experiencing.

FOURTH
Here is a DRAFT of a discussion about Prime95 - there are lot's of tests included here. Run as many as you can.

DRAFT Prime95 testing procedure
This is in case you are getting errors in Prime95 and want to nail down the cause

Run HDD diag and MemTest prior to Prime95

Run Blend test
Run Inplace Large FFT's test
Run Small FFT's test

Run CPU Stress Tests
- http://downloadcenter.intel.com/Detail_Desc.aspx?agr=Y&DwnldID=19182&lang=eng
- 7Byte : Hot CPU Tester Pro
- 7Byte : BurnIn64
- CPU Stress test - Overclock.net - Overclocking.net
- Fossil Free Online CPU Load or Stress Test.
- CPU Stability Test description, System Resources Tune-Up. Downloads List By All Time Popularity | PCWorld - PCWorld
- CPU Stress test - Overclock.net - Overclocking.net
- |MG| CPU Stability Test 6.0 Download
- LinX - A simple Linpack interface - XtremeSystems Forums

Run Video Stress Tests
- FurMark: VGA Stress Test, Graphics Card and GPU Stability Test, Burn-in Test, OpenGL Benchmark and GPU Temperature | oZone3D.Net
- МИРNVIDIA / Утилиты / VMT
- МИРNVIDIA / Утилиты / Artifact Locator

Swap RAM sticks around per Steps 7 through 10 of this link and run Prime95 (in Blend mode) on each stick/slot: Memory Diagnostics
This is because of issues found in this topic: http://www.sevenforums.com/crashes-debugging/124155-blue-screens-again-2.html#post1076674
************************
DISCUSSION:
Small FFT's test CPU cache and very little memory.
Large FFT's access' a lot of memory - but in-place option keeps it limited
Blend is not run in-place, so it cycles the tests through a lot of RAM

All tests stress the CPU
In-place large FFT's and Blend also test CPU/RAM interface (mobo in all but Athlon64 and Intel i-series)
- This would then be testing the memory controller onboard the CPU in the Athlon64 and i-series processors
In-place large FFT's stress CPU more than Blend
MemTest is better at testing RAM

Prime 95 tests 3 things:
- Memory
- CPU/RAM interface (mobo in all but Athlon64 and Intel i-series)
- CPU

FWIW - the distinction between RAM and different types of memory in the system is one that I've made. The documentation that I've read speaks of RAM issues and CPU cache - and doesn't mention the other aspects. BUT, this is just speculation on my part, so we'll have to see how it works for us.
Link to explanation about i-series CPU/RAM interface: Intel Core - Wikipedia, the free encyclopedia

Common features of all Nehalem based processors include an integrated DDR3 memory controller as well as QuickPath Interconnect or PCI Express and Direct Media Interface on the processor replacing the aging quad-pumped Front Side Bus used in all earlier Core processors.

Post back the results of each test as they complete - and we'll move on from there.[/QUOTE]


Hello,
The problems started when I play games like Call Of Duty,Prince Of Persia and such mid-high range full screen games,with yahoo messenger in the background.The game runs fine without any problems.But if some one messages me in the background,I have to quit the game.When I do that,just after doing it,display the desktop and at that moment BSOD occurs..the code of the bsod at that time is 0x50 that is PAGE_FAULT_IN_NON_PAGED_AREA.I had a previous "new"system of 9500GT graphics card and had this issue with games and yahoo messenger.I thought it could be a hardware issue and I sold it and bought new components and assembled it.This new system contains GT 240 graphics card.This one is too showing the exact error.So I am really worried since I spent a lot of money for this one by simply selling a "new" system at a low cost.So I came here and asked about this.I hadn't heard about Verifier before.I learned about it's features from here only.When I enable it,more and more bsods came and some times computer won't boot at all.It will either show bsods during boot up,or will hang displaying windows 7 logo(no hard disk front light at that time,during booting up ,I mean during animation,light will flash and when it becomes stuck,light will stop and I have to reboot the system manually) and some times it will boot normally without any errors.The frequent bsods with verifier are 0xc9,0x7e,0xa and latest 0xd1(occurred only 1 time).I have tested RAM with memtest86+ and passed without any errors(7 or 8 passes,I don't rem and I put the test in the night..to morning).Checked graphics card with furmark test and results are good,no artifacts in the screen and so of temperature.I have replaced the ram with another ram,still there is the issue.My friend has the system of the same configuration but he have a high rated p.s.u (500W) and don't have a graphics card.I put my graphics card there and there too same bsod occurred.I have replaced the ram,hard disk and processor of the same model).When I contacted nvidia,they told since games are working perfectly without the messenger and verifier,then there is no issue with card.When I contacted Intel,they told either the board has incompatibility with the card or windows 7 issue.Also they haven't tested this card with this board.I have updated bios,drivers and windows.Still the issue is there.
*.There is no bsods under normal condition without verifier and gaming with yahoo messenger.
*.No bsods with Windows XP SP3 and Vista SP2.
*.The board is operating at 1066Mhz for RAM and CPU.CPU is a C2D E7500 2.93 Ghz (1066Mhz) and RAM is a Kingston 2 GB DDR3 1333Mhz.Since the board supports downclocking of RAM and it is the only available memory in this area ,I bought this.
My friend's system with this configuration(but no graphics card and higher P.S.U) is using the same model of RAM(1333Mhz).
*.If I use onboard graphics with Windows 7 driver(WDDM 1.1),bsod occurs with verifier.But if I use driver released by Intel I don't get bsods with verifier.This was same in friend's system too.
I hope all these information are helpful.

 

[easwar2641993]

Thinking about this, it seems as if the motherboard is actually the cause. You are getting a strange hybrid of symptoms common to hardware and software causes, and based on what you said about that PCIe driver giving BSODs under driver verifier, I wonder if that is the cause.

Try installing updated chipset drivers: Intel® Driver Update Utility

...Summary of the dumps:

[FONT=lucida console]
Built by: 7601.17514.x86fre.win7sp1_rtm.101119-1850
Debug session time: Mon Feb 28 07:00:27.336 2011 (UTC - 5:00)
System Uptime: 0 days 0:00:06.130
Probably caused by : ntkrpamp.exe ( nt!KiTrap0E+2cf )
PROCESS_NAME:  System
BUGCHECK_STR:  DISABLED_INTERRUPT_FAULT
DEFAULT_BUCKET_ID:  VERIFIER_ENABLED_VISTA_MINIDUMP
FAILURE_BUCKET_ID:  DISABLED_INTERRUPT_FAULT_VRF_CODE_AV_BAD_IP_nt!KiTrap0E+2cf
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7601.17514.x86fre.win7sp1_rtm.101119-1850
Debug session time: Mon Feb 28 04:43:04.145 2011 (UTC - 5:00)
System Uptime: 0 days 0:00:07.940
*** WARNING: Unable to verify timestamp for nvlddmkm.sys
*** ERROR: Module load completed but symbols could not be loaded for nvlddmkm.sys
BUGCHECK_STR:  0xc9_c
DEFAULT_BUCKET_ID:  VERIFIER_ENABLED_VISTA_MINIDUMP
PROCESS_NAME:  System
FAILURE_BUCKET_ID:  0xc9_c_VRF_dxgkrnl!DpiQueryBusInterface+78
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7601.17514.x86fre.win7sp1_rtm.101119-1850
Debug session time: Mon Feb 28 04:31:47.938 2011 (UTC - 5:00)
System Uptime: 0 days 0:06:35.733
*** WARNING: Unable to verify timestamp for nvlddmkm.sys
*** ERROR: Module load completed but symbols could not be loaded for nvlddmkm.sys
Probably caused by : pci.sys ( pci!PciStallForPowerChange+78 )
DEFAULT_BUCKET_ID:  NULL_CLASS_PTR_DEREFERENCE
PROCESS_NAME:  System
BUGCHECK_STR:  0x7E
FAILURE_BUCKET_ID:  0x7E_VRF_pci!PciStallForPowerChange+78
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7601.17514.x86fre.win7sp1_rtm.101119-1850
Debug session time: Mon Feb 28 04:20:37.406 2011 (UTC - 5:00)
System Uptime: 0 days 0:00:12.091
BUGCHECK_STR:  0xc9_c
DEFAULT_BUCKET_ID:  VERIFIER_ENABLED_VISTA_MINIDUMP
PROCESS_NAME:  System
FAILURE_BUCKET_ID:  0xc9_c_VRF_nt!IovpCompleteRequest+3c
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7601.17514.x86fre.win7sp1_rtm.101119-1850
Debug session time: Mon Feb 28 04:10:23.244 2011 (UTC - 5:00)
System Uptime: 0 days 0:00:05.038
BUGCHECK_STR:  0xc9_c
DEFAULT_BUCKET_ID:  VERIFIER_ENABLED_VISTA_MINIDUMP
PROCESS_NAME:  System
FAILURE_BUCKET_ID:  0xc9_c_VRF_nt!IovpCompleteRequest+3c
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7601.17514.x86fre.win7sp1_rtm.101119-1850
Debug session time: Mon Feb 28 04:00:31.164 2011 (UTC - 5:00)
System Uptime: 0 days 0:00:05.959
BUGCHECK_STR:  0xc9_c
DEFAULT_BUCKET_ID:  VERIFIER_ENABLED_VISTA_MINIDUMP
PROCESS_NAME:  System
FAILURE_BUCKET_ID:  0xc9_c_VRF_nt!IovpCompleteRequest+3c
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
  
[/FONT]

NEW VERIFIER BSOD WITHOUT GRAPHICS CARD!!!!!!!!!!
PAGE_FAULT_IN_NON_PAGED_AREA:huh:

 

[usasma]

*.There is no bsods under normal condition without verifier and gaming with yahoo messenger.

Then you don't have a problem - Driver Verifier is for testing, not for running under normal circumstances.
Also, when you run Driver Verifier it slows your system down - which you don't need on a gaming system.

You appear to have isolated one problem to the video card - as it BSOD's in other systems also.
I'd either live with it (and not use Driver Verifier) or I'd get a new, compatible video card.

Use Intel driver that doesn't cause BSOD's in verifier - that means it's more stable than the WDDM driver. FWIW - Microsoft doesn't do compatibility testing (except for the WHQL program) - so Intel drivers at the Microsoft/Windows Update website are usually older than the one's from Intel.

I'll look at the new BSOD after work. A quick look suggests that both are blaming ntkrpamp.exe - which would indicate that it's not a 3rd party driver problem.

Please turn off Driver Verifier.

 

[easwar2641993]

*.There is no bsods under normal condition without verifier and gaming with yahoo messenger.

Then you don't have a problem - Driver Verifier is for testing, not for running under normal circumstances.
Also, when you run Driver Verifier it slows your system down - which you don't need on a gaming system.

You appear to have isolated one problem to the video card - as it BSOD's in other systems also.
I'd either live with it (and not use Driver Verifier) or I'd get a new, compatible video card.

Use Intel driver that doesn't cause BSOD's in verifier - that means it's more stable than the WDDM driver. FWIW - Microsoft doesn't do compatibility testing (except for the WHQL program) - so Intel drivers at the Microsoft/Windows Update website are usually older than the one's from Intel.

I'll look at the new BSOD after work. A quick look suggests that both are blaming ntkrpamp.exe - which would indicate that it's not a 3rd party driver problem.

Please turn off Driver Verifier.

I will definitely do that.Two days before,when I used to install more stable drivers for the GT 240,I installed a 197.45 driver and without verifier,during game play CoD4MW ,it triggered a BSOD.When I looked more about the cause using BlueScreenViewer,I think it was still blaming a Windows Core File.I don't remember what was the name of it.But the code was 0x116.When I looked in Reliability monitor and problems,a 0x117 incident occurred prior to 0x116 BSOD..Video Hardware Failure.So what I did is I reinstalled the driver to 258.99 or some in 250.xx series.After that the problem wouldn't occurred again.Yesterday I installed Windows XP and installed a 25x.xx version of driver.Enabled verifier (with complete settings including low resource simulation).Played CoD4MW with it.At first it worked fine for some time.After that I played Black Ops for some time.After that,again,I came back to CoD4MW.This time,during game play,computer became stuck and a grey-black screen appeared with a sound of recorder in headphones(the usual sound
of computer when bsod occurs).But it didn't show "blue screen".So I restarted the PC manually and checked for dumps.No dumps or information about Bsod was reported by system though dumping was enabled.Very strange it was.Then I came back to Windows 7 and searched for various NVIDIA Forceware drivers.Since 197.45 caused a problem,I decided to run 195.xx version,196.xx version.While using both the drivers,this 0x117 error occurred.It occurred just when I was watching a video of small resolution(say 3xx x 2xx).So,is it because of a faulty graphics card or lack of Power supply?If I run a new graphics card with insufficient P.S.U,will it damage G.P.U permanently?Since we have exams ,so computer is highly needed.So,If we buy a new P.S.U of well rated above 500W and a new ASUS/GIGABYTE motherboard,the problem will be solved then?Or If that wont help us,then I would RMA the card and install the replaced one with this new mobo and P.S.U,the problem will be solved then?

I am really sorry to test the graphics card or get a card from others and install that in my system to test is not possible here in Kerala,India.I have asked many people including computer shop keepers.They are not at all willing to give me any component for "testing purpose".They will give for "testing" but we have to buy the component and so there is no need of returning that to them.Really horrible is the situation here.Only 1 friend helped me in this case.They gave me their C.P.U to test.But the problem is they don't have a graphics card and is using similar configurations(motherboard,cpu,hard disk,optical drive and ram).And they have a powerful PSU but it is unrated and company is Zebronics I think.(500W).

Now my next question is my PSU is Cooler Master Elite Power 350W.It has 12V1 and 12V2 supplies.12V1 provides 10A and 12V2 provides 13A.When I looked in the supply diagram of this PSU,12V2 is the one which supply power to C.P.U,hard disks and optical drivers while 12V1 gives power to motherboard components and its accessories via 12x2 connector.(20+4).I think that one is giving power to PCI-E too.If it is the case then,my GT-240 requires 18A at 12V rail when configured with Intel Core 2 Duo.So,that 18A is the total of 10A+13A or 10A only?

 

[easwar2641993]

*.There is no bsods under normal condition without verifier and gaming with yahoo messenger.

Then you don't have a problem - Driver Verifier is for testing, not for running under normal circumstances.
Also, when you run Driver Verifier it slows your system down - which you don't need on a gaming system.

You appear to have isolated one problem to the video card - as it BSOD's in other systems also.
I'd either live with it (and not use Driver Verifier) or I'd get a new, compatible video card.

Use Intel driver that doesn't cause BSOD's in verifier - that means it's more stable than the WDDM driver. FWIW - Microsoft doesn't do compatibility testing (except for the WHQL program) - so Intel drivers at the Microsoft/Windows Update website are usually older than the one's from Intel.

I'll look at the new BSOD after work. A quick look suggests that both are blaming ntkrpamp.exe - which would indicate that it's not a 3rd party driver problem.

Please turn off Driver Verifier.

http://www.intel.com/Assets/PDF/specupdate/307014.pdf
can you please go to page no:12 and tell me is there any issues with the card and board compatibility..there are some errata for the PCI Express addon cards.
When I use standard settings,then there won't be any issues.But the issues or bsods starts if I enable verifier for "Force Pending I/O requests".So is there any connection between the errata and the issue?

 

[usasma]

You have both the Intel and the nVidia video card drivers working - please uninstall one of them.
Also, your nVidia drivers are from July of 2010 - please update both the nVidia chipset and the nVidia video drivers.

BSOD BUGCHECK SUMMARY

[FONT=lucida console]
Built by: 7601.17514.x86fre.win7sp1_rtm.101119-1850
Debug session time: Mon Feb 28 23:32:02.006 2011 (UTC - 5:00)
System Uptime: 0 days 0:00:07.630
DEFAULT_BUCKET_ID:  VERIFIER_ENABLED_VISTA_MINIDUMP
BUGCHECK_STR:  0x50
PROCESS_NAME:  System
FAILURE_BUCKET_ID:  0x50_VRF_nt!IopCreateFile+673
Bugcheck code 00000050
Arguments ffffffe1 00000001 82c7a9b4 00000000
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7601.17514.x86fre.win7sp1_rtm.101119-1850
Debug session time: Mon Feb 28 22:14:00.585 2011 (UTC - 5:00)
System Uptime: 0 days 0:00:06.380
BUGCHECK_STR:  0xc9_c
DEFAULT_BUCKET_ID:  VERIFIER_ENABLED_VISTA_MINIDUMP
PROCESS_NAME:  System
FAILURE_BUCKET_ID:  0xc9_c_VRF_nt!IovpCompleteRequest+3c
Bugcheck code 000000C9
Arguments 0000000c 8751f4e8 8be56f68 00000000
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``[/FONT]

BE SURE TO TURN DRIVER VERIFIER OFF!!!

I saw the previous STOP 0x116/0x117 errors and they could be from the things that I've discussed. For more info on those errors, please have a look at these links:
BSOD Index STOP 0x116
BSOD Index STOP 0x117
http://www.sevenforums.com/crash-lo...op-0x116-video_tdr_error-troubleshooting.html
(STOP 0x116 and 0x117 errors are very similar - so troubleshooting them is the same).

You'll have to do what I've suggested in order to help us figure out where the hardware problem lies.
Start with "First" and move on to the others.

 

[easwar2641993]

You have both the Intel and the nVidia video card drivers working - please uninstall one of them.
Also, your nVidia drivers are from July of 2010 - please update both the nVidia chipset and the nVidia video drivers.

BSOD BUGCHECK SUMMARY

[FONT=lucida console]
Built by: 7601.17514.x86fre.win7sp1_rtm.101119-1850
Debug session time: Mon Feb 28 23:32:02.006 2011 (UTC - 5:00)
System Uptime: 0 days 0:00:07.630
DEFAULT_BUCKET_ID:  VERIFIER_ENABLED_VISTA_MINIDUMP
BUGCHECK_STR:  0x50
PROCESS_NAME:  System
FAILURE_BUCKET_ID:  0x50_VRF_nt!IopCreateFile+673
Bugcheck code 00000050
Arguments ffffffe1 00000001 82c7a9b4 00000000
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7601.17514.x86fre.win7sp1_rtm.101119-1850
Debug session time: Mon Feb 28 22:14:00.585 2011 (UTC - 5:00)
System Uptime: 0 days 0:00:06.380
BUGCHECK_STR:  0xc9_c
DEFAULT_BUCKET_ID:  VERIFIER_ENABLED_VISTA_MINIDUMP
PROCESS_NAME:  System
FAILURE_BUCKET_ID:  0xc9_c_VRF_nt!IovpCompleteRequest+3c
Bugcheck code 000000C9
Arguments 0000000c 8751f4e8 8be56f68 00000000
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``[/FONT]

BE SURE TO TURN DRIVER VERIFIER OFF!!!

I saw the previous STOP 0x116/0x117 errors and they could be from the things that I've discussed. For more info on those errors, please have a look at these links:
BSOD Index STOP 0x116
BSOD Index STOP 0x117
http://www.sevenforums.com/crash-lo...op-0x116-video_tdr_error-troubleshooting.html
(STOP 0x116 and 0x117 errors are very similar - so troubleshooting them is the same).

You'll have to do what I've suggested in order to help us figure out where the hardware problem lies.
Start with "First" and move on to the others.

Now the verifier is turned off now and no problems after installing 259.96 version.Anyway I will install latest version but it has a problem.That driver makes the system shut down slow.There is no problem with 260.xx driver too.The problem is only with the latest version.
I have heard about data loss may occur if 1333mhz RAM is used on a board that supports only upto 1066mhz frequency though it supports downclocking.Is that right?I am using such a ram on a board that supports upto 1066mhz.That might be the reason of getting blue screen even using with onboard graphics since it shares memory from this one.

 

[easwar2641993]

You have both the Intel and the nVidia video card drivers working - please uninstall one of them.
Also, your nVidia drivers are from July of 2010 - please update both the nVidia chipset and the nVidia video drivers.

BSOD BUGCHECK SUMMARY

[FONT=lucida console]
Built by: 7601.17514.x86fre.win7sp1_rtm.101119-1850
Debug session time: Mon Feb 28 23:32:02.006 2011 (UTC - 5:00)
System Uptime: 0 days 0:00:07.630
DEFAULT_BUCKET_ID:  VERIFIER_ENABLED_VISTA_MINIDUMP
BUGCHECK_STR:  0x50
PROCESS_NAME:  System
FAILURE_BUCKET_ID:  0x50_VRF_nt!IopCreateFile+673
Bugcheck code 00000050
Arguments ffffffe1 00000001 82c7a9b4 00000000
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7601.17514.x86fre.win7sp1_rtm.101119-1850
Debug session time: Mon Feb 28 22:14:00.585 2011 (UTC - 5:00)
System Uptime: 0 days 0:00:06.380
BUGCHECK_STR:  0xc9_c
DEFAULT_BUCKET_ID:  VERIFIER_ENABLED_VISTA_MINIDUMP
PROCESS_NAME:  System
FAILURE_BUCKET_ID:  0xc9_c_VRF_nt!IovpCompleteRequest+3c
Bugcheck code 000000C9
Arguments 0000000c 8751f4e8 8be56f68 00000000
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``[/FONT]

BE SURE TO TURN DRIVER VERIFIER OFF!!!

I saw the previous STOP 0x116/0x117 errors and they could be from the things that I've discussed. For more info on those errors, please have a look at these links:
BSOD Index STOP 0x116
BSOD Index STOP 0x117
http://www.sevenforums.com/crash-lo...op-0x116-video_tdr_error-troubleshooting.html
(STOP 0x116 and 0x117 errors are very similar - so troubleshooting them is the same).

You'll have to do what I've suggested in order to help us figure out where the hardware problem lies.
Start with "First" and move on to the others.

Haiii..everyone!!pls help me in this..i bought a new motherboard ASUS P5G41T-M-LX board..when i installed the board with the same processor,ram,graphics card,harddisk and optical drive with same power supply 350W,the light on the boards turns on.but when I press the power button,the system won't turns on.no cpu fan spin,psu fan spin,no display,no graphics card spin,no hard disk spin..what could be the issue??but the power indicator on the board turns on..i checked all the components in old board and works fine..

 

[DeanP]

Sounds like if the new motherboard is incompatible or faulty - or even both.
STOP 0x116 is related to faulty RAM or GPU.