Lots of Win7 x64 BSODs

[Kyjibo]

Ever since I installed 64-bit onto this machine I have been plagued with constant BSODs. Every time I think I have resolved the problem it just waits a few days and then comes roaring back.

I have already:
1) run memtest: 15 passes, no errors
2) Updated my bios, reset my bios to defaults.
3) Examined my Sound, Network and Video cards for more recent drivers.
4) Re-Seated and rearranged ram and Video/Sound/Network cards.

I am really at my wits end here - can anyone help me with this?

 

[zigzag3143]

Ever since I installed 64-bit onto this machine I have been plagued with constant BSODs. Every time I think I have resolved the problem it just waits a few days and then comes roaring back.

I have already:
1) run memtest: 15 passes, no errors
2) Updated my bios, reset my bios to defaults.
3) Examined my Sound, Network and Video cards for more recent drivers.
4) Re-Seated and rearranged ram and Video/Sound/Network cards.

I am really at my wits end here - can anyone help me with this?

These crashes were caused by several different things. With so many different causes one has to start thinking about a hardware problem.. Use these to find out what it means and how to diagnose it. http://www.sevenforums.com/crash-lockup-debug-how/35349-2-int-stop-0x124-what-means-what-try.html

Let us know if you need help

030710-20046-01.dmp    3/7/2010 1:01:56 AM    ATTEMPTED_WRITE_TO_READONLY_MEMORY    0x000000be    fffff880`045b8710    80000001`77d4e121    fffff800`03be0400    00000000`0000000a    athrx.sys    athrx.sys+157710                    x64        C:\Users\K\Desktop\New folder (4)\030710-20046-01.dmp    2    15    7600    
030310-28501-01.dmp    3/4/2010 12:56:58 AM    DRIVER_IRQL_NOT_LESS_OR_EQUAL    0x000000d1    00000000`008b0040    00000000`00000002    00000000`00000000    fffff880`04595e00    athrx.sys    athrx.sys+10ae00                    x64        C:\Users\K\Desktop\New folder (4)\030310-28501-01.dmp    2    15    7600    
030610-16052-01.dmp    3/6/2010 11:08:34 PM    DRIVER_IRQL_NOT_LESS_OR_EQUAL    0x000000d1    00000000`00000000    00000000`00000002    00000000`00000000    fffff880`03b4a480    USBPORT.SYS    USBPORT.SYS+7480                    x64        C:\Users\K\Desktop\New folder (4)\030610-16052-01.dmp    2    15    7600    
032410-19827-01.dmp    3/24/2010 8:09:30 PM    DRIVER_IRQL_NOT_LESS_OR_EQUAL    0x000000d1    00000000`00000001    00000000`00000002    00000000`00000000    fffff880`0447a808    cmudax3.sys    cmudax3.sys+26808                    x64        C:\Users\K\Desktop\New folder (4)\032410-19827-01.dmp    2    15    7600    
032410-23400-01.dmp    3/24/2010 7:12:26 PM    DRIVER_IRQL_NOT_LESS_OR_EQUAL    0x000000d1    00000000`00000004    00000000`00000002    00000000`00000001    fffff880`0489af82    cmudax3.sys    cmudax3.sys+6cf82                    x64        C:\Users\K\Desktop\New folder (4)\032410-23400-01.dmp    2    15    7600    
032910-20170-01.dmp    3/29/2010 11:03:18 PM    DRIVER_IRQL_NOT_LESS_OR_EQUAL    0x000000d1    00000000`00000000    00000000`00000002    00000000`00000001    fffff880`04c82111    cmudax3.sys    cmudax3.sys+1f111                    x64        C:\Users\K\Desktop\New folder (4)\032910-20170-01.dmp    2    15    7600    
040310-18345-01.dmp    4/3/2010 4:41:58 AM    DRIVER_IRQL_NOT_LESS_OR_EQUAL    0x000000d1    ffffffff`fa800536    00000000`00000002    00000000`00000001    fffffa80`04d3f6f8    ntoskrnl.exe    ntoskrnl.exe+71f00                    x64        C:\Users\K\Desktop\New folder (4)\040310-18345-01.dmp    2    15    7600    
040210-19890-01.dmp    4/2/2010 1:45:56 AM    IRQL_NOT_LESS_OR_EQUAL    0x0000000a    fffffa80`053fa658    00000000`00000002    00000000`00000001    fffff800`028d2b75    hidusb.sys    hidusb.sys+248f                    x64        C:\Users\K\Desktop\New folder (4)\040210-19890-01.dmp    2    15    7600    
030410-20950-01.dmp    3/4/2010 3:05:52 PM    PAGE_FAULT_IN_NONPAGED_AREA    0x00000050    fffff800`022df7b0    00000000`00000008    fffff800`022df7b0    00000000`00000000    fltmgr.sys    fltmgr.sys+fd5a                    x64        C:\Users\K\Desktop\New folder (4)\030410-20950-01.dmp    2    15    7600    
032010-17128-01.dmp    3/20/2010 1:34:20 PM    PFN_LIST_CORRUPT    0x0000004e    00000000`00000099    00000000`0012dae8    00000000`00000002    00000000`0012daa7    ntoskrnl.exe    ntoskrnl.exe+71f00                    x64        C:\Users\K\Desktop\New folder (4)\032010-17128-01.dmp    2    15    7600    
032010-22510-01.dmp    3/20/2010 4:19:16 PM    PFN_LIST_CORRUPT    0x0000004e    00000000`00000099    00000000`00046bfb    00000000`00000000    00000000`00000001    ntoskrnl.exe    ntoskrnl.exe+71f00                    x64        C:\Users\K\Desktop\New folder (4)\032010-22510-01.dmp    2    15    7600    
032310-16692-01.dmp    3/23/2010 11:11:12 PM    PFN_LIST_CORRUPT    0x0000004e    00000000`00000099    00000000`00059008    00000000`00000002    00000000`00059007    ntoskrnl.exe    ntoskrnl.exe+71f00                    x64        C:\Users\K\Desktop\New folder (4)\032310-16692-01.dmp    2    15    7600    
040310-18361-01.dmp    4/3/2010 4:27:48 AM    SYSTEM_SERVICE_EXCEPTION    0x0000003b    00000000`c0000005    fffff960`000d2ad3    fffff880`053ee0c0    00000000`00000000    win32k.sys    win32k.sys+c2ad3                    x64        C:\Users\K\Desktop\New folder (4)\040310-18361-01.dmp    2    15    7600    
032010-17472-01.dmp    3/20/2010 1:36:44 PM    SYSTEM_THREAD_EXCEPTION_NOT_HANDLED    0x1000007e    ffffffff`c0000005    fffff880`01055513    fffff880`02ffd438    fffff880`02ffcc90    fileinfo.sys    fileinfo.sys+1066                    x64        C:\Users\K\Desktop\New folder (4)\032010-17472-01.dmp    2    15    7600

 

[Kyjibo]

Well, some of those BSODs I think were resolved by other things. For instance, when I updated my network drivers the athrx.sys BSODs stopped and when i reinstalled my audio drivers the cmudax.sys BSODs stopped. When I reseated the RAM, cleaned out the DIMM slots, and reset the pagefile the PFN_LIST_CORRUPT errors stopped. This is what I mean when I say that it keeps coming back.

It acts as if the problem was resolved but then something else starts crashing it a few days later.