Hi,
I seem to be having a problem with BSOD which started to occur a few days ago. I ran across these boards whilst searching for answers (yet finding none) and the folks around here seem to have a grip on how to decode BSOD dumps.
My setup:
Athlon64 3000+ @ 1.8ghz (Winchestor core 90nm)
2x512mb kingston pc400 valueram (in dual channel mode)
Gigabyte k8ns 939 ultra motherboard (nforce3 ultra chipset, realtek ac97 audio, sata, 8x agp etc)
radeon x800xt (256mb, agp)
320gb seagate 7200rpm hdd
400w silentpower psu
The system is at stock speeds with the ram timings being set by spd. With the current weather conditions here (cold) and the low heat disipation of the athlon64 processors, the cpu rarely hits 20C above ambient and that is with an hour or so of constant compiling being done.
I have done a bit of sleuthing about with the dumps and windbger.
The 0x8e bsod is always:
KERNEL_MODE_EXCEPTION_NOT_HANDLED (8e)
--snip help text from windbg--
Arguments:
Arg1: c0000005, The exception code that was not handled
Arg2: bf80195d, The address that the exception occurred at
Arg3: aedeaba4, Trap Frame
Arg4: 00000000
EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at "0x%08lx" referenced memory at "0x%08lx". The memory could not be "%s".
FAULTING_IP:
win32k!HMAssignmentLock+3b
bf80195d ff4f04 dec dword ptr [edi+4]
The error is always at the same address with win32k.sys. The process name usually varies with whatever I may be doing at the time.
I do not have a full memory dump from a 0x50 bsod but there are several minidumps which I have attached from the 0x8e and 0x50 bsods. There are also a few from when I turned on the driver verifier, those dumps did not help me any but may help if someone looks at them. (Sandra is mentioned in a few of the dumps but I have removed it due to the Sandra service causing faults in verify).
I have tested my ram with the ms memory diagnostic software for a few runs but have not run into any errors. I am going to leave my computer running memtest86+ overnight tonight to see if I can get any errors from the ram. I have changed the harddrive on which windows was installed to rule out the harddrive from the equation. I also tried removing all the hardware from my system that I could while still being able to boot windows.
On a sidenote, Prime95 crashes when run in torture mode when it is set on blended. I don't know if its related to my computer or to selinux in fedora but a kernel compile in fedora5 fails with a bad kernel being produced (it doesnt however bomb out in the compiling, just in the linking).
Summing it all up, I have not as yet discovered a way to produce these bluescreens other then to use my computer normally. These bluescreens can pop up multiple times within an hour or not at all during an entire day of use. Any help or advice would be greatly appreciated. I will post the results of the overnight memtest if anything interesting occurs. Thankyou for reading.
note: the zips of the mini-dumps are in chronological order (or should be anyhow) 1 being the oldest set, 3 being the newer.
I seem to be having a problem with BSOD which started to occur a few days ago. I ran across these boards whilst searching for answers (yet finding none) and the folks around here seem to have a grip on how to decode BSOD dumps.
My setup:
Athlon64 3000+ @ 1.8ghz (Winchestor core 90nm)
2x512mb kingston pc400 valueram (in dual channel mode)
Gigabyte k8ns 939 ultra motherboard (nforce3 ultra chipset, realtek ac97 audio, sata, 8x agp etc)
radeon x800xt (256mb, agp)
320gb seagate 7200rpm hdd
400w silentpower psu
The system is at stock speeds with the ram timings being set by spd. With the current weather conditions here (cold) and the low heat disipation of the athlon64 processors, the cpu rarely hits 20C above ambient and that is with an hour or so of constant compiling being done.
I have done a bit of sleuthing about with the dumps and windbger.
The 0x8e bsod is always:
KERNEL_MODE_EXCEPTION_NOT_HANDLED (8e)
--snip help text from windbg--
Arguments:
Arg1: c0000005, The exception code that was not handled
Arg2: bf80195d, The address that the exception occurred at
Arg3: aedeaba4, Trap Frame
Arg4: 00000000
EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at "0x%08lx" referenced memory at "0x%08lx". The memory could not be "%s".
FAULTING_IP:
win32k!HMAssignmentLock+3b
bf80195d ff4f04 dec dword ptr [edi+4]
The error is always at the same address with win32k.sys. The process name usually varies with whatever I may be doing at the time.
I do not have a full memory dump from a 0x50 bsod but there are several minidumps which I have attached from the 0x8e and 0x50 bsods. There are also a few from when I turned on the driver verifier, those dumps did not help me any but may help if someone looks at them. (Sandra is mentioned in a few of the dumps but I have removed it due to the Sandra service causing faults in verify).
I have tested my ram with the ms memory diagnostic software for a few runs but have not run into any errors. I am going to leave my computer running memtest86+ overnight tonight to see if I can get any errors from the ram. I have changed the harddrive on which windows was installed to rule out the harddrive from the equation. I also tried removing all the hardware from my system that I could while still being able to boot windows.
On a sidenote, Prime95 crashes when run in torture mode when it is set on blended. I don't know if its related to my computer or to selinux in fedora but a kernel compile in fedora5 fails with a bad kernel being produced (it doesnt however bomb out in the compiling, just in the linking).
Summing it all up, I have not as yet discovered a way to produce these bluescreens other then to use my computer normally. These bluescreens can pop up multiple times within an hour or not at all during an entire day of use. Any help or advice would be greatly appreciated. I will post the results of the overnight memtest if anything interesting occurs. Thankyou for reading.
note: the zips of the mini-dumps are in chronological order (or should be anyhow) 1 being the oldest set, 3 being the newer.