Showing results for 
Search instead for 
Did you mean: 
New member
1 0 0 0
Message 1 of 2
Flag Post

Permanent Blue Screen (BSOD) Error on HP Probook 430 G5

HP Recommended
Probook 430 G5
Microsoft Windows 10 (64-bit)

We are experiencing Blue Screen Error since last month and thus performed the following steps:


1. Performed thorough system check in cmd (sfc /scannow). No issues found. All good.


(Contacted hp support via telephone & E-mail, were told to perform following)


2. Performed diagnostics test both in BIOS as well as in Windows 10. No issues found. All good.


3. Downloaded actual HP Firmware Pack. 


4. Downloaded HP SoftPaq Download Manager (SDM) and installed all  required updates. Blue Screen issue remains.


5.  HP technician visited with new motherboard and replaced it with the existing one. Performed all checks and it looked OK.


6. Now after 1 week of motherboard replacement, start having the system freeze (BSOD) issue., i.e. SYSTEM_SERVICE_EXCEPTION.


PS: My company bought 2 new laptops and my colleague has the same model, Probook 430 G5 , he also got the same blue screen problem yesterday. We also tried installing new Windows' images both in German and English languages. But, the problem persists, unfortunately.


Please help us what to do next!


Kind regards,

Imran Mehr

Level 6
Level 6
139 139 18 36
Message 2 of 2
Flag Post
HP Recommended


The stop code indicates that executing code had an exception and the thread that was below it, is a system thread.

The !analyze debug extension displays information about the bug check and can be very helpful in determining the root cause.

For more information see the following topics:

Crash dump analysis using the Windows debuggers (WinDbg)

Analyzing a Kernel-Mode Dump File with WinDbg

Using the !analyze Extension and !analyze

In the past, this error has been linked to excessive paged pool usage and may occur due to user-mode graphics drivers crossing over and passing bad data to the kernel code. If you suspect this is the case, use the pool options in driver verifier to gather additional information.


To debug this problem: Use the .cxr (Display Context Record) command with Parameter 3, and then use kb (Display Stack Backtrace). You can also set a breakpoint in the code leading up to this stop code and attempt to single step forward into the faulting code.

For general troubleshooting of Windows bug check codes, follow these suggestions:

  • If you recently added hardware to the system, try removing or replacing it. Or check with the manufacturer to see if any patches are available.

  • If new device drivers or system services have been added recently, try removing or updating them. Try to determine what changed in the system that caused the new bug check code to appear.

  • Look in Device Manager to see if any devices are marked with the exclamation point (!). Review the events log displayed in driver properties for any faulting driver. Try updating the related driver.

  • Check the System Log in Event Viewer for additional error messages that might help pinpoint the device or driver that is causing the error. For more information, see Open Event Viewer. Look for critical errors in the system log that occurred in the same time window as the blue screen.

  • For additional general troubleshooting information, see Blue Screen Data.

0 Kudos
Warning Be alert for scammers posting fake support phone numbers and/or email addresses on the community. If you think you have received a fake HP Support message, please report it to us by clicking on "Flag Post".
† The opinions expressed above are the personal opinions of the authors, not of HP. By using this site, you accept the Terms of Use and Rules of Participation