Bsod crash problem?Please help......

[vuqar1618]

Hi
Please help for my problem.I would be very appreciated.
My computer is Hp pavilion dv7

I use windows 7 ultimate 64 bit

I have Bsod (Blue screen) problem.
I already have cleaned my pc from registry errors,scanned my computer for viruses so no problem.
BSOD error code is 4e
i also have who crashed report

[FONT=Segoe UI, Arial]On Sat 1/7/2012 10:08:36 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\010712-16068-01.dmp
This was probably caused by the following module: [FONT=Segoe UI, Arial]ntoskrnl.exe[/FONT] (nt+0x7CC40)
Bugcheck code: 0x4E (0x7, 0x25F7E3, 0x1, 0x0)
Error: [FONT=Segoe UI, Arial]PFN_LIST_CORRUPT[/FONT]
file path: C:\Windows\system32\ntoskrnl.exe
product: [FONT=Segoe UI, Arial]Microsoft® Windows® Operating System[/FONT]
company: [FONT=Segoe UI, Arial]Microsoft Corporation[/FONT]
description: NT Kernel & System
Bug check description: This indicates that the page frame number (PFN) list is corrupted.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem. This might be a case of memory corruption. More often memory corruption happens because of software errors in buggy drivers, not because of faulty RAM modules.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time.
[/FONT]

[FONT=Segoe UI, Arial]On Sat 1/7/2012 10:08:36 AM GMT your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: [FONT=Segoe UI, Arial]netwns64.sys[/FONT] (NETwNs64+0x1DD918)
Bugcheck code: 0x4E (0x7, 0x25F7E3, 0x1, 0x0)
Error: [FONT=Segoe UI, Arial]PFN_LIST_CORRUPT[/FONT]
file path: C:\Windows\system32\drivers\netwns64.sys
product: [FONT=Segoe UI, Arial]Intel® Wireless WiFi Link Adapter[/FONT]
company: [FONT=Segoe UI, Arial]Intel Corporation[/FONT]
description: Intel® Wireless WiFi Link Driver
Bug check description: This indicates that the page frame number (PFN) list is corrupted.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem. This might be a case of memory corruption. More often memory corruption happens because of software errors in buggy drivers, not because of faulty RAM modules.
A third party driver was identified as the probable root cause of this system error. It is suggested you look for an update for the following driver: netwns64.sys (Intel® Wireless WiFi Link Driver, Intel Corporation).
Google query: [FONT=Segoe UI, Arial]netwns64.sys Intel Corporation PFN_LIST_CORRUPT[/FONT]


[/FONT]

[FONT=Segoe UI, Arial]On Mon 1/2/2012 2:27:21 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\010212-17690-01.dmp
This was probably caused by the following module: [FONT=Segoe UI, Arial]ntoskrnl.exe[/FONT] (nt+0x7CC40)
Bugcheck code: 0x3B (0xC000001D, 0xFFFFFA80082CCF30, 0xFFFFF8800BB42B70, 0x0)
Error: [FONT=Segoe UI, Arial]SYSTEM_SERVICE_EXCEPTION[/FONT]
file path: C:\Windows\system32\ntoskrnl.exe
product: [FONT=Segoe UI, Arial]Microsoft® Windows® Operating System[/FONT]
company: [FONT=Segoe UI, Arial]Microsoft Corporation[/FONT]
description: NT Kernel & System
Bug check description: This indicates that an exception happened while executing a routine that transitions from non-privileged code to privileged code.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time.
[/FONT]

Please help my PC report (Windows_NT6_BSOD_jcgriff2 folder & the PERFMON HTML file) is in this link

Download Pc report.rar for free on uploading.com

Please help!

 

[usasma]

Daemon Tools is known to cause BSOD's on some Win7 systems. Please uninstall the program and then use this free tool to ensure that the troublesome sptd.sys driver is removed from your system: DuplexSecure - FAQ - Remove 64 bit sptd.sys

Beyond that, I'd have to suspect either your networking drivers (wired and/or wireless). Please update these drivers from the PC Manufacturer's website.

If that doesn't stop the BSOD's, then please run Driver Verifier according to these instructions:

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/Win7 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 "Special Pool", "Force Pending I/O Requests" and "Low Resource Simulation" and click "Next"
- 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 wait for 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. If it doesn't crash for you, then let it run for at least 36 hours of continuous operation (an estimate on my part).

Reboot into Windows (after the crash) and turn off Driver 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:

Delete these registry keys to stop Driver Verifier from loading (works in XP, Vista, Win7):
        HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Session Manager\Memory Management\VerifyDrivers
        HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Session Manager\Memory Management\VerifyDriverLevel

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

BSOD BUGCHECK SUMMARY

[font=lucida console]
Loading Dump File [C:\Users\FUBAR\_jcgriff2_\dbug\__Kernel__\010712-16068-01.dmp]
Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506
Debug session time: Sat Jan  7 05:08:36.734 2012 (UTC - 5:00)
System Uptime: 0 days 1:01:18.340
Probably caused by : tcpip.sys ( tcpip!TcpCompleteTcbSend+40 )
BUGCHECK_STR:  0x4E_7
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  System
FAILURE_BUCKET_ID:  X64_0x4E_7_tcpip!TcpCompleteTcbSend+40
Bugcheck code 0000004E
Arguments 00000000`00000007 00000000`0025f7e3 00000000`00000001 00000000`00000000
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Loading Dump File [C:\Users\FUBAR\_jcgriff2_\dbug\__Kernel__\010212-17690-01.dmp]
Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506
Debug session time: Mon Jan  2 09:27:21.024 2012 (UTC - 5:00)
System Uptime: 0 days 0:51:58.273
Probably caused by : ntkrnlmp.exe ( nt!KiSystemServiceHandler+7c )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0x3B
PROCESS_NAME:  firefox.exe
FAILURE_BUCKET_ID:  X64_0x3B_nt!KiSystemServiceHandler+7c
Bugcheck code 0000003B
Arguments 00000000`c000001d fffffa80`082ccf30 fffff880`0bb42b70 00000000`00000000
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
  
  [/font]

 

[vuqar1618]

Daemon Tools is known to cause BSOD's on some Win7 systems. Please uninstall the program and then use this free tool to ensure that the troublesome sptd.sys driver is removed from your system: DuplexSecure - FAQ - Remove 64 bit sptd.sys

Beyond that, I'd have to suspect either your networking drivers (wired and/or wireless). Please update these drivers from the PC Manufacturer's website.

If that doesn't stop the BSOD's, then please run Driver Verifier according to these instructions:

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/Win7 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 "Special Pool", "Force Pending I/O Requests" and "Low Resource Simulation" and click "Next"
- 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 wait for 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. If it doesn't crash for you, then let it run for at least 36 hours of continuous operation (an estimate on my part).

Reboot into Windows (after the crash) and turn off Driver 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:

Delete these registry keys to stop Driver Verifier from loading (works in XP, Vista, Win7):
        HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Session Manager\Memory Management\VerifyDrivers
        HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Session Manager\Memory Management\VerifyDriverLevel

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

BSOD BUGCHECK SUMMARY

[font=lucida console]
Loading Dump File [C:\Users\FUBAR\_jcgriff2_\dbug\__Kernel__\010712-16068-01.dmp]
Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506
Debug session time: Sat Jan  7 05:08:36.734 2012 (UTC - 5:00)
System Uptime: 0 days 1:01:18.340
Probably caused by : tcpip.sys ( tcpip!TcpCompleteTcbSend+40 )
BUGCHECK_STR:  0x4E_7
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  System
FAILURE_BUCKET_ID:  X64_0x4E_7_tcpip!TcpCompleteTcbSend+40
Bugcheck code 0000004E
Arguments 00000000`00000007 00000000`0025f7e3 00000000`00000001 00000000`00000000
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Loading Dump File [C:\Users\FUBAR\_jcgriff2_\dbug\__Kernel__\010212-17690-01.dmp]
Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506
Debug session time: Mon Jan  2 09:27:21.024 2012 (UTC - 5:00)
System Uptime: 0 days 0:51:58.273
Probably caused by : ntkrnlmp.exe ( nt!KiSystemServiceHandler+7c )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0x3B
PROCESS_NAME:  firefox.exe
FAILURE_BUCKET_ID:  X64_0x3B_nt!KiSystemServiceHandler+7c
Bugcheck code 0000003B
Arguments 00000000`c000001d fffffa80`082ccf30 fffff880`0bb42b70 00000000`00000000
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
  
  [/font]

Thanks!