Win 7 64-bit BSOD

Fells

December 14, 2009 3:36:57 PM

Hi All,

I've been having random BSOD's since upgrading to Win 7 64-bit (never had a single BSOD while using XP Pro for over a year).
I've had pretty much every BSOD error message I've ever heard of in the last two months, quota manger, cache manager, bad pool caller, system thread, irq less than equal to, changes to system files, the list goes on...
The BSOD's can happen as often as two in a row, or as little as once every week, the reason for them (according to the minidump analysis) ranges from MSN and Firefox to svhost.exe and other windows services.
I've scanned my HDD with MHDD and found no slow/bad sectors, I've posted on the Corsair forums, tested all my ram (1 stick at a time in different slots) with Memtest and had no errors.
I've run stress tests with Everest for a few hours and had no crashes, I've also updated all my drivers (using Driver Genius).
MSINFO32 and Device Manager don't show any problem devices or drivers and my PSU (850Watt) is solid.
The only thing I haven't changed is my OC'ing (but this was stable under XP - 5 hours of stress testing with Prime95).
Short of a total re-image/wipe any ideas? If you like i can upload my dump files. PC Spec below.

Any help is appreciated, cheers.

Intel Core 2 Quad Q6600 G0 Stepping (2.4GHz 1066MHz) @3.2GHz
ASUS P5K-E/WIFI-AP AiLifestyle Series
2 x Corsair 2GB Kit (2x1GB) DDR2 800MHz/PC2-6400 XMS2 Memory Non-ECC Unbuffered CL4(4-4-4-12) E.P.P. Heat Spreader
Creative SoundBlaster X-Fi Xtreme Gamer Soundcard
NEC Optiarc AD-7170S-0S 18x DVD±RW/DL/RAM Serial ATA
Antec TruePower Quattro 850W Modular PSU 80PLUS Energy Efficiency
Seagate ST3500630AS 500GB Hard Drive SATAII 16MB Cache 7200RPM
Powercolour ATI HD 4870 1GB

More about : win bit bsod

| E-mail me updates
| Report abuse

Kewlx25

December 14, 2009 5:07:17 PM

If you have onboard sound, try this if you're willing

Remove your X-FI sound card, see if it goes away.

I'm not sure if this will work, but... In the World of Warcraft forums at one point there were a lot of people complaining about Win7 crashing. They all seemed to have difference CPUs/Video cards/etc, but they did seem to all be sporting Creative sound cards.

It's worth a shot and I'm curious if this actually works.

| Report abuse

Fells

December 15, 2009 3:22:56 PM

Thanks for the reply.

I'll do that and see how it is over the next few days, and report back either way

| Report abuse

Fells

December 17, 2009 7:14:57 PM

No joy, I uninstalled all the Creative software, used driver sweeper to remove anything left over - Been using the on board sound for two days and had my first BSOD today (minidump below)

BugCheck 50, {fffffa8007309a18, 0, fffff80002f7b78c, 2}

Could not read faulting driver name
Probably caused by : memory_corruption ( nt!MiEmptyPageAccessLog+dc )

Followup: MachineOwner
---------

2: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

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: fffffa8007309a18, memory referenced.
Arg2: 0000000000000000, value 0 = read operation, 1 = write operation.
Arg3: fffff80002f7b78c, If non-zero, the instruction address which referenced the bad memory
address.
Arg4: 0000000000000002, (reserved)

Debugging Details:
------------------

Could not read faulting driver name

READ_ADDRESS: GetPointerFromAddress: unable to read from fffff800030ad0e0
fffffa8007309a18

FAULTING_IP:
nt!MiEmptyPageAccessLog+dc
fffff800`02f7b78c 488b08 mov rcx,qword ptr [rax]

MM_INTERNAL_CODE: 2

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT

BUGCHECK_STR: 0x50

PROCESS_NAME: explorer.exe

CURRENT_IRQL: 0

TRAP_FRAME: fffff880033168e0 -- (.trap 0xfffff880033168e0)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=fffffa8007309a18 rbx=0000000000000000 rcx=0000000000000160
rdx=fffff8a007c990a8 rsi=0000000000000000 rdi=0000000000000000
rip=fffff80002f7b78c rsp=fffff88003316a70 rbp=fffffa8004b32000
r8=fffffa80054d002d r9=fffffa8004013048 r10=fffffa8005505c30
r11=fffffa80055041e0 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0 nv up ei ng nz na pe nc
nt!MiEmptyPageAccessLog+0xdc:
fffff800`02f7b78c 488b08 mov rcx,qword ptr [rax] ds:fffffa80`07309a18=????????????????
Resetting default scope

LAST_CONTROL_TRANSFER: from fffff80002ef4bc2 to fffff80002e76f00

STACK_TEXT:
fffff880`03316778 fffff800`02ef4bc2 : 00000000`00000050 fffffa80`07309a18 00000000`00000000 fffff880`033168e0 : nt!KeBugCheckEx
fffff880`03316780 fffff800`02e74fee : 00000000`00000000 00000000`0005c42d 00000000`00000200 fffff800`02e851ed : nt! ?? ::FNODOBFM::`string'+0x40f90
fffff880`033168e0 fffff800`02f7b78c : 00000000`00000000 fffffa80`05505c70 fffffa80`054d7630 fffffa80`054d7630 : nt!KiPageFault+0x16e
fffff880`03316a70 fffff800`02ef7a5c : fffffa80`054d7630 00000003`00000000 00000000`0005c42d fffffa80`07309a18 : nt!MiEmptyPageAccessLog+0xdc
fffff880`03316ae0 fffff800`02e8b6e2 : 00000000`00008923 00000000`00000000 fffffa80`00000000 00000000`00000002 : nt! ?? ::FNODOBFM::`string'+0x4997b
fffff880`03316b80 fffff800`02e8b96f : 00000000`00000008 fffff880`03316c10 00000000`00000001 fffffa80`00000000 : nt!MmWorkingSetManager+0x6e
fffff880`03316bd0 fffff800`0311a166 : fffffa80`039ed680 00000000`00000080 fffffa80`039cd040 00000000`00000001 : nt!KeBalanceSetManager+0x1c3
fffff880`03316d40 fffff800`02e55486 : fffff880`02f63180 fffffa80`039ed680 fffff880`02f6dfc0 00000000`00000000 : nt!PspSystemThreadStartup+0x5a
fffff880`03316d80 00000000`00000000 : fffff880`03317000 fffff880`03311000 fffff880`03316820 00000000`00000000 : nt!KxStartSystemThread+0x16

STACK_COMMAND: kb

FOLLOWUP_IP:
nt!MiEmptyPageAccessLog+dc
fffff800`02f7b78c 488b08 mov rcx,qword ptr [rax]

SYMBOL_STACK_INDEX: 3

SYMBOL_NAME: nt!MiEmptyPageAccessLog+dc

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: nt

DEBUG_FLR_IMAGE_TIMESTAMP: 4a5bc600

IMAGE_NAME: memory_corruption

FAILURE_BUCKET_ID: X64_0x50_nt!MiEmptyPageAccessLog+dc

BUCKET_ID: X64_0x50_nt!MiEmptyPageAccessLog+dc

Followup: MachineOwner
---------

2: kd> .trap 0xfffff880033168e0
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=fffffa8007309a18 rbx=0000000000000000 rcx=0000000000000160
rdx=fffff8a007c990a8 rsi=0000000000000000 rdi=0000000000000000
rip=fffff80002f7b78c rsp=fffff88003316a70 rbp=fffffa8004b32000
r8=fffffa80054d002d r9=fffffa8004013048 r10=fffffa8005505c30
r11=fffffa80055041e0 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0 nv up ei ng nz na pe nc
nt!MiEmptyPageAccessLog+0xdc:
fffff800`02f7b78c 488b08 mov rcx,qword ptr [rax] ds:fffffa80`07309a18=????????????????

| Report abuse

Fells

January 22, 2010 6:24:32 AM

A fresh re-install of the Win 7 64-bit with nothing but the windows drivers installed caused the same errors as before, even a second install of it with the latest downloaded drivers also saw random crashes.

I installed the 32-bit version and haven't had a single crash. This leads me to believe that there is a part of my HW or maybe the 4x1GB sticks which are causing issues in 64-bit.

Anyway, thought I'd add that in the event anyone else has the same issues and can't resolve them.

| Report abuse