So I have literally been battling blue screens for weeks now. I have rebuilt my entire computer, ditched that, bought an OEM machine, and the problem still persists. Really the only thing has remained the same through my now 3 Windows reinstalls is the software I'm using. As such, I'm very certain this is a software problem, but because the minidumps aren't pointing to specific driver .exes, I'm not sure where I should start pruning my software. In the past week it's blue screen 7 times, I've analyzed all of the dumps with Windows Debugger, and they all essentially say the same thing. Here's a representative minidump:
So I have literally been battling blue screens for weeks now. I have rebuilt my entire computer, ditched that, bought an OEM machine, and the problem still persists. Really the only thing has remained the same through my now 3 Windows reinstalls is the software I'm using. As such, I'm very certain this is a software problem, but because the minidumps aren't pointing to specific driver .exes, I'm not sure where I should start pruning my software. In the past week it's blue screen 7 times, I've analyzed all of the dumps with Windows Debugger, and they all essentially say the same thing. Here's a representative minidump:
Could not read faulting driver name
Probably caused by : ntkrnlmp.exe ( nt!CmpFindValueByNameFromCache+12f )
Followup: MachineOwner
---------
0: kd> !analyze -v
PAGE_FAULT_IN_NONPAGED_AREA (50)
Invalid system memory was referenced. This cannot be protected by try-except,
it must be protected by a Probe. Typically the address is just plain bad or it
is pointing at freed memory.
Arguments:
Arg1: fffff6f45000b100, memory referenced.
Arg2: 0000000000000000, value 0 = read operation, 1 = write operation.
Arg3: fffff800030eaae2, If non-zero, the instruction address which referenced the bad memory
address.
Arg4: 0000000000000005, (reserved)
Debugging Details:
------------------
Could not read faulting driver name
READ_ADDRESS: GetPointerFromAddress: unable to read from fffff8000330d0e0
fffff6f45000b100
FAULTING_IP:
nt!MiAgeWorkingSet+1c2
fffff800`030eaae2 488b19 mov rbx,qword ptr [rcx]
MM_INTERNAL_CODE: 5
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
BUGCHECK_STR: 0x50
PROCESS_NAME: System
CURRENT_IRQL: 0
TRAP_FRAME: fffff880033167a0 -- (.trap 0xfffff880033167a0)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=0000007ffffffff8 rbx=0000000000000000 rcx=fffff6f45000b100
rdx=0000000000000001 rsi=0000000000000000 rdi=0000000000000000
rip=fffff800030eaae2 rsp=fffff88003316930 rbp=007ffff45000b106
r8=0000000000000001 r9=fffff80003261b40 r10=0000000000000005
r11=0000000000000000 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0 nv up ei ng nz na po cy
nt!MiAgeWorkingSet+0x1c2:
fffff800`030eaae2 488b19 mov rbx,qword ptr [rcx] ds:fffff6f4`5000b100=????????????????
Resetting default scope
LAST_CONTROL_TRANSFER: from fffff80003154b91 to fffff800030d6f00
STACK_TEXT:
fffff880`03316638 fffff800`03154b91 : 00000000`00000050 fffff6f4`5000b100 00000000`00000000 fffff880`033167a0 : nt!KeBugCheckEx
fffff880`03316640 fffff800`030d4fee : 00000000`00000000 00000980`00000000 00000000`00000000 00000000`00000801 : nt! ?? ::FNODOBFM::`string'+0x40f5b
fffff880`033167a0 fffff800`030eaae2 : 00000003`00000000 c8200001`09efa963 00000000`00000000 00000000`00001482 : nt!KiPageFault+0x16e
fffff880`03316930 fffff800`03157a0e : fffff800`03261b40 fffff880`00000001 00000000`00000001 fffff880`03316bb0 : nt!MiAgeWorkingSet+0x1c2
fffff880`03316ae0 fffff800`030eb6e2 : 00000000`0000e6c1 00000000`00000000 fffffa80`00000000 00000000`00000002 : nt! ?? ::FNODOBFM::`string'+0x49926
fffff880`03316b80 fffff800`030eb96f : 00000000`00000008 fffff880`03316c10 00000000`00000001 fffffa80`00000000 : nt!MmWorkingSetManager+0x6e
fffff880`03316bd0 fffff800`0337a166 : fffffa80`03591680 00000000`00000080 fffffa80`0356d040 00000000`00000001 : nt!KeBalanceSetManager+0x1c3
fffff880`03316d40 fffff800`030b5486 : fffff880`009e8180 fffffa80`03591680 fffff880`009f2fc0 5754905d`d199fa38 : nt!PspSystemThreadStartup+0x5a
fffff880`03316d80 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxStartSystemThread+0x16
STACK_COMMAND: kb
FOLLOWUP_IP:
nt!MiAgeWorkingSet+1c2
fffff800`030eaae2 488b19 mov rbx,qword ptr [rcx]
SYMBOL_STACK_INDEX: 3
SYMBOL_NAME: nt!MiAgeWorkingSet+1c2
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: nt
DEBUG_FLR_IMAGE_TIMESTAMP: 4a5bc600
IMAGE_NAME: memory_corruption
FAILURE_BUCKET_ID: X64_0x50_nt!MiAgeWorkingSet+1c2
BUCKET_ID: X64_0x50_nt!MiAgeWorkingSet+1c2
Followup: MachineOwner
In this dump, Firefox is causing the problem, but I've actually reinstalled Firefox 3 times now, disabled add-ons, and so forth, nothing seems to affect the BSODs. Similar, Photoshop has been stopped working (crashing on start "Appcrash" in the error reports), and I've reinstalled that 2x now. The most recent version is old (I thought maybe CS4 was causing problems), but yesterday CS2 stopped working as well. For some reason a quick restart solved that one, but I'm essentially waiting for it to corrupt itself irreparably as well.
I ran Memtest86+ from the bootable iso and it says my memory is A-okay, after more than a hour of testing.
I haven't found a repeatable way to provoke the bluescreens, it seems to be fairly random. I'm always able to reboot without incident.
What I have noticed is that I have a lot of general system instability. Firefox, photoshop, thunderbird, and chrome crash several times a day seemingly unprovoked. The error messages I get are generally cryptic and don't point to any obvious problem (I may just not be good at troubleshooting specific program crashes though).
Yesterday my programs were crashing on load, and some were simply saying that .dlls were missing or corrupt. I restarted and it seems to have (at least temporarily) fixed the problem.
If I can't find a solution, I'll probably just reformat and reinstall XP again because it appears to like my hardware/software setup much better. Just in case it's helpful, here are my system specs:
Intel Core i3 2.93Ghz
4 GB RAM DDR3 1333mhz
64 bit Windows 7 Home Premium
500 GB SataII WD HD
Intel H55 Mobo chipset
ATI Radeon HD4350
This is a clean (and legit) install of Windows 7 on a newly formatted partition, so there shouldn't be any dual booting weirdness.
Any help you could lend would be very much appreciated, as I said, I've been wrestling with this for ages, and it feels like I'm getting nowhere.
-George
So I have literally been battling blue screens for weeks now. I have rebuilt my entire computer, ditched that, bought an OEM machine, and the problem still persists. Really the only thing has remained the same through my now 3 Windows reinstalls is the software I'm using. As such, I'm very certain this is a software problem, but because the minidumps aren't pointing to specific driver .exes, I'm not sure where I should start pruning my software. In the past week it's blue screen 7 times, I've analyzed all of the dumps with Windows Debugger, and they all essentially say the same thing. Here's a representative minidump:
Could not read faulting driver name
Probably caused by : ntkrnlmp.exe ( nt!CmpFindValueByNameFromCache+12f )
Followup: MachineOwner
---------
0: kd> !analyze -v
PAGE_FAULT_IN_NONPAGED_AREA (50)
Invalid system memory was referenced. This cannot be protected by try-except,
it must be protected by a Probe. Typically the address is just plain bad or it
is pointing at freed memory.
Arguments:
Arg1: fffff6f45000b100, memory referenced.
Arg2: 0000000000000000, value 0 = read operation, 1 = write operation.
Arg3: fffff800030eaae2, If non-zero, the instruction address which referenced the bad memory
address.
Arg4: 0000000000000005, (reserved)
Debugging Details:
------------------
Could not read faulting driver name
READ_ADDRESS: GetPointerFromAddress: unable to read from fffff8000330d0e0
fffff6f45000b100
FAULTING_IP:
nt!MiAgeWorkingSet+1c2
fffff800`030eaae2 488b19 mov rbx,qword ptr [rcx]
MM_INTERNAL_CODE: 5
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
BUGCHECK_STR: 0x50
PROCESS_NAME: System
CURRENT_IRQL: 0
TRAP_FRAME: fffff880033167a0 -- (.trap 0xfffff880033167a0)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=0000007ffffffff8 rbx=0000000000000000 rcx=fffff6f45000b100
rdx=0000000000000001 rsi=0000000000000000 rdi=0000000000000000
rip=fffff800030eaae2 rsp=fffff88003316930 rbp=007ffff45000b106
r8=0000000000000001 r9=fffff80003261b40 r10=0000000000000005
r11=0000000000000000 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0 nv up ei ng nz na po cy
nt!MiAgeWorkingSet+0x1c2:
fffff800`030eaae2 488b19 mov rbx,qword ptr [rcx] ds:fffff6f4`5000b100=????????????????
Resetting default scope
LAST_CONTROL_TRANSFER: from fffff80003154b91 to fffff800030d6f00
STACK_TEXT:
fffff880`03316638 fffff800`03154b91 : 00000000`00000050 fffff6f4`5000b100 00000000`00000000 fffff880`033167a0 : nt!KeBugCheckEx
fffff880`03316640 fffff800`030d4fee : 00000000`00000000 00000980`00000000 00000000`00000000 00000000`00000801 : nt! ?? ::FNODOBFM::`string'+0x40f5b
fffff880`033167a0 fffff800`030eaae2 : 00000003`00000000 c8200001`09efa963 00000000`00000000 00000000`00001482 : nt!KiPageFault+0x16e
fffff880`03316930 fffff800`03157a0e : fffff800`03261b40 fffff880`00000001 00000000`00000001 fffff880`03316bb0 : nt!MiAgeWorkingSet+0x1c2
fffff880`03316ae0 fffff800`030eb6e2 : 00000000`0000e6c1 00000000`00000000 fffffa80`00000000 00000000`00000002 : nt! ?? ::FNODOBFM::`string'+0x49926
fffff880`03316b80 fffff800`030eb96f : 00000000`00000008 fffff880`03316c10 00000000`00000001 fffffa80`00000000 : nt!MmWorkingSetManager+0x6e
fffff880`03316bd0 fffff800`0337a166 : fffffa80`03591680 00000000`00000080 fffffa80`0356d040 00000000`00000001 : nt!KeBalanceSetManager+0x1c3
fffff880`03316d40 fffff800`030b5486 : fffff880`009e8180 fffffa80`03591680 fffff880`009f2fc0 5754905d`d199fa38 : nt!PspSystemThreadStartup+0x5a
fffff880`03316d80 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxStartSystemThread+0x16
STACK_COMMAND: kb
FOLLOWUP_IP:
nt!MiAgeWorkingSet+1c2
fffff800`030eaae2 488b19 mov rbx,qword ptr [rcx]
SYMBOL_STACK_INDEX: 3
SYMBOL_NAME: nt!MiAgeWorkingSet+1c2
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: nt
DEBUG_FLR_IMAGE_TIMESTAMP: 4a5bc600
IMAGE_NAME: memory_corruption
FAILURE_BUCKET_ID: X64_0x50_nt!MiAgeWorkingSet+1c2
BUCKET_ID: X64_0x50_nt!MiAgeWorkingSet+1c2
Followup: MachineOwner
In this dump, Firefox is causing the problem, but I've actually reinstalled Firefox 3 times now, disabled add-ons, and so forth, nothing seems to affect the BSODs. Similar, Photoshop has been stopped working (crashing on start "Appcrash" in the error reports), and I've reinstalled that 2x now. The most recent version is old (I thought maybe CS4 was causing problems), but yesterday CS2 stopped working as well. For some reason a quick restart solved that one, but I'm essentially waiting for it to corrupt itself irreparably as well.
I ran Memtest86+ from the bootable iso and it says my memory is A-okay, after more than a hour of testing.
I haven't found a repeatable way to provoke the bluescreens, it seems to be fairly random. I'm always able to reboot without incident.
What I have noticed is that I have a lot of general system instability. Firefox, photoshop, thunderbird, and chrome crash several times a day seemingly unprovoked. The error messages I get are generally cryptic and don't point to any obvious problem (I may just not be good at troubleshooting specific program crashes though).
Yesterday my programs were crashing on load, and some were simply saying that .dlls were missing or corrupt. I restarted and it seems to have (at least temporarily) fixed the problem.
If I can't find a solution, I'll probably just reformat and reinstall XP again because it appears to like my hardware/software setup much better. Just in case it's helpful, here are my system specs:
Intel Core i3 2.93Ghz
4 GB RAM DDR3 1333mhz
64 bit Windows 7 Home Premium
500 GB SataII WD HD
Intel H55 Mobo chipset
ATI Radeon HD4350
This is a clean (and legit) install of Windows 7 on a newly formatted partition, so there shouldn't be any dual booting weirdness.
Any help you could lend would be very much appreciated, as I said, I've been wrestling with this for ages, and it feels like I'm getting nowhere.
-George
My Computer
- Computer Manufacturer/Model Number
- Cyberpower Inc
- OS
- Windows 7
- CPU
- Intel Core i3 2.93 Ghz
- Motherboard
- Gigabyte H55M-Ud2H
- Memory
- 4 GB DDR3 1333Mhz
- Graphics Card(s)
- ATI Radeon 4350
- Sound Card
- Integrated Realtek
- Monitor(s) Displays
- 1 HP L2045w 20.1 LCD
- Hard Drives
- 1 USB 500 GB WD 7200rpm
1 SataII 3MB 1.5 TB 7200rpm
1 SataII 3MB 500 GB 7200rpm
- PSU
- 420W
- Case
- V3 Gaming Case
- Cooling
- 2 80mm case fans + psu fan
