Help Please,I am desperate(Win 7 64 bit Random BSOD)

PoeticJustice · 09 Dec 2009

My Specs:
Gigabyte Ga p55 Ud5
Intel Core i7 2.80
Team 4 gb DDR3 1600 mhz
Thermaltake Toughpower 750 watt
Zotac Gtx 275 1792 mb
Razer Deathadder

1-I have run memtest all throught night no errors.
2-I applied Passmark Stress Test no errors
3-I have run Windows Memory Diagnostic Tool no errors
4-Tried Psu on another Pc no errors
5-I have run the diagnostic tool for Western Digital and scanned every bite for hours no errors
6-I have run verifier.exe
7-I have tried almost every possible drivers(Forceware for Nvidia, every version of realtek sound and network controllers

I installed windbg and symbol files for win7 rtm and set the symbol files path but it says I am not using the correct symbols, so I need to find out if a bad driver is causing this, my deathadder in verifier.exe seemed to be faulty.I uninstalled it but Bsods keeps on randomly, while surfing, extracting rar files, at random.I zipped the minidump files and uploaded, any help will be appreciated.......

Zippyshare.com - minidump.rar

Blue Screen Messages are like that:

Special_Memory_Pool_Detected
System_Service_Exception
Irq_Less_or_Equal
ntfs.sys
win2k.sys

I think I got every possible Bsod message,if I can't find out the reason I will turn back to Vista

I made a clean install and all my drivers are up to date....

zigzag3143 · 09 Dec 2009

PoeticJustice said:

My Specs:
Gigabyte Ga p55 Ud5
Intel Core i7 2.80
Team 4 gb DDR3 1600 mhz
Thermaltake Toughpower 750 watt
Zotac Gtx 275 1792 mb
Razer Deathadder

1-I have run memtest all throught night no errors.
2-I applied Passmark Stress Test no errors
3-I have run Windows Memory Diagnostic Tool no errors
4-Tried Psu on another Pc no errors
5-I have run the diagnostic tool for Western Digital and scanned every bite for hours no errors
6-I have run verifier.exe
7-I have tried almost every possible drivers(Forceware for Nvidia, every version of realtek sound and network controllers

I installed windbg and symbol files for win7 rtm and set the symbol files path but it says I am not using the correct symbols, so I need to find out if a bad driver is causing this, my deathadder in verifier.exe seemed to be faulty.I uninstalled it but Bsods keeps on randomly, while surfing, extracting rar files, at random.I zipped the minidump files and uploaded, any help will be appreciated.......

Zippyshare.com - minidump.rar

Blue Screen Messages are like that:

Special_Memory_Pool_Detected
System_Service_Exception
Irq_Less_or_Equal
ntfs.sys
win2k.sys

I think I got every possible Bsod message,if I can't find out the reason I will turn back to Vista

I made a clean install and all my drivers are up to date....

Hi and welcome

these two dmps were identical. both point to the video driver. Video driver should be updated.

Hope this helps

Ken J+

Code:

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


Loading Dump File [C:\Users\K\Desktop\112909-19718-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*d:\symbols*http://msdl.microsoft.com/download/symbols
Executable search path is: 
Windows 7 Kernel Version 7600 MP (8 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Machine Name:
Kernel base = 0xfffff800`0285f000 PsLoadedModuleList = 0xfffff800`02a9ce50
Debug session time: Sat Nov 28 19:00:22.795 2009 (GMT-5)
System Uptime: 0 days 0:04:07.810
Loading Kernel Symbols
...............................................................
................................................................
...............
Loading User Symbols
Loading unloaded module list
....
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck D1, {0, 2, 0, fffff880048ce8cf}

Unable to load image \SystemRoot\system32\DRIVERS\nvlddmkm.sys, Win32 error 0n2
*** ERROR: Module load completed but symbols could not be loaded for nvlddmkm.sys
Probably caused by : nvlddmkm.sys ( nvlddmkm+868cf )

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

0: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

DRIVER_IRQL_NOT_LESS_OR_EQUAL (d1)
An attempt was made to access a pageable (or completely invalid) address at an
interrupt request level (IRQL) that is too high.  This is usually
caused by drivers using improper addresses.
If kernel debugger is available get stack backtrace.
Arguments:
Arg1: 0000000000000000, memory referenced
Arg2: 0000000000000002, IRQL
Arg3: 0000000000000000, value 0 = read operation, 1 = write operation
Arg4: fffff880048ce8cf, address which referenced memory

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


READ_ADDRESS: GetPointerFromAddress: unable to read from fffff80002b070e0
 0000000000000000 

CURRENT_IRQL:  2

FAULTING_IP: 
nvlddmkm+868cf
fffff880`048ce8cf 0f8452010000    je      nvlddmkm+0x86a27 (fffff880`048cea27)

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

BUGCHECK_STR:  0xD1

PROCESS_NAME:  System

TRAP_FRAME:  fffff80000b9c380 -- (.trap 0xfffff80000b9c380)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=0000000000000000 rbx=0000000000000000 rcx=0000000000000000
rdx=0000000000000000 rsi=0000000000000000 rdi=0000000000000000
rip=fffff880048ce8cf rsp=fffff80000b9c510 rbp=fffffa8004e68000
 r8=fffffa8004df01a0  r9=00000000002ac63d r10=0000000000000000
r11=0000000029727f69 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei pl zr na po nc
nvlddmkm+0x868cf:
fffff880`048ce8cf 0f8452010000    je      nvlddmkm+0x86a27 (fffff880`048cea27) [br=1]
Resetting default scope

LAST_CONTROL_TRANSFER:  from fffff800028d0469 to fffff800028d0f00

STACK_TEXT:  
fffff800`00b9c238 fffff800`028d0469 : 00000000`0000000a 00000000`00000000 00000000`00000002 00000000`00000000 : nt!KeBugCheckEx
fffff800`00b9c240 fffff800`028cf0e0 : fffff880`03167180 fffff880`04848000 00000000`002ac63d 00000000`00000000 : nt!KiBugCheckDispatch+0x69
fffff800`00b9c380 fffff880`048ce8cf : 00000000`002ac63d fffff800`00b9c618 fffff800`00000007 fffff800`00b9c600 : nt!KiPageFault+0x260
fffff800`00b9c510 00000000`002ac63d : fffff800`00b9c618 fffff800`00000007 fffff800`00b9c600 00000000`00000000 : nvlddmkm+0x868cf
fffff800`00b9c518 fffff800`00b9c618 : fffff800`00000007 fffff800`00b9c600 00000000`00000000 00000000`002ac63d : 0x2ac63d
fffff800`00b9c520 fffff800`00000007 : fffff800`00b9c600 00000000`00000000 00000000`002ac63d fffff800`02a49e80 : 0xfffff800`00b9c618
fffff800`00b9c528 fffff800`00b9c600 : 00000000`00000000 00000000`002ac63d fffff800`02a49e80 fffff800`02a4c080 : 0xfffff800`00000007
fffff800`00b9c530 00000000`00000000 : 00000000`002ac63d fffff800`02a49e80 fffff800`02a4c080 fffff800`02a57c40 : 0xfffff800`00b9c600


STACK_COMMAND:  kb

FOLLOWUP_IP: 
nvlddmkm+868cf
fffff880`048ce8cf 0f8452010000    je      nvlddmkm+0x86a27 (fffff880`048cea27)

SYMBOL_STACK_INDEX:  3

SYMBOL_NAME:  nvlddmkm+868cf

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nvlddmkm

IMAGE_NAME:  nvlddmkm.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  4a0c8387

FAILURE_BUCKET_ID:  X64_0xD1_nvlddmkm+868cf

BUCKET_ID:  X64_0xD1_nvlddmkm+868cf

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

PoeticJustice · 09 Dec 2009

Thank you very much for your instant reply and can you please tell me why I can't open minidump files even though I installed Win7 rtm symbol packages and set the symbol files path in windbg.....

Which Nvidia Driver do you recommend because including official drivers and forceware drivers I tried all of them but Bsods go on...

Thank you again....

usasma · 09 Dec 2009

How to open minidump files: WinDbg Analysis Report

Use the latest, WHQL certified GeForce video driver for your OS.

The Special_Memory_Pool_Detected error was not included in the dumps that you uploaded. Please upload the entire contents of the C:\Windows\Minidump folder.

Please run Driver Verifier again, using these settings/actions exactly as written:

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

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

Then, here's the procedure:
- Go to Start and type in "verifier" (without the quotes) and press Enter
- Select "Create custom settings (for code developers)" and click "Next"
- Select "Select individual settings from a full list" and click "Next"
- Select everything EXCEPT FOR "Low Resource Simulation" and click "Next"
- Select "Automatically select unsigned drivers" and click "Next"
If no drivers show up, then select "Select driver names from a list" and click "Next"
Then select all drivers NOT provided by Microsoft and click "Next"
- Select "Finish" on the next page.

Reboot the system and waitfor it to crash to the Blue Screen. Continue to use your system normally, and if you know what causes the crash, do that repeatedly. The objective here is to get the system to crash because Driver Verifier is stressing the drivers out.

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

If you can't get into Windows because it crashes too soon, try it in Safe Mode.
If you can't get into Safe Mode, try using System Restore from your installation DVD to set the system back to the previous restore point that you created.
If that doesn't work, post back and we'll have to see about fixing the registry entry off-line.

More info on this at this link: Using Driver Verifier to identify issues with Windows drivers for advanced users

PoeticJustice · 10 Dec 2009

I tried that ran verifier.exe and exactly did as you described.I restarted and I watched "Windows is starting" for 15 minutes and restarted again.This time, I could log into Windows and went into "Computer Management" There were two critical errors "Kernel Power 41" but in "Windows" folder there were no "Minidump" folder.And I didn't get any bluescreens.May be when windows didn't start it gave the bsod without a blue screen.I can't see what is happening I ran all the possible tests to prove that no hardware is defected and I tried every possible driver, so they say Windows 7 is the best ever, I had never seen a BSOD in Xp or Vista so let's discuss which one is the best....

Thanks for your reply if I get a Bsod and if windows generates dump files I will ask assistance again.Thanks in advance....

After a few restart tries I got a blue screen on start up, here is the minidump file:

http://www8.zippyshare.com/v/78245057/file.html

And on other start up, after I have seen the desktop BSOD appeared:

PAGE_FAULT_IN_NON_PAGED_AREA and that is the minidump:

http://www34.zippyshare.com/v/44713935/file.html

And this is the last one:
http://www30.zippyshare.com/v/7237359/file.html

zigzag3143 · 10 Dec 2009

PoeticJustice said:

Thank you very much for your instant reply and can you please tell me why I can't open minidump files even though I installed Win7 rtm symbol packages and set the symbol files path in windbg.....

Which Nvidia Driver do you recommend because including official drivers and forceware drivers I tried all of them but Bsods go on...

Thank you again....

PJ

there are many reasons why you might not be able to open the minidump files. What is the path you use for the symbol directories?

It should spefiy both local pathes and remote in case a sysbol that is nec is not on your machine.

Ken J+

reghakr · 10 Dec 2009

For now, go to Start > Run, and type cmd. Now type sfc /scannow

This will scan for currupted files

It may be the win32k.sys file that's corrupted

PoeticJustice · 10 Dec 2009

I tried and it says I must be an admin running a sfc console, do I need to say that that is a home computer and I am the only user as an admin...All those must be a kind of joke and also Windbg says I don't have permission to open the dump files, but when I right click on permissions tab my username is listed, that must a kind of joke....

Can someone please analyse the dump files in my previous message cause I am about to crash my new Pc into pieces and will swear not to touch a computer again, I have never felt so desperate before, I made a new system, paid a lot of money and I can't do anything because of those problems....

reghakr · 10 Dec 2009

It may have something to do with the User Account Control..Just temporarily, go to Control Panel > User Accounts click the Change Use Account control setting and move the slider down to never notify

Take owne ship of he file, not just check and see i you name appears.

I could never understand why some people recommend running at an elevated command prompt. I have never had that message on any windows 7 installation,.

I don't remember the proper way, but use Windows Explorer an navigate ti the C:\windows\System32 directory. locate cmd,exe, right-click an choose Run a Administrator

That should get you in to run sfc /cannow.

usasma · 11 Dec 2009

Well this is just grand! 3 Verifier enabled memory dumps and they can't agree on what the problem is!
It's either hard drive or network

First, please disable Driver Verifier by deleting the current settings.
Then reboot
Then setup Driver Verifier again, this time selecting ONLY the Microsoft drivers
Then run Driver Verifier again.

I'd expect that nothing will change, but we've gotta take a look at it to be sure.
I also wonder if this will point us to a hardware failure rather than a driver issue.

In the meantime, please try this stuff:

CHKDSK /R
Run CHKDSK /R from an elevated (Run as adminstrator) Command Prompt.
When it tells you it can't do it right now - and asks you if you'd like to do it at the next reboot - answer Y (for Yes) and press Enter. Then reboot and let the test run. It may take a while for it to run, but keep an occasional eye on it to see if it generates any errors. See "CHKDSK LogFile" below in order to check the results of the test.

Elevated Command Prompt
Go to Start and type in "cmd.exe" (without the quotes)
At the top of the Search Box, right click on Cmd.exe and select "Run as administrator"

CHKDSK LogFile
Go to Start and type in "eventvwr.msc" (without the quotes) and press Enter
Expand the Windows logs heading, then select the Application log file entry.
Double click on the Source column header.
Scroll down the list until you find the Chkdsk entry.
Copy/paste the results into your next post.

Conduct a free, hard drive diagnostic: HD Diagnostic

Download the latest version of your networking drivers
Uninstall the currently installed network drivers
Install the freshly downloaded drivers
Test to see if you get further BSOD's