- Joined
- Aug 8, 2010
- Messages
- 545 (0.11/day)
- Location
- TX
System Name | MSI GF63 Thin |
---|---|
Processor | Intel® Core™ i5-10300H @4.50GHz |
Motherboard | MSI GF63 Thin System Board |
Cooling | MSI GF63 Thin Stock Cooling |
Memory | 8GB (1x 8GB) Hynix DDR4 2666MHz |
Video Card(s) | NVIDIA GeForce GTX 1650 Max-Q 4GB GDDR6 @1740MHz |
Storage | KIOXIA 256GB NVMe SSD |
Display(s) | MSI Optix G24C165Hz 1ms |
Software | Windows 10 Pro 64bit |
Hello TPU!
Yesterday when I booted up my Laptop (specs on the side), I got a BSOD giving me no process or any other information.
IT's kinda like a luck game.
The BSOD only happens on boot up and only every 2nd or 3rd time....
I have no idea, what would possibly cause this.
I checked the advanced HDD SMART status and also the RAM with the PC Doctor.
No errors found....drivers should all be up2date.
Here are error info and dump file:
Here the DUMP FILE INFO
Yesterday when I booted up my Laptop (specs on the side), I got a BSOD giving me no process or any other information.
IT's kinda like a luck game.
The BSOD only happens on boot up and only every 2nd or 3rd time....
I have no idea, what would possibly cause this.
I checked the advanced HDD SMART status and also the RAM with the PC Doctor.
No errors found....drivers should all be up2date.
Here are error info and dump file:
Problem signature:
Problem Event Name: BlueScreen
OS Version: 6.1.7601.2.1.0.768.3
Locale ID: 1033
Additional information about the problem:
BCCode: 1000007e
BCP1: C0000005
BCP2: 82A5D4A4
BCP3: 80786888
BCP4: 80786460
OS Version: 6_1_7601
Service Pack: 1_0
Product: 768_1
Here the DUMP FILE INFO
Windows 7 Kernel Version 7601 (Service Pack 1) MP (2 procs) Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 7601.17790.x86fre.win7sp1_gdr.120305-1505
Machine Name:
Kernel base = 0x8283a000 PsLoadedModuleList = 0x829834d0
Debug session time: Thu May 3 11:52:19.429 2012 (UTC - 4:00)
System Uptime: 0 days 0:00:07.410
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M (1000007e)
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.
Some common problems are exception code 0x80000003. This means a hard
coded breakpoint or assertion was hit, but this system was booted
/NODEBUG. This is not supposed to happen as developers should never have
hardcoded breakpoints in retail code, but ...
If this happens, make sure a debugger gets connected, and the
system is booted /DEBUG. This will let us see why this breakpoint is
happening.
Arguments:
Arg1: c0000005, The exception code that was not handled
Arg2: 82a5d4a4, The address that the exception occurred at
Arg3: 80786888, Exception Record Address
Arg4: 80786460, Context Record Address
Debugging Details:
------------------
EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at "0x%08lx" referenced memory at "0x%08lx". The memory could not be "%s".
FAULTING_IP:
nt!ObpLookupDirectoryEntry+2b
82a5d4a4 0fb702 movzx eax,word ptr [edx]
EXCEPTION_RECORD: 80786888 -- (.exr 0xffffffff80786888)
ExceptionAddress: 82a5d4a4 (nt!ObpLookupDirectoryEntry+0x0000002b)
ExceptionCode: c0000005 (Access violation)
ExceptionFlags: 00000000
NumberParameters: 2
Parameter[0]: 00000000
Parameter[1]: 00002680
Attempt to read from address 00002680
CONTEXT: 80786460 -- (.cxr 0xffffffff80786460)
eax=80786900 ebx=00000000 ecx=85f65494 edx=00002680 esi=80786988 edi=00000007
eip=82a5d4a4 esp=80786950 ebp=80786960 iopl=0 nv up ei pl nz na po nc
cs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000 efl=00010202
nt!ObpLookupDirectoryEntry+0x2b:
82a5d4a4 0fb702 movzx eax,word ptr [edx] ds:0023:00002680=????
Resetting default scope
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
PROCESS_NAME: System
CURRENT_IRQL: 0
ERROR_CODE: (NTSTATUS) 0xc0000005 - The instruction at "0x%08lx" referenced memory at "0x%08lx". The memory could not be "%s".
EXCEPTION_PARAMETER1: 00000000
EXCEPTION_PARAMETER2: 00002680
READ_ADDRESS: GetPointerFromAddress: unable to read from 829a3848
Unable to read MiSystemVaType memory at 82982e20
00002680
FOLLOWUP_IP:
nt!ObpLookupDirectoryEntry+2b
82a5d4a4 0fb702 movzx eax,word ptr [edx]
BUGCHECK_STR: 0x7E
LAST_CONTROL_TRANSFER: from 82a5d382 to 82a5d4a4
STACK_TEXT:
80786960 82a5d382 8ba5b1f0 85f65494 00000000 nt!ObpLookupDirectoryEntry+0x2b
8078699c 82a45cf7 85f654a8 85f49000 85f654b8 nt!ObpDeleteNameCheck+0xfb
807869b4 829fd49e 85f654b8 00000000 85e5caac nt!ObMakeTemporaryObject+0x93
80786b94 82beb4fc 00000001 00000000 80786bcc nt!IopLoadDriver+0x921
80786be0 82beb19f 00000007 8080a6c0 00000000 nt!IopInitializeSystemDrivers+0x163
80786c64 82bef1b1 0080a6c0 84f44ac0 84f44750 nt!IoInitSystem+0x6de
80786d48 829c64c6 80786d90 82a43056 8080a6c0 nt!Phase1InitializationDiscard+0xd01
80786d50 82a43056 8080a6c0 d5e7e20e 00000000 nt!Phase1Initialization+0xd
80786d90 828eb219 829c64b9 8080a6c0 00000000 nt!PspSystemThreadStartup+0x9e
00000000 00000000 00000000 00000000 00000000 nt!KiThreadStartup+0x19
SYMBOL_STACK_INDEX: 0
SYMBOL_NAME: nt!ObpLookupDirectoryEntry+2b
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: nt
IMAGE_NAME: ntkrpamp.exe
DEBUG_FLR_IMAGE_TIMESTAMP: 4f5583be
STACK_COMMAND: .cxr 0xffffffff80786460 ; kb
FAILURE_BUCKET_ID: 0x7E_nt!ObpLookupDirectoryEntry+2b
BUCKET_ID: 0x7E_nt!ObpLookupDirectoryEntry+2b
Followup: MachineOwner
---------