FREQUENT BSoD

Hi everyone

I have been having some troubles recently with my new build, about a week ago i started up and when i got into windows i got an error saying the ATI Catalyst Control had become corrupt (dont remember the exact error) so i went into device manager and it was empty... after trying a few things i decided to reinstall windows. it ran flawlesly for about a week and then wham 3 blue screens within half an hour.. then it started to run fine, 2 days later another 2 within half an hour and then ran fine, last night i got 1 blue screen and then it ran fine. im not sure what is causing this problem but when its about to happen some applications wont start or give errors when i try to start them then the screen scrambles for a split second and then BSoD and memory dump begins.....

Anyone got any ideas?
Thanks

SUPAD4V3 said:

Hi everyone

I have been having some troubles recently with my new build, about a week ago i started up and when i got into windows i got an error saying the ATI Catalyst Control had become corrupt (dont remember the exact error) so i went into device manager and it was empty... after trying a few things i decided to reinstall windows. it ran flawlesly for about a week and then wham 3 blue screens within half an hour.. then it started to run fine, 2 days later another 2 within half an hour and then ran fine, last night i got 1 blue screen and then it ran fine. im not sure what is causing this problem but when its about to happen some applications wont start or give errors when i try to start them then the screen scrambles for a split second and then BSoD and memory dump begins.....

Anyone got any ideas?
Thanks

We need the actual dmp file created when your computer crashed. Use these instructions to find it and upload it to us. https://www.sevenforums.com/crash-loc...d-problem.html

Let us know if you need help

Ken

Thanks for the quick reply, the computer is at home and i am at work right now, i will try to get teh dmp file when i get home

Thanks again

SUPAD4V3 said:

Hi everyone

I have been having some troubles recently with my new build, about a week ago i started up and when i got into windows i got an error saying the ATI Catalyst Control had become corrupt (dont remember the exact error) so i went into device manager and it was empty... after trying a few things i decided to reinstall windows. it ran flawlesly for about a week and then wham 3 blue screens within half an hour.. then it started to run fine, 2 days later another 2 within half an hour and then ran fine, last night i got 1 blue screen and then it ran fine. im not sure what is causing this problem but when its about to happen some applications wont start or give errors when i try to start them then the screen scrambles for a split second and then BSoD and memory dump begins.....

Anyone got any ideas?
Thanks

We need the actual dmp file created when your computer crashed. Use these instructions to find it and upload it to us. https://www.sevenforums.com/crash-loc...d-problem.html

Let us know if you need help

Ken

how do i find the dump files?

SUPAD4V3 said:

how do i find the dump files?

easy


We need the actual dmp file created when your computer crashed. Use these instructions to find it and upload it to us. https://www.sevenforums.com/crash-loc...d-problem.html

Let us know if you need help

Ken

Sorry had to read it twice, was under the impression i had to convert them or something, my computer at home with the problems wouldnt let me zip up these files either, and a friendbrought over his hard drive and it showed up once now doesnt show up under computer but under devices and printers it sees it. not sure whats going on there either

Hi,

First thing I noticed in your dump files was this driver:

Code:

ASACPI.sys   Mon Mar 28 15:30:36 2005

ASACPI.sys - ASUS ACPI Driver; near guaranteed to cause BSODs on Windows 7 systems. Update link here, update instructions (slideshow) here (note that in the last step you select the ATK0110 driver in the list instead of the one mentioned)

Update that first and see what happens.

Regards,
Reventon

BUGCHECK SUMMARY

Code:

Built by: 7600.16539.amd64fre.win7_gdr.100226-1909
Debug session time: Thu Jul  8 19:52:38.468 2010 (GMT+12)
System Uptime: 0 days 0:07:02.701
BugCheck 19, {22, 20000000000, 0, 0}
Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+72f8 )
BUGCHECK_STR:  0x19_22
PROCESS_NAME:  System
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
Built by: 7600.16539.amd64fre.win7_gdr.100226-1909
Debug session time: Wed Jul  7 17:25:25.714 2010 (GMT+12)
System Uptime: 0 days 0:07:28.962
BugCheck 19, {22, 20000000000, 0, 0}
Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+72f8 )
BUGCHECK_STR:  0x19_22
PROCESS_NAME:  System
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
Built by: 7600.16539.amd64fre.win7_gdr.100226-1909
Debug session time: Tue Jul  6 21:25:51.726 2010 (GMT+12)
System Uptime: 0 days 0:04:51.585
BugCheck 24, {1904fb, fffff88001fa45d8, fffff88001fa3e40, fffff800018b0bb3}
Probably caused by : Ntfs.sys ( Ntfs!NtfsDeleteScb+108 )
PROCESS_NAME:  System
BUGCHECK_STR:  0x24
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
Built by: 7600.16539.amd64fre.win7_gdr.100226-1909
Debug session time: Tue Jul  6 21:20:10.762 2010 (GMT+12)
System Uptime: 0 days 0:07:37.621
BugCheck 19, {22, 20000000000, 0, 0}
Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+72f8 )
BUGCHECK_STR:  0x19_22
PROCESS_NAME:  System
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
Built by: 7600.16539.amd64fre.win7_gdr.100226-1909
Debug session time: Sat Jul  3 14:53:33.698 2010 (GMT+12)
System Uptime: 0 days 0:06:52.946
BugCheck 50, {fffffaa00772c050, 0, fffff80001b9b0a2, 5}
Probably caused by : memory_corruption ( nt!MiRelocateImagePfn+3a )
BUGCHECK_STR:  0x50
PROCESS_NAME:  svchost.exe
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
Built by: 7600.16539.amd64fre.win7_gdr.100226-1909
Debug session time: Sat Jul  3 14:44:29.136 2010 (GMT+12)
System Uptime: 0 days 2:14:41.010
BugCheck 1A, {41790, fffffa80004648e0, ffff, 0}
Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+33946 )
BUGCHECK_STR:  0x1a_41790
PROCESS_NAME:  SearchProtocol
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
Built by: 7600.16539.amd64fre.win7_gdr.100226-1909
Debug session time: Sat Jul  3 12:29:03.881 2010 (GMT+12)
System Uptime: 0 days 0:21:29.115
BugCheck 24, {1904fb, fffff88001da45d8, fffff88001da3e40, fffff80001866bb3}
Probably caused by : Ntfs.sys ( Ntfs!NtfsDeleteScb+108 )
PROCESS_NAME:  System
BUGCHECK_STR:  0x24
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨

Thankyou,

Did this file appear in all the dumps?

Yes it did. There is still a large possibility that it could still be hardware caused; but deal with that first