Different BSODS at Cold Boot

alaineman · 15 May 2011

Hi,

The BSODs started 4 months after purchase. I replaced RAM with new sticks, which did not do anything. Replaced them with other brand RAM and that still did not solve the issue. Replaced motherboard 2 times and then with an other brand and that still did not work. Reinstalling windows does not solve it.

Now I have different RAM and a different motherboard and the symptoms are still BSODs at cold boot startup: Page_fault_in_nonpaged_area, Memory_management, Attempted_write_to_readonly_memory. When I replaced motherboard, I immediately got BSOD at startup even without windows 7 installed.

I have let my pc get checked and they said it was the motherboard although it did not solve the issue.

chkdsk and memtest passed without errors.

Config:
i7 860
Motherboards: MSI p55-gd65/Gigabyte p55A-UD3
RAM: OCZ Platinum DDR3 PC3-10666 Low Voltage/Corsair XMS3 TW3X4G1333C9
Samsung F3 1tb
club 3d 5850
corsair hx 750w
Mugen 2 cpu cooler

Windows 7 64bit Retail
Age of system is 1 year-1week old

alaineman · 16 May 2011

Bump, I have like 8 BSODs every cold boot and then suddenly it appears to be working just fine.

I hate karma.

fimble · 16 May 2011

Hi Alaineman and Welcome to the Forum.

Your last five dumps return (newest >> oldest):

STOP 0x0000000A: IRQL_NOT_LESS_OR_EQUAL
Usual causes: Kernel mode driver, System Service, BIOS, Windows, Virus scanner, Backup tool, compatibility

STOP 0x0000001A: MEMORY_MANAGEMENT
Usual causes: Device driver, memory, kernel

STOP 0x000000BE: ATTEMPTED_WRITE_TO_READONLY_MEMORY
Usual causes: Device driver, Memory

STOP 0x0000001A: MEMORY_MANAGEMENT
Usual causes: Device driver, memory, kernel

STOP 0x0000007E: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED (go to top of page)
Usual causes: Insufficient disk space, Device driver, Video card, BIOS, Breakpoint with no debugger attached, Hardware incompatibility, Faulty system service, Memory, 3rd party remote control,

Your latest dump file lists CI.dll as the probable cause. This is a Windows System file and for it to be the cause of your crashes is highly unlikely, but possible!
Old and incompatible drivers can and do cause issues with Windows 7, often giving false error codes.

As a Priority:

Create a System Repair Disc. Using the command prompt option, run sfc /scannow.

Bugcheck Analysis:

Code:

*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck A, {0, 2, 1, fffff80002c46337}

Probably caused by : CI.dll ( CI!I_ReloadCatalogs+14a )

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

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

IRQL_NOT_LESS_OR_EQUAL (a)
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.
Arguments:
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: fffff80002c46337, address which referenced memory

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


WRITE_ADDRESS: GetPointerFromAddress: unable to read from fffff80002eb50e0
 0000000000000000 

CURRENT_IRQL:  2

FAULTING_IP: 
nt!KeSetEventBoostPriority+3f
fffff800`02c46337 f00fba2907      lock bts dword ptr [rcx],7

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

BUGCHECK_STR:  0xA

PROCESS_NAME:  System

TRAP_FRAME:  fffff880033290e0 -- (.trap 0xfffff880033290e0)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=0000000000000002 rbx=0000000000000000 rcx=0000000000000000
rdx=fffffa80034d2f20 rsi=0000000000000000 rdi=0000000000000000
rip=fffff80002c46337 rsp=fffff88003329270 rbp=fffffa8001958040
 r8=0000000000000000  r9=0000000000000000 r10=007e004600330038
r11=fffff8a000b43010 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei ng nz na pe nc
nt!KeSetEventBoostPriority+0x3f:
fffff800`02c46337 f00fba2907      lock bts dword ptr [rcx],7 ds:000a:00000000`00000000=????????
Resetting default scope

LAST_CONTROL_TRANSFER:  from fffff80002c7cc69 to fffff80002c7d700

STACK_TEXT:  
fffff880`03328f98 fffff800`02c7cc69 : 00000000`0000000a 00000000`00000000 00000000`00000002 00000000`00000001 : nt!KeBugCheckEx
fffff880`03328fa0 fffff800`02c7b8e0 : fffff801`000a0008 fffff880`009e9180 00000000`00000000 fffff980`03271c00 : nt!KiBugCheckDispatch+0x69
fffff880`033290e0 fffff800`02c46337 : fffff880`033297e0 fffff880`012c2335 00000000`00000000 fffffa80`00010000 : nt!KiPageFault+0x260
fffff880`03329270 fffff800`02c87854 : 00000000`00000001 fffff980`02eca200 00000000`00000000 fffff800`02cc3fa1 : nt!KeSetEventBoostPriority+0x3f
fffff880`033292e0 fffff880`012c038c : fffffa80`02541bd0 00000000`00000000 00010000`00013438 fffffa80`02541b01 : nt!ExpReleaseResourceForThreadLite+0x2cf
fffff880`03329340 fffff880`012c1501 : fffff880`03329840 00000000`00000000 fffffa80`0256cde0 fffffa80`035d0010 : Ntfs!NtfsQueryDirectory+0xdfc
fffff880`033296e0 fffff880`012c386f : fffffa80`02541bd0 00000000`00000000 fffff880`033297e0 00000000`00000000 : Ntfs!NtfsCommonDirectoryControl+0xa1
fffff880`03329720 fffff880`010f923f : fffffa80`035d03b0 fffffa80`035d0010 fffffa80`02541bd0 fffff880`03329748 : Ntfs!NtfsFsdDirectoryControl+0x10f
fffff880`03329790 fffff880`010f76df : fffffa80`0256cde0 fffffa80`035caa20 fffffa80`0256cd00 fffffa80`035d0010 : fltmgr!FltpLegacyProcessingAfterPreCallbacksCompleted+0x24f
fffff880`03329820 fffff800`02f99a1d : fffffa80`035d0010 fffff880`03329a50 fffff880`03329b88 fffff880`03329978 : fltmgr!FltpDispatch+0xcf
fffff880`03329880 fffff800`02c7c953 : fffffa80`01958040 fffff880`03329a50 fffff880`03329b88 fffff880`03329978 : nt!NtQueryDirectoryFile+0x1ad
fffff880`03329960 fffff800`02c78ef0 : fffff880`00c0e3f6 00000000`00000000 fffff8a0`00f9c8e8 00000000`00300000 : nt!KiSystemServiceCopyEnd+0x13
fffff880`03329b68 fffff880`00c0e3f6 : 00000000`00000000 fffff8a0`00f9c8e8 00000000`00300000 ffffffff`8000015c : nt!KiServiceLinkage
fffff880`03329b70 fffff880`00c0d6e5 : ffffffff`80000154 00000000`c0000428 fffff880`0332a048 00000000`000002e9 : CI!I_ReloadCatalogs+0x14a
fffff880`03329d10 fffff880`00c0b9cd : fffff880`03329f60 ffffffff`00000001 00000000`00000000 fffff880`00000000 : CI!I_FindFileOrHeaderHashInCatalogs+0x409
fffff880`03329db0 fffff880`00c0c381 : fffffa80`03308e40 fffff880`03329f60 00000000`00008004 00000000`00000000 : CI!CipFindFileHash+0xf9
fffff880`03329e80 fffff880`00c0afbb : 00000000`00000001 fffff880`0332a140 00000000`00000000 00000000`00000000 : CI!CipValidateFileHash+0x311
fffff880`03329ff0 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : CI!CiValidateImageHeader+0x213


STACK_COMMAND:  kb

FOLLOWUP_IP: 
CI!I_ReloadCatalogs+14a
fffff880`00c0e3f6 4532f6          xor     r14b,r14b

SYMBOL_STACK_INDEX:  d

SYMBOL_NAME:  CI!I_ReloadCatalogs+14a

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: CI

IMAGE_NAME:  CI.dll

DEBUG_FLR_IMAGE_TIMESTAMP:  4a5be01d

FAILURE_BUCKET_ID:  X64_0xA_CI!I_ReloadCatalogs+14a

BUCKET_ID:  X64_0xA_CI!I_ReloadCatalogs+14a

Followup: MachineOwner

Your drivers appear to be in pretty good order.
Drivers:

Code:

fffff880`00f0d000 fffff880`00f64000   ACPI     ACPI.sys     Tue Jul 14 00:19:34 2009 (4A5BC106)
fffff880`040c9000 fffff880`04153000   afd      afd.sys      Tue Jul 14 00:21:40 2009 (4A5BC184)
fffff880`00e4d000 fffff880`00e58000   amdxata  amdxata.sys  Fri Mar 19 16:18:18 2010 (4BA3A3CA)
fffff880`041f3000 fffff880`041fb000   AppleCharger AppleCharger.sys Tue Apr 27 04:54:05 2010 (4BD65FDD)
fffff880`00e1a000 fffff880`00e23000   atapi    atapi.sys    Tue Jul 14 00:19:47 2009 (4A5BC113)
fffff880`00e23000 fffff880`00e4d000   ataport  ataport.SYS  Tue Jul 14 00:19:52 2009 (4A5BC118)
fffff880`044bc000 fffff880`0450c000   atikmpag atikmpag.sys Wed Apr 20 02:22:32 2011 (4DAE3558)
fffff880`019d5000 fffff880`019dc000   Beep     Beep.SYS     Tue Jul 14 01:00:13 2009 (4A5BCA8D)
fffff880`01897000 fffff880`018a8000   blbdrive blbdrive.sys Tue Jul 14 00:35:59 2009 (4A5BC4DF)
fffff880`019a2000 fffff880`019cc000   cdrom    cdrom.sys    Tue Jul 14 00:19:54 2009 (4A5BC11A)
fffff880`00c00000 fffff880`00cc0000   CI       CI.dll       Tue Jul 14 02:32:13 2009 (4A5BE01D)
fffff880`0193c000 fffff880`0196c000   CLASSPNP CLASSPNP.SYS Tue Jul 14 00:19:58 2009 (4A5BC11E)
fffff880`00d29000 fffff880`00d87000   CLFS     CLFS.SYS     Tue Jul 14 00:19:57 2009 (4A5BC11D)
fffff880`01000000 fffff880`01073000   cng      cng.sys      Tue Jul 14 00:49:40 2009 (4A5BC814)
fffff880`0196c000 fffff880`0197a000   crashdmp crashdmp.sys Tue Jul 14 01:01:01 2009 (4A5BCABD)
fffff880`040a6000 fffff880`040c4000   dfsc     dfsc.sys     Tue Jul 14 00:23:44 2009 (4A5BC200)
fffff880`04097000 fffff880`040a6000   discache discache.sys Tue Jul 14 00:37:18 2009 (4A5BC52E)
fffff880`01926000 fffff880`0193c000   disk     disk.sys     Tue Jul 14 00:19:57 2009 (4A5BC11D)
fffff880`01986000 fffff880`0198f000   dump_atapi dump_atapi.sys Tue Jul 14 00:19:47 2009 (4A5BC113)
fffff880`0197a000 fffff880`01986000   dump_dumpata dump_dumpata.sys Tue Jul 14 00:19:47 2009 (4A5BC113)
fffff880`0198f000 fffff880`019a2000   dump_dumpfve dump_dumpfve.sys Tue Jul 14 00:21:51 2009 (4A5BC18F)
fffff880`01142000 fffff880`01156000   fileinfo fileinfo.sys Tue Jul 14 00:34:25 2009 (4A5BC481)
fffff880`010f6000 fffff880`01142000   fltmgr   fltmgr.sys   Tue Jul 14 00:19:59 2009 (4A5BC11F)
fffff880`013f2000 fffff880`013fc000   Fs_Rec   Fs_Rec.sys   Tue Jul 14 00:19:45 2009 (4A5BC111)
fffff880`018ec000 fffff880`01926000   fvevol   fvevol.sys   Sat Sep 26 03:34:26 2009 (4ABD7DB2)
fffff880`01400000 fffff880`0144a000   fwpkclnt fwpkclnt.sys Tue Jul 14 00:21:08 2009 (4A5BC164)
fffff800`031e9000 fffff800`03232000   hal      hal.dll      Tue Jul 14 02:27:36 2009 (4A5BDF08)
fffff880`015f0000 fffff880`015f9000   hwpolicy hwpolicy.sys Tue Jul 14 00:19:22 2009 (4A5BC0FA)
fffff880`018ce000 fffff880`018e4000   intelppm intelppm.sys Tue Jul 14 00:19:25 2009 (4A5BC0FD)
fffff800`00baf000 fffff800`00bb9000   kdcom    kdcom.dll    Sat Feb 05 12:21:45 2011 (4D4D40D9)
fffff880`013c7000 fffff880`013e1000   ksecdd   ksecdd.sys   Tue Jul 14 00:20:54 2009 (4A5BC156)
fffff880`015b3000 fffff880`015de000   ksecpkg  ksecpkg.sys  Fri Dec 11 06:03:32 2009 (4B21E0B4)
fffff880`00cd1000 fffff880`00d15000   mcupdate_GenuineIntel mcupdate_GenuineIntel.dll Tue Jul 14 02:29:10 2009 (4A5BDF66)
fffff880`00e00000 fffff880`00e1a000   mountmgr mountmgr.sys Tue Jul 14 00:19:54 2009 (4A5BC11A)
fffff880`01850000 fffff880`0185b000   Msfs     Msfs.SYS     Tue Jul 14 00:19:47 2009 (4A5BC113)
fffff880`00f6d000 fffff880`00f77000   msisadrv msisadrv.sys Tue Jul 14 00:19:26 2009 (4A5BC0FE)
fffff880`01156000 fffff880`011b4000   msrpc    msrpc.sys    Tue Jul 14 00:21:32 2009 (4A5BC17C)
fffff880`0408c000 fffff880`04097000   mssmbios mssmbios.sys Tue Jul 14 00:31:10 2009 (4A5BC3BE)
fffff880`015de000 fffff880`015f0000   mup      mup.sys      Tue Jul 14 00:23:45 2009 (4A5BC201)
fffff880`01461000 fffff880`01553000   ndis     ndis.sys     Tue Jul 14 00:21:40 2009 (4A5BC184)
fffff880`041c7000 fffff880`041d6000   netbios  netbios.sys  Tue Jul 14 01:09:26 2009 (4A5BCCB6)
fffff880`04153000 fffff880`04198000   netbt    netbt.sys    Tue Jul 14 00:21:28 2009 (4A5BC178)
fffff880`01553000 fffff880`015b3000   NETIO    NETIO.SYS    Tue Jul 14 00:21:46 2009 (4A5BC18A)
fffff880`0185b000 fffff880`0186c000   Npfs     Npfs.SYS     Tue Jul 14 00:19:48 2009 (4A5BC114)
fffff880`04080000 fffff880`0408c000   nsiproxy nsiproxy.sys Tue Jul 14 00:21:02 2009 (4A5BC15E)
fffff800`02c0d000 fffff800`031e9000   nt       ntkrnlmp.exe Sat Apr 09 05:14:44 2011 (4D9FDD34)
fffff880`01225000 fffff880`013c7000   Ntfs     Ntfs.sys     Fri Mar 11 03:39:25 2011 (4D79996D)
fffff880`019cc000 fffff880`019d5000   Null     Null.SYS     Tue Jul 14 00:19:37 2009 (4A5BC109)
fffff880`041a1000 fffff880`041c7000   pacer    pacer.sys    Tue Jul 14 01:09:41 2009 (4A5BCCC5)
fffff880`00fb7000 fffff880`00fcc000   partmgr  partmgr.sys  Tue Jul 14 00:19:58 2009 (4A5BC11E)
fffff880`00f77000 fffff880`00faa000   pci      pci.sys      Tue Jul 14 00:19:51 2009 (4A5BC117)
fffff880`00fe1000 fffff880`00fe8000   pciide   pciide.sys   Tue Jul 14 00:19:49 2009 (4A5BC115)
fffff880`00fe8000 fffff880`00ff8000   PCIIDEX  PCIIDEX.SYS  Tue Jul 14 00:19:48 2009 (4A5BC114)
fffff880`013e1000 fffff880`013f2000   pcw      pcw.sys      Tue Jul 14 00:19:27 2009 (4A5BC0FF)
fffff880`00d15000 fffff880`00d29000   PSHED    PSHED.dll    Tue Jul 14 02:32:23 2009 (4A5BE027)
fffff880`0402f000 fffff880`04080000   rdbss    rdbss.sys    Tue Jul 14 00:24:09 2009 (4A5BC219)
fffff880`01835000 fffff880`0183e000   RDPCDD   RDPCDD.sys   Tue Jul 14 01:16:34 2009 (4A5BCE62)
fffff880`0183e000 fffff880`01847000   rdpencdd rdpencdd.sys Tue Jul 14 01:16:34 2009 (4A5BCE62)
fffff880`01847000 fffff880`01850000   rdprefmp rdprefmp.sys Tue Jul 14 01:16:35 2009 (4A5BCE63)
fffff880`011b4000 fffff880`011ee000   rdyboost rdyboost.sys Tue Jul 14 00:34:34 2009 (4A5BC48A)
fffff880`041d6000 fffff880`041f3000   serial   serial.sys   Tue Jul 14 01:00:40 2009 (4A5BCAA8)
fffff880`01452000 fffff880`0145c000   speedfan speedfan.sys Sat Dec 18 11:03:51 2010 (4D0C9517)
fffff880`0144a000 fffff880`01452000   spldr    spldr.sys    Mon May 11 17:56:27 2009 (4A0858BB)
fffff880`01600000 fffff880`017fd000   tcpip    tcpip.sys    Mon Jun 14 04:39:04 2010 (4C15A458)
fffff880`0188a000 fffff880`01897000   TDI      TDI.SYS      Tue Jul 14 00:21:18 2009 (4A5BC16E)
fffff880`0186c000 fffff880`0188a000   tdx      tdx.sys      Tue Jul 14 00:21:15 2009 (4A5BC16B)
fffff880`0401b000 fffff880`0402f000   termdd   termdd.sys   Tue Jul 14 01:16:36 2009 (4A5BCE64)
fffff880`018a8000 fffff880`018ce000   tunnel   tunnel.sys   Tue Jul 14 01:09:37 2009 (4A5BCCC1)
fffff880`00faa000 fffff880`00fb7000   vdrvroot vdrvroot.sys Tue Jul 14 01:01:31 2009 (4A5BCADB)
fffff880`019dc000 fffff880`019ea000   vga      vga.sys      Tue Jul 14 00:38:47 2009 (4A5BC587)
fffff880`01800000 fffff880`01825000   VIDEOPRT VIDEOPRT.SYS Tue Jul 14 00:38:51 2009 (4A5BC58B)
fffff880`00fcc000 fffff880`00fe1000   volmgr   volmgr.sys   Tue Jul 14 00:19:57 2009 (4A5BC11D)
fffff880`00d87000 fffff880`00de3000   volmgrx  volmgrx.sys  Tue Jul 14 00:20:33 2009 (4A5BC141)
fffff880`01073000 fffff880`010bf000   volsnap  volsnap.sys  Tue Jul 14 00:20:08 2009 (4A5BC128)
fffff880`04000000 fffff880`0401b000   wanarp   wanarp.sys   Tue Jul 14 01:10:21 2009 (4A5BCCED)
fffff880`01825000 fffff880`01835000   watchdog watchdog.sys Tue Jul 14 00:37:35 2009 (4A5BC53F)
fffff880`00e5a000 fffff880`00efe000   Wdf01000 Wdf01000.sys Tue Jul 14 00:22:07 2009 (4A5BC19F)
fffff880`00efe000 fffff880`00f0d000   WDFLDR   WDFLDR.SYS   Tue Jul 14 00:19:54 2009 (4A5BC11A)
fffff880`04198000 fffff880`041a1000   wfplwf   wfplwf.sys   Tue Jul 14 01:09:26 2009 (4A5BCCB6)
fffff880`00f64000 fffff880`00f6d000   WMILIB   WMILIB.SYS   Tue Jul 14 00:19:51 2009 (4A5BC117)

That's all I can think of at this moment in time! Let us know how it goes.

HTH.

alaineman · 16 May 2011

Thanks for your time fimble!

I have a windows 7 disc, should I still make that repair disc?
Also the first BSODs I get are the PAGE_FAULT_IN_NONPAGED_AREA Stop: 0×00000050, but these occur before windows can startup and my pc doesn't create a memory dump.

fimble · 16 May 2011

alaineman said:

Thanks for your time fimble!

I have a windows 7 disc, should I still make that repair disc?

I would. It's different from the "Install disk". Although if you can get into 7 at the mo it isn't an essential, but could soon be. Always handy to have, errr, handy!

alaineman said:

Also the first BSODs I get are the PAGE_FAULT_IN_NONPAGED_AREA Stop: 0×00000050, but these occur before windows can startup and my pc doesn't create a memory dump.

STOP 0x00000050: PAGE_FAULT_IN_NONPAGED_AREA
Usual causes: Defective hardware (particularly memory - but not just RAM), Faulty system service, Antivirus, Device driver, NTFS corruption, BIOS.

Might be wise to run a couple of hardware tests to check, initially, your memory.
Memtest86+ 4.20 download.
Guide to using Memtest86+
Also see: RAM - How to Test with Memtest86+
CPU - Stress Test with Prime95. Run the "Blend" and "Small FFTs" tests.

BTW. What AV are you running?

fimble · 16 May 2011

alaineman said:

Bump, I have like 8 BSODs every cold boot and then suddenly it appears to be working just fine.

Could well be a memory issue. Think of it like a car. Every time it fails to start, it gets slightly warmer. Then it'll hit a comfortable temperature and off it goes (a pretty crap analogy, but you get the picture!).

alaineman · 16 May 2011

fimble said:

STOP 0x00000050: PAGE_FAULT_IN_NONPAGED_AREA
Usual causes: Defective hardware (particularly memory - but not just RAM), Faulty system service, Antivirus, Device driver, NTFS corruption, BIOS.

Might be wise to run a couple of hardware tests to check, initially, your memory.
Memtest86+ 4.20 download.
Guide to using Memtest86+
Also see: RAM - How to Test with Memtest86+
CPU - Stress Test with Prime95. Run the "Blend" and "Small FFTs" tests.

BTW. What AV are you running?

I have ran memtest and it did not result any errors, and I was using avast, but now I've switched to MSE

fimble · 16 May 2011

OK. If you can get into Safe Mode without a problem, run sfc /scannow from there. If you are having issues getting in to your system, use the repair disc option.

The CI.dll (I believe) is critical to the boot, so need to make sure it is "in good order".

alaineman · 16 May 2011

I've gotten into safe mode and ran the sfc, at 50% +- it stopped verificating (The requested operation could no be performed). Then I got a blue screen with PAGE_.. when trying to scan again. I rebooted, tried again and then it completed but it could not repair all damaged sectors. It saved the log which I added as an attachment.

fimble · 16 May 2011

alaineman said:

...Then I got a blue screen with PAGE_.. when trying to scan again.

That could well have again been:
STOP 0x00000050: PAGE_FAULT_IN_NONPAGED_AREA
Usual causes: Defective hardware (particularly memory - but not just RAM), Faulty system service, Antivirus, Device driver, NTFS corruption, BIOS.

I'd suggest running the sfc /scannow from the repair disc as your system wouldn't be running while doing it.