Mikedabike
Well-known member
Hi back again, got 2 BSOD dumps here any obvious info jumping out at anyone? Thanks.
[10v1803b17134 x64] BC 0xd1, 0x1E, 0x124
- Thread starter Mikedabike
- Start date
re: BSOD again - Bugcheck 0x000000d1
Hello,
One of the crash dumps shows the Killer Network driver as being a problem:
The current driver is dated as follows: bwcW10x64.sys Tue Feb 9 10:23:57 2016See if you can find a newer one.
Hello,
One of the crash dumps shows the Killer Network driver as being a problem:
Code:
[COLOR=#1e1e1e]BugCheck D1, {1, 2, 0, fffff806018a43a0}[/COLOR]
[COLOR=#1e1e1e]*** WARNING: Unable to verify timestamp for [/COLOR][COLOR=#1e1e1e]bwcW10x64.sys[/COLOR]
[COLOR=#1e1e1e]*** ERROR: Module load completed but symbols could not be loaded for bwcW10x64.sys[/COLOR]
[COLOR=#1e1e1e]Probably caused by : [/COLOR][COLOR=#1e1e1e]bwcW10x64.sys ( bwcW10x64+43a0 )[/COLOR]The current driver is dated as follows: bwcW10x64.sys Tue Feb 9 10:23:57 2016See if you can find a newer one.
Mikedabike
Well-known member
re: BSOD again - Bugcheck 0x000000d1
Thanks for the speedy response :) i have hopefully updated the right driver ethernet has changed so thats a newer one,(i downloaded the killer drivers only option, hoping it did them all) i also had an ME driver i updated to no idea if thats connected to crash or not, hope it is as simple as that this time round. Thanks again hope to not be back despite you all being so damn nice :)
Thanks for the speedy response :) i have hopefully updated the right driver ethernet has changed so thats a newer one,(i downloaded the killer drivers only option, hoping it did them all) i also had an ME driver i updated to no idea if thats connected to crash or not, hope it is as simple as that this time round. Thanks again hope to not be back despite you all being so damn nice :)
- May 7, 2013
- 10,400
re: BSOD again - Bugcheck 0x000000d1
Have you been experiencing any further issues?
Have you been experiencing any further issues?
Mikedabike
Well-known member
re: BSOD again - Bugcheck 0x000000d1
one more, i have had BSOD every since i had the comp, they come and go, this was a single crash this time, a few weeks later. I can go a couple of months between crashes or i can have 2 or 3 on a trot then stop. I have learned to live with it as 2 years of the pattern has not really led me any where. Still if you see omething it is always appreciated.
one more, i have had BSOD every since i had the comp, they come and go, this was a single crash this time, a few weeks later. I can go a couple of months between crashes or i can have 2 or 3 on a trot then stop. I have learned to live with it as 2 years of the pattern has not really led me any where. Still if you see omething it is always appreciated.
- May 7, 2013
- 10,400
re: BSOD again - Bugcheck 0x000000d1
I'll have a look at the file tonight for you.
I'll have a look at the file tonight for you.
- May 7, 2013
- 10,400
re: BSOD again - Bugcheck 0x000000d1
[/COLOR]
The first parameter indicates that an invalid memory address was accessed. The exception seems to have been raised when the internal clock was being reset. The exception record doesn't seem to have been captured by the debugger correctly either.
However, judging by the bugcheck parameters, we can assume that the operation was a read operation and the address seems to be invalid too. The third parameter indicates a read operation and the fourth parameter provides the address which was being referenced.
Did you update the network driver properly? It appears to be in the raw stack just before the crash occured.
The download page seems to be here - Other Downloads
Code:
[COLOR=#ff0000]BugCheck 1E[/COLOR][COLOR=#1e1e1e], {[/COLOR][COLOR=#008000]ffffffffc0000005[/COLOR][COLOR=#1e1e1e], fffff8037274bbff, [/COLOR][COLOR=#0000cd]0[/COLOR][COLOR=#1e1e1e], ffffffffffffffff[/COLOR][COLOR=#1e1e1e]}[/COLOR][COLOR=#1e1e1e]
Probably caused by : [/COLOR][COLOR=#1e1e1e]ntkrnlmp.exe ( nt!KeResumeClockTimerFromIdle+7f )The first parameter indicates that an invalid memory address was accessed. The exception seems to have been raised when the internal clock was being reset. The exception record doesn't seem to have been captured by the debugger correctly either.
Code:
2: kd> [COLOR=#008000].exr 0xffff808db683f3d0[/COLOR]
ExceptionAddress: 0000000000000000
ExceptionCode: 00000000
ExceptionFlags: 00000000
NumberParameters: 0However, judging by the bugcheck parameters, we can assume that the operation was a read operation and the address seems to be invalid too. The third parameter indicates a read operation and the fourth parameter provides the address which was being referenced.
Did you update the network driver properly? It appears to be in the raw stack just before the crash occured.
Code:
2: kd> [COLOR=#008000]lmvm bwcW10x64[/COLOR]
start end module name
fffff809`b9c40000 fffff809`b9fa5000 bwcW10x64 T (no symbols)
Loaded symbol image file: bwcW10x64.sys
Image path: bwcW10x64.sys
Image name: bwcW10x64.sys
Timestamp: [COLOR=#ff0000]Tue Feb 09 18:23:57 2016[/COLOR] (56BA2EBD)
CheckSum: 00027384
ImageSize: 00365000
Translations: 0000.04b0 0000.04e4 0409.04b0 0409.04e4The download page seems to be here - Other Downloads
Mikedabike
Well-known member
re: BSOD again - Bugcheck 0x000000d1
I have reinstalled it again, there was a a slight change in numbers from 1.5.1 822 x64 to 1.5.1 844 x64 so maybe that will help? I will have to wait and see, thanks for your help again.
I have reinstalled it again, there was a a slight change in numbers from 1.5.1 822 x64 to 1.5.1 844 x64 so maybe that will help? I will have to wait and see, thanks for your help again.
- May 7, 2013
- 10,400
re: BSOD again - Bugcheck 0x000000d1
Thanks Mike, looks like it has updated to a newer version.
Thanks Mike, looks like it has updated to a newer version.
Mikedabike
Well-known member
re: BSOD again - Bugcheck 0x000000d1
Not sure if i should start a new post or not so for now adding this here. After the last episode of BSOD i updated the drivers u suggested and them went one step further by unselecting the offending program from start up, and until today that had stopped the issues... would greatly appreciate any insight into the latest crash, i had for the first time in a very long time started to relax about this never ending story..! Thanks in advanced. mike
Not sure if i should start a new post or not so for now adding this here. After the last episode of BSOD i updated the drivers u suggested and them went one step further by unselecting the offending program from start up, and until today that had stopped the issues... would greatly appreciate any insight into the latest crash, i had for the first time in a very long time started to relax about this never ending story..! Thanks in advanced. mike
re: BSOD again - Bugcheck 0x000000d1
New bios available: 7.30.
drmk.sys shows an older date.
peauth.sys shows a future date.
Verify their dates directly in their properties in c:\windows\system32\drivers.
If they are different (than 2017-2018), then launch these commands from an elevated command prompt and show their results:
New bios available: 7.30.
drmk.sys shows an older date.
peauth.sys shows a future date.
Verify their dates directly in their properties in c:\windows\system32\drivers.
If they are different (than 2017-2018), then launch these commands from an elevated command prompt and show their results:
And an offline virus scan could help too... Or open a new topic in security arena sub-forum and ask for help, searching for malware.
Mikedabike
Well-known member
re: BSOD again - Bugcheck 0x000000d1
dmk.sys 29 september 2017 20:40:59 < all 3 dates show the same
PEAuth.sys 11 April 2018 06:08:52
30 March 2018 10:29:10
11 April 2018 06:08:52
That is what i see in the driver folder.
Any other info i should be looking at? Will check out the bios update asap and will do a full virus scan, but only running windows scanner as ws advised here to get rid of my AVG a while back.
dmk.sys 29 september 2017 20:40:59 < all 3 dates show the same
PEAuth.sys 11 April 2018 06:08:52
30 March 2018 10:29:10
11 April 2018 06:08:52
That is what i see in the driver folder.
Any other info i should be looking at? Will check out the bios update asap and will do a full virus scan, but only running windows scanner as ws advised here to get rid of my AVG a while back.
Mikedabike
Well-known member
Re: BSOD again - Bugcheck 0x000000d1
And still i am getting random BSOD anything helpful in these last 2 reports please, dated 14th and 16th of this month. 14th was just afer start up, nothing much going on with comp at the time, the 16th, 5 mins ago i ws watching a youtube vid on Firefox, steam was downloading update so nothing heavy going on then either.
And still i am getting random BSOD anything helpful in these last 2 reports please, dated 14th and 16th of this month. 14th was just afer start up, nothing much going on with comp at the time, the 16th, 5 mins ago i ws watching a youtube vid on Firefox, steam was downloading update so nothing heavy going on then either.
Mikedabike
Well-known member
Re: BSOD again - Bugcheck 0x000000d1
And another crash today, this one was during gaming. Really would appreciate some insight here if poss. Thanks in advance.
And another crash today, this one was during gaming. Really would appreciate some insight here if poss. Thanks in advance.
Mikedabike
Well-known member
Re: BSOD again - Bugcheck 0x000000d1
And another, this is getting worse over last 3 days, no new programs on comp in that time, windows update on the 14th is only additions.
And another, this is getting worse over last 3 days, no new programs on comp in that time, windows update on the 14th is only additions.
Mikedabike
Well-known member
Ok thanks for the advice. I will run a driver verifier once i get a clear 24 hour comp free time frame, but in the meantime i have fouund a few things that may be of interest to you. Going to my motherboard website i noticed they recommend a 2015 driver over newer ones for the killer drivers, something that came up before in a dump as a possable cause. ( ASRock > Fatal1ty Z170 Gaming K4 ) (Atheros Killer Lan driver ver:1.1.56.1651) The origional driver i had on my comp was newer than this, and i updated that to a much newer one after it was pointed out here i was on an old one. I have just installed the 2015 driver as reccomended on the web site to try this. Anyway i thought this info may be of use to anyone else with the same MB Fatal1ty Z170 Gaming K4 Series. Will let you know what happens.
I think you might be misinterpreting the ASRock recommendation. The driver version is unimportant. The problem being addressed in the recommendation is the Killer Performance Suite software which gets installed by default using the installer available from the motherboard product support page. They want you to get rid of the software, reboot, and then run the installer but manually change the options so that only the driver gets installed. The software is notorious for causing problems so if it got installed you should remove it.
Mikedabike
Well-known member
Thanks for pointing that out, i totally missed it. I uninstalled the extra software and re updated driver alone. I have managed to be BSOD free for a week or two but hey presto, just as i felt it may be ok, crashed again just now. I include the dump just incase, i do need to run driver verifyer still, but right now my comp is busy 24/7, if anything shows in this dump, appreciate the insight, if not i will try to get a verify done as soon as time permits. Thank you for your help.
This bugcheck happened because of a double fault exception. It looks like a system thread stack might have run out of space. A fault occurred so the system tried to push a trap frame but there was no room on the stack which caused another fault; double fault so crash the system. However, it looks like it might have been stuck in a repeated fault or recursive call which caused the stack to run out of space.
Looking at the initial trap frame it looks like all it was trying to do was add 10 hex to a CPU register (rcx). I'm not sure why that would cause a fault but maybe I'm misinterpreting:
The only thing that comes to mind is that perhaps the memory where the opcode resides is marked as non-executable but that doesn't seem to be the case. Strange - perhaps somebody else can have a look.
Another thing (which could just be a coincidence) is that the dumps show core 2 running the thread which triggers the crash in all of the dumps you've provided. Honestly, though, I'm a bit worried about the CPU since the title of your post mentions a 0x124 bugcheck. None of the dumps you've made available are 0x124 bugchecks, though, unless I've missed it. It does look like there might be a very slight overclock on the CPU.
I wouldn't expect it to be enough to cause a problem but I've seen BIOS turbo and automated overclocking cause strange and subtle problems. I'd recommend disabling any overclocking or performance turbo settings in the BIOS if they aren't already.
Code:
STACK_TEXT:
fffff38d`f6038f90 fffff803`c63b3f42 : 158d4800`23a1cb0d 28438b48`0023a1bc 39480000`06400548 48000b7c`c4850f11 : nt!KiDispatchException+0x2c
fffff38d`f6039140 fffff803`c63b069c : 3840ffcb`e93ae8cd c6850f00`2388d635 d7313e3d`83000b7b d705f805`940f01ff : nt!KiExceptionDispatch+0xc2
fffff38d`f6039320 fffff803`c63b507e : fffff803`c6264b4a 4489480f`458b48c0 48ffb5ec`71e82024 e246e8d8`8b7f4d8b : nt!KiGeneralProtectionFault+0x2dc
fffff38d`f60394b8 fffff803`c6264b4a : 4489480f`458b48c0 48ffb5ec`71e82024 e246e8d8`8b7f4d8b 48c0990f`db85ffb5 : nt!memset+0x7e
fffff38d`f60394c0 fffff803`c62643db : 19d6058d`4800c065 458948c0`570f001d b845c7b8`458d4cc8 020006ba`00000030 : nt!KiOpDecode+0x2e
fffff38d`f6039520 fffff803`c6263ec2 : fffff38d`f6039db8 fffff38d`f6039b00 fffff38d`f6039600 fffff38d`f603a140 : nt!KiPreprocessFault+0x93
fffff38d`f60395d0 fffff803`c63b3f42 : e88b4cce`8b41d68b c38b44ff`cbd383e8 f88b4cce`8b41d68b c38b44ff`cbd373e8 : nt!KiDispatchException+0x1b2
fffff38d`f6039c80 fffff803`c63b069c : 48202464`894c000f ede80250`8d41cb8b 32880fc0`85ffee4c 44c6c033`45000b73 : nt!KiExceptionDispatch+0xc2
fffff38d`f6039e60 fffff803`c63b507e : fffff803`c6264b4a 00000100`202444c7 0de80000`0001b841 7d880fc0`85ffb5f8 : nt!KiGeneralProtectionFault+0x2dc
fffff38d`f6039ff8 fffff803`c6264b4a : 00000100`202444c7 0de80000`0001b841 7d880fc0`85ffb5f8 850f045f`39000b8a : nt!memset+0x7e
fffff38d`f603a000 fffff803`c62643db : ffb5f7b8`e8000000 000b8a30`880fc085 8a26850f`01047f83 0001b90c`578b000b : nt!KiOpDecode+0x2e
fffff38d`f603a060 fffff803`c6263ec2 : fffff38d`f603a8f8 fffff38d`f603a640 fffff38d`f603a140 fffff38d`f603ac80 : nt!KiPreprocessFault+0x93
fffff38d`f603a110 fffff803`c63b3f42 : 48a44589`c0458d4c 8d058d48`70244c8d 8948ce8b`44ffda17 4c83d78b`48282444 : nt!KiDispatchException+0x1b2
fffff38d`f603a7c0 fffff803`c63b069c : 8d48c033`45202444 8de8ce8b`48402454 0fc085f8`8bffb5f7 5e8d4900`00008088 : nt!KiExceptionDispatch+0xc2
fffff38d`f603a9a0 fffff803`c63b507e : fffff803`c6264b4a 89661604`8d41c88b 4d8d4cca`b70f4b04 8d440000`000abadf : nt!KiGeneralProtectionFault+0x2dc
fffff38d`f603ab38 fffff803`c6264b4a : 89661604`8d41c88b 4d8d4cca`b70f4b04 8d440000`000abadf 48fff12b`41e80242 : nt!memset+0x7e
fffff38d`f603ab40 fffff803`c62643db : 30af45c7`4824448d 30244489`48000000 c0570f40`244c8d48 c9334528`246c8944 : nt!KiOpDecode+0x2e
fffff38d`f603aba0 fffff803`c6263ec2 : fffff38d`f603b438 fffff38d`f603b180 fffff38d`f603ac80 fffff38d`f603b7c0 : nt!KiPreprocessFault+0x93
fffff38d`f603ac50 fffff803`c63b3f42 : 05e86e49`7350b841 8548f08b`48ffcbfd 4810488d`486174c0 896607b7`0f084889 : nt!KiDispatchException+0x1b2
fffff38d`f603b300 fffff803`c63b069c : 48085889`48c48b48 48564157`56106889 a824b48b`4860ec83 608348db`33000000 : nt!KiExceptionDispatch+0xc2
fffff38d`f603b4e0 fffff803`c63b507e : fffff803`c6264b4a fffff38d`00000003 fffff38d`f603f6b0 fffff803`c62f30cc : nt!KiGeneralProtectionFault+0x2dc
fffff38d`f603b678 fffff803`c6264b4a : fffff38d`00000003 fffff38d`f603f6b0 fffff803`c62f30cc fffff803`c6263058 : nt!memset+0x7e
fffff38d`f603b680 fffff803`c62643db : fffff38d`00000202 fffff38d`f603f6b0 fffff38d`f6030018 fffff38d`f603b820 : nt!KiOpDecode+0x2e
fffff38d`f603b6e0 fffff803`c6263ec2 : fffff38d`f603bf78 fffff38d`f603bcc0 fffff38d`f603b7c0 fffff38d`f603c300 : nt!KiPreprocessFault+0x93
fffff38d`f603b790 fffff803`c63b3f42 : 00000202`0018002b 00000000`00000002 fffff38d`f603f6b0 fffff803`c638187c : nt!KiDispatchException+0x1b2
fffff38d`f603be40 fffff803`c63b069c : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiExceptionDispatch+0xc2
fffff38d`f603c020 fffff803`c63b507e : fffff803`c6264b4a 33a974c0`00000005 49000010`00000008 41ffb0dd`f9e8ce00 : nt!KiGeneralProtectionFault+0x2dc
fffff38d`f603c1b8 fffff803`c6264b4a : 33a974c0`00000005 49000010`00000008 41ffb0dd`f9e8ce00 ffffdf8a`69510080 : nt!memset+0x7e
fffff38d`f603c1c0 fffff803`c62643db : 00000001`00000003 00000000`00000000 00000000`000000ff 00000000`00000000 : nt!KiOpDecode+0x2e
fffff38d`f603c220 fffff803`c6263ec2 : fffff38d`f603cab8 fffff38d`f603c800 fffff38d`f603c300 fffff38d`f603ce40 : nt!KiPreprocessFault+0x93
fffff38d`f603c2d0 fffff803`c63b3f42 : ffff8900`89000001 fffff38d`00000000 0000ff02`00000011 ffffff02`f603ff02 : nt!KiDispatchException+0x1b2
fffff38d`f603c980 fffff803`c63b069c : fffff38d`f603cc30 fffff38d`f603cba8 fffff38d`f603cb90 00000000`00000000 : nt!KiExceptionDispatch+0xc2
fffff38d`f603cb60 fffff803`c63b507e : fffff803`c6264b4a fffff803`c6380ba0 fffff38d`f603fa10 00000000`00000002 : nt!KiGeneralProtectionFault+0x2dc
fffff38d`f603ccf8 fffff803`c6264b4a : fffff803`c6380ba0 fffff38d`f603fa10 00000000`00000002 00000000`00000001 : nt!memset+0x7e
fffff38d`f603cd00 fffff803`c62643db : ffffdf8a`60760c00 fffff803`c94f4a84 00000000`0000005a fffff803`c94f4d60 : nt!KiOpDecode+0x2e
fffff38d`f603cd60 fffff803`c6263ec2 : fffff38d`f603d5f8 fffff38d`f603d340 fffff38d`f603ce40 fffff38d`f603d980 : nt!KiPreprocessFault+0x93
fffff38d`f603ce10 fffff803`c63b3f42 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiDispatchException+0x1b2
fffff38d`f603d4c0 fffff803`c63b069c : ffffdf8a`00008900 00000000`00008900 fffff38d`f603d8b8 ffffdf8a`60786300 : nt!KiExceptionDispatch+0xc2
fffff38d`f603d6a0 fffff803`c63b507e : fffff803`c6264b4a 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiGeneralProtectionFault+0x2dc
fffff38d`f603d838 fffff803`c6264b4a : 00000000`00000000 00000000`00000000 00000000`00000000 ffffdf8a`66e6e1a0 : nt!memset+0x7e
fffff38d`f603d840 fffff803`c62643db : fffff803`c620b000 fffff38d`f603de00 fffff38d`f603f388 fffff38d`f603f6b0 : nt!KiOpDecode+0x2e
fffff38d`f603d8a0 fffff803`c6263ec2 : fffff38d`f603e138 fffff38d`f603de80 fffff38d`f603d980 fffff38d`f603e4c0 : nt!KiPreprocessFault+0x93
fffff38d`f603d950 fffff803`c63b3f42 : ffffdf8a`61373370 ffffdf8a`00001f80 00000000`00000001 fffff803`c6382bd1 : nt!KiDispatchException+0x1b2
fffff38d`f603e000 fffff803`c63b069c : 00000000`000000ff 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiExceptionDispatch+0xc2
fffff38d`f603e1e0 fffff803`c63b507e : fffff803`c6264b4a 00000000`00000001 fffff803`c62260dd ffffdf8a`59c7c4b0 : nt!KiGeneralProtectionFault+0x2dc
fffff38d`f603e378 fffff803`c6264b4a : 00000000`00000001 fffff803`c62260dd ffffdf8a`59c7c4b0 00000000`00000001 : nt!memset+0x7e
fffff38d`f603e380 fffff803`c62643db : fffff38d`f603f388 fffff38d`f603f6b0 00000000`00000002 00000000`00000001 : nt!KiOpDecode+0x2e
fffff38d`f603e3e0 fffff803`c6263ec2 : fffff38d`f603ec78 fffff38d`f603e9c0 fffff38d`f603e4c0 fffff38d`f603f000 : nt!KiPreprocessFault+0x93
fffff38d`f603e490 fffff803`c63b3f42 : ffffdf8a`5bd6f820 9a81babd`441a9995 00000000`00000000 fffff803`c623402c : nt!KiDispatchException+0x1b2
fffff38d`f603eb40 fffff803`c63b069c : fffff803`c990a228 fffff803`c94bd969 ffffffff`ffffffff fffff803`c94f4904 : nt!KiExceptionDispatch+0xc2
fffff38d`f603ed20 fffff803`c63b507e : fffff803`c6264b4a ffffdf8a`66eead00 00000000`00000000 00000000`00000001 : nt!KiGeneralProtectionFault+0x2dc
fffff38d`f603eeb8 fffff803`c6264b4a : ffffdf8a`66eead00 00000000`00000000 00000000`00000001 ffffdf8a`5bdcd190 : nt!memset+0x7e
fffff38d`f603eec0 fffff803`c62643db : ffffdf8a`5bdcd150 fffff803`c94e1cf7 ffffdf8a`5bdcd190 fffff38d`f603f0e9 : nt!KiOpDecode+0x2e
fffff38d`f603ef20 fffff803`c6263ec2 : fffff38d`f603f7b8 fffff38d`f603f500 fffff38d`f603f000 ffffdf8a`689b3080 : nt!KiPreprocessFault+0x93
fffff38d`f603efd0 fffff803`c63b3f42 : fffff803`c6680240 ffffffff`00000030 00000000`000000ff 00000218`ffffffff : nt!KiDispatchException+0x1b2
fffff38d`f603f680 fffff803`c63b069c : 00000000`00000000 ffffdf8a`685b8870 fffff38d`f603fa18 fffff803`c62d353c : nt!KiExceptionDispatch+0xc2
fffff38d`f603f860 fffff803`c63b507e : fffff803`c62a8d77 00000000`00000003 00000000`00000002 00000000`00000000 : nt!KiGeneralProtectionFault+0x2dc
fffff38d`f603f9f8 fffff803`c62a8d77 : 00000000`00000003 00000000`00000002 00000000`00000000 01d41270`13834777 : nt!memset+0x7e
fffff38d`f603fa00 fffff803`c63a6a5c : ffffffff`00000000 ffffab00`74ccf180 ffffab00`74cdf200 ffffdf8a`689b3080 : nt!PoIdle+0x187
fffff38d`f603fb60 00000000`00000000 : fffff38d`f6040000 fffff38d`f6039000 00000000`00000000 00000000`00000000 : nt!KiIdleLoop+0x2c
Code:
2: kd> .trap fffff38d`f603f860
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=fffff38df603fa74 rbx=0000000000000000 rcx=fffff38df603fa74
rdx=0000000000000000 rsi=0000000000000000 rdi=0000000000000000
rip=fffff803c63b507e rsp=fffff38df603f9f8 rbp=fffff38df603fb00
r8=fffff38df603fb18 r9=0101010101010101 r10=ffffdf8a60789000
r11=fffff38df603fb58 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0 nv up di ng nz na po nc
nt!memset+0x7e:
[COLOR=#008000]fffff803`c63b507e[/COLOR] 4883c110 add rcx,10h
Code:
2: kd> !pte [COLOR=#008000]fffff803`c63b507e[/COLOR]
VA fffff803c63b507e
PXE at FFFF81C0E0703F80 PPE at FFFF81C0E07F0078 PDE at FFFF81C0FE00F188 PTE at FFFF81FC01E31DA8
contains 0000000003B08063 contains 0000000003B09063 contains 00000000024008E3 contains 0000000000000000
pfn 3b08 ---DA--KW[COLOR=#008000]E[/COLOR]V pfn 3b09 ---DA--KW[COLOR=#008000]E[/COLOR]V pfn 2400 --LDA--KW[COLOR=#008000]E[/COLOR]V LARGE PAGE pfn 2435
Code:
2: kd> !sysinfo cpuinfo
[CPU Information]
~MHz = REG_DWORD 4008Has Sysnative Forums helped you? Please consider donating to help us support the site!