BSOD on startup! IRQL_NOT_LESS_OR_EQUAL please help!

#1
Hi, this problem jsut started this morning. No new hardware or software installed.

Every startup after the windows screen I get a BSOD of the IRQLNOTLESSOREQUAL

I've seen another bsod that said page_fault_in_nonpaged_area

I've tried startup repair, it didn't work.

It won't let me start up normally ever. I can sometimes get into safemode without it giving me a bsod. I've been in safe mode for about 45 mins now without a bsod. I'm using another computer to write this, because I can't start safemode with networking.

I looked in my event viewer and see a msg saying: The computer has rebooted from a bugcheck. The bugcheck was: 0x0000000a (0x00000000000008, 0x0...2, 0x0...0, 0xfffff80003069571) a dump was saved in c:\windows\memory.dmp

Using BlueScreenViewer, it is saying I have 13 crashes (all from today). One says KMODE_EXCEPTION_NOT_HANDLED caused by driver hal.dll. The red files to go with it are hal.dll and ntoskrnl.exe

The other 12 crashes are all IRQL_NOT_LESS_OR_EQUAL caused by driver ntoskrnl.exe.

I ran a sfc/scannow and it said "Windows REsource Protection found corrupt files but was unable to fix some of them."

I have the CBS.log, and the bluescreenview log here: View attachment logs.zip

Here is the event viewer log: View attachment events.zip

Please help if you can!
 


Last edited:
#3
Ok, I got all the info from SFdiag, but when running cpuID, I get the error msg "The error code 0x43C (1084) occured during initialization. IT then opens, but displays no info in Memory or SPD. I'll put a copy of the error log in with the sfdiag.

I tried taking one stick of ram out, got the blue screen, so I tried the other, and still got th eblue screen. I have run memtest, and it says there are no errors


EDIT: It seems both windows and bios are reporting the wrong size ram. I have 8gb. 2x2gb and a 4gb stick. If I put both 2gb in the dual mem channels, and take out the 4, it says I have 2gb of ram. If I take out a 2gb and put in the 4gb, instead of showing 6, it shows 3. So it seems like it's always half what it should be.


Thanks for the reply

View attachment Seven Forums.zip
 


Last edited:
#4
Memory Management 1a
IRQL_NOT_LESS_OR_EQUAL (a)

Update ASUS ATK0110 ACPI Utility:
ASACPI.sys Sun Mar 27 22:30:36 2005


I have 8gb. 2x2gb and a 4gb stick. If I put both 2gb in the dual mem channels, and take out the 4, it says I have 2gb of ram. If I take out a 2gb and put in the 4gb, instead of showing 6, it shows 3. So it seems like it's always half what it should be.
RAM is likely the problem, are you sure the sticks are compatible and matching?






Crash Dumps:

Code:
Microsoft (R) Windows Debugger Version 6.12.0002.633 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [F:\a\Minidump\D M P\DMP\020411-37955-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Mini Kernel Dump does not have process information
Symbol search path is: SRV*c:\websymbols*http://msdl.microsoft.com/download/symbols
Executable search path is: 
Unable to load image Unknown_Module_00000000`00000000, Win32 error 0n2
*** WARNING: Unable to verify timestamp for Unknown_Module_00000000`00000000
Unable to add module at 00000000`00000000
WARNING: .reload failed, module list may be incomplete
Debugger can not determine kernel base address
Windows 7 Kernel Version 7600 MP (2 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7600.16397.amd64fre.win7_gdr_staging.090720-1852
Machine Name:
Kernel base = 0xfffff800`0301b000 PsLoadedModuleList = 0xfffff800`03258e50
Debug session time: Fri Feb  4 12:50:36.546 2011 (UTC - 5:00)
System Uptime: 0 days 0:01:02.042
Unable to load image Unknown_Module_00000000`00000000, Win32 error 0n2
*** WARNING: Unable to verify timestamp for Unknown_Module_00000000`00000000
Unable to add module at 00000000`00000000
WARNING: .reload failed, module list may be incomplete
Debugger can not determine kernel base address
Loading Kernel Symbols
.Unable to load image Unknown_Module_00000000`00000000, Win32 error 0n2
*** WARNING: Unable to verify timestamp for Unknown_Module_00000000`00000000
Unable to add module at 00000000`00000000

Loading User Symbols
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck A, {8, 2, 0, fffff80003069571}

***** Debugger could not find nt in module list, module list might be corrupt, error 0x80070057.

Probably caused by : Unknown_Image ( ANALYSIS_INCONCLUSIVE )

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

0: 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: 0000000000000008, memory referenced
Arg2: 0000000000000002, IRQL
Arg3: 0000000000000000, 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: fffff80003069571, address which referenced memory

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

***** Debugger could not find nt in module list, module list might be corrupt, error 0x80070057.


READ_ADDRESS: unable to get nt!MmSpecialPoolStart
unable to get nt!MmSpecialPoolEnd
unable to get nt!MmPoolCodeStart
unable to get nt!MmPoolCodeEnd
 0000000000000008 

CURRENT_IRQL:  0

FAULTING_IP: 
+3239613234303530
fffff800`03069571 488b5108        mov     rdx,qword ptr [rcx+8]

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

BUGCHECK_STR:  0xA

LAST_CONTROL_TRANSFER:  from fffff8000308c4a9 to fffff8000308cf40

STACK_TEXT:  
fffff800`0591f738 fffff800`0308c4a9 : 00000000`0000000a 00000000`00000008 00000000`00000002 00000000`00000000 : 0xfffff800`0308cf40
fffff800`0591f740 00000000`0000000a : 00000000`00000008 00000000`00000002 00000000`00000000 fffff800`03069571 : 0xfffff800`0308c4a9
fffff800`0591f748 00000000`00000008 : 00000000`00000002 00000000`00000000 fffff800`03069571 fffffa80`024566a8 : 0xa
fffff800`0591f750 00000000`00000002 : 00000000`00000000 fffff800`03069571 fffffa80`024566a8 00000000`00000000 : 0x8
fffff800`0591f758 00000000`00000000 : fffff800`03069571 fffffa80`024566a8 00000000`00000000 00000000`00000000 : 0x2


STACK_COMMAND:  kb

SYMBOL_NAME:  ANALYSIS_INCONCLUSIVE

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: Unknown_Module

IMAGE_NAME:  Unknown_Image

DEBUG_FLR_IMAGE_TIMESTAMP:  0

BUCKET_ID:  CORRUPT_MODULELIST




Microsoft (R) Windows Debugger Version 6.12.0002.633 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [F:\a\Minidump\D M P\DMP\020411-37471-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*c:\websymbols*http://msdl.microsoft.com/download/symbols
Executable search path is: 
Windows 7 Kernel Version 7600 MP (2 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7600.16397.amd64fre.win7_gdr_staging.090720-1852
Machine Name:
Kernel base = 0xfffff800`02455000 PsLoadedModuleList = 0xfffff800`02692e50
Debug session time: Fri Feb  4 12:16:56.708 2011 (UTC - 5:00)
System Uptime: 0 days 0:01:05.379
Loading Kernel Symbols
.

Press ctrl-c (cdb, kd, ntsd) or ctrl-break (windbg) to abort symbol loads that take too long.
Run !sym noisy before .reload to track down problems loading symbols.

..............................................................
...............................
Loading User Symbols
Loading unloaded module list
......
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck A, {8, 2, 0, fffff800024a3571}

Probably caused by : ataport.SYS ( ataport!IdeCompleteScsiIrp+62 )

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

0: 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: 0000000000000008, memory referenced
Arg2: 0000000000000002, IRQL
Arg3: 0000000000000000, 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: fffff800024a3571, address which referenced memory

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


READ_ADDRESS: GetPointerFromAddress: unable to read from fffff800026fd0e0
 0000000000000008 

CURRENT_IRQL:  2

FAULTING_IP: 
nt!KiInsertQueueApc+1e9
fffff800`024a3571 488b5108        mov     rdx,qword ptr [rcx+8]

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

BUGCHECK_STR:  0xA

PROCESS_NAME:  svchost.exe

TRAP_FRAME:  fffff80000ba0880 -- (.trap 0xfffff80000ba0880)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=0000000000000000 rbx=0000000000000000 rcx=0000000000000000
rdx=fffffa80038e9e08 rsi=0000000000000000 rdi=0000000000000000
rip=fffff800024a3571 rsp=fffff80000ba0a10 rbp=fffff8000263fe80
 r8=0000000000000000  r9=0000000000000000 r10=0000000000000000
r11=0000000000000002 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei pl zr na po nc
nt!KiInsertQueueApc+0x1e9:
fffff800`024a3571 488b5108        mov     rdx,qword ptr [rcx+8] ds:00000000`00000008=????????????????
Resetting default scope

LAST_CONTROL_TRANSFER:  from fffff800024c64a9 to fffff800024c6f40

STACK_TEXT:  
fffff800`00ba0738 fffff800`024c64a9 : 00000000`0000000a 00000000`00000008 00000000`00000002 00000000`00000000 : nt!KeBugCheckEx
fffff800`00ba0740 fffff800`024c5120 : 00000000`00000001 fffffa80`03c23650 fffffa80`024296a8 fffff880`00c87656 : nt!KiBugCheckDispatch+0x69
fffff800`00ba0880 fffff800`024a3571 : fffff800`0263fe80 fffffa80`038e9e01 00000000`00000000 00000000`00000002 : nt!KiPageFault+0x260
fffff800`00ba0a10 fffff800`024a6830 : fffffa80`03c23650 00000000`00000002 00000000`00000000 fffffa80`038e9e08 : nt!KiInsertQueueApc+0x1e9
fffff800`00ba0a40 fffff800`024c9d4b : 00000000`00000000 00000000`a000000c 00000000`00000000 00000000`00000000 : nt!KeInsertQueueApc+0x80
fffff800`00ba0aa0 fffff880`00dbc41a : 00000000`00007a00 00000000`00000001 fffffa80`038f4010 00000000`00000000 : nt!IopfCompleteRequest+0xbdb
fffff800`00ba0b80 fffff880`00dbc242 : fffffa80`038f4010 fffff880`00dbeb3b fffffa80`03bcfa50 fffffa80`0311a7d0 : ataport!IdeCompleteScsiIrp+0x62
fffff800`00ba0bb0 fffff880`00db6e32 : 00000000`00000000 00000000`00000000 fffffa80`02429500 fffffa80`0311a7d0 : ataport!IdeCommonCrbCompletion+0x5a
fffff800`00ba0be0 fffff880`00dbf7ed : fffffa80`024281a0 fffffa80`038f4010 00000000`00000000 fffffa80`038f4010 : ataport!IdeTranslateCompletedRequest+0x236
fffff800`00ba0d10 fffff880`00dbf0ec : fffffa80`024281a0 00000000`00000000 fffffa80`024281a0 00000000`00000000 : ataport!IdeProcessCompletedRequests+0x4d5
fffff800`00ba0e40 fffff800`024d25dc : fffff800`0263fe80 fffffa80`00001011 fffffa80`02428050 fffffa80`02428118 : ataport!IdePortCompletionDpc+0x1a8
fffff800`00ba0f00 fffff800`024cd065 : 00000000`00000000 fffffa80`03b8f2e0 00000000`00000000 fffff880`00dbef44 : nt!KiRetireDpcList+0x1bc
fffff800`00ba0fb0 fffff800`024cce7c : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxRetireDpcList+0x5
fffff880`02f31800 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiDispatchInterruptContinue


STACK_COMMAND:  kb

FOLLOWUP_IP: 
ataport!IdeCompleteScsiIrp+62
fffff880`00dbc41a 8bc3            mov     eax,ebx

SYMBOL_STACK_INDEX:  6

SYMBOL_NAME:  ataport!IdeCompleteScsiIrp+62

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: ataport

IMAGE_NAME:  ataport.SYS

DEBUG_FLR_IMAGE_TIMESTAMP:  4a5bc118

FAILURE_BUCKET_ID:  X64_0xA_ataport!IdeCompleteScsiIrp+62

BUCKET_ID:  X64_0xA_ataport!IdeCompleteScsiIrp+62

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



Drivers:

Code:
start             end                 module name
fffff880`0238a000 fffff880`023c8000   1394ohci 1394ohci.sys Mon Jul 13 20:07:12 2009 (4A5BCC30)
fffff880`00e00000 fffff880`00e57000   ACPI     ACPI.sys     Mon Jul 13 19:19:34 2009 (4A5BC106)
fffff880`010a0000 fffff880`010ab000   amdxata  amdxata.sys  Tue May 19 13:56:59 2009 (4A12F2EB)
fffff880`023c8000 fffff880`023d0000   ASACPI   ASACPI.sys   Sun Mar 27 22:30:36 2005 (42476C4C)
fffff880`00c86000 fffff880`00c8f000   atapi    atapi.sys    Mon Jul 13 19:19:47 2009 (4A5BC113)
fffff880`00db3000 fffff880`00ddd000   ataport  ataport.SYS  Mon Jul 13 19:19:52 2009 (4A5BC118)
fffff960`00b50000 fffff960`00bb1000   ATMFD    ATMFD.DLL    Mon Jul 13 19:38:13 2009 (4A5BC565)
fffff880`0186f000 fffff880`01876000   Beep     Beep.SYS     Mon Jul 13 20:00:13 2009 (4A5BCA8D)
fffff880`023d0000 fffff880`023e1000   blbdrive blbdrive.sys Mon Jul 13 19:35:59 2009 (4A5BC4DF)
fffff880`02353000 fffff880`0237d000   cdrom    cdrom.sys    Tue Jul 21 02:54:09 2009 (4A656611)
fffff880`00e86000 fffff880`00f46000   CI       CI.dll       Mon Jul 13 21:32:13 2009 (4A5BE01D)
fffff880`01800000 fffff880`01830000   CLASSPNP CLASSPNP.SYS Mon Jul 13 19:19:58 2009 (4A5BC11E)
fffff880`00cf8000 fffff880`00d56000   CLFS     CLFS.SYS     Mon Jul 13 19:19:57 2009 (4A5BC11D)
fffff880`01406000 fffff880`01479000   cng      cng.sys      Mon Jul 13 19:49:40 2009 (4A5BC814)
fffff880`023e1000 fffff880`023f1000   CompositeBus CompositeBus.sys Mon Jul 13 20:00:33 2009 (4A5BCAA1)
fffff880`028b8000 fffff880`028c6000   crashdmp crashdmp.sys Mon Jul 13 20:01:01 2009 (4A5BCABD)
fffff880`019ca000 fffff880`019e0000   disk     disk.sys     Mon Jul 13 19:19:57 2009 (4A5BC11D)
fffff880`028d2000 fffff880`028db000   dump_atapi dump_atapi.sys Mon Jul 13 19:19:47 2009 (4A5BC113)
fffff880`028c6000 fffff880`028d2000   dump_dumpata dump_dumpata.sys Mon Jul 13 19:19:47 2009 (4A5BC113)
fffff880`028db000 fffff880`028ee000   dump_dumpfve dump_dumpfve.sys Mon Jul 13 19:21:51 2009 (4A5BC18F)
fffff880`0289b000 fffff880`028a7000   Dxapi    Dxapi.sys    Mon Jul 13 19:38:28 2009 (4A5BC574)
fffff960`004a0000 fffff960`004be000   dxg      dxg.sys      Mon Jul 13 19:38:28 2009 (4A5BC574)
fffff880`0290f000 fffff880`02945000   fastfat  fastfat.SYS  Mon Jul 13 19:23:28 2009 (4A5BC1F0)
fffff880`013e4000 fffff880`013f1000   fdc      fdc.sys      Mon Jul 13 20:00:54 2009 (4A5BCAB6)
fffff880`010f7000 fffff880`0110b000   fileinfo fileinfo.sys Mon Jul 13 19:34:25 2009 (4A5BC481)
fffff880`02285000 fffff880`02290000   flpydisk flpydisk.sys Mon Jul 13 20:00:54 2009 (4A5BCAB6)
fffff880`010ab000 fffff880`010f7000   fltmgr   fltmgr.sys   Mon Jul 13 19:19:59 2009 (4A5BC11F)
fffff960`009b0000 fffff960`009b9000   framebuf framebuf.dll unavailable (00000000)
fffff880`0148a000 fffff880`01494000   Fs_Rec   Fs_Rec.sys   Mon Jul 13 19:19:45 2009 (4A5BC111)
fffff880`01990000 fffff880`019ca000   fvevol   fvevol.sys   Mon Jul 13 19:22:15 2009 (4A5BC1A7)
fffff880`0188d000 fffff880`018d7000   fwpkclnt fwpkclnt.sys Mon Jul 13 19:21:08 2009 (4A5BC164)
fffff880`0237d000 fffff880`0238a000   GEARAspiWDM GEARAspiWDM.sys Mon May 18 08:17:04 2009 (4A1151C0)
fffff800`0240c000 fffff800`02455000   hal      hal.dll      Tue Jul 21 06:29:39 2009 (4A659893)
fffff880`0110b000 fffff880`0112f000   HDAudBus HDAudBus.sys Mon Jul 13 20:06:13 2009 (4A5BCBF5)
fffff880`0183e000 fffff880`01857000   HIDCLASS HIDCLASS.SYS Mon Jul 13 20:06:21 2009 (4A5BCBFD)
fffff880`01857000 fffff880`0185f080   HIDPARSE HIDPARSE.SYS Mon Jul 13 20:06:17 2009 (4A5BCBF9)
fffff880`01830000 fffff880`0183e000   hidusb   hidusb.sys   Mon Jul 13 20:06:22 2009 (4A5BCBFE)
fffff880`01987000 fffff880`01990000   hwpolicy hwpolicy.sys Mon Jul 13 19:19:22 2009 (4A5BC0FA)
fffff880`0112f000 fffff880`0114d000   i8042prt i8042prt.sys Mon Jul 13 19:19:57 2009 (4A5BC11D)
fffff880`013f1000 fffff880`01400000   kbdclass kbdclass.sys Mon Jul 13 19:19:50 2009 (4A5BC116)
fffff800`00bb7000 fffff800`00bba000   kdcom    kdcom.dll    Fri Jan 21 08:17:13 2011 (4D398759)
fffff880`02230000 fffff880`02273000   ks       ks.sys       Mon Jul 13 20:00:31 2009 (4A5BCA9F)
fffff880`013ca000 fffff880`013e4000   ksecdd   ksecdd.sys   Mon Jul 13 19:20:54 2009 (4A5BC156)
fffff880`011c4000 fffff880`011ef000   ksecpkg  ksecpkg.sys  Mon Jul 13 19:50:34 2009 (4A5BC84A)
fffff880`00ca0000 fffff880`00ce4000   mcupdate_GenuineIntel mcupdate_GenuineIntel.dll Mon Jul 13 21:29:10 2009 (4A5BDF66)
fffff880`0221f000 fffff880`0222e000   mouclass mouclass.sys Mon Jul 13 19:19:50 2009 (4A5BC116)
fffff880`02871000 fffff880`0287e000   mouhid   mouhid.sys   Mon Jul 13 20:00:20 2009 (4A5BCA94)
fffff880`00c6c000 fffff880`00c86000   mountmgr mountmgr.sys Mon Jul 13 19:19:54 2009 (4A5BC11A)
fffff880`019f0000 fffff880`019fb000   Msfs     Msfs.SYS     Mon Jul 13 19:19:47 2009 (4A5BC113)
fffff880`00e60000 fffff880`00e6a000   msisadrv msisadrv.sys Mon Jul 13 19:19:26 2009 (4A5BC0FE)
fffff880`01166000 fffff880`011c4000   msrpc    msrpc.sys    Mon Jul 13 19:21:32 2009 (4A5BC17C)
fffff880`023f1000 fffff880`023fc000   mssmbios mssmbios.sys Mon Jul 13 19:31:10 2009 (4A5BC3BE)
fffff880`01975000 fffff880`01987000   mup      mup.sys      Mon Jul 13 19:23:45 2009 (4A5BC201)
fffff880`01494000 fffff880`01586000   ndis     ndis.sys     Mon Jul 13 19:21:40 2009 (4A5BC184)
fffff880`01586000 fffff880`015e6000   NETIO    NETIO.SYS    Mon Jul 13 19:21:46 2009 (4A5BC18A)
fffff880`015e6000 fffff880`015f7000   Npfs     Npfs.SYS     Mon Jul 13 19:19:48 2009 (4A5BC114)
fffff800`02455000 fffff800`02a32000   nt       ntkrnlmp.exe Tue Jul 21 03:01:07 2009 (4A6567B3)
fffff880`01227000 fffff880`013ca000   Ntfs     Ntfs.sys     Mon Jul 13 19:20:47 2009 (4A5BC14F)
fffff880`01866000 fffff880`0186f000   Null     Null.SYS     Mon Jul 13 19:19:37 2009 (4A5BC109)
fffff880`01013000 fffff880`0103e000   nvstor   nvstor.sys   Wed May 20 02:45:37 2009 (4A13A711)
fffff880`00d89000 fffff880`00d9e000   partmgr  partmgr.sys  Mon Jul 13 19:19:58 2009 (4A5BC11E)
fffff880`00d56000 fffff880`00d89000   pci      pci.sys      Mon Jul 13 19:19:51 2009 (4A5BC117)
fffff880`00e77000 fffff880`00e7e000   pciide   pciide.sys   Mon Jul 13 19:19:49 2009 (4A5BC115)
fffff880`00c5c000 fffff880`00c6c000   PCIIDEX  PCIIDEX.SYS  Mon Jul 13 19:19:48 2009 (4A5BC114)
fffff880`01479000 fffff880`0148a000   pcw      pcw.sys      Mon Jul 13 19:19:27 2009 (4A5BC0FF)
fffff880`00ce4000 fffff880`00cf8000   PSHED    PSHED.dll    Mon Jul 13 21:32:23 2009 (4A5BE027)
fffff880`02200000 fffff880`0220b000   rdpbus   rdpbus.sys   Mon Jul 13 20:17:46 2009 (4A5BCEAA)
fffff880`0193b000 fffff880`01975000   rdyboost rdyboost.sys Mon Jul 13 19:34:34 2009 (4A5BC48A)
fffff880`0103e000 fffff880`010a0000   storport storport.sys Mon Jul 13 20:01:18 2009 (4A5BCACE)
fffff880`0222e000 fffff880`0222f480   swenum   swenum.sys   Mon Jul 13 20:00:18 2009 (4A5BCA92)
fffff880`01603000 fffff880`01800000   tcpip    tcpip.sys    Mon Jul 13 19:25:34 2009 (4A5BC26E)
fffff880`0220b000 fffff880`0221f000   termdd   termdd.sys   Mon Jul 13 20:16:36 2009 (4A5BCE64)
fffff960`00660000 fffff960`0066a000   TSDDD    TSDDD.dll    Mon Jul 13 20:16:34 2009 (4A5BCE62)
fffff880`0281d000 fffff880`02871000   udfs     udfs.sys     Mon Jul 13 19:23:37 2009 (4A5BC1F9)
fffff880`02273000 fffff880`02285000   umbus    umbus.sys    Tue Jul 21 03:48:37 2009 (4A6572D5)
fffff880`028a7000 fffff880`028b8000   usbaapl64 usbaapl64.sys Thu Sep 16 22:19:05 2010 (4C92D019)
fffff880`0287e000 fffff880`0289b000   usbccgp  usbccgp.sys  Sat Jun 13 04:31:03 2009 (4A3363C7)
fffff880`022ea000 fffff880`022ebf00   USBD     USBD.SYS     Sat Jun 13 04:30:46 2009 (4A3363B6)
fffff880`02342000 fffff880`02353000   usbehci  usbehci.sys  Sat Jun 13 04:30:51 2009 (4A3363BB)
fffff880`02290000 fffff880`022ea000   usbhub   usbhub.sys   Tue Jul 21 03:49:00 2009 (4A6572EC)
fffff880`0114d000 fffff880`01158000   usbohci  usbohci.sys  Sat Jun 13 04:30:51 2009 (4A3363BB)
fffff880`022ec000 fffff880`02342000   USBPORT  USBPORT.SYS  Sat Jun 13 04:30:55 2009 (4A3363BF)
fffff880`00e6a000 fffff880`00e77000   vdrvroot vdrvroot.sys Mon Jul 13 20:01:31 2009 (4A5BCADB)
fffff880`01876000 fffff880`01884000   vga      vga.sys      Mon Jul 13 19:38:47 2009 (4A5BC587)
fffff880`01200000 fffff880`01225000   VIDEOPRT VIDEOPRT.SYS Mon Jul 13 19:38:51 2009 (4A5BC58B)
fffff880`018d7000 fffff880`018e7000   vmstorfl vmstorfl.sys Mon Jul 13 19:42:54 2009 (4A5BC67E)
fffff880`00d9e000 fffff880`00db3000   volmgr   volmgr.sys   Mon Jul 13 19:19:57 2009 (4A5BC11D)
fffff880`00c00000 fffff880`00c5c000   volmgrx  volmgrx.sys  Mon Jul 13 19:20:33 2009 (4A5BC141)
fffff880`018e7000 fffff880`01933000   volsnap  volsnap.sys  Mon Jul 13 19:20:08 2009 (4A5BC128)
fffff880`019e0000 fffff880`019f0000   watchdog watchdog.sys Mon Jul 13 19:37:35 2009 (4A5BC53F)
fffff880`00f46000 fffff880`00fea000   Wdf01000 Wdf01000.sys Mon Jul 13 19:22:07 2009 (4A5BC19F)
fffff880`00fea000 fffff880`00ff9000   WDFLDR   WDFLDR.SYS   Mon Jul 13 19:19:54 2009 (4A5BC11A)
fffff960`00080000 fffff960`0038f000   win32k   win32k.sys   Mon Jul 13 19:40:16 2009 (4A5BC5E0)
fffff880`00e57000 fffff880`00e60000   WMILIB   WMILIB.SYS   Mon Jul 13 19:19:51 2009 (4A5BC117)
fffff880`028ee000 fffff880`0290f000   WudfPf   WudfPf.sys   Mon Jul 13 20:05:37 2009 (4A5BCBD1)

Unloaded modules:
fffff880`01830000 fffff880`0183e000   crashdmp.sys
    Timestamp: unavailable (00000000)
    Checksum:  00000000
    ImageSize:  0000E000
fffff880`0183e000 fffff880`0184a000   dump_ataport
    Timestamp: unavailable (00000000)
    Checksum:  00000000
    ImageSize:  0000C000
fffff880`0184a000 fffff880`01853000   dump_atapi.s
    Timestamp: unavailable (00000000)
    Checksum:  00000000
    ImageSize:  00009000
fffff880`01853000 fffff880`01866000   dump_dumpfve
    Timestamp: unavailable (00000000)
    Checksum:  00000000
    ImageSize:  00013000
fffff880`01933000 fffff880`0193b000   spldr.sys
    Timestamp: unavailable (00000000)
    Checksum:  00000000
    ImageSize:  00008000
fffff880`0110b000 fffff880`01166000   bdfsfltr.sys
    Timestamp: unavailable (00000000)
    Checksum:  00000000
    ImageSize:  0005B000
 


#5
Yes, it is a matching set. It's been working for 3 years.

Memtest didn't show anything, and I've tried all 3 sticks by themselves, and still get a bsod. I can get into safe mode sometimes, sometimes it still gives me the bsod

What is that update asus atk?
 


#6
Yes, it is a matching set. It's been working for 3 years.
I believe you, but if you would let me I'd like to see memory and SPD of each slot.

http://windows7forums.com/blue-scre...mportant-every-thread-starter-please-see.html


ASUS ATK0110 ACPI Utility -- asus support --> downloads for your motherboard --> Utilities --> ATK0110 ACPI Utility.
 


#7
when running cpuID, I get the error msg "The error code 0x43C (1084) occured during initialization. It then opens, but displays no info in Memory or SPD. So I can't see the info in cpuid
 


#8
Yea, clear. If you're sure it's good then it's good, best when sticks are from the same batch.
 


#9
Ya they were bought as a pack, and have a sticker on them saying "kit of 2"

Should I just reinstall?
 


This website is not affiliated, owned, or endorsed by Microsoft Corporation. It is a member of the Microsoft Partner Program.