nvlddmkm.sys PAGE_FAULT_IN_NONPAGED_AREA

[Hollywood2]

First my system went into sleep mode while I was using it two days later I am flying a sim and it locks up about 45 seconds later it jumped a few frames and did so until I manually shut it down. ctrl alt delete had no affect I believe my keyboard did not show signs of a crash it would still light up if I pressed Caps Lock the only way to shut down was to force it with button it rebooted everything good until I opened a different flight sim which it crashed again as above. on reboot got BSOD displaying 0000000050 PAGE_FAULT_IN_NONPAGED_AREA naming nvlddmkm.sys as the cause
I have updated, outdated, even asked my cousin for a date, nothing worked I can boot from safe mode from there I can uninstall the nvidia drivers and on reboot let windows install generic drivers and from what I read here that is to do with vga and not using it which explains why with windows drivers I cannot fly even the simplest games DirectX is not happening the dxdiag tool says everything in honky dory but that because it list no drivers, I have a hp dv9335nr dual intel t-5300 @ 1.73GHz 2 GB mem GeForce Go 7600 running windows 7 upgrade 64 bit also I believe I found a link here to a free tool that deciphers a crash dump file ( BlueScreenView) and it says that ntoskrnl.exe is the cause and the BSOD names nvlddmkm.sys when I use window drivers for video the rating used to be 4.6 now it is 1.0 . I did the memtest overnight, I ran chkdsk /f, sfc /scannow, even found a Update for Windows 7 for x64-based Systems (KB976972)download from microsoft in relations to nvidia which required activation check. C:\NVIDIA\WinVista64\179.48\IS\Display
I hope I have supplied anyone with enough info to shine some light on my situation and any info you need please tell me so i can provide it

Thank you

041610-24944-01.dmp 4/16/2010 7:55:25 PM PAGE_FAULT_IN_NONPAGED_AREA 0x00000050 fffff880`30050464 00000000`00000000 fffff880`04a19686 00000000`00000002 ntoskrnl.exe ntoskrnl.exe+71f00 NT Kernel & System Microsoft® Windows® Operating System Microsoft Corporation 6.1.7600.16385 (win7_rtm.090713-1255) x64 C:\Windows\MiniDump\041610-24944-01.dmp 2 15 7600

ntoskrnl.exe ntoskrnl.exe+efbc2 fffff800`0305d000 fffff800`0363a000 0x005dd000 0x4a5bc600 7/13/2009 4:40:48 PM Microsoft® Windows® Operating System NT Kernel & System 6.1.7600.16385 (win7_rtm.090713-1255) Microsoft Corporation C:\Windows\system32\ntoskrnl.exe

041510-32448-01.dmp 4/15/2010 3:27:45 PM PAGE_FAULT_IN_NONPAGED_AREA 0x00000050 fffff880`30050464 00000000`00000000 fffff880`0498a796 00000000`00000002 ntoskrnl.exe ntoskrnl.exe+71f00 NT Kernel & System Microsoft® Windows® Operating System Microsoft Corporation 6.1.7600.16385 (win7_rtm.090713-1255) x64 C:\Windows\MiniDump\041510-32448-01.dmp 2 15 7600

ntoskrnl.exe ntoskrnl.exe+efbc2 fffff800`03009000 fffff800`035e6000 0x005dd000 0x4a5bc600 7/13/2009 4:40:48 PM Microsoft® Windows® Operating System NT Kernel & System 6.1.7600.16385 (win7_rtm.090713-1255) Microsoft Corporation C:\Windows\system32\ntoskrnl.exe

THANKS

 

[Jonathan_King]

Welcome to SF!

BSV seems to blame most crashes on ntsokrnl, to the point where we tend to discredit its advice. We prefer Microsoft's program Debugging Tools for Windows.

Could you please upload your dmps for analysis? http://www.sevenforums.com/crash-lockup-debug-how/34900-1-novice-how-ask-help-bsod-problem.html

I wonder if your graphics card is defective. Try changing it out for another one, of you have one.

 

[Crispy]

Make sure your have the latest drivers, you can grab them from here: Welcome to NVIDIA - World Leader in Visual Computing Technologies

 

[Hollywood2]

Is this the info you wanted? sys specs

<?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
- <speccydata version="1.00.125" formatversion="1.0">
- <mainsection title="Summary">
- <section title="Operating System">
<data title="">MS Windows 7 64-bit</data>

</section>


- <section title="CPU">
<data title="Intel Mobile Core 2 Duo @ 1.73GHz">111 °F</data>

<data title="Merom 65nm Technology" />

</section>


- <section title="RAM">
<data title="">2.0GB Dual-Channel DDR2 @ 266MHz 4-4-4-12</data>

</section>


- <section title="Motherboard">
<data title="">Quanta 30BD (U2E1)</data>

</section>


- <section title="Graphics">
<data title="HP 2009 @ 1024x768" />

<data title="256MB Standard VGA Graphics Adapter (HP)" />

</section>


- <section title="Hard Drives">
<data title="160GB Hitachi Hitachi HTS541616J9SA00 ATA Device (IDE)">96 °F</data>

<data title="500GB Hitachi Hitachi HTS545050B9A300 ATA Device (IDE)">110 °F</data>

<data title="3GB SD Memory Card (NULL)" />

</section>


- <section title="Optical Drives">
<data title="HL-DT-ST DVD+-RW GSA-T21N ATA Device" />

</section>


- <section title="Audio">
<data title="Conexant High Definition Audio" />

</section>


</mainsection>


- <mainsection title="Operating System">
<data title="">MS Windows 7 64-bit</data>

<data title="">Installation Date: 14 April 2010, 19:45</data>

</mainsection>


- <mainsection title="CPU">
- <section title="Intel Mobile Core 2 Duo">
<data title="Cores">2</data>

<data title="Threads">2</data>

<data title="Name">Intel Mobile Core 2 Duo</data>

<data title="Code Name">Merom</data>

<data title="Package">Socket 479 mPGA</data>

<data title="Technology">65nm</data>

<data title="Specification">Intel(R) Core(TM)2 CPU T5300 @ 1.73GHz</data>

<data title="Family">6</data>

<data title="Extended family">6</data>

<data title="Model">F</data>

<data title="Extended model">F</data>

<data title="Stepping">2</data>

<data title="Revision">L2</data>

<data title="Instructions">MMX, SSE, SSE2, SSE3, SSSE3, EM64T</data>

<data title="Bus speed">132.7 MHz</data>

<data title="Rated Bus speed">530.9 MHz</data>

<data title="Stock core speed">1733 MHz</data>

<data title="Stock bus speed">133 MHz</data>

<data title="Average Temperature">111 °F</data>

- <section title="Caches">
<data title="L1 data cache size">2 x 32 KBytes</data>

<data title="L1 instructions cache size">2 x 32 KBytes</data>

<data title="L2 unified cache size">2048 KBytes</data>

</section>


- <section title="Core 0">
<data title="Core speed">1729.4 MHz</data>

<data title="Multiplier">x 13.0</data>

<data title="Bus speed">132.7 MHz</data>

<data title="Rated Bus speed">530.9 MHz</data>

<data title="Temperature">110 °F</data>

- <section title="Thread 1">
<data title="APIC ID">0</data>

</section>


</section>


- <section title="Core 1">
<data title="Core speed">1729.4 MHz</data>

<data title="Multiplier">x 13.0</data>

<data title="Bus speed">132.7 MHz</data>

<data title="Rated Bus speed">530.9 MHz</data>

<data title="Temperature">112 °F</data>

- <section title="Thread 1">
<data title="APIC ID">1</data>

</section>


</section>


</section>


</mainsection>


- <mainsection title="RAM">
- <section title="Memory">
<data title="Type">DDR2</data>

<data title="Size">2048 MBytes</data>

<data title="Channels #">Dual</data>

<data title="DRAM frequency">265.4 MHz</data>

<data title="CAS# Latency (CL)">4 clocks</data>

<data title="RAS# to CAS# delay (tRCD)">4 clocks</data>

<data title="RAS# precharge (tRP)">4 clocks</data>

<data title="Cycle time (tRAS)">12 clocks</data>

<data title="Bank cycle time (tRС)">16 clocks</data>

</section>


- <section title="SPD">
<data title="Number of SPD modules">2</data>

- <section title="Slot #1">
<data title="Type">DDR2</data>

<data title="Size">1024 MBytes</data>

<data title="Manufacturer">Qimonda</data>

<data title="Max bandwidth">PC2-5300 (333 MHz)</data>

<data title="Part number">64T128021HDL3SB</data>

<data title="Serial number">02125617</data>

<data title="Week/year">10 / 07</data>

<data title="SPD Ext.">EPP</data>

- <section title="JEDEC #3">
<data title="Frequency">333.3 MHz</data>

<data title="CAS# latency">5.0</data>

<data title="RAS# to CAS#">6</data>

<data title="RAS# Precharge">6</data>

<data title="tRAS">16</data>

<data title="tRC">21</data>

<data title="Voltage">1.800 V</data>

</section>


- <section title="JEDEC #2">
<data title="Frequency">266.7 MHz</data>

<data title="CAS# latency">4.0</data>

<data title="RAS# to CAS#">4</data>

<data title="RAS# Precharge">4</data>

<data title="tRAS">12</data>

<data title="tRC">16</data>

<data title="Voltage">1.800 V</data>

</section>


- <section title="JEDEC #1">
<data title="Frequency">200.0 MHz</data>

<data title="CAS# latency">3.0</data>

<data title="RAS# to CAS#">3</data>

<data title="RAS# Precharge">3</data>

<data title="tRAS">9</data>

<data title="tRC">12</data>

<data title="Voltage">1.800 V</data>

</section>


</section>


- <section title="Slot #2">
<data title="Type">DDR2</data>

<data title="Size">1024 MBytes</data>

<data title="Manufacturer">Qimonda</data>

<data title="Max bandwidth">PC2-5300 (333 MHz)</data>

<data title="Part number">64T128021HDL3SB</data>

<data title="Serial number">050BE421</data>

<data title="Week/year">10 / 07</data>

<data title="SPD Ext.">EPP</data>

- <section title="JEDEC #3">
<data title="Frequency">333.3 MHz</data>

<data title="CAS# latency">5.0</data>

<data title="RAS# to CAS#">6</data>

<data title="RAS# Precharge">6</data>

<data title="tRAS">16</data>

<data title="tRC">21</data>

<data title="Voltage">1.800 V</data>

</section>


- <section title="JEDEC #2">
<data title="Frequency">266.7 MHz</data>

<data title="CAS# latency">4.0</data>

<data title="RAS# to CAS#">4</data>

<data title="RAS# Precharge">4</data>

<data title="tRAS">12</data>

<data title="tRC">16</data>

<data title="Voltage">1.800 V</data>

</section>


- <section title="JEDEC #1">
<data title="Frequency">200.0 MHz</data>

<data title="CAS# latency">3.0</data>

<data title="RAS# to CAS#">3</data>

<data title="RAS# Precharge">3</data>

<data title="tRAS">9</data>

<data title="tRC">12</data>

<data title="Voltage">1.800 V</data>

</section>


</section>


</section>


</mainsection>


- <mainsection title="Motherboard">
<data title="Manufacturer">Quanta</data>

<data title="Model">30BD</data>

<data title="Version">Rev 1</data>

<data title="Chipset vendor">Intel</data>

<data title="Chipset model">i945PM</data>

<data title="Chipset revision">03</data>

<data title="Southbridge vendor">Intel</data>

<data title="Southbridge model">82801GHM (ICH7-M/U)</data>

<data title="Southbridge revision">B0</data>

- <section title="BIOS">
<data title="Brand">Hewlett-Packard</data>

<data title="Version">F.2D</data>

<data title="Date">11/26/2008</data>

</section>


</mainsection>


- <mainsection title="Graphics">
- <section title="Monitor">
<data title="Name">HP 2009 on Standard VGA Graphics Adapter</data>

<data title="Current Resolution">1024x768 pixels</data>

<data title="Work Resolution">1024x728 pixels</data>

<data title="State">enabled, primary, VgaCompatible</data>

<data title="Monitor Width">1024</data>

<data title="Monitor Height">768</data>

<data title="Monitor Bpp">32 bits per pixel</data>

<data title="Monitor Frequency">1 Hz</data>

<data title="Device">\\.\DISPLAY1\Monitor0</data>

</section>


- <section title="Standard VGA Graphics Adapter">
<data title="GPU">G73M</data>

<data title="Device ID">10DE-0398</data>

<data title="Revision">A2</data>

<data title="Subvendor">HP (103C)</data>

<data title="Technology">90 nm</data>

<data title="Transistors">177 M</data>

<data title="Release Date">2006</data>

<data title="DirectX Support">9.0c</data>

<data title="DirectX Shader Model">3.0</data>

<data title="OpenGL Support">2.0</data>

<data title="BIOS Version">Chip Rev</data>

<data title="ROPs">12</data>

<data title="Shaders">Vertex 12/Pixel 12</data>

<data title="Memory Type">GDDR3</data>

<data title="Memory">256 MB</data>

<data title="Bus Width">128 Bit</data>

</section>


</mainsection>


- <mainsection title="Hard Drives">
- <section title="Hitachi HTS541616J9SA00 ATA Device">
<data title="Manufacturer">Hitachi</data>

<data title="Product Family">Travelstar</data>

<data title="Series prefix">Standard</data>

<data title="Speed, expressed in Revolutions Per Minute (rpm)">5400</data>

<data title="Model capacity for this specific drive">160GB</data>

<data title="Interface">IDE</data>

<data title="Capacity">160GB</data>

<data title="Real size">160,041,885,696 bytes</data>

- <section title="S.M.A.R.T">
<data title="01 Read Error Rate">100 (098 worst) Data 0000000000</data>

<data title="02 Throughput Performance">100 (100) Data 0000000000</data>

<data title="03 Spin-Up Time">177 (100) Data 0000000002</data>

<data title="04 Start/Stop Count">096 (096) Data 000000193F</data>

<data title="05 Reallocated Sectors Count">100 (100) Data 0000000000</data>

<data title="07 Seek Error Rate">100 (100) Data 0000000000</data>

<data title="08 Seek Time Performance">100 (100) Data 0000000000</data>

<data title="09 Power-On Hours (POH)">075 (075) Data 0000002C5E</data>

<data title="0A Spin Retry Count">100 (100) Data 0000000000</data>

<data title="0C Device Power Cycle Count">098 (098) Data 000000118B</data>

<data title="BF G-sense error rate">100 (094) Data 0000000000</data>

<data title="C0 Power-off Retract Count">100 (100) Data 0000000071</data>

<data title="C1 Load/Unload Cycle Count">067 (067) Data 0000052495</data>

<data title="C2 Temperature">166 (090) Data 00000C0021</data>

<data title="C4 Reallocation Event Count">100 (100) Data 0000000000</data>

<data title="C5 Current Pending Sector Count">100 (100) Data 0000000000</data>

<data title="C6 Uncorrectable Sector Count">100 (100) Data 0000000000</data>

<data title="C7 UltraDMA CRC Error Count">200 (253) Data 0000000007</data>

<data title="DF Load/Unload Retry Count">100 (100) Data 0000000000</data>

<data title="Temperature">96 °F</data>

<data title="Temperature range">ok (less than 122 °F)</data>

<data title="Status">Good</data>

</section>


- <section title="Partition 0">
<data title="Partition ID">Disk #0, Partition #0</data>

<data title="Disk Letter">D:</data>

<data title="File System">NTFS</data>

<data title="Volume Serial Number">24FAA2DE</data>

<data title="Size">149.05GB</data>

<data title="Used Space">10.06GB (7%)</data>

<data title="Free Space">138.99GB (93%)</data>

</section>


</section>


- <section title="Hitachi HTS545050B9A300 ATA Device">
<data title="Manufacturer">Hitachi</data>

<data title="Product Family">Travelstar</data>

<data title="Series prefix">Standard</data>

<data title="Speed, expressed in Revolutions Per Minute (rpm)">5400</data>

<data title="Model capacity for this specific drive">500GB</data>

<data title="Interface">IDE</data>

<data title="Capacity">500GB</data>

<data title="Real size">500,107,862,016 bytes</data>

- <section title="S.M.A.R.T">
<data title="01 Read Error Rate">100 (100 worst) Data 0000000000</data>

<data title="02 Throughput Performance">100 (100) Data 0000000000</data>

<data title="03 Spin-Up Time">179 (179) Data 0000000001</data>

<data title="04 Start/Stop Count">100 (100) Data 000000034E</data>

<data title="05 Reallocated Sectors Count">100 (100) Data 0000000000</data>

<data title="07 Seek Error Rate">100 (100) Data 0000000000</data>

<data title="08 Seek Time Performance">100 (100) Data 0000000000</data>

<data title="09 Power-On Hours (POH)">092 (092) Data 0000000EDF</data>

<data title="0A Spin Retry Count">100 (100) Data 0000000000</data>

<data title="0C Device Power Cycle Count">100 (100) Data 000000033D</data>

<data title="BF G-sense error rate">100 (100) Data 0000000000</data>

<data title="C0 Power-off Retract Count">100 (100) Data 000000000F</data>

<data title="C1 Load/Unload Cycle Count">096 (096) Data 000000A42A</data>

<data title="C2 Temperature">125 (125) Data 00000D002C</data>

<data title="C4 Reallocation Event Count">100 (100) Data 0000000000</data>

<data title="C5 Current Pending Sector Count">100 (100) Data 0000000000</data>

<data title="C6 Uncorrectable Sector Count">100 (100) Data 0000000000</data>

<data title="C7 UltraDMA CRC Error Count">200 (200) Data 0000000000</data>

<data title="DF Load/Unload Retry Count">100 (100) Data 0000000000</data>

<data title="Temperature">110 °F</data>

<data title="Temperature range">ok (less than 122 °F)</data>

<data title="Status">Good</data>

</section>


- <section title="Partition 0">
<data title="Partition ID">Disk #1, Partition #0</data>

<data title="Size">100 MB</data>

</section>


- <section title="Partition 1">
<data title="Partition ID">Disk #1, Partition #1</data>

<data title="Disk Letter">E:</data>

<data title="File System">NTFS</data>

<data title="Volume Serial Number">40FBB525</data>

<data title="Size">75.86GB</data>

<data title="Used Space">12.02GB (16%)</data>

<data title="Free Space">63.83GB (84%)</data>

</section>


- <section title="Partition 2">
<data title="Partition ID">Disk #1, Partition #2</data>

<data title="Disk Letter">F:</data>

<data title="File System">NTFS</data>

<data title="Volume Serial Number">0C25579D</data>

<data title="Size">172.69GB</data>

<data title="Used Space">51.35GB (30%)</data>

<data title="Free Space">121.35GB (70%)</data>

</section>


- <section title="Partition 3">
<data title="Partition ID">Disk #1, Partition #3</data>

<data title="Disk Letter">C:</data>

<data title="File System">NTFS</data>

<data title="Volume Serial Number">FEB9F0DC</data>

<data title="Size">217.11GB</data>

<data title="Used Space">30.42GB (15%)</data>

<data title="Free Space">186.69GB (85%)</data>

</section>


</section>


- <section title="SD Memory Card">
<data title="Manufacturer">Unknown manufacturer</data>

<data title="Interface">NULL</data>

<data title="Capacity">3GB</data>

<data title="Real size">3,963,617,280 bytes</data>

- <section title="S.M.A.R.T">
<data title="S.M.A.R.T not supported" />

</section>


- <section title="Partition 0">
<data title="Partition ID">Disk #2, Partition #0</data>

<data title="Disk Letter">J:</data>

<data title="File System">NTFS</data>

<data title="Volume Serial Number">88197284</data>

<data title="Size">3.69GB</data>

<data title="Used Space">3.68GB (100%)</data>

<data title="Free Space">5MB (0%)</data>

</section>


</section>


</mainsection>


- <mainsection title="Optical Drives">
- <section title="HL-DT-ST DVD+-RW GSA-T21N ATA Device">
<data title="Media Type">DVD Writer</data>

<data title="Name">HL-DT-ST DVD+-RW GSA-T21N ATA Device</data>

<data title="Availability">Running/Full Power</data>

<data title="Capabilities">Random Access, Supports Writing, Supports Removable Media</data>

<data title="Config Manager Error Code">Device is working properly.</data>

<data title="Config Manager User Config">FALSE</data>

<data title="Drive">G:</data>

<data title="Media Loaded">FALSE</data>

<data title="SCSI Bus">0</data>

<data title="SCSI Logical Unit">0</data>

<data title="SCSI Port">0</data>

<data title="SCSI Target Id">0</data>

<data title="Status">OK</data>

</section>


</mainsection>


- <mainsection title="Audio">
- <section title="Sound Card">
<data title="Conexant High Definition Audio" />

</section>


- <section title="Playback devices">
<data title="SPDIF Interface (Conexant High Definition Audio)" />

<data title="Speakers (Conexant High Definition Audio)">(default)</data>

</section>


- <section title="Recording device">
<data title="Microphone (Conexant High Definition Audio)" />

</section>


</mainsection>


- <mainsection title="Peripherals">
- <section title="Standard PS/2 Keyboard">
<data title="Device kind">Keyboard</data>

<data title="Device name">Standard PS/2 Keyboard</data>

</section>


- <section title="HID Keyboard Device">
<data title="Device kind">Keyboard</data>

<data title="Device name">HID Keyboard Device</data>

</section>


- <section title="HID Keyboard Device">
<data title="Device kind">Keyboard</data>

<data title="Device name">HID Keyboard Device</data>

<data title="Vendor">Unknown</data>

</section>


- <section title="HID-compliant mouse">
<data title="Device kind">Mouse</data>

<data title="Device name">HID-compliant mouse</data>

<data title="Vendor">Logitech</data>

</section>


- <section title="PS/2 Compatible Mouse">
<data title="Device kind">Mouse</data>

<data title="Device name">PS/2 Compatible Mouse</data>

</section>


- <section title="HP Pavilion Webcam">
<data title="Device kind">Camera/scanner</data>

<data title="Device name">HP Pavilion Webcam</data>

<data title="Vendor">Unknown</data>

<data title="Location">0000.001d.0007.004.000.000.000.000.000</data>

<data title="Comment">HP Pavilion Webcam</data>

</section>


- <section title="Disk drive">
<data title="Device kind">USB storage</data>

<data title="Device name">Disk drive</data>

<data title="Vendor">SEAGATE</data>

<data title="Comment">Seagate Desktop USB Device</data>

</section>


- <section title="Disk drive">
<data title="Device kind">USB storage</data>

<data title="Device name">Disk drive</data>

<data title="Vendor">VERBATIM</data>

<data title="Comment">Verbatim STORE N GO USB Device</data>

</section>


</mainsection>


- <mainsection title="Network">
<data title="You are connected to the internet" />

<data title="Connected through">Sprint Mobile Broadband - Sierra Wireless</data>

<data title="IP Address">173.147.26.58</data>

<data title="Adapter Type">PPP</data>

- <section title="WinInet Info">
<data title="">Sprint Mobile Broadband - Sierra Wireless</data>

<data title="">Local system has a valid connection to the Internet, but it might or might not be currently connected.</data>

<data title="">Local system uses a modem to connect to the Internet.</data>

<data title="">Local system have RAS to connect to the Internet.</data>

</section>


- <section title="Wi-fi Info">
<data title="">Wifi not enabled.</data>

</section>


- <section title="WinHTTPInfo">
<data title="WinHTTPSessionProxyType">No proxy</data>

<data title="Session Proxy" />

<data title="Session Proxy Bypass" />

<data title="Connect Retries">5</data>

<data title="Connect Timeout">60000</data>

<data title="HTTP Version">HTTP 1.1</data>

<data title="Max Connects Per 1.0 Servers">INFINITE</data>

<data title="Max Connects Per Servers">INFINITE</data>

<data title="Max HTTP automatic redirects">10</data>

<data title="Max HTTP status continue">10</data>

<data title="Send Timeout">30000</data>

<data title="IEProxy Auto Detect">No</data>

<data title="IEProxy Auto Config" />

<data title="IEProxy" />

<data title="IEProxy Bypass" />

<data title="Default Proxy Config Access Type">No proxy</data>

<data title="Default Config Proxy" />

<data title="Default Config Proxy Bypass" />

</section>


</mainsection>


</speccydata>

 

[Jonathan_King]

Thanks for the specs. That may come in handy.

Could you please upload your dmps though? That's what we need to diagnose your problem. http://www.sevenforums.com/crash-lockup-debug-how/34900-1-novice-how-ask-help-bsod-problem.html

 

[Hollywood2]

i do not know what to do to provide the info you want i downloaded that iso and burned a disc i guess i'll see what it does?
sorry

 

[Hollywood2]

i hope this helps thank you

 

[Jonathan_King]

Copy the files in C:\Windows\Minidump to the desktop. Select all of them, right-click>send to>compressed folder.

Then upload the folder to this site. On your next post, you will see a paperclip icon in the edit bar.

 

[Hollywood2]

i hope this helps and thank you for the help, really thank you
dale

 

[zigzag3143]

i hope this helps and thank you for the help, really thank you
dale

HW

this one was caused by your video driver ( nvlddmkm.sys). I would scrape this off and install a fresh copy.

Let us know if you need help

Ken

Microsoft (R) Windows Debugger Version 6.11.0001.404 X86
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [D:\Users\K\Desktop\041810-22464-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: F:\Symbols
Executable search path is: 
Windows 7 Kernel Version 7600 MP (2 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7600.16539.amd64fre.win7_gdr.100226-1909
Machine Name:
Kernel base = 0xfffff800`03054000 PsLoadedModuleList = 0xfffff800`03291e50
Debug session time: Sun Apr 18 13:45:52.426 2010 (GMT-4)
System Uptime: 0 days 0:00:37.705
Loading Kernel Symbols
...............................................................
................................................................
............
Loading User Symbols
Loading unloaded module list
....
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 50, {fffff88030050464, 0, fffff880049bf686, 2}

Unable to load image \SystemRoot\system32\DRIVERS\nvlddmkm.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for nvlddmkm.sys
*** ERROR: Module load completed but symbols could not be loaded for nvlddmkm.sys

Could not read faulting driver name
Probably caused by : nvlddmkm.sys ( nvlddmkm+172686 )

Followup: MachineOwner
---------

1: 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: fffff88030050464, memory referenced.
Arg2: 0000000000000000, value 0 = read operation, 1 = write operation.
Arg3: fffff880049bf686, If non-zero, the instruction address which referenced the bad memory
    address.
Arg4: 0000000000000002, (reserved)

Debugging Details:
------------------


Could not read faulting driver name

READ_ADDRESS: GetPointerFromAddress: unable to read from fffff800032fc0e0
 fffff88030050464 

FAULTING_IP: 
nvlddmkm+172686
fffff880`049bf686 8b0488          mov     eax,dword ptr [rax+rcx*4]

MM_INTERNAL_CODE:  2

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

BUGCHECK_STR:  0x50

PROCESS_NAME:  csrss.exe

CURRENT_IRQL:  0

TRAP_FRAME:  fffff88002e717d0 -- (.trap 0xfffff88002e717d0)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=fffff88010000000 rbx=0000000000000000 rcx=0000000008014119
rdx=0000000000000001 rsi=0000000000000000 rdi=0000000000000000
rip=fffff880049bf686 rsp=fffff88002e71960 rbp=fffffa80051531b0
 r8=0000000000005c00  r9=0000000020050464 r10=fffffa80051531b0
r11=fffffa8002f11010 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei pl nz na pe nc
nvlddmkm+0x172686:
fffff880`049bf686 8b0488          mov     eax,dword ptr [rax+rcx*4] ds:0001:fffff880`30050464=????????
Resetting default scope

LAST_CONTROL_TRANSFER:  from fffff80003143832 to fffff800030c4600

STACK_TEXT:  
fffff880`02e71668 fffff800`03143832 : 00000000`00000050 fffff880`30050464 00000000`00000000 fffff880`02e717d0 : nt!KeBugCheckEx
fffff880`02e71670 fffff800`030c26ee : 00000000`00000000 fffffa80`051531b0 00000000`00000000 fffff800`03253888 : nt! ?? ::FNODOBFM::`string'+0x40f00
fffff880`02e717d0 fffff880`049bf686 : 00000000`00000000 fffff880`049eae70 fffffa80`018ecb00 fffffa80`02e96560 : nt!KiPageFault+0x16e
fffff880`02e71960 00000000`00000000 : fffff880`049eae70 fffffa80`018ecb00 fffffa80`02e96560 fffffa80`018ecb00 : nvlddmkm+0x172686


STACK_COMMAND:  kb

FOLLOWUP_IP: 
nvlddmkm+172686
fffff880`049bf686 8b0488          mov     eax,dword ptr [rax+rcx*4]

SYMBOL_STACK_INDEX:  3

SYMBOL_NAME:  nvlddmkm+172686

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nvlddmkm

IMAGE_NAME:  nvlddmkm.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  49b1201f

FAILURE_BUCKET_ID:  X64_0x50_nvlddmkm+172686

BUCKET_ID:  X64_0x50_nvlddmkm+172686

Followup: MachineOwner
---------

 

[Hollywood2]

sorry i am not very good at this, i used the microsoft iso i downloaded and came up with this i hope it helps thanks, dale


Microsoft (R) Windows Debugger Version 6.12.0002.633 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.

Loading Dump File [C:\Users\fcku\Desktop\041810-22464-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available
Symbol search path is: *** Invalid ***
****************************************************************************
* Symbol loading may be unreliable without a symbol search path. *
* Use .symfix to have the debugger choose a symbol path. *
* After setting your symbol path, use .reload to refresh symbol locations. *
****************************************************************************
Executable search path is:
*********************************************************************
* Symbols can not be loaded because symbol path is not initialized. *
* *
* The Symbol Path can be set by: *
* using the _NT_SYMBOL_PATH environment variable. *
* using the -y <symbol_path> argument when starting the debugger. *
* using .sympath and .sympath+ *
*********************************************************************
Unable to load image \SystemRoot\system32\ntoskrnl.exe, Win32 error 0n2
*** WARNING: Unable to verify timestamp for ntoskrnl.exe
*** ERROR: Module load completed but symbols could not be loaded for ntoskrnl.exe
Windows 7 Kernel Version 7600 MP (2 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7600.16539.amd64fre.win7_gdr.100226-1909
Machine Name:
Kernel base = 0xfffff800`03054000 PsLoadedModuleList = 0xfffff800`03291e50
Debug session time: Sun Apr 18 10:45:52.426 2010 (UTC - 7:00)
System Uptime: 0 days 0:00:37.705
*********************************************************************
* Symbols can not be loaded because symbol path is not initialized. *
* *
* The Symbol Path can be set by: *
* using the _NT_SYMBOL_PATH environment variable. *
* using the -y <symbol_path> argument when starting the debugger. *
* using .sympath and .sympath+ *
*********************************************************************
Unable to load image \SystemRoot\system32\ntoskrnl.exe, Win32 error 0n2
*** WARNING: Unable to verify timestamp for ntoskrnl.exe
*** ERROR: Module load completed but symbols could not be loaded for ntoskrnl.exe
Loading Kernel Symbols
...............................................................
................................................................
............
Loading User Symbols
Loading unloaded module list
....
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 50, {fffff88030050464, 0, fffff880049bf686, 2}
***** Kernel symbols are WRONG. Please fix symbols to do analysis.
*************************************************************************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!_KPRCB ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!KPRCB ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!_KPRCB ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!KPRCB ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!_KPRCB ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!_KPRCB ***
*** ***
*************************************************************************
Unable to load image \SystemRoot\system32\DRIVERS\nvlddmkm.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for nvlddmkm.sys
*** ERROR: Module load completed but symbols could not be loaded for nvlddmkm.sys
*************************************************************************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!_KPRCB ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!_KPRCB ***
*** ***
*************************************************************************
Probably caused by : nvlddmkm.sys ( nvlddmkm+172686 )
Followup: MachineOwner
---------
1: 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: fffff88030050464, memory referenced.
Arg2: 0000000000000000, value 0 = read operation, 1 = write operation.
Arg3: fffff880049bf686, If non-zero, the instruction address which referenced the bad memory
address.
Arg4: 0000000000000002, (reserved)
Debugging Details:
------------------
***** Kernel symbols are WRONG. Please fix symbols to do analysis.
*************************************************************************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!_KPRCB ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!KPRCB ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!_KPRCB ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!KPRCB ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!_KPRCB ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!_KPRCB ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!_KPRCB ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!_KPRCB ***
*** ***
*************************************************************************
ADDITIONAL_DEBUG_TEXT:
Use '!findthebuild' command to search for the target build information.
If the build information is available, run '!findthebuild -s ; .reload' to set symbol path and load symbols.
FAULTING_MODULE: fffff80003054000 nt
DEBUG_FLR_IMAGE_TIMESTAMP: 49b1201f
READ_ADDRESS: unable to get nt!MmSpecialPoolStart
unable to get nt!MmSpecialPoolEnd
unable to get nt!MmPoolCodeStart
unable to get nt!MmPoolCodeEnd
fffff88030050464
FAULTING_IP:
nvlddmkm+172686
fffff880`049bf686 8b0488 mov eax,dword ptr [rax+rcx*4]
MM_INTERNAL_CODE: 2
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
BUGCHECK_STR: 0x50
CURRENT_IRQL: 0
LAST_CONTROL_TRANSFER: from fffff80003143832 to fffff800030c4600
STACK_TEXT:
fffff880`02e71668 fffff800`03143832 : 00000000`00000050 fffff880`30050464 00000000`00000000 fffff880`02e717d0 : nt+0x70600
fffff880`02e71670 00000000`00000050 : fffff880`30050464 00000000`00000000 fffff880`02e717d0 00000000`00000002 : nt+0xef832
fffff880`02e71678 fffff880`30050464 : 00000000`00000000 fffff880`02e717d0 00000000`00000002 0005d1f6`0337fc7d : 0x50
fffff880`02e71680 00000000`00000000 : fffff880`02e717d0 00000000`00000002 0005d1f6`0337fc7d 00000000`00000000 : 0xfffff880`30050464

STACK_COMMAND: .bugcheck ; kb
FOLLOWUP_IP:
nvlddmkm+172686
fffff880`049bf686 8b0488 mov eax,dword ptr [rax+rcx*4]
SYMBOL_NAME: nvlddmkm+172686
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: nvlddmkm
IMAGE_NAME: nvlddmkm.sys
BUCKET_ID: WRONG_SYMBOLS
Followup: MachineOwner
---------
Log file could not be opened

 

[Hollywood2]

so delete everything nvidia? nvidia is not installed as we speak i am using vga drivers from windows.

 

[Hollywood2]

sAME THING blue screen lights up the room, says PAGE_FAULT_IN_NONPAGE_AREA NVLDDMKM.SYSANY OTHER SUGGESTION WILL BE APPRECIATED thanks,Hollywood2

 

[JMH]

Hollywood2,
Refer back to zigzag 3143's post please.
Note - visit the web site of the manufacturer of the hardware/program to get the latest drivers (DON'T use Windows Update or the Update driver function of Device Manager).
- if there are difficulties in locating them, post back with questions and someone will try and help you locate the appropriate program.
Thanks.
Jan.

 

[Hollywood2]

dmp zip

Thanks

 

[JMH]

Hollywood2,
Earlier on you were given advice re updating your video driver ( nvlddmkm.sys).
HAVE YOU DONE THIS YET?

***Note - visit the web site of the manufacturer of the hardware/program to get the latest drivers.
(DON'T use Windows Update or the Update driver function of Device Manager).***

 

[Hollywood2]

I deleted all nvidia and tried to install nvidia 196.34 it would not so i installed 179.48 and rebooted and you called it a normal boot, DirectX was back, i could fly again, machine felt normal for two hours and thats when i ran windows assessment tool and right back to BSOD
thanks

 

[Jonathan_King]

Keep looking for more drivers. Play around with different versions until you find one that works.

Also, please keep uploading your dmps as they come.