Multiple BSOD errors on Windows 7

[smahoney07]

Asus M4A79XTD EVO motherboard
AMD Phenom II X4 965 Black Edition Deneb 3.4GHz Socket AM3 125W
G.SKILL Ripjaws Series 8GB (2 x 4GB) 240-Pin DDR3 SDRAM DDR3 1600
Radeon HD 5870 (Cypress XT) 1GB 256-bit DDR5
hec X-Power Pro 600 600W Continuous @ 40°C ATX12V V2.2 SLI Ready
Western Digital Caviar Blue WD10EALS 1TB 7200 RPM SATA 3.0Gb/s
LITE-ON Black 12X Blu-ray Burner with Blu-ray 3D feature SATA
Microsoft Windows 7 Home Premium 64-bit 1-Pack for System Builders - OEM


Worked great for about a month. Then the bsods started happening. Did chkdsk. Ran Memtest ALOT. Reseated memory. If someone could point me in the right direction I would appreciate it.

Heres info from bluescreenview. Ill upload the minidump files if i need to.

Dump File : 032911-26410-01.dmp
Crash Time : 3/29/2011 4:36:12 PM
Bug Check String : IRQL_NOT_LESS_OR_EQUAL
Bug Check Code : 0x0000000a
Parameter 1 : 00000000`00002000
Parameter 2 : 00000000`00000002
Parameter 3 : 00000000`00000001
Parameter 4 : fffff800`01cfb0a2
Caused By Driver : hal.dll
Caused By Address : hal.dll+5156
File Description : Hardware Abstraction Layer DLL
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 : G:\Windows\Minidump\032911-26410-01.dmp
Processors Count : 4
Major Version : 15
Minor Version : 7600
Dump File Size : 271,408
==================================================

==================================================
Dump File : 032911-29218-01.dmp
Crash Time : 3/29/2011 4:18:35 PM
Bug Check String : IRQL_NOT_LESS_OR_EQUAL
Bug Check Code : 0x0000000a
Parameter 1 : ffffffff`fffffd20
Parameter 2 : 00000000`00000002
Parameter 3 : 00000000`00000000
Parameter 4 : fffff800`01c45daa
Caused By Driver : ntoskrnl.exe
Caused By Address : ntoskrnl.exe+70740
File Description : NT Kernel & System
Product Name : Microsoft® Windows® Operating System
Company : Microsoft Corporation
File Version : 6.1.7600.16695 (win7_gdr.101026-1503)
Processor : x64
Computer Name :
Full Path : G:\Windows\Minidump\032911-29218-01.dmp
Processors Count : 4
Major Version : 15
Minor Version : 7600
Dump File Size : 271,408
==================================================

==================================================
Dump File : 032911-30201-01.dmp
Crash Time : 3/29/2011 3:31:02 PM
Bug Check String : SYSTEM_THREAD_EXCEPTION_NOT_HANDLED
Bug Check Code : 0x0000007e
Parameter 1 : ffffffff`c000001d
Parameter 2 : fffff880`04abe0cb
Parameter 3 : fffff880`057109e8
Parameter 4 : fffff880`05710250
Caused By Driver :
Caused By Address :
File Description :
Product Name :
Company :
File Version :
Processor : x64
Computer Name :
Full Path : G:\Windows\Minidump\032911-30201-01.dmp
Processors Count : 4
Major Version : 15
Minor Version : 7600
Dump File Size : 262,144
==================================================

==================================================
Dump File : 032911-25599-01.dmp
Crash Time : 3/29/2011 7:02:47 AM
Bug Check String : MEMORY_MANAGEMENT
Bug Check Code : 0x0000001a
Parameter 1 : 00000000`00008886
Parameter 2 : fffffa80`04c95000
Parameter 3 : fffffa80`060de030
Parameter 4 : 00000000`00000105
Caused By Driver : ntoskrnl.exe
Caused By Address : ntoskrnl.exe+70740
File Description : NT Kernel & System
Product Name : Microsoft® Windows® Operating System
Company : Microsoft Corporation
File Version : 6.1.7600.16695 (win7_gdr.101026-1503)
Processor : x64
Computer Name :
Full Path : G:\Windows\Minidump\032911-25599-01.dmp
Processors Count : 4
Major Version : 15
Minor Version : 7600
Dump File Size : 271,408
==================================================

==================================================
Dump File : 032811-33711-01.dmp
Crash Time : 3/28/2011 2:05:56 PM
Bug Check String : MEMORY_MANAGEMENT
Bug Check Code : 0x0000001a
Parameter 1 : 00000000`00005003
Parameter 2 : fffff700`01080000
Parameter 3 : 00000000`00000a7e
Parameter 4 : 00000a80`000034fc
Caused By Driver : ntoskrnl.exe
Caused By Address : ntoskrnl.exe+70740
File Description : NT Kernel & System
Product Name : Microsoft® Windows® Operating System
Company : Microsoft Corporation
File Version : 6.1.7600.16695 (win7_gdr.101026-1503)
Processor : x64
Computer Name :
Full Path : G:\Windows\Minidump\032811-33711-01.dmp
Processors Count : 4
Major Version : 15
Minor Version : 7600
Dump File Size : 262,144
==================================================

==================================================
Dump File : 032811-35474-01.dmp
Crash Time : 3/28/2011 11:18:23 AM
Bug Check String : IRQL_NOT_LESS_OR_EQUAL
Bug Check Code : 0x0000000a
Parameter 1 : 000000d0`4c6f6f58
Parameter 2 : 00000000`00000002
Parameter 3 : 00000000`00000001
Parameter 4 : fffff800`0288edb2
Caused By Driver : hal.dll
Caused By Address : hal.dll+5156
File Description : Hardware Abstraction Layer DLL
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 : G:\Windows\Minidump\032811-35474-01.dmp
Processors Count : 4
Major Version : 15
Minor Version : 7600
Dump File Size : 275,648
==================================================

==================================================
Dump File : 032811-34523-01.dmp
Crash Time : 3/28/2011 11:12:52 AM
Bug Check String : DRIVER_IRQL_NOT_LESS_OR_EQUAL
Bug Check Code : 0x000000d1
Parameter 1 : 00000000`00000010
Parameter 2 : 00000000`00000002
Parameter 3 : 00000000`00000000
Parameter 4 : fffff880`03e71f32
Caused By Driver : dxgmms1.sys
Caused By Address : dxgmms1.sys+bf32
File Description : DirectX Graphics MMS
Product Name : Microsoft® Windows® Operating System
Company : Microsoft Corporation
File Version : 6.1.7600.16748 (win7_gdr.110125-1530)
Processor : x64
Computer Name :
Full Path : G:\Windows\Minidump\032811-34523-01.dmp
Processors Count : 4
Major Version : 15
Minor Version : 7600
Dump File Size : 275,648
==================================================

==================================================
Dump File : 032811-36535-01.dmp
Crash Time : 3/28/2011 11:06:35 AM
Bug Check String : NTFS_FILE_SYSTEM
Bug Check Code : 0x00000024
Parameter 1 : 00000000`001904fb
Parameter 2 : fffff880`02f92bb8
Parameter 3 : fffff880`02f92410
Parameter 4 : fffff800`028bee47
Caused By Driver : Ntfs.sys
Caused By Address : Ntfs.sys+213d8
File Description : NT File System Driver
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 : G:\Windows\Minidump\032811-36535-01.dmp
Processors Count : 4
Major Version : 15
Minor Version : 7600
Dump File Size : 275,648
==================================================

I have the hard drive installed in my other computer right now. Thank you very much for any help at all!!!

 

[Route44]

Please do the following so that we can read your dumps:

My Computer > C Drive > Windows Folder > Minidump Folder > Minidump Files.

It is these files that we need (not the folder). Attach to your next post the five most recent dumps. Notice the Manage Attachments button at the bottom when you go to post the next time. You can Zip up to five files per Zip; if you only have one or two you don’t need to zip them, just attach as is. Please do us a favor and don’t Zip each one individually.

* By the way, nice system.

 

[smahoney07]

Sorry it took me 5 days to get em up. hope you guys can steer me in the right direction. id greatly appreciate it.

 

[Route44]

Your issue is with memory corruption. Therefore you’ll need to run Memtest on your RAM.

1. Go to www.memtest.org and download the latest ISO version which is 4.20. It is free and perfectly safe.

2. Burn ISO to a CD.

3. Place CD in your drive and reboot with CD in drive. (You might have to place your drive as first bootable in your BIOS) The test will take over.


There is a Tutorial: How to use Memtest in our Guides and Tutorials forum; follow the instructions. There is a newer version than what is listed; use the newer. If you need to see what the Memtest screen looks like go to reply #21. The third screen is the Memtest screen.

Step1 - Let it run for a LONG time. The rule is a minimum of 7 Passes; the more Passes after 7 so much the better. The only exception is if you start getting errors before 7 Passes then you can skip to Step 2.

There are 8 individual tests per Pass. Many people will start this test before going to bed and check it the next day.

If you have errors you have corrupted memory and it needs to be replaced.

Step 2 – Because of errors you need to run this test per stick of RAM. Take out one and run the test. Then take that one out and put the other in and run the test. If you start getting errors before 7 Passes you know that stick is corrupted and you don’t need to run the test any further on that stick.


* Get back to us with the results.


*** If Memtest shows no errors then find the voltage specs of your RAM and compare it to the voltage setting in your BIOS. Do they match?

 

[smahoney07]

Ran memtest on both sticks. Errors immediatly after test 4 started.. Ran with stick #1 and had no errors for 5 passes and then memtest was interrupted and stopped. So i restarted it and had errors immediatly. Ran stick #2 and got immediate errors. Both sticks with errors. How does something like this happen? Everything worked fine and then just got shitty.

 

[Route44]

Good question and honestly we don't know why memory suddenly goes bad, but it is a very common problem.

I had four sticks of RAM in a 4x512 configuration once go bad on me all at the same time.

The RAM manufacture should replace them free of charge.

 

[smahoney07]

I picked up 2 sticks of corsair from best buy to use for a few weeks until my gskill gets returned. Ill let you know what happens when i get em in. Im crossing my fingers that they work fine.

 

[Route44]

I had to do the same thing as well but I went with Kingston Value RAM (good memory) that I could find at NewEgg.com. Only one stick of 512 but it worked - slow system - but it worked until Crucial came through with four sticks.

* Keep us updated.

 

[smahoney07]

Started it up and got system service exception and irql errors. Then it let me start up for long enoughh to get a windows update and start a chkdsk. Ill post my dumps later on.

 

[smahoney07]

New dump file. im on my pc right now actually. im crossing my fingers. jeeze its been so long. I miss my baby. I wanna tear up lol.

 

[Route44]

The error code is 0xD1 and these are caused either by faulty drivers or faulty or mismatched memory.

The driver cited is volmgr.sys whjich is a Windows OS driver and engages at start up. This is a Windows driver for managing Windows volumes.

The thing is when OS drivers are cited they are often too general to be of much diagnostic help. Nothing else was cited.

 

[smahoney07]

Heres newer dumps from today. I started windows driver verifier and got a bsod that said it tried to stop a driver from corrupting the system. its starting up and just shutting down after a few minutes of windows booting. Thought maybe power supply but it works under safe mode for now so that doesnt seem to be the issue.

 

[Route44]

If you can boot up via Safe Mode the issue is often due to drivers as the following will confirm.


The most important error code is 0x000000C4: DRIVER_VERIFIER_DETECTED_VIOLATION
This is the general bug check code for fatal errors that the Driver Verifier finds. In other words a driver was caught before it could load causing corruption and in order to prevent this occurring Windows Blue Screened.

The driver in question is AsUpIO.sys and this is from Asus that loads at boot-up. It is a utility that came with your motherboard chipset drivers, etc. Many people have had issues with this driver and Asus utilities in general. Now to be fair there are many who don't have problems.

Since this utility does not appear essential you could uninstall it as many have done. Just a suggestion.

 

[smahoney07]

It seems as though my new memory now has errors after a day. Could a bad mobo or psu be corrupting my memory?

 

[Route44]

* Find the voltage specs of your RAM and compare it to the voltage setting in your BIOS. Do they match?

 

[smahoney07]

Yes they do 1.5v

 

[Route44]

Yes they do 1.5v

Hmmm, okay does your memory configuration follow what the manual directs? Also, is this Corsair listed on Asus' memory recommended list for this motherboard?

 

[smahoney07]

I took my corsair back to best buy since they werent working. So i took my compaq and put my power supply and video card in it and it was great for a few days even acted a bit faster and now it gets memory management bsods lol! Is there any way my psu or vga could cause this issue. When i get my gskill back i dont want to ruin it for no reason.

 

[Route44]

Good question. Post the latest minidumps and I'll read them.

 

[smahoney07]

It may have been months,but shes alive! Bad M4A79xtd Evo mobo. I'm sure so many of you know how damn excited I am. I feel like my 2 year old does when she shits in the pot. I'm so effin happy. Thank you so much for your help!