[Vincent Mayer]

Recently upgraded computer motherboard, CPU and RAM. 4GIGs just wasn't cutting it anymore. All parts seem to be in fine working order, no HDD errors, RAM has passed memtest 8 times with no errors. CPU seems to be fine and all temps are well below normal. Only problems is im getting multiple BDOS every day, and all different messages and at random times, startup, middle of web browsing, and once when live messenger crashed, once when Rainmeter crashed. ive gotten Service Exception, Page Fault, Bad Pool Caller, Memory Management. And those are just the ones i can remember.

After a few days of this and running hardware diagnostics i just hoped it was a driver error or windows install corrupt and did a reformat on a different hard drive. But im still getting BSODs, have had 1 so far since the re-install last night.

Attaching all minidumps from before and after the re-install in hopes that someone can help me solve this.


System spec are:
Mobo:: GIGABYTE GA-890GPA-UD3H AM3 AMD 890GX
CPU:: AMD Phenom II X6 1090T Black Edition @ stock clock(3.2Ghz)
RAM:: Mushkin Enhanced Silverline 8GB DDR3 1333
GPU:: MSI N260GTX Twin Frozr
PSU:: CORSAIR CMPSU-850TX 850W


Drivers should all be up to date.

Attached Files

•  Vince Minidumps.zip   178.35KB   86 downloads

[Advertisements]

Download BlueScreenView
No installation required.
Double click on BlueScreenView.exe file to run the program.
When scanning is done, go Edit>Select All.
Go File>Save Selected Items, and save the report as BSOD.txt.
Open BSOD.txt in Notepad, copy all content, and paste it into your next reply.

Thanks to Broni for the instructions and program

[rshaffer61]

Download BlueScreenView
No installation required.
Double click on BlueScreenView.exe file to run the program.
When scanning is done, go Edit>Select All.
Go File>Save Selected Items, and save the report as BSOD.txt.
Open BSOD.txt in Notepad, copy all content, and paste it into your next reply.

Thanks to Broni for the instructions and program

[Vincent Mayer]

==================================================
Process File : Dwm.exe
Event Name : Stopped working
Event Time : 4/15/2011 1:16:39 AM
User Name : Vincent
Exception Code : 0xc0000005
Exception Offset : 0x000026d0
Fault Module Name : dxgi.dll
Fault Module Version: 6.1.7600.16385
Process Path : C:\Windows\system32\Dwm.exe
Report File Size : 7,114
Report File Path : C:\Users\Vincent\AppData\Local\Microsoft\Windows\WER\ReportArchive\AppCrash_Dwm.exe_f7d2796fd41f675d818a8d4904e54363c88f0_17a6ddd1\Report.wer
==================================================

==================================================
Process File : WerFault.exe
Event Name : Shut down unexpectedly
Event Time : 4/15/2011 2:52:41 PM
User Name : Vincent
Exception Code :
Exception Offset :
Fault Module Name :
Fault Module Version:
Process Path : C:\Windows\System32\WerFault.exe
Report File Size : 4,546
Report File Path : C:\Users\Vincent\AppData\Local\

[rshaffer61]

Tutorial for running chkdsk in Vista\Win 7 located HERE.

[Vincent Mayer]

have run checkdisk on all drives. still getting BSODs

Last nights BSOD while i was sleeping

==================================================
Dump File : 041611-22308-01.dmp
Crash Time : 4/16/2011 3:25:29 PM
Bug Check String : MEMORY_MANAGEMENT
Bug Check Code : 0x0000001a
Parameter 1 : 00000000`00061940
Parameter 2 : 00000000`0f886000
Parameter 3 : 00000000`00000200
Parameter 4 : 00000000`00000000
Caused By Driver : ntoskrnl.exe
Caused By Address : ntoskrnl.exe+71f00
File Description : NT Kernel & System
Product Name : Microsoft® Windows® Operating System
Company : Microsoft Corporation
File Version : 6.1.7600.16385 (win7_rtm.090713-1255)
Processor : x64
Computer Name :
Full Path : C:\Windows\Minidump\041611-22308-01.dmp
Processors Count : 6
Major Version : 15
Minor Version : 7600
Dump File Size : 292,720
==================================================





and yesterdays

==================================================
Dump File : 041511-26988-01.dmp
Crash Time : 4/15/2011 2:52:30 PM
Bug Check String : MEMORY_MANAGEMENT
Bug Check Code : 0x0000001a
Parameter 1 : 00000000`00003452
Parameter 2 : 000007ff`fffdc000
Parameter 3 : fffff700`01085218
Parameter 4 : 9b200001`88831c66
Caused By Driver : tcpip.sys
Caused By Address : tcpip.sys+65ab7
File Description :
Product Name :
Company :
File Version :
Processor : x64
Computer Name :
Full Path : C:\Windows\Minidump\041511-26988-01.dmp
Processors Count : 6
Major Version : 15
Minor Version : 7600
Dump File Size : 292,672
==================================================

[rshaffer61]

0x0000001A: MEMORY_MANAGEMENT
(Click to consult the online MSDN article.)
This memory management error is usually hardware related. See the General Troubleshooting of STOP Messages checklist above. If this occurs while installing Windows, also check the Windows system requirements including the amount of RAM and disk space required to load the operating system. If none of the above resolves the problem, see the MSDN article linked above for further steps.

This is the only BSOD error code you are getting according to the post you just made.
Now comes the work. I'm going to start with the two most obvious choices of the issue.
The Hard drive and the memory.

Run hard drive diagnostics: http://www.tacktech....ay.cfm?ttid=287
Make sure, you select tool, which is appropriate for the brand of your hard drive.
Depending on the program, it'll create bootable floppy, or bootable CD.
If downloaded file is of .iso type, use ImgBurn: http://www.imgburn.com/ to burn .iso file to a CD (select "Write image file to disc" option), and make the CD bootable.

NOTE. If your hard drive is made by Toshiba, try the Hitachi DFT CD Image version of the software

Thanks to Broni for the instructions

[Vincent Mayer]

HDD diagnostics all report no problems.

new BSOD tonight, happened when playing World of tanks.
some other odd behavior is games randomly just close, no crash message or lockup, just close and shove me to desktop.


==================================================
Dump File : 041711-34351-01.dmp
Crash Time : 4/17/2011 2:43:05 AM
Bug Check String : PFN_LIST_CORRUPT
Bug Check Code : 0x0000004e
Parameter 1 : 00000000`00000099
Parameter 2 : 00000000`0013b95b
Parameter 3 : 00000000`00000002
Parameter 4 : 00000000`0013b95a
Caused By Driver : ntoskrnl.exe
Caused By Address : ntoskrnl.exe+71f00
File Description : NT Kernel & System
Product Name : Microsoft® Windows® Operating System
Company : Microsoft Corporation
File Version : 6.1.7600.16385 (win7_rtm.090713-1255)
Processor : x64
Computer Name :
Full Path : C:\Windows\Minidump\041711-34351-01.dmp
Processors Count : 6
Major Version : 15
Minor Version : 7600
Dump File Size : 292,720
==================================================

[rshaffer61]

If you have more than one RAM module installed, try starting computer with one RAM stick at a time.

NOTE Keep in mind, the manual check listed above is always superior to the software check, listed below. DO NOT proceed with memtest, if you can go with option A

B. If you have only one RAM stick installed...
...run memtest...

1. Download - Pre-Compiled Bootable ISO (.zip)
2. Unzip downloaded memtest86+-2.11.iso.zip file.
3. Inside, you'll find memtest86+-2.11.iso file.
4. Download, and install ImgBurn: http://www.imgburn.com/
5. Insert blank CD into your CD drive.
6. Open ImgBurn, and click on Write image file to disc
7. Click on Browse for a file... icon:



8. Locate memtest86+-2.11.iso file, and click Open button.
9. Click on ImgBurn green arrow to start burning bootable memtest86 CD:



10. Once the CD is created, boot from it, and memtest will automatically start to run. You may have to change the boot sequence in your BIOS to make it work right.

To change Boot Sequence in your BIOS

Reboot the system and at the first post screen (where it is counting up memory) start tapping the DEL button
This will enter you into the Bios\Cmos area.
Find the Advanced area and click Enter
Look for Boot Sequence or Boot Options and highlight that click Enter
Now highlight the first drive and follow the directions on the bottom of the screen on how to modify it and change it to CDrom.
Change the second drive to the C or Main Drive
Once that is done then click F10 to Save and Exit
You will prompted to enter Y to verify Save and Exit. Click Y and the system will now reboot with the new settings.


The running program will look something like this depending on the size and number of ram modules installed:




It's recommended to run 5-6 passes. Each pass contains very same 8 tests.

This will show the progress of the test. It can take a while. Be patient, or leave it running overnight.



The following image is the test results area:



The most important item here is the “errors” line. If you see ANY errors, even one, most likely, you have bad RAM.

[Vincent Mayer]

each stick passed memtest 3 times with no errors. have changed slot layout to 2 and 4 instead of 1 and 3, maybe they weren't seating properly.


i also have a new symptom, PSU is making a buzzing/jolting sound every second and keeping my machine from powering on. if i unplug it, the sound slowly dies out. i gave it a little bump on the top of the case and the sound stoped, and the machine was able to start up.

could this BSOD issue be a PSU failing of some sort, maybe not keeping proper voltages to RAM or other components?

sadly i don't think i have another PSU in the house able to power my main rig to test it.

Edited by Vincent Mayer, 17 April 2011 - 07:17 PM.

[rshaffer61]

Could be the PSU or it could be the fan on the cpu.
Open the system up and then turn it on. See if you can figure out where the sound is actually coming from.

[Vincent Mayer]

CPU heatsink is brand new and works fine. im sure the buzzing is comming from PSU as it starts the second i plug the cord in before i even push the power button, and does the same thing if i use the switch on the PSU itself. i just did the rebuild last week, and case/gpu and heatsink fans are cleaned. the only thing i didnt check at the time was PSU.

doesn't seem like a fan issue though, fan isn't on when the PSU is just pluged into the wall.

will pull it out and bench check it.

[rshaffer61]

doesn't seem like a fan issue though, fan isn't on when the PSU is just pluged into the wall.

You are correct and if the buzzing when there is no actual power going to the mobo then it must be coming from the PSU.
This is not a good sign and means that the psu is probably failing or has failed.
I would not suggest leaving it plugged in as it may short out causing a fire.