Solved BSOD after about 40 minutes of run time.

[ripski]

Hi

I really hope you can help. I built a PC for a mate. It was great until after about 1 month it started freezing when windows 7 was booting up. I tried to reinstall the OS but that froze also at different stages of install. To cut a long story short I swapped the GX card and RAM, then the MB but still had the same issue. I them swapped the CPU. This worked and I re-installed the OS. About a week later it started freezing on win7 boot screen again. I replace the CPU again and all was great. Soon though I started getting a BSOD after about 40 minutes of run time. I have tried installing the OS again but the old issue happens when it freezes during set-up. I have wasted and lot of time and money on this and now have come across this fab site. I hope I have uploaded the correct files. Thanks.

 

[Pauly]

Hello ripski, Welcome to SF

Just ran your dump file which is slightly inconclusive, if you have more please post a few more recent ones for comparison
dump states error code 0xDE POOL_CORRUPTION_IN_FILE_AREA
as you have already changed several components my initial thought would be to check HDD

 

[ripski]

Thanks for the quick response.

I have just got the PC back from my mate. I updated the firmware of the SSD and messed around opening pictures to see if I still got the BSOD. I did after about 30 minutes and have attached the new file. Thank you for your help.

 

[Pauly]

Just had a look at next dump which is 0x1A memory management BSOD Index

*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 1A, {403, fffff6800026b588, 9980000072e5f867, fffff7800026b588}
Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+320ec )
Followup: MachineOwner
---------
0: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************
MEMORY_MANAGEMENT (1a)
    # Any other values for parameter 1 must be individually examined.
Arguments:
Arg1: 0000000000000403, The subtype of the bugcheck.
Arg2: fffff6800026b588
Arg3: 9980000072e5f867
Arg4: fffff7800026b588
Debugging Details:
------------------

BUGCHECK_STR:  0x1a_403
CUSTOMER_CRASH_COUNT:  1
DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT
PROCESS_NAME:  Photoshop.exe
CURRENT_IRQL:  0
LAST_CONTROL_TRANSFER:  from fffff80002e2f8e6 to fffff80002e8bfc0
STACK_TEXT:  
fffff880`09ac2668 fffff800`02e2f8e6 : 00000000`0000001a 00000000`00000403 fffff680`0026b588 99800000`72e5f867 : nt!KeBugCheckEx
fffff880`09ac2670 fffff800`02ebd1b7 : 00000000`00000000 fffff680`0026b610 fffffa80`0701bb30 fffffa80`07cf60d0 : nt! ?? ::FNODOBFM::`string'+0x320ec
fffff880`09ac2820 fffff800`02e7881f : fffffa80`00000000 00000000`4d6dafff 00000000`00000000 00000000`00000000 : nt!MiDeleteVirtualAddresses+0x41f
fffff880`09ac29e0 fffff800`02e8b253 : ffffffff`ffffffff 00000000`43e698a0 00000000`43e69868 00000000`00008000 : nt!NtFreeVirtualMemory+0x61f
fffff880`09ac2ae0 00000000`778314fa : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
00000000`43e697d8 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x778314fa

STACK_COMMAND:  kb
FOLLOWUP_IP: 
nt! ?? ::FNODOBFM::`string'+320ec
fffff800`02e2f8e6 cc              int     3
SYMBOL_STACK_INDEX:  1
SYMBOL_NAME:  nt! ?? ::FNODOBFM::`string'+320ec
FOLLOWUP_NAME:  MachineOwner
MODULE_NAME: nt
IMAGE_NAME:  ntkrnlmp.exe
DEBUG_FLR_IMAGE_TIMESTAMP:  503f82be
FAILURE_BUCKET_ID:  X64_0x1a_403_nt!_??_::FNODOBFM::_string_+320ec
BUCKET_ID:  X64_0x1a_403_nt!_??_::FNODOBFM::_string_+320ec
Followup: MachineOwner
---------

Run memtest to analyse ram, leave to run overnight preferably or ideally min 7-8 passes
http://www.sevenforums.com/tutorials/105647-ram-test-memtest86.html

will have a look at drivers etc and come back

 

[Pauly]

Your graphics drivers are mentioned in the second dump and they do not look very recent i would recommend updating them
Do not install beta drivers stick with official releases preferably WHQL certified and after uninstalling old ones you can run http://www.sevenforums.com/tutorials/83814-drivers-clean-left-over-files-after-uninstalling.html to clear out old before installing new as this can sometimes cause conflicts

 

[ripski]

I uninstalled the video drivers and ran the Driver Sweep, great little app btw. Installed the latest drivers and so far it's looking promising. My mate will be giving a good test now so fingers crossed. If it does BSOD again I will run memtest.

Thanks for your help so far Pauly, I will post back if the problem has been resolved.

 

[Pauly]

Good mate sounds like progress, memtest would be the next step and again if you get any more dumps post them and we can have a look

 

[ripski]

Well, just got the PC back from my mate...BSOD a plenty! Ran Memtest86 and got an error after about 90 seconds. I have swapped over my RAM with his and he has taken it away for testing. I on the other hand are waiting for a BSOD I hope I have now found the problem and I will let ya know how it goes.

Thanks.

 

[Pauly]

OK what a kind friend you are ! let us know if you need anything

 

[ripski]

Well good news. My mates computer is stable and mine hasn't crashed either. Not sure why the memory module is stable on by rig but my mates doesn't ring me up everyday complaining about his PC. Thanks for your help, it was all down to you