Random BSOD's

Toggle sidebar Toggle sidebar
S

scoughlin1

Member
Jun 15, 2004
58
0
0
I've had problems with random reboots for probably a couple months now at the least. The computer used to just restart without a blue screen even though I told it to not automatically restart when there was an error, but now it's courteous enough to tell me what went wrong. Over and over its a kernel overflow error, the last error code it gave me was 0X0000007F (0X00000008, 0X80042000, 0X00000000, 0X00000000). I looked it up and I found this page : http://support.microsoft.com/?kbid=822789
and of course I noticed that it says it could also be a memory error, I just replaced my memory a few days ago to try and fix things (I was due for a mem upgrade anyway) but it still BSOD's me atleast once a day. I had Symantec Antivirus installed and tried that registry fix they recommended but I still had crashes. Today I got rid of Symantec and downloaded a trial of Bit Defender and I got the same BSOD. I'd really like to fix this problem soon since its been a serious thorn in my side for quite some time. What do you think is causing this? Thanks.
 
S

scoughlin1

Member
Jun 15, 2004
58
0
0
By the way: my system...
XP Pro
Antec TruePower 480W
Abit IC7-Max3
P4 2.4C
1GB Corsair XMS pc 3700
Radeon 9700 pro
36.7GB WD Raptor
120GB SATA Seagate
120GB WD
Pioneer 4x dvd burner
 
N

nanaki333

Diamond Member
Sep 14, 2002
3,772
13
81
heh.. lemme know when you find a solution to that. mine used to randomly do that too, now it just locks up on me. i've swapped out every component. only original thing left is my case and i still have basically the same issues. swapping out my mobo made it go from random BSOD to random lockups. :(
 
L

L1FE

Senior member
Dec 23, 2003
545
0
71
Maybe you're overheating? What are the temps on your system? Does it always randomly reboot or are you ever doing anything specific that in general causes the lockups? If it is a heat problem, maybe add a couple of fans in that sucker.
 
S

scoughlin1

Member
Jun 15, 2004
58
0
0
I don't think it has anything to do with heat. My hard drives all run in the 90-95F range, motherboard is usually around 80, PSU in the low 90's, and the cpu is in the mid 80's. These are all idle temps of course. Like I said, I just bought new ram a few days ago so if it's already error ridden that would be odd. I tested my other memory overnight about a week ago and it came up with no errors, and I'm still getting the same BSOD's with new memory. My cpu is running at stock speed and I haven't even touched the memory timings or anything like that since replacing it.
 
F

Frito

Member
Jun 2, 2004
30
0
0
Try turning down the CAS to 3 and taking the speed down a notch see how it runs then.
 
S

scoughlin1

Member
Jun 15, 2004
58
0
0
I honestly don't understand why this would be a memory problem. I'm getting the exact errors with new memory that I got with the old stuff, which would signal that it probably has nothing at all to do with the ram, correct?
 
S

scoughlin1

Member
Jun 15, 2004
58
0
0
No one knows? The only pattern I can see is the crashes usually occur in the evening or overnight. I think only once has it crashed when I was playing a game, it's usually when I'm sleeping or just sitting here talking to people and listening to music. It's been suggested elsewhere that one of my hard drives could be causing the problem and possibly it's just a corrupted XP install.
 
S

Sianath

Senior member
Sep 1, 2001
437
0
0
Stop 7F is almost always hardware (either memory or CPU). If you got a mini dump (64k) send it to me at sianath@hotmail.com and I'll take a look at it. If you didn't, configure your machine to capture one (right-click my computer, properties, advanced, startup and recovery) and send it to me.

:)
 
S

scoughlin1

Member
Jun 15, 2004
58
0
0
Thanks Sianath, I'll be sure to do that if and when I have another crash. I had it set to do a complete memory dump but I just now set it to 64kb.

Edit: I have a couple of minidump files from the 6th and 7th of this month which is before I set it to do complete dumps. They may or may not be useful since I changed my memory exactly a week ago today and my motherboard about 10 days ago.
 
S

Sianath

Senior member
Sep 1, 2001
437
0
0
If you want, send me the minidumps and I'll check 'em out. They may not give a ton of detail, but depending on the error they can be enough sometimes. :)
 
S

scoughlin1

Member
Jun 15, 2004
58
0
0
Just had another crash overnight, but it didn't leave a minidump for me. This probably means it just rebooted without a blue screen which is how it does it quite a bit. I'll send you the old dump files and let you take a look.
 
S

Sianath

Senior member
Sep 1, 2001
437
0
0
There are very few cases where we will bugcheck and NOT give a memory dump. If ASR is enabled (automatic system recovery) we won't get a good dump, if there isn't a large enough page file, if it's a triple-fault (which I haven't seen since VPC prior to us taking it over) or if it's a hardware reset (due to some type of hardware failure).

Please send me what you have, I'm curious now. :)
 
S

Sianath

Senior member
Sep 1, 2001
437
0
0
Set it for a kernel dump and see if you can get one. One of your minidumps is corrupt, the other looks like memory corruption. If you are getting frequent bugchecks that are all different stop codes, chances are likely that it's memory, cpu, or a bad driver.

1: kd> r
Last set context:
eax=00000000 ebx=0000001d ecx=f79bd794 edx=f79bd9d0 esi=f766cde9 edi=00000000
eip=805c153b esp=f79fd768 ebp=00000002 iopl=0 nv up ei pl nz na pe nc
cs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000 efl=00010202
nt!MiRememberUnloadedDriver+0x62:
805c153b 8b4704 mov eax,[edi+0x4] ds:0023:00000004=????????

The highlighted section is our stack base pointer (unless we are using FPO). That memory address is NEVER valid, regardless of what it's used for. We either have something corrupting the memory, or bad hardware.

I can't check in the minidump the CPU version information, so you should check and make sure you have the most current microcode (updated with BIOS normally, see highlight below for where version normally is).

1: kd> !cpuid
Unable to get information for processor 0
CP F/M/S Manufacturer MHz
1 15,2,9 GenuineIntel 2405

1: kd> !cpuinfo
CP F/M/S Manufacturer MHz Update Signature Current Signature Features
1 15,2,9 0 0000000000000000 0000000000000000 00000000


How frequent are the bugchecks? If it happens fairly routinely, I'd like you to do something for me to get us a better dump (the problem is that since we don't have a suspect driver it will negatively impact performance until we get the dump).

If you're willing to take the performance hit, I want you to enable special pool.

Start, Run, Verifier, Create custom settings, Select individual settings, Special Pool

Now we have a choice... if you want to try the first one with just unsigned drivers, choose that option and get a dump. If that one doesn't show us anything either, we can go back and set this for ALL drivers (that's the performance hit).

This catches when a driver overruns their pool allocation (by far the most common form of memory corruption) and bugchecks the box as soon as that happens. This way we can see who is doing it.

:)
 
S

scoughlin1

Member
Jun 15, 2004
58
0
0
k, I enabled the special pool and set it for unsigned drivers. it listed probably 6 or 7 things and then told me to reboot.
 
S

scoughlin1

Member
Jun 15, 2004
58
0
0
Also I set it to do kernel dumps. I noticed this program named debugging tools for windows and I opened both of the dump files I sent you with it. The first was corrupt and the second one said the likely problem was ntoskrnl.exe.
 
S

scoughlin1

Member
Jun 15, 2004
58
0
0
Well I got another BSOD about an hour ago. I saw it go to the blue screen and it was the same error as before. It doesn't seem that it left a minidump file however, unless I'm just not looking in the right place.

Edit: I had it set to not overwrite the dump file when a new error occured. I changed this and hopefully it'll put something out next time. The current memory.dmp file is 523mb.
 
S

scoughlin1

Member
Jun 15, 2004
58
0
0
Another crash a couple hours ago. The mouse froze, maybe about 2 seconds later the screen went black and the computer rebooted. It once again didn't leave any sort of error report for me :(
 
You must log in or register to reply here.

TRENDING THREADS

COMPANY
RESOURCES
FOLLOW
Top Bottom