Share via

BSOD Bugcheck code: 0x4A

Anonymous
2015-06-11T11:22:12+00:00

i found a thread who might have the same issue (http://answers.microsoft.com/en-us/windows/wiki/windows\_other-system/blue-screen-of-death-bsod/1939df35-283f-4830-a4dd-e95ee5d8669d)

since i made the dmp and msino i started my own one and hoping to get help. I'm also using bitdefender but it is the up to date version of 2015.

Anyways i would be glad if you could tell me what is causing this issue.

On Thu 11.06.2015 10:36:45 GMT your computer crashed

crash dump file: C:\Windows\Minidump\061115-81401-01.dmp

This was probably caused by the following module: ntoskrnl.exe (nt+0x748C0)

Bugcheck code: 0x4A (0x7723DC2A, 0x2, 0x0, 0xFFFFF88002C8CCA0)

Error: IRQL_GT_ZERO_AT_SYSTEM_SERVICE

file path: C:\Windows\system32\ntoskrnl.exe

product: Microsoft® Windows® Operating System

company: Microsoft Corporation

description: NT Kernel & System

dmp + msinfo:

https://onedrive.live.com/redir?resid=fee1caa9253a58cb!108&authkey=!ADZNM7YKJYVxt\_8&ithint=file%2crar

Thanks

Windows for home | Previous Windows versions | Performance and system failures

Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.

0 comments No comments

3 answers

Sort by: Most helpful
  1. Anonymous
    2015-06-11T16:32:57+00:00

    i forgot to mention that i can access windows after restarting and

    everything seems to work out quite fine. I have this BSOD maybe once a

    month. Do i stil have to run that tese in safe mode or can i just do

    under normal running conditions or does the BSOD appear again when

    drivers get tested?

    Was this answer helpful?

    1 person found this answer helpful.
    0 comments No comments
  2. Anonymous
    2015-06-11T23:36:13+00:00

    Verifier does not need to be run in safe mode.  It is designed to crash when the mis behaving driver is loaded

    Was this answer helpful?

    0 comments No comments
  3. Anonymous
    2015-06-11T12:04:21+00:00

    **These crashes were related to memory corruption (probably caused by a driver).**Please run these two tests to verify your memory and find which driver is causing the problem.  Please run verifier first.  You do not need to run memtest yet unless verifier does not find the cause, or you want to.

    If you are over-clocking anything reset to default before running these tests.

    In other words STOP!!!  If you do not know what this means you probably are not



    1-Driver verifier (for complete directions see our wiki here)

    **2-Memtest. (**You can read more about running memtest here)


    Was this answer helpful?

    0 comments No comments