BSOD

I am getting BSOSs more frequently that is making my pc unusable. I have attached the latest .dmp created. I would like to know if someone could help me find what is causing the BSODs.

Thank you

Edit:I tried attaching the .dmp file but I was unable to. I have uploaded it to google docs, I hope this is ok: https://docs.google.com/open?id=0B3EFAMxyI1ASUmYwZmdYWUhVcEk

I have been looking at other people with BSOD and have provided more information:

Here are my dump files:

==================================================
Dump File : 042312-23228-01.dmp
Crash Time : 4/23/2012 6:02:36 PM
Bug Check String : PFN_LIST_CORRUPT
Bug Check Code : 0x0000004e
Parameter 1 : 00000000`00000002
Parameter 2 : 00000000`0004510c
Parameter 3 : 00000000`000bfe8f
Parameter 4 : 00000000`00000001
Caused By Driver : hal.dll
Caused By Address : hal.dll+7b7f
File Description :
Product Name :
Company :
File Version :
Processor : x64
Crash Address : ntoskrnl.exe+7cc40
Stack Address 1 :
Stack Address 2 :
Stack Address 3 :
Computer Name :
Full Path : C:\Windows\Minidump\042312-23228-01.dmp
Processors Count : 2
Major Version : 15
Minor Version : 7601
Dump File Size : 274,416
==================================================

==================================================
Dump File : 042112-31543-01.dmp
Crash Time : 4/21/2012 10:31:18 PM
Bug Check String : MEMORY_MANAGEMENT
Bug Check Code : 0x0000001a
Parameter 1 : 00000000`00041790
Parameter 2 : fffffa80`01ff2d80
Parameter 3 : 00000000`0000ffff
Parameter 4 : 00000000`00000000
Caused By Driver : ntoskrnl.exe
Caused By Address : ntoskrnl.exe+7cc40
File Description : NT Kernel & System
Product Name : Microsoft® Windows® Operating System
Company : Microsoft Corporation
File Version : 6.1.7601.17640 (win7sp1_gdr.110622-1506)
Processor : x64
Crash Address : ntoskrnl.exe+7cc40
Stack Address 1 :
Stack Address 2 :
Stack Address 3 :
Computer Name :
Full Path : C:\Windows\Minidump\042112-31543-01.dmp
Processors Count : 2
Major Version : 15
Minor Version : 7601
Dump File Size : 274,472
==================================================

==================================================
Dump File : 042112-32276-01.dmp
Crash Time : 4/21/2012 7:25:29 PM
Bug Check String : PFN_LIST_CORRUPT
Bug Check Code : 0x0000004e
Parameter 1 : 00000000`00000002
Parameter 2 : 00000000`000b6f74
Parameter 3 : 00000000`000bfe8f
Parameter 4 : 00000000`00000001
Caused By Driver : ntoskrnl.exe
Caused By Address : ntoskrnl.exe+7cc40
File Description : NT Kernel & System
Product Name : Microsoft® Windows® Operating System
Company : Microsoft Corporation
File Version : 6.1.7601.17640 (win7sp1_gdr.110622-1506)
Processor : x64
Crash Address : ntoskrnl.exe+7cc40
Stack Address 1 :
Stack Address 2 :
Stack Address 3 :
Computer Name :
Full Path : C:\Windows\Minidump\042112-32276-01.dmp
Processors Count : 2
Major Version : 15
Minor Version : 7601
Dump File Size : 274,416
==================================================

==================================================
Dump File : 042112-21964-01.dmp
Crash Time : 4/21/2012 2:46:51 PM
Bug Check String : PFN_LIST_CORRUPT
Bug Check Code : 0x0000004e
Parameter 1 : 00000000`00000002
Parameter 2 : 00000000`0004c991
Parameter 3 : 00000000`000bfe8f
Parameter 4 : 00000000`00000001
Caused By Driver : Ntfs.sys
Caused By Address : Ntfs.sys+ee95
File Description :
Product Name :
Company :
File Version :
Processor : x64
Crash Address : ntoskrnl.exe+7cc40
Stack Address 1 :
Stack Address 2 :
Stack Address 3 :
Computer Name :
Full Path : C:\Windows\Minidump\042112-21964-01.dmp
Processors Count : 2
Major Version : 15
Minor Version : 7601
Dump File Size : 274,416
==================================================

==================================================
Dump File : 042012-29515-01.dmp
Crash Time : 4/20/2012 4:40:49 PM
Bug Check String : MEMORY_MANAGEMENT
Bug Check Code : 0x0000001a
Parameter 1 : 00000000`00005003
Parameter 2 : fffff700`01080000
Parameter 3 : 00000000`00002186
Parameter 4 : 00002187`0010430c
Caused By Driver : win32k.sys
Caused By Address : win32k.sys+c7341
File Description :
Product Name :
Company :
File Version :
Processor : x64
Crash Address : ntoskrnl.exe+7cc40
Stack Address 1 :
Stack Address 2 :
Stack Address 3 :
Computer Name :
Full Path : C:\Windows\Minidump\042012-29515-01.dmp
Processors Count : 2
Major Version : 15
Minor Version : 7601
Dump File Size : 274,416
==================================================

==================================================
Dump File : 042012-29905-01.dmp
Crash Time : 4/20/2012 3:00:46 PM
Bug Check String : KMODE_EXCEPTION_NOT_HANDLED
Bug Check Code : 0x0000001e
Parameter 1 : ffffffff`c000001d
Parameter 2 : fffffa80`083f2de9
Parameter 3 : 00000000`00000000
Parameter 4 : fffff800`02c48e00
Caused By Driver : ntoskrnl.exe
Caused By Address : ntoskrnl.exe+7cc40
File Description : NT Kernel & System
Product Name : Microsoft® Windows® Operating System
Company : Microsoft Corporation
File Version : 6.1.7601.17640 (win7sp1_gdr.110622-1506)
Processor : x64
Crash Address : ntoskrnl.exe+7cc40
Stack Address 1 :
Stack Address 2 :
Stack Address 3 :
Computer Name :
Full Path : C:\Windows\Minidump\042012-29905-01.dmp
Processors Count : 2
Major Version : 15
Minor Version : 7601
Dump File Size : 274,416
==================================================

==================================================
Dump File : 041812-59077-01.dmp
Crash Time : 4/18/2012 11:03:37 PM
Bug Check String : PFN_LIST_CORRUPT
Bug Check Code : 0x0000004e
Parameter 1 : 00000000`00000099
Parameter 2 : 00000000`0008a93c
Parameter 3 : 00000000`00000002
Parameter 4 : 00000000`0008a8f8
Caused By Driver : win32k.sys
Caused By Address : win32k.sys+8ce2c
File Description :
Product Name :
Company :
File Version :
Processor : x64
Crash Address : ntoskrnl.exe+7cc40
Stack Address 1 :
Stack Address 2 :
Stack Address 3 :
Computer Name :
Full Path : C:\Windows\Minidump\041812-59077-01.dmp
Processors Count : 2
Major Version : 15
Minor Version : 7601
Dump File Size : 274,416
==================================================

==================================================
Dump File : 041312-42525-01.dmp
Crash Time : 4/13/2012 9:07:58 PM
Bug Check String : PAGE_FAULT_IN_NONPAGED_AREA
Bug Check Code : 0x00000050
Parameter 1 : ffffffff`ffffffd0
Parameter 2 : 00000000`00000001
Parameter 3 : fffff800`02a976a3
Parameter 4 : 00000000`00000000
Caused By Driver : ntoskrnl.exe
Caused By Address : ntoskrnl.exe+7cc40
File Description : NT Kernel & System
Product Name : Microsoft® Windows® Operating System
Company : Microsoft Corporation
File Version : 6.1.7601.17640 (win7sp1_gdr.110622-1506)
Processor : x64
Crash Address : ntoskrnl.exe+7cc40
Stack Address 1 :
Stack Address 2 :
Stack Address 3 :
Computer Name :
Full Path : C:\Windows\Minidump\041312-42525-01.dmp
Processors Count : 2
Major Version : 15
Minor Version : 7601
Dump File Size : 274,416
==================================================

And here is my speccy snapshot: http://speccy.piriform.com/results/15dmBm3m7vgB1ELf6xGaNSB

Hi Murph -
Just for a quick try there are 2 things to try -

First go to Device Manager and look for any items with ( ! or ? ) beside them, and try to update the drivers (ask if not sure) -
Next - Only as a guess - Can you remove your ESET Antivirus for a few days and just use Microsoft Security Essentials as a replacement - Direct MSE link

Someone else will add to this later for you -

Thank You -

Yup, I check and there are three devices listed under "Other Devices"

1. Biometric Coprocessor (This is the fingerprint reader that i don't use)
2. Mass Storage Controller
3. Unknown device

I can find the driver for the 1st device, but I don't know where to find the drivers for the last 2 devices, nor do I know what those devices are.

As for removing ESET, i would rather right now, but I will if it is absolutely necessary.

Ok On Device Manger Right clcik on Mass Storage and select update Driver software and see if windows can determine the driver for the missing devices.

The BSOD are related to Memory

Run Memory x86 http://www.sevenforums.com/tutorials/105647-ram-test-memtest86.html This process will check your Ram.

you can let it go all night or If there is no faults before 10 percent your ram is usually fine.

Ran it 100% last night, no errors.

I tried finding a driver for each of the devices with a "?" next to them, windows couldn't find a driver for any of them.

EDIT: I went to toshiba's driver page and manually downloaded the drivers, and now the only device with a "?" next to it is the device named "unknown device". So thats 2 down out of 3

As per coxchris, many of these PFN_LIST_CORRUPT items are memory related, but Memtest usually finds something.
The other reason could often be the missing drivers that you have mentioned.
Can you also try to post a Screen shot of the Unknown Device in device manager -

When was your last BSOD and can you list it from Blue Screen View please -

Thanks -

...
==================================================
Dump File : 042312-23228-01.dmp
Crash Time : 4/23/2012 6:02:36 PM
Bug Check String : PFN_LIST_CORRUPT
Bug Check Code : 0x0000004e
Parameter 1 : 00000000`00000002
Parameter 2 : 00000000`0004510c
Parameter 3 : 00000000`000bfe8f
Parameter 4 : 00000000`00000001
Caused By Driver : hal.dll
Caused By Address : hal.dll+7b7f
File Description :
Product Name :
Company :
File Version :
Processor : x64
Crash Address : ntoskrnl.exe+7cc40
Stack Address 1 :
Stack Address 2 :
Stack Address 3 :
Computer Name :
Full Path : C:\Windows\Minidump\042312-23228-01.dmp
Processors Count : 2
Major Version : 15
Minor Version : 7601
Dump File Size : 274,416
==================================================
...

I think we have a good case for collecting some more information about what might be going on here. I had a look at the dump that you did upload, and I would like to have a look at a few more.

Please follow the instructions: BSOD Posting Instructions: Windows 7 - Vista

(Note: When you run BSOD_Windows7_Vista_v2.64_jcgriff2_.exe, it will also run autoruns.exe ... and both need to be in the same location!)
... with one exception in the following line:

• "4. Zip up the entire output folder + PERFMON and attach the zip file to your next post."

The BC forums will allow a total attachment size of only 512 kb (and what you need to attach will exceed this limit). Please upload the zip file to a file sharing website of your choice and and post a link to it in this thread so that we can access your uploaded zip file. I will have a look at the contained information and see if I can shed some light on your BSOD issue.

See the suggestions in the following links for recommendations on file sharing websites:

• http://lifehacker.com/388284/best-online-file-sharing-services
• http://www.hongkiat.com/blog/15-great-free-online-file-sharing-alternatives/
• http://www.smashingapps.com/2008/08/28/5-best-free-file-hosting-services-to-store-your-files.html

Please Publish a Snapshot using Speccy, and post a link to it in this thread. Already done!

Please download MiniToolBox, save it to your desktop and run it.

• Checkmark the following checkboxes:
  
  • List Installed Programs
• Click Go.
  When the scan is finished, a text file will open in a Notepad window.
• Copy the entire contents of the Notepad window, and paste in your reply.
  (Result.txt will be saved in the same directory the tool is run.)

Output folder + PERFMON: https://docs.google.com/open?id=0B3EFAMxyI1ASSHdqSlhXM1pSNkE

· OS - Windows 7
· x64
· What was original installed OS on system: Windows Vista Ultimate 32bit
· OEM
· Age of system (hardware): Approx. 2006
· Age of OS installation - have you re-installed the OS: A month - installed windows 7 on first try.

· CPU: speccy
· Video Card: speccy
· MotherBoard: speccy
· Power Supply - brand & wattage: speccy

· System Manufacturer: speccy
· Exact model number (if laptop, check label on bottom): speccy

EDIT: I ran driver verifier and my computer did not BSOD, so I believe that is all I have to do for that step (correct me if I'm wrong).

Thanks. Give me a few hours and I will get back to you.

EDIT: I ran driver verifier and my computer did not BSOD, so I believe that is all I have to do for that step (correct me if I'm wrong).

Re: Driver Verifier
If you have enabled DV, then leave the computer running for the next 36 hours. It doesn't matter whether you are using the computer doing your normal activity or not using it at all. If the system crashes, zip up the minidump that is produced and attach the .zip file to a reply.

If the computer does not crash during the 36 hours with DV running, then turn DV off: It will be of no use. We are looking for a VERIFIER_ENABLED crash dump: Anything else is not likely to be of much use.

*** Do not forget to turn DV off when you have finished with it! ***

BSOD-ed just now, here is the zipped up dump:

Unfortunately, the crash dump is not useful: The VERIFIER_ENABLED minidump has flagged a Windows system file (ataport.sys) which is unlikely to be the actual cause of the problem.

I spent some time last night, wading through the information that you supplied. Taking into consideration that this Windows installation is barely 1 month old, there is far too much evidence in the event logs of file corruption, application hangs and crashes, failed updates etc. etc. to persist with any further investigation in the hope of creating a sustainable fully functioning system. I suggest starting again with a fresh installation of Windows performed in the correct manner after thoroughly checking the laptop's hardware along with a BIOS update if available, and hopefully get a better result this time around.

The laptop originally came with Vista 32-bit on it and you installed Windows Ultimate 64-bit a month ago:

• Do you have a genuine retail Microsoft Windows Ultimate 64-bit installation disk purchased for this purpose?

What is the complete model number of this laptop?

• Look at the label on the underside to get the full details.
  TOSHIBA Satellite P105-xxxx?

========================
BSOD BUGCHECK SUMMARY
................................................................
Loading Dump File [C:\CactusIsland\Murph236_BC\042712-31137-01\042712-31137-01.dmp]
Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506
Debug session time: Fri Apr 27 14:51:38.373 2012 (UTC + 10:00)
System Uptime: 0 days 0:03:23.557
Probably caused by : ataport.SYS ( ataport!GenPnpRefPdoExtensionWithTag+4f )
DRIVER_IRQL_NOT_LESS_OR_EQUAL (d1)
DEFAULT_BUCKET_ID: VERIFIER_ENABLED_VISTA_MINIDUMP
BUGCHECK_STR: 0xD1
PROCESS_NAME: svchost.exe
FAILURE_BUCKET_ID: X64_0xD1_VRF_ataport!GenPnpRefPdoExtensionWithTag+4f
Bugcheck code 000000D1
Arguments 00000000`00100054 00000000`00000002 00000000`00000000 fffff880`0114c977
................................................................