BSOD UNEXPECTED_KERNEL_MODE_TRAP 0x0000007f after graphics driver

[x BlueRobot]

Boot into Safe Mode, the Intel driver won't be running, however, I'm wondering if it will still appear within the list for selecting drivers from.

 

[NeoJediX]

Run u talking about the Intel driver coming up on the list of driver verification? If so, no. I manually added it as well as adding monitor.sys, which also did not show up on the verification list.

 

[x BlueRobot]

Okay, are you able to manually add the driver, and then boot into Windows normally?

 

[NeoJediX]

I can manually add to list and boot normally if Intel is disabled. If Intel driver is enabled, I don't even get to BSOD. Soon after the status bar appears for a few seconds, the screen goes blank and system stops loading. Have to reboot holding down the power button then restart in safe mode.

 

[Arc]

NeoJediX, I am believing that the display adapter (onboard) is corrupted. Within this installation, it behaved the same irrespective of the driver versions.

But you may go for a clean reinstall and see if it is behaving the same or not before deciding finally.

 

[NeoJediX]

Arc, I'm not sure you read this whole thread, but I've already done a clean reinstall of Win7. And if it's a corrupt onboard graphics driver, I would expect the same problem on other OS. Yet, it works fine on WinXP and Mint (linux). There is something strange going on between Win7 and Intel graphics driver.

 

[Arc]

I read the entire thread many a times. Not getting any idea other than a corrupt display adapter. Windows 7 needs much graphics capacity/ability than XP/Mint, even if it is starter.

Its over weeks you are getting the same issue, with all the driver version you tried. And that issue is unique to you. Nobody else reported about such an error. Which is able to isolate the issue as anything to be personalized to you. Only hardware can be that thing.

It is display that is failing here. The display here is onboard. A motherboard component. So the problem is with the motherboard. At the same time, it is starter. Available as OEM only. OEM licenses are tagged with motherboard. If the board is gone, the license is gone, too.

So, the best way to use the warranty. A failing motherboard is subject to full replacement.

Why there is no problem with XP or Mint? As they dont need so dense graphics like Windows 7 (even a starter). Gradually they will also start to cause problems, but the machine will run out of warranty then. For OEM, ifs too bad.

It was my only intention to post in your thread is to make you cautious about it. If you cannot take it rightly, my earnest apologies. Unsubscribing from your thread, as the further discussions may attract me to post again.

If it gets solved, please let me know. I am always open-minded to learn. If I am wrong, I will be happy, from within.

 

[NeoJediX]

Arc, thanks for the suggestion. Ultimately, u might be right about the onboard graphics on the mb...I'm open to that possibility. But I'm also curious to see if there are other possible workarounds since I'm not so sure I qualify for a mb replacement. Afterall, I can just go ahead and use WinXP or Mint, but I'm also determined see if I can find a resolution using Win7 (e.g. is there a way to make the driver use less resource or not to divide by zero etc.) I'll keep u posted if we do find a solution. Thanks again.

 

[x BlueRobot]

The only method to truly stop a driver from causing problems, is to have access to the driver's source code and then rewrite the code for the drivers, which are most likely to be written within C or C++. You would have to work for Intel and be part of their development team to have such access.

Linux Mint even requires less resources than Windows XP.