Custom built PC has BSOD after a year with no issues

[jase888]

I built a custom built PC about a year ago, it worked perfect and had no issues. It was used more as a media server and to share documents and backup pictures, so it was always on pretty much. I made sure it was well cooled and it never had any issues.

I reformat it as it seemed to be restarting itself and I thought a reformat and clean up of all the rubbish on it would do it good. Since reformatting it seems to have a BSOD issue, it is completely random too, sometimes its as soon as it starts up and other times it waits a while.

Here's what I have done so far:
-Checked all drivers are up to date and installed correctly
-Checked all components are seated correctly to the motherboard
-Booted in safe mode to see if programs worked in there as read on google to check (they do)

So I read on another forum here someone said to get the Windows mini dump log, I have attached to this could anyone help me out please?

Thanks,
Jason

 

[YoYo155]

Start> http://www.sevenforums.com/bsod-help-support/96879-blue-screen-death-bsod-posting-instructions.html

 

[jase888]

thanks for the quick reply, I ran that program but it didn't put them in a folder on my desktop. So I have tried to get the files manually as I could see where it had put them but not sure if I have got them all.

Also I noticed in the files it thinks my GPU is amd radeon 7450 and its a 6450, not sure if thats anything or just the logs error.

I have a few updates I have seen that I am doing as we speak, but that would not cause BSOD just because all the updates weren't installed.

Any advice appreciated

 

[jase888]

whoops heres the attachment

 

[jase888]

Bsod

Hi

I built a PC last year and it worked fine with Windows 7 Professional on but I reformat it recently as it seemed to be restarting itself it seemed but wasn't to sure as was a media server so never saw it do it just things had closed and error messages came up saying "windows had closed due to error"

I've attached the logs that was told to in different post, it didn't quite work so I had to manually add them so may be missing a few.

Any ideas are appreciated been trying to fix this for a long time

 

[x BlueRobot]

Go to this directory, and then upload the dump files:

C:\Windows\Minidump

 

[Arc]

It appears that you havent executed the SF diag tool properly ... as it missed some other info too, not only the crash dumps. Try it again .... Blue Screen of Death (BSOD) Posting Instructions.

 

[YoYo155]

, The files you uploaded are missing some critical files if you may I have to ask you to have another
run of the SFDT and upload all the files it generates.

Other than that your bugcheck is probably caused by a driver:

BugCheck 1A, {[COLOR=Blue][U][B]41790[/B][/U][/COLOR], fffffa8000e80dd0, [COLOR=Blue][U][B]ffff[/B][/U][/COLOR], 0}

Arguments 1 & 3 are indicative of a device driver which unlocked the page table (Arg 1)
more time than it locked it.

• x BlueRobot, has a great entry about this subject CLICK to read more.
  

Start by running Driver Verifier, in-order to make you system crash a couple of time.
Driver Verifier will hopefully help us pinpoint the culprit.

:warn:Read Carefully before you enable Driver Verifier!

• http://www.sevenforums.com/crash-lo...g-driver-verifier-identify-issues-drivers.htm

 

[jase888]

thanks for the feedback guys, heres the last few mini dump files, I can't seem to get the softare to read them and still wouldnt be sure what I was exactly looking for

 

[x BlueRobot]

[COLOR=Red]BugCheck 19[/COLOR], {[COLOR="Blue"]3[/COLOR], [COLOR="SeaGreen"]fffffa8003629e20[/COLOR], dffffa8003629e20, 99fffa8003629e20}

Probably caused by : Pool_Corruption ( nt!ExDeferredFreePool+a53 )

Usual causes:  Device driver

It appears that the pool freelist is corrupt, the pool freelist is a linked list which contains all the available pool allocations (blocks) to be used by device drivers.

0: kd> [COLOR="SeaGreen"]!poolval fffffa8003629e20[/COLOR]
Pool page fffffa8003629e20 region is Nonpaged pool

Validating Pool headers for pool page: fffffa8003629e20

Pool page [ fffffa8003629000 ] is __inVALID.

Analyzing linked list...
[ fffffa8003629000 --> fffffa80036299e0 ([COLOR="Red"]size = 0x9e0 bytes[/COLOR])]: Corrupt region


Scanning for single bit errors...

None found

0: kd> [COLOR="SeaGreen"]!pool fffffa8003629e20[/COLOR]
GetPointerFromAddress: unable to read from fffff800032af100
Pool page fffffa8003629e20 region is GetUlongFromAddress: unable to read from fffff800032af1c0
Nonpaged pool
 fffffa8003629000 size:  620 previous size:    0  (Allocated)  .... (Protected)

The pool allocation also has the Protected bit set, which basically adds some extra checking when freeing pool allocations.

0: kd> [COLOR="SeaGreen"]dt nt!_POOL_HEADER fffffa8003629e20[/COLOR]
   +0x000 PreviousSize     : 0y01100000 (0x60)
   +0x000 PoolIndex        : 0y11100100 (0xe4)
   +0x000 BlockSize        : 0y01001011 (0x4b)
   +0x000 PoolType         : 0y00001000 (0x8)
   +0x000 Ulong1           : 0x84be460
   +0x004 PoolTag          : 0xfffff8a0
   +0x008 ProcessBilled    : 0xfffff8a0`084be460 _EPROCESS
   +0x008 AllocatorBackTraceIndex : 0xe460
   +0x00a PoolTagHash      : 0x84b

This seems to be a clear driver problem, there is also a pending IRP associated with the crashed thread, although the stack for the IRP can't be revealed since this information wasn't retained within the Minidump.

0: kd> [COLOR="SeaGreen"]!verifier[/COLOR]

Verify Level 0 ... enabled options are:

Summary of All Verifier Statistics

RaiseIrqls                             0x0
AcquireSpinLocks                       0x0
Synch Executions                       0x0
Trims                                  0x0

Pool Allocations Attempted             0x0
Pool Allocations Succeeded             0x0
Pool Allocations Succeeded SpecialPool 0x0
Pool Allocations With NO TAG           0x0
Pool Allocations Failed                0x0
Resource Allocations Failed Deliberately   0x0

Current paged pool allocations         0x0 for 00000000 bytes
Peak paged pool allocations            0x0 for 00000000 bytes
Current nonpaged pool allocations      0x0 for 00000000 bytes
Peak nonpaged pool allocations         0x0 for 00000000 bytes

Driver Verifier doesn't seem to be enabled, please follow:

Run Driver Verifier to scan for any corrupted drivers which may be causing problems, this program works by running various stress tests on drivers, in order to produce a BSOD which will locate the driver; run for least 24 hours:

• http://www.sevenforums.com/tutorials/101379-driver-verifier-enable-disable.html

   Information

Additional Help - http://www.sevenforums.com/crash-lo...-driver-verifier-identify-issues-drivers.html

 

[jase888]

Thanks for the detailed response, I have run drive verifier however as it says on thta guide, but my PC only lasts about 2-5 mins each time before the screen comes up with stripes across it and stops working without a hard reset.

How do I find out which driver is causing this?

Also I have taken 1 stick of RAM out and the PC seems to not do the BSOD when I don't have drive verifier running, its gone 2 days without but not sure if this is just chance.

 

[x BlueRobot]

Have you tried booting into Safe Mode? Only the most basic drivers will be loaded.