I have had this nagging BSOD after my computer has been up for more than a week and I try to share a DVD across my home network (too poor and too much of a tightwad to spend money for a DVD drive for my netbook hooked to my sound system and TV in my bedroom upstairs).
A crash every 8-9 days really isn't that big of a deal for me (and will be a pain to diagnose as it doesn't happen frequently) as I like to shut it down every night anyways but I wanted to figure the root cause. Could be a malfunctioning part, but I have thoroughly tested my RAM after I got it, my CPU unlock is stable and has been for some time, even under Prime95 for several hours, and my GPU has been stable even OC'ed for about a year and a half but who knows. Here are two copies of the Windows Recovery prompt that I have recorded:
Problem Event Name: BlueScreen
OS Version: 6.1.7601.2.1.0.768.3
Locale ID: 1033
Additional information about the problem:
OS Version: 6_1_7601
Service Pack: 1_0
Files that help describe the problem:
If the online privacy statement is not available, please read our privacy statement offline:
Windows 7 Home Premium 64 Bit
AMD Phenom II x4 B45 @3.2GHz
8GB G. Skill DDR3 1333 RAM
MSI GTX 460 1GB (Stock since the first BSOD)
This evening I got it to share the DVD and then it hit a bad part of the DVD and froze. VLC wouldn't connect to the rig after it crashed then when I came down it was slow and then it crashed. VLC 2.0.1 also had a hard time installing before I started... I just thought I would post this to see if anyone would have any ideas. Any would be greatly appreciated. Thanks!
An attempt was made to access a pageable (or completely invalid) address at an
interrupt request level (IRQL) that is too high. This is usually
caused by drivers using improper addresses.
If a kernel debugger is available get the stack backtrace.
Arg1: 0000000000000000, memory referenced
Arg2: 0000000000000002, IRQL
Arg3: 0000000000000001, bitfield :
bit 0 : value 0 = read operation, 1 = write operation
bit 3 : value 0 = not an execute operation, 1 = execute operation (only on chips which support this level of status)
Arg4: fffff80002eca704, address which referenced memory
WRITE_ADDRESS: GetPointerFromAddress: unable to read from fffff8000310a100
TRAP_FRAME: fffff8800a5cb650 -- (.trap 0xfffff8800a5cb650)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=0000000000000000 rbx=0000000000000000 rcx=fffffa8008fcda20
rdx=fffffa800d78f020 rsi=0000000000000000 rdi=0000000000000000
rip=fffff80002eca704 rsp=fffff8800a5cb7e0 rbp=fffff8000304de80
r8=fffffa80076f9b00 r9=fffffa8008fcda20 r10=fffff80003062301
r11=0000000000000000 r12=0000000000000000 r13=0000000000000000
iopl=0 nv up ei ng nz na pe nc
fffff800`02eca704 488910 mov qword ptr [rax],rdx ds:6000:00000000`00000000=????????????????
Resetting default scope
LAST_CONTROL_TRANSFER: from fffff80002ed82e9 to fffff80002ed8d40
And a quick Google Search pulls up "Probably caused by : ntkrnlmp.exe" means one of the following:
•Require a microcode update that is not applied by the computer's basic input/output system (BIOS).
•Are damaged or defective.
•Are operating outside their specified ranges for temperature, power, or other conditions.
So my guess is my unlocked CPU is throwing fits... Guess I can add some more voltage and if that does work just make sure to restart it every now and again cause I like my unlock.