Frontpage
Forums
Tutorials
Members
Calendar
Subscription
Donate
Links
Contact 
HelpSincerly Dan <Frustrated Dan>
Attached File(s)
-
Minidump.rar (128.74K)
Number of downloads: 7
Page 1 of 1
BlueScreen Crashes For nothing +minidump
Blue screen errors for nothing + Minidump
Rate Topic:
#1
Posted 08 December 2008 - 07:12 AM
Have formatted like 5 times Gettin blue screen errors stop messages replaced ram hdd everything system works for like a week then gets blue screens its driving me nuts i can post minidumps ANY HELP Would be Good If problem is fixed Ill even pay the person 50$ for fixing Please email me at iliketomoo@hotmail.com Or post here I am uploading minidump am posting files from another computer as i am sick of watching reboots on other computer.
Sincerly Dan <Frustrated Dan>
Sincerly Dan <Frustrated Dan>
Back to top
#2
- Gustatus similis pullus
-
- Group: Supervisor
- Posts: 11,208
- Joined: 09-September 01
- OS:Windows RT
-
Country:
-
Posted 08 December 2008 - 10:17 AM
Well, you've got everything from an Outpost firewall crash, to a win32k.sys glyph error, to NTFS flush errors. The only common thread is that in each case. the memory manager is reading memory pages, and an invalid page has been passed. I don't know if this is an actual memory error, or if you have a driver problem, but I would definitely run memtest86 against the RAM in that machine. I'm leaning towards bad RAM, but on the off chance your mem test does come back clean, it is possible that these crashes might be caused by Outpost firewall:
Again, I don't know if this is a victim of another problem, or the source of the problem, but since you have memory dumps that are all over the place in terms of callstacks and bugcheck codes, I'd start with the memory and not drivers on the system.
1: kd> kb ChildEBP RetAddr Args to Child WARNING: Stack unwind information not available. Following frames may be wrong. bad03898 b978f8cb 00000000 88d6a638 bad038d0 AfwCore+0x1b250 bad038a8 b9790a8a 00000001 00000000 88c51188 AfwCore+0x1b8cb bad038d0 b979fe0c 88d6a638 bad039cc 88c458b0 AfwCore+0x1ca8a bad039d8 b97a6767 000006eb 00000000 00000000 AfwCore+0x2be0c bad03ad0 b97834c9 88c458b0 8a2f1350 88c458a8 AfwCore+0x32767 bad03af0 b9776df7 bad03b1c bad03b2c b9777781 AfwCore+0xf4c9 bad03afc b9777781 00000001 8a2f12b8 b9781d90 AfwCore+0x2df7 bad03b2c b978283d 8a060f18 88eb8858 88eb88e4 AfwCore+0x3781 bad03b48 804ef19f 8a060f18 88eb8858 88eb8908 AfwCore+0xe83d bad03bb4 804ef19f 88da78c0 88eb8858 88eb8858 nt!IopfCallDriver+0x31 bad03bc4 80583953 8a2fef10 000000a8 8a692ad0 nt!IopfCallDriver+0x31 bad03bf4 805bca16 8a66fa00 88da78c0 0012019f nt!IopCloseFile+0x26b bad03c28 805bc33f 8a66fa00 00000001 8a692ad0 nt!ObpDecrementHandleCount+0xd8 bad03c50 805bc3dd e1000eb0 8a2fef28 00001fd8 nt!ObpCloseHandleTableEntry+0x14d bad03c98 805bc515 00001fd8 00000000 00000000 nt!ObpCloseHandle+0x87 bad03cac 8054162c 80001fd8 bad03d3c 804fff41 nt!NtClose+0x1d bad03cac 804fff41 80001fd8 bad03d3c 804fff41 nt!KiFastCallEntry+0xfc bad03d28 b69c7bff 80001fd8 88b65390 b69c4cb6 nt!ZwClose+0x11 bad03d3c b69c7bbc 88b65390 b69c67a8 bad03d68 afd!AfdFreeConnectionResources+0x28 bad03d4c b69c486a 88b65408 8a294540 89772858 afd!AfdFreeConnection+0x5c 1: kd> .bugcheck Bugcheck code 100000D1 Arguments 00000000 00000002 00000000 b978f250
Again, I don't know if this is a victim of another problem, or the source of the problem, but since you have memory dumps that are all over the place in terms of callstacks and bugcheck codes, I'd start with the memory and not drivers on the system.
#3
Posted 08 December 2008 - 11:31 AM
[quote name='cluberti' date='Dec 8 2008, 11:17 AM' post='817198']
Well, you've got everything from an Outpost firewall crash, to a win32k.sys glyph error, to NTFS flush errors. The only common thread is that in each case. the memory manager is reading memory pages, and an invalid page has been passed. I don't know if this is an actual memory error, or if you have a driver problem, but I would definitely run memtest86 against the RAM in that machine. I'm leaning towards bad RAM, but on the off chance your mem test does come back clean, it is possible that these crashes might be caused by Outpost firewall:
what does that mean to me? my firewall bullguard is causing it bad? Or i should turn off windows firewall What?
I got xp 32 bit and 4 gig of ram in system Should i be usin 64 bit to make use of the full ram? I took it to a computer shop to get fixed they said they ran memtest on it and told me it needed new ram so i got new ram went from 2 gig of ram to 4 gig ive replaced hdd and other stuff can you help me in detail how to fix it? Iliketomoo@hotmail.com hell if u can permo fix it ill even pay you
Well, you've got everything from an Outpost firewall crash, to a win32k.sys glyph error, to NTFS flush errors. The only common thread is that in each case. the memory manager is reading memory pages, and an invalid page has been passed. I don't know if this is an actual memory error, or if you have a driver problem, but I would definitely run memtest86 against the RAM in that machine. I'm leaning towards bad RAM, but on the off chance your mem test does come back clean, it is possible that these crashes might be caused by Outpost firewall:
what does that mean to me? my firewall bullguard is causing it bad? Or i should turn off windows firewall What?
I got xp 32 bit and 4 gig of ram in system Should i be usin 64 bit to make use of the full ram? I took it to a computer shop to get fixed they said they ran memtest on it and told me it needed new ram so i got new ram went from 2 gig of ram to 4 gig ive replaced hdd and other stuff can you help me in detail how to fix it? Iliketomoo@hotmail.com hell if u can permo fix it ill even pay you
#4
- Gustatus similis pullus
-
- Group: Supervisor
- Posts: 11,208
- Joined: 09-September 01
- OS:Windows RT
-
Country:
-
Posted 08 December 2008 - 07:16 PM
It means check the RAM in the system, and if you find problems, investigate there. If the RAM turns up clean, start looking at the outpost firewall driver as the culprit.
Share this topic:
Page 1 of 1