I have VERY bad luck with BSODs. My old PC BSODed so bad that it would corrupt the C partition about 10 times, then it would attack the D partition... this happened to TWO machines. Anyway, when it hit my machine at home I had to rebuild a new PC since I had no freaken clue wtf was causing this, it was not hardware (all diagnostic tests passed), and it was not software(I kept restoring a fresh image every time, an image that had proved to be stable for the longest time).
Now I'm getting more bad luck, my new machine randomly BSODs, OR freezes completely, cursor and all. The BSODs are too fast, but say something about DRIVER_KRNDL_10101001 then a bunch of hex values, it's not your typical NT BSOD with tons of writing, it's like 2 lines. I can tell when it's going to happen since sometimes the system will beep, freeze, the screen will turn off, then come back on to the BSOD, then it reboots.
what's going on? I'm a comp sci student so obviously know what I'm doing, but this has me stuned, win2k was not this bad at me before....
System specs:
AMD 64 3200+
Asus A8V
2X 512MB of DDR ram (forget speed, I think it's 2700) dual channel
120GB seagate sata HDD
Nvidia gforce 4 4200TI
Software running while it happends:
-Sygate personal firewall
- MSN
- AVG
- Asus Probe
OS is windows 2000 SP4
I use other programs, but it does not always crash with those programs, the ones above are the only always on programs.
Also I have VMware and as far as I know there's some services related to VMware that run such as the network stuff. But VMware itself is not always on when it happends.
I checked the event log but only errors I find is something about DCOM which are far from the time of the crashes:
Anyone have a clue what's going on? Is there a way to "capture" BSODs so I can post more info next time it happends? It's exponentially more often. It used to be once or twice a month then per week, and now, today I got 2... so the next step is total corruption of my HDD like all other times.
I've done plenty of memetests, HDD tests etc... so I know it's not that. My CPU/Mobo temps are also super low. Around 30 for cpu and 20 for mobo.
Been doing some research with the little info I have and found another BSOD I got a couple of times: IRQL_NOT_LESS_OR_EQUAL I got that a couple of times too, but have not seen it in a while, now it's the DRIVER_NTKRNL one and a system file (no time to write it down)
Edit: Just got another... this time it said something about page_fault but again, too fast to read it properly. This is getting F-ing rediculous.
Now I'm getting more bad luck, my new machine randomly BSODs, OR freezes completely, cursor and all. The BSODs are too fast, but say something about DRIVER_KRNDL_10101001 then a bunch of hex values, it's not your typical NT BSOD with tons of writing, it's like 2 lines. I can tell when it's going to happen since sometimes the system will beep, freeze, the screen will turn off, then come back on to the BSOD, then it reboots.
what's going on? I'm a comp sci student so obviously know what I'm doing, but this has me stuned, win2k was not this bad at me before....
System specs:
AMD 64 3200+
Asus A8V
2X 512MB of DDR ram (forget speed, I think it's 2700) dual channel
120GB seagate sata HDD
Nvidia gforce 4 4200TI
Software running while it happends:
-Sygate personal firewall
- MSN
- AVG
- Asus Probe
OS is windows 2000 SP4
I use other programs, but it does not always crash with those programs, the ones above are the only always on programs.
Also I have VMware and as far as I know there's some services related to VMware that run such as the network stuff. But VMware itself is not always on when it happends.
I checked the event log but only errors I find is something about DCOM which are far from the time of the crashes:
Code:
Event Type: Error
Event Source: DCOM
Event Category: None
Event ID: 10010
Date: 10/7/2005
Time: 10:14:45 PM
User: DESTROYER\ryan
Computer: DESTROYER
Description:
The server {73AA8F59-DBC4-11D0-AF5C-00A02448799A} did not register with DCOM within the required timeout.
Anyone have a clue what's going on? Is there a way to "capture" BSODs so I can post more info next time it happends? It's exponentially more often. It used to be once or twice a month then per week, and now, today I got 2... so the next step is total corruption of my HDD like all other times.
I've done plenty of memetests, HDD tests etc... so I know it's not that. My CPU/Mobo temps are also super low. Around 30 for cpu and 20 for mobo.
Been doing some research with the little info I have and found another BSOD I got a couple of times: IRQL_NOT_LESS_OR_EQUAL I got that a couple of times too, but have not seen it in a while, now it's the DRIVER_NTKRNL one and a system file (no time to write it down)
Edit: Just got another... this time it said something about page_fault but again, too fast to read it properly. This is getting F-ing rediculous.