BSOD windows 7 64 bit

[hihallie3]

so i got my pc a few weeks ago and have had several issues since i have checked all the ram is in correct and working e.c.t

custom built pc,
2x2g ddr3 ram
intel i5 processor
nvidia geforce gt 250

the issue was originally getting the BSOD before even getting to the windows login screen this was fixed by installing a 64 bit version of windows 7 ultimate instead of windows 32 bit ultimate.

now upon logging in my pc restarts after some times on 50% of the occasions with various BSOD with many different messages,

Cache_Manager
Memory_manager

and others i am by no means a computer wizz kid and would like to know how to solve this issue if possible andy helpful input would be welcomed.

 

[richc46]

Usually we ask for the dump reports. May be needed later, but sounds like memory, doesn't, it?

Download and test with this
Guide to using Memtest86+
Its not the OS, since the problem ocurred on the prior system, too.

 

[hihallie3]

used the software you said and it found no issues with the ram in addition to using the software, i took out 1 of the 2gb ram sticks loading my pc with only 1 and it worked, and then switched them round and ran it with the other stick in.

so basically no BSOD with only 2gb of ram in however with 4gb of ram my pc decides to BSOD

 

[hihallie3]

ok got some dump files for you to look at there is 4 different ones from 4 different BSOD errors please take a look and help me with some assistance

 

[richc46]

STOP 0x0000001A: MEMORY_MANAGEMENT

Usual causes: Device driver, memory, kernel

34
Usual causes: Insufficient physical memory, Indexing, Device driver



STOP 0x00000019: BAD_POOL_HEADER

Usual causes: Device driver

The reports are pointing toward memory as your own tests have shown. Make sure that the slots are all working properly.

 

[richc46]

used the software you said and it found no issues with the ram in addition to using the software, i took out 1 of the 2gb ram sticks loading my pc with only 1 and it worked, and then switched them round and ran it with the other stick in.

so basically no BSOD with only 2gb of ram in however with 4gb of ram my pc decides to BSOD

Did you run the test with one stick of ram on each test and run for six passes?

 

[hihallie3]

i cant seem to get the files to burn to a disk for memstek

i have a file called MT410 and the disk isnt called boot when i burn it
i also have a file called boot, with memstest ( cant burn) and boot in it which i have burned before but it didnt work when i loaded the pc. :/

 

[richc46]

Try starting the burn process from scratch.

 

[hihallie3]

finished the testing with memtest 86 and both memory sticks passed there test on all 6 passes for each one. any other ideas on the solution ?

 

[richc46]

I am not able to get a full report, including drivers, from any of the reports. Did you provide the information using these instructions?

http://www.sevenforums.com/tutorials/83172-dump-files-upload-seven-forums.html

 

[hihallie3]

sorry i used another programme to view my dump files then put them on to a note pad and attached them the first time attached to this is the dump files all in the same compressed folder.

 

[richc46]

Because you supplied so many dump reports in addition to the previous mentioned codes, a new code appeared 50


STOP 0x00000050: PAGE_FAULT_IN_NONPAGED_AREA Usual causes: Defective hardware (particularly memory - but not just RAM), Faulty system service, Antivirus, Device driver, NTFS corruption, BIOS

If taken as a whole, the reports indicate memory. Since that appeared in every report. Drivers however can be a cause of memory problems. However we cannot discount the other possiblities as shown.

What I suggest is that you Test your hard drive (NTFS Corruption)
http://www.carrona.org/hddiag.html

Uninstall your Anti Virus and replace with Microsoft Security Essentials, for testing purposes.

First chance I get, I will prepare a report on your drivers.

I think the combination of our combined efforts will solve this problem.

Keep me posted in the event that the problem is solved due to the tests that you will make it will save the work of anzlyzing the drivers.

 

[hihallie3]

ok i will keep you posted after i have tested my hardrive tank you for your time and effort much appreciated

 

[richc46]

 v  
fin pcouffin.sys Tue Dec 05 09:39:30 2006 (457584A2)
    irsir.sys    Sat Jan 19 01:36:11 2008 (47919A5B)
in7 Rt64win7.sys Thu Feb 26 04:04:13 2009 (49A65B0D)
        amdxata.sys  Tue May 19 13:56:59 2009 (4A12F2EB)
    athrx.sys    Tue Jun 09 14:06:49 2009 (4A2EA4B9)

A list of drivers that may be causing the problem, due to age.

If after all tests are complete, we can try a driver verifier test, in the event that the problem is still not solved after all other efforts and the above drivers are replaced.

Pcouffin.sys file descriptionProductname: Patin couffin engine Description: Patin-Couffin low level access layer for CD devices Company: VSO Software File size: Various

athrx.sys, which is the driver for Atheros WLAN card.

amdxata
File description

Storage Filter Driver
Vendor
Advanced Micro Devices


In addition run a thorough anti virus scan. A virus can be hiding anywhere and can cause BSOD also download and run malwarebytes.

 

[hihallie3]

did the hard drive test nothing came up wrong with it, i have updated all the drivers possible and no virus's were found so i guess we will see if the problem continues

 

[richc46]

used the software you said and it found no issues with the ram in addition to using the software, i took out 1 of the 2gb ram sticks loading my pc with only 1 and it worked, and then switched them round and ran it with the other stick in.

so basically no BSOD with only 2gb of ram in however with 4gb of ram my pc decides to BSOD

Seems strange. Sure all ram is good, Sure all sockets are good. Sure that all ram is compatible and purchased at same time?

 

[hihallie3]

the ram was purchased with the pc which was custom built for me at a computer shop near by so i guess they know what there doing, the tests and hard drive showed nothing was faulty so im unsure what caused the BSOD

the quote above was just after running it with 2gb of ram however after running it with 2gb of ram for a day the BSOD still happend

 

[richc46]

Thanks for posting. If BSOD happens again, we will have more information from that new dump. Can compare and eliminate. Good luck

 

[hihallie3]

new BSOD today, managed to run it ok with 4gb of ram however that BSOD happened with no Memory_managment_ or Cahce_memory letters so basically it was a blank BSOD. this happened when i had aviria anti virus installed, i uninstalled it and the BSOD stopped however upon loading my pc next time the screen froze when i had 2 internet explorers open for some reason

 

[richc46]

STOP 0x0000001E: KMODE_EXCEPTION_NOT_HANDLED

Usual causes: Device driver, hardware, System service, compatibility, Remote control programs, memory, BIOS

STOP 0x00000024: NTFS_FILE_SYSTEM

Usual causes: Disk corruption, insufficient physical memory, Device driver, Indexing, Resident antivirus, backup, defrag programs, Disk/Drive failing/failure

STOP 0x00000019: BAD_POOL_HEADER

Usual causes: Device driver

The above represents the findings of your latest dump reports. It is basically the same issues shown on the previous reports.

Driver keeps appearing which warrants a driver stress test. AntiVirus keeps appearing. Use Microsoft Security Essentials with the Windows Firewall for testing purposes until we get this problem solved. We should also do a hard drive test (NTFS as shown)
http://www.carrona.org/hddiag.html. If done already ignore this step.
http://www.sevenforums.com/crash-lo...-driver-verifier-identify-issues-drivers.html
Since we are getting many Dump reports with different causes, it is pointing toward a hardware problem.
My gut says memory. Did you test each ram stick separately, using memtest86? Did you run for at least 6 passes? Memory problems can also be caused by a bad driver. The driver stress test will determine if that is a cause.

The fact that the BSOD continue after the first BSOD reports are to be expected, very rarely are the reports definitive, they are merely a way of pointing toward potential problems.