Randomly BSOD during reboot test

The blue screen issue with bugcheck code 0xEF, after analyzing the dump, it looks like the faulting process has been corrupted by someone, but i have no idea how to further narrow down the suspected range.
The analysis progress is written in following website, any idea would be helpful to me.
Thanks in advanced.
http://swdbg.blogspot.tw/2016/10/criticalprocessdied-ef-ux530ux-ramdomly.html

Do you have a driver loaded on this system? If yes:

  1. What does the driver do?

  2. Is this a clean install of the OS or do you have a bunch of other things
    installed?

  3. Have you run with Driver Verifier?

-scott
OSR
@OSRDrivers

wrote in message news:xxxxx@ntdev…

The blue screen issue with bugcheck code 0xEF, after analyzing the dump, it
looks like the faulting process has been corrupted by someone, but i have no
idea how to further narrow down the suspected range.
The analysis progress is written in following website, any idea would be
helpful to me.
Thanks in advanced.
http://swdbg.blogspot.tw/2016/10/criticalprocessdied-ef-ux530ux-ramdomly.html

  1. No, I don’t have my own driver loaded on the system.

  2. No, it’s not a clean install of the OS, there’s a bunch of 3rd party’s products installed on the system(Customized OS image).

  3. No

Is that helpful to run with Verifier for this kind of issue?


?H???: xxxxx@lists.osr.com ?N?? Scott Noone
?H???: 2016?~10??20?? ?U?? 08:27
???: Windows System Software Devs Interest List
?D??: Re:[ntdev] Randomly BSOD during reboot test

Do you have a driver loaded on this system? If yes:

1. What does the driver do?

2. Is this a clean install of the OS or do you have a bunch of other things
installed?

3. Have you run with Driver Verifier?

-scott
OSR
@OSRDrivers

wrote in message news:xxxxx@ntdev…

The blue screen issue with bugcheck code 0xEF, after analyzing the dump, it
looks like the faulting process has been corrupted by someone, but i have no
idea how to further narrow down the suspected range.
The analysis progress is written in following website, any idea would be
helpful to me.
Thanks in advanced.
http://swdbg.blogspot.tw/2016/10/criticalprocessdied-ef-ux530ux-ramdomly.html
CRITICAL_PROCESS_DIED (ef) UX530UX ramdomly blue screen during S3 stress test.http:
swdbg.blogspot.tw
Our new project encounters a ramdomly system crash during S3 stress test, the bugcheck code is CRITICAL_PROCESS_DIED (ef) which means some…


NTDEV is sponsored by OSR

Visit the list online at: http:
OSR Online NTDEV Listhttp:
www.osronline.com
OSR Online is the homepage for Windows driver writers. The NTDEV, NTFSD, and NTTALK lists are world-wide peer support forums administered by OSR.

MONTHLY seminars on crash dump analysis, WDF, Windows internals and software drivers!
Details at http:
[https://www.osr.com/wp-content/uploads/seminar_map4_big.png]http:

Windows Driver Development Training from OSRhttp:
www.osr.com
Learn Windows driver development, file system development, and debugging from developer/instructors with real-world experience. Seminars taught world-wide.

To unsubscribe, visit the List Server section of OSR Online at http:
ListServer/Forumhttp:
www.osronline.com
List Rules and Etiquette. You get a list of the list rules when you join. But nobody seems to read those notes, so we’re posting some of the most important rules here:</http:></http:></http:></http:></http:></http:></http:></http:>

Verifier can always be useful. Corrupted user mode state can be as a result
of:

  1. Invalid pointer dereferences in a driver. The driver might scribble over
    a user address or use a user address in the wrong process context

  2. DMA scribbles

Verifier might catch these at the point of corruption as opposed to having
to wait until later. Of course, when you have random corruption it’s
difficult to know which drivers to enable Verifier for. I generally start
with any third party drivers and go from there (run Verifier.exe, select
driver names from a list, and sort by Provider).

Lastly, if you can reproduce this don’t underestimate the effectiveness of
selectively disabling things and retrying. It’s not necessarily glamorous or
clever, but can be effective.

-scott
OSR
@OSRDrivers

“dl CU” wrote in message news:xxxxx@ntdev…

1. No, I don’t have my own driver loaded on the system.

2. No, it’s not a clean install of the OS, there’s a bunch of 3rd party’s
products installed on the system(Customized OS image).

3. No

Is that helpful to run with Verifier for this kind of issue?

±H¥óªÌ: xxxxx@lists.osr.com
¥Nªí Scott Noone
±H¥ó¤é´Á: 2016¦~10¤ë20¤é ¤U¤È 08:27
¦¬¥óªÌ: Windows System Software Devs Interest List
¥D¦®: Re:[ntdev] Randomly BSOD during reboot test

Do you have a driver loaded on this system? If yes:

1. What does the driver do?

2. Is this a clean install of the OS or do you have a bunch of other things
installed?

3. Have you run with Driver Verifier?

-scott
OSR
@OSRDrivers

wrote in message news:xxxxx@ntdev…

The blue screen issue with bugcheck code 0xEF, after analyzing the dump, it
looks like the faulting process has been corrupted by someone, but i have no
idea how to further narrow down the suspected range.
The analysis progress is written in following website, any idea would be
helpful to me.
Thanks in advanced.
http://swdbg.blogspot.tw/2016/10/criticalprocessdied-ef-ux530ux-ramdomly.html

CRITICAL_PROCESS_DIED (ef) UX530UX ramdomly blue screen during S3 stress
test.
swdbg.blogspot.tw
Our new project encounters a ramdomly system crash during S3 stress test,
the bugcheck code is CRITICAL_PROCESS_DIED (ef) which means some…


NTDEV is sponsored by OSR

Visit the list online at:
http:

OSR Online NTDEV List
www.osronline.com
OSR Online is the homepage for Windows driver writers. The NTDEV, NTFSD, and
NTTALK lists are world-wide peer support forums administered by OSR.

MONTHLY seminars on crash dump analysis, WDF, Windows internals and software
drivers!
Details at http:

Windows Driver Development Training from OSR
www.osr.com
Learn Windows driver development, file system development, and debugging
from developer/instructors with real-world experience. Seminars taught
world-wide.

To unsubscribe, visit the List Server section of OSR Online at
http:

ListServer/Forum
www.osronline.com
List Rules and Etiquette. You get a list of the list rules when you join.
But nobody seems to read those notes, so we’re posting some of the most
important rules here:</http:></http:></http:>