Multiple BSOD

DW8864 · 02 May 2011

For a week or so now my custom build pc has been crashing and giving me multiple BSOD. I've tried reinstalling windows and ran a memory check, the memory seemed fine and reinstalling did not fix my problem.

I followed the instructions and attached my system health files, though all not of the dmp files are included because I use ccleaner.

Any help would be appreciated.

mgorman87 · 02 May 2011

Your system date changed from 5/2 to 5/9. I would check that out. I also noticed timeouts while you were trying to connect to sites. Are you having network issues that you notice?

Code:

Event[13455]:
  Log Name: System
  Source: Ntfs
  Date: 2011-04-25T17:14:24.685
  Event ID: 55
  Task: N/A
  Level: Error
  Opcode: N/A
  Keyword: Classic
  User: N/A
  User Name: N/A
  Computer: Damon-PC
  Description: 
The file system structure on the disk is corrupt and unusable. Please run the chkdsk utility on the volume \Device\HarddiskVolume2.

Run disk check on your drives - Disk Check

Enable driver verifier - Driver Verifier - Enable and Disable

Please run these tests and report back the results
1. Memtest86 - Run for 7-8 passes - RAM - Test with Memtest86+
2. Prime95 - Run all three tests for 3-4 hours each or until fail - https://www.sevenforums.com/tutorials...t-prime95.html
3. Hard drive scan usings SeaTools - SeaTools for Windows | Seagate - Both long and short tests

BSOD BUGCHECK SUMMARY

Code:


Built by: 7601.17514.amd64fre.win7sp1_rtm.101119-1850
Debug session time: Mon May  2 11:08:54.272 2011 (UTC - 4:00)
System Uptime: 0 days 0:06:02.427
*** WARNING: Unable to verify timestamp for win32k.sys
*** ERROR: Module load completed but symbols could not be loaded for win32k.sys
Probably caused by : Pool_Corruption ( nt!ExDeferredFreePool+cbb )
BUGCHECK_STR:  0x19_3
PROCESS_NAME:  WinSAT.exe
FAILURE_BUCKET_ID:  X64_0x19_3_nt!ExDeferredFreePool+cbb
BiosReleaseDate = 12/22/2010
SystemManufacturer = System manufacturer
SystemProductName = System Product Name
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7601.17514.amd64fre.win7sp1_rtm.101119-1850
Debug session time: Mon May  2 10:59:54.861 2011 (UTC - 4:00)
System Uptime: 0 days 0:02:34.016
Probably caused by : ntkrnlmp.exe ( nt!CcAcquireByteRangeForWrite+5c0 )
BUGCHECK_STR:  0x50
PROCESS_NAME:  System
FAILURE_BUCKET_ID:  X64_0x50_nt!CcAcquireByteRangeForWrite+5c0
BiosReleaseDate = 12/22/2010
SystemManufacturer = System manufacturer
SystemProductName = System Product Name
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``

DW8864 · 11 May 2011

I ran all tests but none of them found any errors. I reinstalled windows 7 and it has been seemingly stable for a few days. But there was one random bsod and I will post the minidump file.

Any assistance would be appreciated.

mgorman87 · 12 May 2011

No minidump was in your report. I did see the bugcheck in your event logs

Code:

STOP 0x0000004E: PFN_LIST_CORRUPT 


 Usual causes:  Device driver, ?memory

Cause

This error is typically caused by a driver passing a bad memory descriptor 
list. For example, the driver might have called MmUnlockPages twice
with the same list.If a kernel debugger is available, examine the stack trace.

If you are still having problems then enable driver verifier
Driver Verifier - Enable and Disable