Weird BSOD Issue
I work for a school district.
Teacher A has a Windows 7 HP laptop on a domain; he's had it for around a year.
He submitted a ticket with me recently: when he saved to his personal storage drive on AD, he got a BSOD. I stopped by to take a look and saw it twice. Thinking it might be a malware issue, I issued him a temp laptop to use until we fixed this one. (Same hardware as his, freshly re-imaged).
Yesterday, he updated the ticket. Now, he gets a BSOD when he signed into Chrome. I was able to see it in action myself, both trying to sign into Chrome and just having it sit there.
Thinking that maybe this is a bad laptop, I issued him a 3rd one. Today; same issue.
The BSOD is a "A driver has overrun a stack-based buffer" "might be malicious" window. I tried setting the minidumps, but they aren't be written for some reason.
This is the only user that's reporting this issue, and other staff members have use fresh laptops with no problems. This has me stumped. Any ideas?
Thanks.
Teacher A has a Windows 7 HP laptop on a domain; he's had it for around a year.
He submitted a ticket with me recently: when he saved to his personal storage drive on AD, he got a BSOD. I stopped by to take a look and saw it twice. Thinking it might be a malware issue, I issued him a temp laptop to use until we fixed this one. (Same hardware as his, freshly re-imaged).
Yesterday, he updated the ticket. Now, he gets a BSOD when he signed into Chrome. I was able to see it in action myself, both trying to sign into Chrome and just having it sit there.
Thinking that maybe this is a bad laptop, I issued him a 3rd one. Today; same issue.
The BSOD is a "A driver has overrun a stack-based buffer" "might be malicious" window. I tried setting the minidumps, but they aren't be written for some reason.
This is the only user that's reporting this issue, and other staff members have use fresh laptops with no problems. This has me stumped. Any ideas?
Thanks.
Comments
-
kohr-ah
Member Posts: 1,277
Get the **** reader from Microsoft.
run the program, load the **** file(the event viewer will tell you where it is saved)
then run
!analyze -v
in the debugger. It usually will tell you exactly what driver is causing the issue. -
TechGuy215
Member Posts: 404 ■■■■□□□□□□
Download and run this:
BlueScreenView - Free download and software reviews - CNET Download.com
A nice little utility that collects all of the BSODS, along with the stopcodes and bugcheckstrings.
You can then check the MSKB for details on those errors, or run them against the utility below:
Windows Error Lookup Tool Free Download
I've had luck in the past using these utilities on BSODs that I just couldn't figure out.
Also, is the Teacher hooking up any peripheral devices to the laptop?* Currently pursuing: PhD: Information Security and Information Assurance
* Certifications: CISSP, CEH, CHFI, CCNA:Sec, CCNA:R&S, CWNA, ITILv3, VCA-DCV, LPIC-1, A+, Network+, Security+, Linux+, Project+, and many more...
* Degrees: MSc: Cybersecurity and Information Assurance; BSc: Information Technology - Security; AAS: IT Network Systems Administration -
Polynomial
Member Posts: 365
This is the best BSOD tool IMO: Resplendence Software - WhoCrashed, automatic crash **** analyzer -
101010
Member Posts: 94 ■■□□□□□□□□
I tried setting the minidumps, but they aren't be written for some reason.
Any chance you have a very small page file, or have virtual memory turned off completely? A pagefile is required for a memory **** to be created, and if you want gather a full memory **** you will need a pagefile that is at least as large as the system memory (plus 1MB for the header).
This page will detail the crash **** process and requirements:
Understanding Crash **** Files - Ask the Performance Team - Site Home - TechNet Blogs2017 Goals:
[x] GCIH
"Well if you're going to have delusions of grandeur, may as well go for the really satisfying ones." - Marcus, Babylon 5