very frustrated new member

[mistersmiff]

Just joined. been learning a lot on the site. i plan to do a lot of studying on these forums.
I built my system almost 3 years ago, and it was rock solid on XP. Never a single BSOD. But since I clean-installed Win7, I've been getting random BSOD's. Gone through 3 or 4 diff video card drivers with no change. Very random. New to the SF Tool being used here. I ran it and had 40+ .dmp's. I only kept the last 5, since they all say the same thing (I think).

Thanks for the help in advance, and please be gentle with me.

 

[The Howling Wolves]

Look in Crashes and bugging area
Someone will be with you shortly.
Welcome mistermiff
View attachment 80594

 

[CarlTR6]

Welcome to the forum, mistermiff. I will take a look at your dmp file(s).

All but one dmp is reporting the stop error code, 4E. One dump reported an error code of 1A. Both of these codes point to memory errors and/or device driver problems.

STOP 0x0000004E: PFN_LIST_CORRUPT

Usual causes: Device driver, ?memory
BSOD Index

STOP 0x0000001A: MEMORY_MANAGEMENT

Usual causes: Device driver, memory, kernel

BSOD Index

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


Loading Dump File [C:\Users\Owner\Downloads\Seven Forums\062010-18860-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available
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`02a0f000 PsLoadedModuleList = 0xfffff800`02c4ce50
Debug session time: Sun Jun 20 21:19:28.257 2010 (GMT-4)
System Uptime: 0 days 7:03:11.192

*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

BugCheck 4E, {7, e17a, e14e, 0}

Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+16dc6 )

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

PFN_LIST_CORRUPT (4e)
Typically caused by drivers passing bad memory descriptor lists (ie: calling
MmUnlockPages twice with the same list, etc).  If a kernel debugger is
available get the stack trace.
Arguments:
Arg1: 0000000000000007, A driver has unlocked a page more times than it locked it
Arg2: 000000000000e17a, page frame number
Arg3: 000000000000e14e, current share count
Arg4: 0000000000000000, 0

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


BUGCHECK_STR:  0x4E_7

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

PROCESS_NAME:  svchost.exe

CURRENT_IRQL:  2

LAST_CONTROL_TRANSFER:  from fffff80002ae1949 to fffff80002a7f600

STACK_TEXT:  
fffff880`085f0228 fffff800`02ae1949 : 00000000`0000004e 00000000`00000007 00000000`0000e17a 00000000`0000e14e : nt!KeBugCheckEx
fffff880`085f0230 fffff800`02a6166c : 00000000`0000e17a 00000000`0000042c fffff8a0`032a91a8 fffff8a0`032a91a8 : nt! ?? ::FNODOBFM::`string'+0x16dc6
fffff880`085f0270 fffff800`02d67ea1 : fffffa80`07239c30 fffff6fc`40054c98 fffff8a0`00000002 00000000`00000000 : nt!MiValidateImagePages+0x3ac
fffff880`085f0310 fffff800`02d675b0 : ffffffff`ffffffff 00000000`00000001 fffff8a0`032af000 00000000`00000015 : nt!MiSwitchBaseAddress+0x61
fffff880`085f0340 fffff800`02d7b3ae : 00000000`00000004 00000000`01000000 00000000`00000000 00000000`00000000 : nt!MiRelocateImageAgain+0x100
fffff880`085f0390 fffff800`02d70b83 : fffff880`085f05f0 00000000`00000000 fffff880`085f0698 fffff880`085f05e8 : nt!MmCreateSection+0x302
fffff880`085f05a0 fffff800`02edd0e3 : 00000000`00000000 fffff8a0`0a77fde8 00000000`00000000 00000000`00000001 : nt!NtCreateSection+0x162
fffff880`085f0620 fffff800`02edd671 : 00000000`00000000 fffff8a0`0a77fde8 fffffa80`0674ba30 fffff880`00000060 : nt!PfpFileBuildReadSupport+0x163
fffff880`085f0710 fffff800`02ee578e : fffff8a0`00000000 fffff8a0`0000000c fffff8a0`00000044 00000000`00000000 : nt!PfpPrefetchFilesTrickle+0x121
fffff880`085f0810 fffff800`02ee6327 : 00000000`00000000 fffff880`085f0ca0 fffff880`085f0a08 fffff8a0`018a3060 : nt!PfpPrefetchRequestPerform+0x30e
fffff880`085f0960 fffff800`02ef28fe : fffff880`085f0a08 00000000`00000001 fffffa80`0708a1a0 00000000`00000000 : nt!PfpPrefetchRequest+0x176
fffff880`085f09d0 fffff800`02ef702e : 00000000`00000000 00000000`019cf580 00000000`0000004f fffffa80`064abb01 : nt!PfSetSuperfetchInformation+0x1ad
fffff880`085f0ab0 fffff800`02a7e853 : fffffa80`0413fa60 00000000`00000000 00000000`00000001 00000000`00000001 : nt!NtSetSystemInformation+0xb91
fffff880`085f0c20 00000000`77ba15aa : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
00000000`019cf558 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x77ba15aa


STACK_COMMAND:  kb

FOLLOWUP_IP: 
nt! ?? ::FNODOBFM::`string'+16dc6
fffff800`02ae1949 cc              int     3

SYMBOL_STACK_INDEX:  1

SYMBOL_NAME:  nt! ?? ::FNODOBFM::`string'+16dc6

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nt

IMAGE_NAME:  ntkrnlmp.exe

DEBUG_FLR_IMAGE_TIMESTAMP:  4b88cfeb

FAILURE_BUCKET_ID:  X64_0x4E_7_nt!_??_::FNODOBFM::_string_+16dc6

BUCKET_ID:  X64_0x4E_7_nt!_??_::FNODOBFM::_string_+16dc6

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

PFN_LIST_CORRUPT (4e)
Typically caused by drivers passing bad memory descriptor lists (ie:  calling
MmUnlockPages twice with the same list, etc).  If a kernel debugger is
available get the stack trace.
Arguments:
Arg1: 0000000000000007, A driver has unlocked a page more times than it  locked it
Arg2: 000000000000e17a, page frame number
Arg3: 000000000000e14e, current share count
Arg4: 0000000000000000, 0

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


BUGCHECK_STR:  0x4E_7

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

PROCESS_NAME:  svchost.exe

CURRENT_IRQL:  2

LAST_CONTROL_TRANSFER:  from fffff80002ae1949 to fffff80002a7f600

STACK_TEXT:  
fffff880`085f0228 fffff800`02ae1949 : 00000000`0000004e  00000000`00000007 00000000`0000e17a 00000000`0000e14e : nt!KeBugCheckEx
fffff880`085f0230 fffff800`02a6166c : 00000000`0000e17a  00000000`0000042c fffff8a0`032a91a8 fffff8a0`032a91a8 : nt! ??  ::FNODOBFM::`string'+0x16dc6
fffff880`085f0270 fffff800`02d67ea1 : fffffa80`07239c30  fffff6fc`40054c98 fffff8a0`00000002 00000000`00000000 :  nt!MiValidateImagePages+0x3ac
fffff880`085f0310 fffff800`02d675b0 : ffffffff`ffffffff  00000000`00000001 fffff8a0`032af000 00000000`00000015 :  nt!MiSwitchBaseAddress+0x61
fffff880`085f0340 fffff800`02d7b3ae : 00000000`00000004  00000000`01000000 00000000`00000000 00000000`00000000 :  nt!MiRelocateImageAgain+0x100
fffff880`085f0390 fffff800`02d70b83 : fffff880`085f05f0  00000000`00000000 fffff880`085f0698 fffff880`085f05e8 :  nt!MmCreateSection+0x302
fffff880`085f05a0 fffff800`02edd0e3 : 00000000`00000000  fffff8a0`0a77fde8 00000000`00000000 00000000`00000001 :  nt!NtCreateSection+0x162
fffff880`085f0620 fffff800`02edd671 : 00000000`00000000  fffff8a0`0a77fde8 fffffa80`0674ba30 fffff880`00000060 :  nt!PfpFileBuildReadSupport+0x163
fffff880`085f0710 fffff800`02ee578e : fffff8a0`00000000  fffff8a0`0000000c fffff8a0`00000044 00000000`00000000 :  nt!PfpPrefetchFilesTrickle+0x121
fffff880`085f0810 fffff800`02ee6327 : 00000000`00000000  fffff880`085f0ca0 fffff880`085f0a08 fffff8a0`018a3060 :  nt!PfpPrefetchRequestPerform+0x30e
fffff880`085f0960 fffff800`02ef28fe : fffff880`085f0a08  00000000`00000001 fffffa80`0708a1a0 00000000`00000000 :  nt!PfpPrefetchRequest+0x176
fffff880`085f09d0 fffff800`02ef702e : 00000000`00000000  00000000`019cf580 00000000`0000004f fffffa80`064abb01 :  nt!PfSetSuperfetchInformation+0x1ad
fffff880`085f0ab0 fffff800`02a7e853 : fffffa80`0413fa60  00000000`00000000 00000000`00000001 00000000`00000001 :  nt!NtSetSystemInformation+0xb91
fffff880`085f0c20 00000000`77ba15aa : 00000000`00000000  00000000`00000000 00000000`00000000 00000000`00000000 :  nt!KiSystemServiceCopyEnd+0x13
00000000`019cf558 00000000`00000000 : 00000000`00000000  00000000`00000000 00000000`00000000 00000000`00000000 : 0x77ba15aa


STACK_COMMAND:  kb

FOLLOWUP_IP: 
nt! ?? ::FNODOBFM::`string'+16dc6
fffff800`02ae1949 cc              int     3

SYMBOL_STACK_INDEX:  1

SYMBOL_NAME:  nt! ?? ::FNODOBFM::`string'+16dc6

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nt

IMAGE_NAME:  ntkrnlmp.exe

DEBUG_FLR_IMAGE_TIMESTAMP:  4b88cfeb

FAILURE_BUCKET_ID:  X64_0x4E_7_nt!_??_::FNODOBFM::_string_+16dc6

BUCKET_ID:  X64_0x4E_7_nt!_??_::FNODOBFM::_string_+16dc6

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

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


Loading Dump File [C:\Users\Owner\Downloads\Seven Forums\061810-28735-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Invalid directory table base value 0x0
Symbol search path is: SRV*c:\symbols*[URL="http://msdl.microsoft.com/download/symbols"]Symbol information[/URL]
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`02a5b000 PsLoadedModuleList = 0xfffff800`02c98e50
Debug session time: Fri Jun 18 19:26:59.217 2010 (GMT-4)
System Uptime: 2 days 18:57:46.121

*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 1A, {41201, fffff680002de6b0, ca3000000e17a867, fffffa80079d5420}

Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+13bb2 )

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

MEMORY_MANAGEMENT (1a)
    # Any other values for parameter 1 must be individually examined.
Arguments:
Arg1: 0000000000041201, The subtype of the bugcheck.
Arg2: fffff680002de6b0
Arg3: ca3000000e17a867
Arg4: fffffa80079d5420

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


BUGCHECK_STR:  0x1a_41201

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

CURRENT_IRQL:  0

LAST_CONTROL_TRANSFER:  from fffff80002b2b57e to fffff80002acb600

STACK_TEXT:  
fffff880`07d549b8 fffff800`02b2b57e : 00000000`0000001a 00000000`00041201 fffff680`002de6b0 ca300000`0e17a867 : nt!KeBugCheckEx
fffff880`07d549c0 fffff800`02a99ace : 00000000`00000010 00000000`00000282 fffff880`07d54a28 ca300000`0e17a867 : nt! ?? ::FNODOBFM::`string'+0x13bb2
fffff880`07d54a00 fffff800`02a9976a : fffffa80`079d5420 fffffa80`068ae930 fffffa80`068ae930 00000000`5bcd6000 : nt!MiQueryAddressState+0x2ae
fffff880`07d54a50 fffff800`02db3ac8 : fffff880`00000004 00000000`5bcd7000 fffffa80`079d5420 00000000`00000000 : nt!MiQueryAddressSpan+0xaa
fffff880`07d54ac0 fffff800`02aca853 : 00000000`00000344 fffffa80`076c8b60 00000000`00001f80 00000000`06f0e798 : nt!NtQueryVirtualMemory+0x386
fffff880`07d54bb0 00000000`772a00ea : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
00000000`06f0e778 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x772a00ea


STACK_COMMAND:  kb

FOLLOWUP_IP: 
nt! ?? ::FNODOBFM::`string'+13bb2
fffff800`02b2b57e cc              int     3

SYMBOL_STACK_INDEX:  1

SYMBOL_NAME:  nt! ?? ::FNODOBFM::`string'+13bb2

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nt

IMAGE_NAME:  ntkrnlmp.exe

DEBUG_FLR_IMAGE_TIMESTAMP:  4b88cfeb

FAILURE_BUCKET_ID:  X64_0x1a_41201_nt!_??_::FNODOBFM::_string_+13bb2

BUCKET_ID:  X64_0x1a_41201_nt!_??_::FNODOBFM::_string_+13bb2

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

I only posted your last two dmp files, one for each code.

In looking through your drivers, I see that you have AVG anti virus installed. AVG is known to cause BSOD, on some systems. I suggest that you uninstall it while trouble shooting using the uninstall tool > Info > Tool (32bit) - Tool (64 bit). If you have AVG Identity Protection installed, uninstall it also >Info > Tool[FONT=&quot]. I recommend that you install MSE and make sure Windows Firewall is turned on.

[/FONT] I also found the following old drivers. Windows 7 does not like older drivers. Update these drivers and recommend that you uninstall Razor.

[FONT=&quot]How To Find Drivers:[/FONT]

- search Google for the name of the driver
- compare the Google results with what's installed on your system to figure out which device/program it belongs to
- 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.
- - The most common drivers are listed on this page: Driver Reference
- - Driver manufacturer links are on this page: Drivers and Downloads

nvm62x64.sys Fri Oct 17 17:01:06 2008 (48F8FD12)
pcouffin.sys Tue Dec 05 09:39:30 2006 (457584A2)
Razerlow.sys Mon Nov 07 01:33:11 2005 (436EF527)
RTCore64.sys Wed May 25 02:39:12 2005 (42941D90)

After you have uninstalled AVG and updated these drivers, run your system and we will go from there. The next step will be to test your RAM.

 

[mistersmiff]

So what does that tell me in Engrish?:shock:

 

[ttran]

Wait for Carl Mistersmiff, he will be back to you, he is doing it!!! We will translate it for you for sure

 

[zigzag3143]

So what does that tell me in Engrish?:shock:

Easy It means you have a memory problem. To test your memory download a 3rd party app called memtestx86, burn it to cd, and run it for at least 7 passes.


Let us know the results


Ken

 

[CarlTR6]

So what does that tell me in Engrish?:shock:

You mean you didn't understand that? I hope it is now explained a little better. I was working on your dmps all that time. Make sure you refresh your page as I edited my comments.

Ken is right on target. A memory test is the next step.

 

[mistersmiff]

Okay, ladies. I ran Memtest ALLLLL night with zero erroes. whats my next step?

 

[CarlTR6]

Good job and thanks for reporting back. I am glad you have no RAM problems.

The next step is to update those drivers I listed above in post #3 if you have not done so and uninstall AVG. Let us know when you have done this.

Then run your computer and see if the BSOD's reoccur.

 

[Vector90Ash]

also... if you download a new driver, be sure to right-click, properties, UNBLOCK before you run the file, as this can (read 'does') cause BSOD.

 

[mistersmiff]

Well, I went searchin for new drivers. Could not find new replacement for nvm62x64.sys or pcouffin.sys. removed RTCore64.sys and updated Razerlow. tried downloading new drivers for motherboard and lost network access completely. I'll wait and see and keep you posted. Thx for the help. See you in the forums.....

 

[CarlTR6]

Thanks for reporting back. Do keep us informed.

 

[mistersmiff]

Well son of a ........ Woke up this a.m. and it had crashed overnite. i thought i had it fixed so i was doing a backup on my backup drive. not even sure if the backup completed. I'm including another SF dump rar with only the last 2 crashed: 1 before I found you fine gentlemen, and the 1 last nite after i change a couple of drivers. But there are no newer drivers for my mobo. What if that's the problem?

 

[ttran]

Please enable driver verifier:
http://www.sevenforums.com/crash-lo...-driver-verifier-identify-issues-drivers.html
Have you done memtest86 with at least 7 passess?

BugCheck 4E, {99, 5d35c, 2, 5d35a}

Probably caused by : memory_corruption ( nt!MiBadShareCount+4c )

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

BugCheck 4E, {7, e17a, e14e, 0}

Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+16dc6 )

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

 

[chev65]

Memory corruption can also be caused by a low voltage situation on the memory controller. Very common when upgrading to Windows 7.

 

[mistersmiff]

i did the Memtest with 7 passes and found 0 errors. can i do the verifier and ONLY select the couple of drivers I suspect? i dont want 2 get into a situation where i can even get back into the system. Quote:

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

My knees are knocking at the thought of it.

 

[ttran]

yes you can do that, please read the instruction. You can do system restore in case you can't get back into system (Safe mode)

~Tuan

 

[CarlTR6]

I would suggest you verify all third party (non Microsoft) drivers.

 

[Rothmclear]

Another option might be hard drive issues. I recently resolved some issues that looked like mem issues and yet it was actually a combination of some OS corruption and some lost allocated mem on hard drives. Trying running checkdisk. Also run "sfc /scannow" from an elevated command prompt.

 

[CarlTR6]

Another option might be hard drive issues. I recently resolved some issues that looked like mem issues and yet it was actually a combination of some OS corruption and some lost allocated mem on hard drives. Trying running checkdisk. Also run "sfc /scannow" from an elevated command prompt.

I agree with running checkdisk.

[FONT=&quot] CHKDSK /R /F:[/FONT]

Run CHKDSK /R /F from an elevated (Run as adminstrator) Command Prompt. Please do this for each hard drive on your system.
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.
[FONT=&quot] Double click on the Source column header.
Scroll down the list until you find the Chkdsk entry (wininit for Windows 7) (winlogon for XP). [/FONT]

Post your results.

Read this for more in depth hard drive checking.

HD Diagnostic