BSOD UNEXPECTED_KERNEL_MODE_TRAP
- Thread starter Ben Davis
- Start date
-
- Tags
- bsod windows 10
-
Hi there and welcome to PC Help Forum (PCHF), a more effective way to get the Tech Support you need!
We have Experts in all areas of Tech, including Malware Removal, Crash Fixing and BSOD's , Microsoft Windows, Computer DIY and PC Hardware, Networking, Gaming, Tablets and iPads, General and Specific Software Support and so much more.
Why not Click Here To Sign Up and start enjoying great FREE Tech Support.
This site uses cookies. By continuing to use this site, you are agreeing to our use of cookies. Learn More.
- Status
Tip
If using a computer and not a mobile phone, please avoid adding multiple posts while waiting for us to reply to your last, edit your last post to include anything that you wish to add, this will ensure nothing gets overlooked which can sometimes happen if a thread has more than one page.
Weird, you seem to have Fat 32 file system info on the HDD, any idea how this has come to be as Fat 32 is normally associated with USB devices.
Before we suggest anything can you answer the above question for us.
We need to first check the integrity of the HDD and then Windows itself, we can`t use the info in the second dmp file atm because the info is not reliable but fwiw a problem between the AV and Nvidea drivers was partially to blame.
Some info here regarding the error being flagged up in the first dmp.
Debug session time: Fri Dec 21 03:45:31.917 2018 (UTC - 5:00)
System Uptime: 0 days 21:34:21.709
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
CACHE_MANAGER (34)
See the comment for FAT_FILE_SYSTEM (0x23)
Arguments:
Arg1: 0000000000051352
Arg2: fffff98d9d27edf8
Arg3: fffff98d9d27e640
Arg4: fffff80261e8f001
Debugging Details:
------------------
***** Kernel symbols are WRONG. Please fix symbols to do analysis.
*************************************************************************
*** ***
*** ***
*** Either you specified an unqualified symbol, or your debugger ***
*** doesn't have full symbol information. Unqualified symbol ***
*** resolution is turned off by default. Please either specify a ***
*** fully qualified symbol module!symbolname, or enable resolution ***
*** of unqualified symbols by typing ".symopt- 100". Note that ***
*** enabling unqualified symbol resolution with network symbol ***
*** server shares in the symbol path may cause the debugger to ***
*** appear to hang for long periods of time when an incorrect ***
*** symbol name is typed or the network symbol server is down. ***
*** ***
*** For some commands to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!_KPRCB ***
*** ***
*************************************************************************
TRIAGER: Could not open triage file : e:\dump_analysis\program\triage\modclass.ini, error 2
*************************************************************************
*** ***
*** ***
*** Either you specified an unqualified symbol, or your debugger ***
*** doesn't have full symbol information. Unqualified symbol ***
*** resolution is turned off by default. Please either specify a ***
*** fully qualified symbol module!symbolname, or enable resolution ***
*** of unqualified symbols by typing ".symopt- 100". Note that ***
*** enabling unqualified symbol resolution with network symbol ***
*** server shares in the symbol path may cause the debugger to ***
*** appear to hang for long periods of time when an incorrect ***
*** symbol name is typed or the network symbol server is down. ***
*** ***
*** For some commands to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!_KPRCB ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** Either you specified an unqualified symbol, or your debugger ***
*** doesn't have full symbol information. Unqualified symbol ***
*** resolution is turned off by default. Please either specify a ***
*** fully qualified symbol module!symbolname, or enable resolution ***
*** of unqualified symbols by typing ".symopt- 100". Note that ***
*** enabling unqualified symbol resolution with network symbol ***
*** server shares in the symbol path may cause the debugger to ***
*** appear to hang for long periods of time when an incorrect ***
*** symbol name is typed or the network symbol server is down. ***
*** ***
*** For some commands to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!_KPRCB ***
*** ***
*************************************************************************
ADDITIONAL_DEBUG_TEXT:
Use '!findthebuild' command to search for the target build information.
If the build information is available, run '!findthebuild -s ; .reload' to set symbol path and load symbols.
MODULE_NAME: nt
FAULTING_MODULE: fffff80261e1d000 nt
DEBUG_FLR_IMAGE_TIMESTAMP: 0
EXCEPTION_RECORD: fffff98d9d27edf8 -- (.exr 0xfffff98d9d27edf8)
ExceptionAddress: fffff80261e8f001 (nt+0x0000000000072001)
ExceptionCode: c000001d (Illegal instruction)
ExceptionFlags: 00000000
NumberParameters: 0
CONTEXT: fffff98d9d27e640 -- (.cxr 0xfffff98d9d27e640)
rax=fffff98d9d27f220 rbx=0000000000000003 rcx=fffff98d9d27f220
rdx=fffff98d9d27f220 rsi=0000000000000000 rdi=fffff98d9d27f140
rip=fffff80261e8f001 rsp=fffff98d9d27f038 rbp=0000000000000001
r8=0000007ffffffff8 r9=0000000000000000 r10=0000000fffffffff
r11=0000000000000001 r12=fffff45dc7962800 r13=000000000000000f
r14=fffff98d9d27f220 r15=ffffcb82bc1cb208
iopl=0 nv up ei ng nz na pe nc
cs=0010 ss=0000 ds=002b es=002b fs=0053 gs=002b efl=00010282
nt+0x72001:
fffff802`61e8f001 0fb78170010000 movzx eax,word ptr [rcx+170h] ds:002b:fffff98d`9d27f390=0010
Resetting default scope
DEFAULT_BUCKET_ID: WIN8_DRIVER_FAULT
BUGCHECK_STR: 0x34
CURRENT_IRQL: 0
EXCEPTION_STR: 0x0
LAST_CONTROL_TRANSFER: from fffff8026201b8ad to fffff80261e8f001
STACK_TEXT:
fffff98d`9d27f038 fffff802`6201b8ad : 00000000`00000000 fffff802`6288ca84 00001f80`0010000f 0053002b`002b0010 : nt+0x72001
fffff98d`9d27f040 00000000`00000000 : fffff802`6288ca84 00001f80`0010000f 0053002b`002b0010 00000202`0000002b : nt+0x1fe8ad
FOLLOWUP_IP:
nt+72001
fffff802`61e8f001 0fb78170010000 movzx eax,word ptr [rcx+170h]
SYMBOL_STACK_INDEX: 0
SYMBOL_NAME: nt+72001
FOLLOWUP_NAME: MachineOwner
IMAGE_NAME: ntoskrnl.exe
STACK_COMMAND: .cxr 0xfffff98d9d27e640 ; kb
BUCKET_ID: WRONG_SYMBOLS
Followup: MachineOwner
If using a computer and not a mobile phone, please avoid adding multiple posts while waiting for us to reply to your last, edit your last post to include anything that you wish to add, this will ensure nothing gets overlooked which can sometimes happen if a thread has more than one page.
Weird, you seem to have Fat 32 file system info on the HDD, any idea how this has come to be as Fat 32 is normally associated with USB devices.
Before we suggest anything can you answer the above question for us.
We need to first check the integrity of the HDD and then Windows itself, we can`t use the info in the second dmp file atm because the info is not reliable but fwiw a problem between the AV and Nvidea drivers was partially to blame.
Some info here regarding the error being flagged up in the first dmp.
Debug session time: Fri Dec 21 03:45:31.917 2018 (UTC - 5:00)
System Uptime: 0 days 21:34:21.709
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
CACHE_MANAGER (34)
See the comment for FAT_FILE_SYSTEM (0x23)
Arguments:
Arg1: 0000000000051352
Arg2: fffff98d9d27edf8
Arg3: fffff98d9d27e640
Arg4: fffff80261e8f001
Debugging Details:
------------------
***** Kernel symbols are WRONG. Please fix symbols to do analysis.
*************************************************************************
*** ***
*** ***
*** Either you specified an unqualified symbol, or your debugger ***
*** doesn't have full symbol information. Unqualified symbol ***
*** resolution is turned off by default. Please either specify a ***
*** fully qualified symbol module!symbolname, or enable resolution ***
*** of unqualified symbols by typing ".symopt- 100". Note that ***
*** enabling unqualified symbol resolution with network symbol ***
*** server shares in the symbol path may cause the debugger to ***
*** appear to hang for long periods of time when an incorrect ***
*** symbol name is typed or the network symbol server is down. ***
*** ***
*** For some commands to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!_KPRCB ***
*** ***
*************************************************************************
TRIAGER: Could not open triage file : e:\dump_analysis\program\triage\modclass.ini, error 2
*************************************************************************
*** ***
*** ***
*** Either you specified an unqualified symbol, or your debugger ***
*** doesn't have full symbol information. Unqualified symbol ***
*** resolution is turned off by default. Please either specify a ***
*** fully qualified symbol module!symbolname, or enable resolution ***
*** of unqualified symbols by typing ".symopt- 100". Note that ***
*** enabling unqualified symbol resolution with network symbol ***
*** server shares in the symbol path may cause the debugger to ***
*** appear to hang for long periods of time when an incorrect ***
*** symbol name is typed or the network symbol server is down. ***
*** ***
*** For some commands to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!_KPRCB ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** Either you specified an unqualified symbol, or your debugger ***
*** doesn't have full symbol information. Unqualified symbol ***
*** resolution is turned off by default. Please either specify a ***
*** fully qualified symbol module!symbolname, or enable resolution ***
*** of unqualified symbols by typing ".symopt- 100". Note that ***
*** enabling unqualified symbol resolution with network symbol ***
*** server shares in the symbol path may cause the debugger to ***
*** appear to hang for long periods of time when an incorrect ***
*** symbol name is typed or the network symbol server is down. ***
*** ***
*** For some commands to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!_KPRCB ***
*** ***
*************************************************************************
ADDITIONAL_DEBUG_TEXT:
Use '!findthebuild' command to search for the target build information.
If the build information is available, run '!findthebuild -s ; .reload' to set symbol path and load symbols.
MODULE_NAME: nt
FAULTING_MODULE: fffff80261e1d000 nt
DEBUG_FLR_IMAGE_TIMESTAMP: 0
EXCEPTION_RECORD: fffff98d9d27edf8 -- (.exr 0xfffff98d9d27edf8)
ExceptionAddress: fffff80261e8f001 (nt+0x0000000000072001)
ExceptionCode: c000001d (Illegal instruction)
ExceptionFlags: 00000000
NumberParameters: 0
CONTEXT: fffff98d9d27e640 -- (.cxr 0xfffff98d9d27e640)
rax=fffff98d9d27f220 rbx=0000000000000003 rcx=fffff98d9d27f220
rdx=fffff98d9d27f220 rsi=0000000000000000 rdi=fffff98d9d27f140
rip=fffff80261e8f001 rsp=fffff98d9d27f038 rbp=0000000000000001
r8=0000007ffffffff8 r9=0000000000000000 r10=0000000fffffffff
r11=0000000000000001 r12=fffff45dc7962800 r13=000000000000000f
r14=fffff98d9d27f220 r15=ffffcb82bc1cb208
iopl=0 nv up ei ng nz na pe nc
cs=0010 ss=0000 ds=002b es=002b fs=0053 gs=002b efl=00010282
nt+0x72001:
fffff802`61e8f001 0fb78170010000 movzx eax,word ptr [rcx+170h] ds:002b:fffff98d`9d27f390=0010
Resetting default scope
DEFAULT_BUCKET_ID: WIN8_DRIVER_FAULT
BUGCHECK_STR: 0x34
CURRENT_IRQL: 0
EXCEPTION_STR: 0x0
LAST_CONTROL_TRANSFER: from fffff8026201b8ad to fffff80261e8f001
STACK_TEXT:
fffff98d`9d27f038 fffff802`6201b8ad : 00000000`00000000 fffff802`6288ca84 00001f80`0010000f 0053002b`002b0010 : nt+0x72001
fffff98d`9d27f040 00000000`00000000 : fffff802`6288ca84 00001f80`0010000f 0053002b`002b0010 00000202`0000002b : nt+0x1fe8ad
FOLLOWUP_IP:
nt+72001
fffff802`61e8f001 0fb78170010000 movzx eax,word ptr [rcx+170h]
SYMBOL_STACK_INDEX: 0
SYMBOL_NAME: nt+72001
FOLLOWUP_NAME: MachineOwner
IMAGE_NAME: ntoskrnl.exe
STACK_COMMAND: .cxr 0xfffff98d9d27e640 ; kb
BUCKET_ID: WRONG_SYMBOLS
Followup: MachineOwner
Not entirely sure 'how to answer your question' / 'if this helps' but I did kinda recently transfer my OS onto an ssd and I remember having a couple problems doing so, and it was something about an OS couldn't be moved from one drive to the other for some reason about it being a different type (possibly fat32 vs ntfs) and I had to format a hdd to get it working. Also the hard drives are quite old.
Edit: Pc went and crashed again
Edit 2: Computer has successfully crashed more than 6 times in the past hour, but only one was a bsod (The other ones were marked as kernel power 41 in event viewer, may have just lost power?)
Edit: Pc went and crashed again
Edit 2: Computer has successfully crashed more than 6 times in the past hour, but only one was a bsod (The other ones were marked as kernel power 41 in event viewer, may have just lost power?)
Last edited:
A somewhat cryptic answer, can you explain what you mean by "kinda recently transfer my OS onto an ssd" how was this done.
The two dmp files are of no use but they do suggest serious problems with Windows.
I attempted to use a program called EaseUS partition master to transfer windows to my ssd, however something I did with the transfer I did incorrectly which forced me to reinstall windows via a usb (got the software from the microsoft webpage). Also what kind of serious problems with windows do you mean?
The correct term to have used would have been either clone or migrate and not transfer, not being pedantic but you would be surprised at how many people do not know that you cannot drag and drop/transfer Windows or any other program for that matter from one drive to another.
The present version of Windows that you are running is corrupt, this could be as a result of a bad download, it not installing properly or the storage device that Windows is on has issues.
What device are you presently running Windows from.
The present version of Windows that you are running is corrupt, this could be as a result of a bad download, it not installing properly or the storage device that Windows is on has issues.
What device are you presently running Windows from.
A good choice of SSD so flaky thumbdrive or download the more likely.
I would suggest that you start afresh including downloading a new ISO, preferably to another 8GB or above thumbdrive if you have one, it would also be of benefit if you had the drivers for the MB on disk or a thumbdrive and when the time comes to install Windows you install it on its own partition on the SSD, 200GB if just for Windows 10 or 250GB if for Windows 10 and any applications.
I would suggest that you start afresh including downloading a new ISO, preferably to another 8GB or above thumbdrive if you have one, it would also be of benefit if you had the drivers for the MB on disk or a thumbdrive and when the time comes to install Windows you install it on its own partition on the SSD, 200GB if just for Windows 10 or 250GB if for Windows 10 and any applications.
- Status