BSOD's Again after replacement KomputerBay RAM installation


Well-Known Member
I renamed both the files mentioned and still a bsod. This time while the PC was idle, ill have to run a large Memtest tonight, see if i can get it to read more intensively. I got MSE and got rid of Norton first. I know the slots are fine becuase it only does this with the new RAM. Would it be illegal on this site to post the amazon link for the RAM, and the MSI site for my mobo, for you to check to see if anything could be compatibility problems. Well, heres the new dump, hot off the Bugcheck-Bull**** press...

View attachment


Windows Forum Admin
Staff member
Premium Supporter
Microsoft MVP
* *
* Bugcheck Analysis *
* *

This is a very common bugcheck. Usually the exception address pinpoints
the driver/function that caused the problem. Always note this address
as well as the link date of the driver/image that contains this address.
Arg1: 0000000000000000, The exception code that was not handled
Arg2: 0000000000000000, The address that the exception occurred at
Arg3: 0000000000000000, Parameter 0 of the exception
Arg4: 0000000000000000, Parameter 1 of the exception

Debugging Details:

EXCEPTION_CODE: (Win32) 0 (0) - The operation completed successfully.

00000000`00000000 ?? ???

EXCEPTION_PARAMETER1: 0000000000000000

EXCEPTION_PARAMETER2: 0000000000000000






EXCEPTION_RECORD: fffff88002f8ca28 -- (.exr 0xfffff88002f8ca28)
ExceptionAddress: fffff800035f7f04 (hal!HalpHpetQueryCount+0x0000000000000036)
ExceptionCode: c0000005 (Access violation)
ExceptionFlags: 00000000
NumberParameters: 2
Parameter[0]: 0000000000000000
Parameter[1]: 000000000000010c
Attempt to read from address 000000000000010c

TRAP_FRAME: fffff88002f8cad0 -- (.trap 0xfffff88002f8cad0)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=000000000000010c rbx=0000000000000000 rcx=000000900000002c
rdx=000000000000010c rsi=0000000000000000 rdi=0000000000000000
rip=fffff800035f7f04 rsp=fffff88002f8cc68 rbp=0000000000000000
r8=000000004c7c1442 r9=00000000017d7840 r10=00000000000249f9
r11=fffffa800a4e9601 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0 nv up ei pl zr na po nc
fffff800`035f7f04 483bc2 cmp rax,rdx
Resetting default scope

LAST_CONTROL_TRANSFER: from fffff80003078d6e to fffff80003081010

fffff880`02f8bb18 fffff800`03078d6e : 00000000`00000010 fffff880`01882d76 fffff880`02f8c290 fffff800`030ad9a8 : nt!KeBugCheck
fffff880`02f8bb20 fffff800`030a675d : fffff800`0328ee70 fffff800`031ccff4 fffff800`03011000 fffff880`02f8ca28 : nt!KiKernelCalloutExceptionHandler+0xe
fffff880`02f8bb50 fffff800`030addd0 : fffff800`031cfa64 fffff880`02f8bbc8 fffff880`02f8ca28 fffff800`03011000 : nt!RtlpExecuteHandlerForException+0xd
fffff880`02f8bb80 fffff800`030badff : fffff880`02f8ca28 fffff880`02f8c290 fffff880`00000000 00000000`00000000 : nt!RtlDispatchException+0x410
fffff880`02f8c260 fffff800`03080682 : fffff880`02f8ca28 00000000`00000000 fffff880`02f8cad0 fffff880`02f64180 : nt!KiDispatchException+0x16f
fffff880`02f8c8f0 fffff800`0307f1fa : 00000000`00000000 00000000`00000000 00000000`00002700 00000000`00000000 : nt!KiExceptionDispatch+0xc2
fffff880`02f8cad0 fffff800`035f7f04 : fffff800`035fc64c 00000090`0000002c 00000000`00000246 fffff880`02f8cc98 : nt!KiPageFault+0x23a
fffff880`02f8cc68 fffff800`035fc64c : 00000090`0000002c 00000000`00000246 fffff880`02f8cc98 00000000`00000018 : hal!HalpHpetQueryCount+0x36
fffff880`02f8cc70 fffff800`0308eb37 : 00000000`ffffffed 00000000`00000000 fffff880`02f6efc0 00000000`00000001 : hal!KeQueryPerformanceCounter+0x74
fffff880`02f8cca0 fffff800`0308974c : fffff880`02f64180 fffff880`00000000 00000000`00000000 fffff880`10018128 : nt!PoIdle+0x5b7
fffff880`02f8cd80 00000000`00000000 : fffff880`02f8d000 fffff880`02f87000 fffff880`02f8cd40 00000000`00000000 : nt!KiIdleLoop+0x2c


fffff800`03078d6e 90 nop


SYMBOL_NAME: nt!KiKernelCalloutExceptionHandler+e



IMAGE_NAME: ntkrnlmp.exe


FAILURE_BUCKET_ID: X64_0x1E_nt!KiKernelCalloutExceptionHandler+e

BUCKET_ID: X64_0x1E_nt!KiKernelCalloutExceptionHandler+e

Followup: MachineOwner
The KMODE_EXCEPTION_NOT_HANDLED bug check has a value of 0x0000001E. This indicates that a kernel-mode program generated an exception which the error handler did not catch.


This is a very common bug check. To interpret it, you must identify which exception was generated.
Common exception codes include:

  • 0x80000002: STATUS_DATATYPE_MISALIGNMENTAn unaligned data reference was encountered.
  • 0x80000003: STATUS_BREAKPOINTA breakpoint or ASSERT was encountered when no kernel debugger was attached to the system.
  • 0xC0000005: STATUS_ACCESS_VIOLATIONA memory access violation occurred. (Parameter 4 of the bug check is the address that the driver attempted to access.)

    This web page gives you some info on the above access violation even though it is for xp. One thing did spring to mind. If your old RAM does not bsod why not use your old stuff and be bsod free.


Well-Known Member
New RAM is 8GB, old is only 4, ill put that back in the second i get the chance. BTW, new BSOD happened like half an hour after the first. Memtest only showing 1 error in 15 hours.

View attachment


Well-Known Member
I have now switched out the new ram and the old RAM a while ago and no probs. I have also sent for KomputerBay's tech support. Though while randomly researching my bios creator on Wikipedia. I found something interesting. When i had quick booting off in my BIOS i would get 2 beeps? This supposedly indicates a parity error in the first 64KiB of RAM.


Windows Forum Admin
Staff member
Premium Supporter
Microsoft MVP
That's using the old or should I say buggered RAM, yes? I'm just relieved to hear your now bsod free..


Well-Known Member
right now i am using the old RAM.


Well-Known Member
Also got a reply back from KomputerBay saying that RAM with 1 memtest error will not cause bsod's.


Windows Forum Admin
Staff member
Premium Supporter
Microsoft MVP
Also got a reply back from KomputerBay saying that RAM with 1 memtest error will not cause bsod's.
Has your system blue screened since changing the RAM over?


Well-Known Member
nope (this writing is to meet character requirements.)


Windows Forum Admin
Staff member
Premium Supporter
Microsoft MVP
Well in my opinion your 8GB set is faulty. It could be that your system isn't compatible with that RAM manufacturer, your motherboard web site should tell you. Even so, if it's showing errors in memtest it has got to be highly suspect especially when your old RAM runs perfectly. It's entirely possible to buy bad RAM off the shelves and you certainly would not be the first.

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