Any updates for us @Brandon Byrnes? After 72 hours I will assume your issue is solved unless I hear back from you
Windows 10 Blue Screen DRIVER_IRQL_NOT_LESS_OR_EQUAL
Collapse
X
-
Originally posted by jmarketAny updates for us @Brandon Byrnes? After 72 hours I will assume your issue is solved unless I hear back from youComment
-
Originally posted by jmarketThat is correct. Have you had more BSODโs since my last message?Comment
-
Originally posted by jmarketThat is correct. Have you had more BSODโs since my last message?Comment
-
Much appreciated for the dump file
The BSODs you are experiencing are indeed caused by one driver, the touchpad driver.
Before we go futher, what make and model is the laptop in question? Every laptop uses a different driver for their hardwareComment
-
Originally posted by jmarketMuch appreciated for the dump file
The BSODs you are experiencing are indeed caused by one driver, the touchpad driver.
Before we go futher, what make and model is the laptop in question? Every laptop uses a different driver for their hardwareComment
-
Originally posted by jmarketTry the driver listed hereComment
-
Okay, now iโm getting ******, I just had another BSOD this time its related to TCPIP, here is the dump file, please help. I donโt know whats going on with this D*** laptop. Is there a utility you could recommend that I can run that would give you an idea of whats going on with this thing? Also isnโt Windows supposed to save all minidump files, This was the only one in the folder, the other one isnโt there anymore.Comment
-
Hmm that is very weird indeed.
This may be a bigger problem than we think. Let me have you run a tool to check your hard disk.
[ul]
[li]Click on the Start button and in the search box, type Command Prompt[/li][li]When you see Command Prompt on the list, right-click on it and select Run as administrator[/li][li]When command prompt opens, copy and paste the following command into it, press Enter.[/li]
[ICODE]sfc /scannow[/ICODE]
[li]Wait for this to finish before you continue[/li][li]Copy and paste the following command, press Enter.[/li]
[ICODE]findstr /c:"[SR]" %windir%\logs\cbs\cbs.log > %userprofile%\Desktop\sfc.txt[/ICODE]
[/ul]
That will create sfc.txt on your Desktop. Please attach sfc.txt to your next post:
[ul]
[li]Open Reply window. Click โMore Reply Optionsโ.[/li][li]Go to the end of your text (if any).[/li][li]Under โAttach Filesโ click โChoose Files..โ[/li][li]For โFile nameโ paste this: %userprofile%\Desktop\sfc.txt[/li][li]Click the โAdd to Postโ link which will appear on the right when the file has been uploaded.[/li][li]Click โAdd Replyโ.[/li][/ul]
After the above instructions are complete, please do the below again for me. I will have to do deeper digging into this.
Please download the Sysnative BSOD Dump + System File Collection App - save to Documents folder.
Run the app - Double-click on the downloaded EXE file
Output = new folder created in Documents + a zipped version โ SysnativeFileCollectionApp folder + SysnativeFileCollectionApp.zip.
Please note that the app averages ~3 minutes to run on most systems; other systems - it my take as long as 10-15 minutes to run. Please be patient.
Also note: The app auto-zips the SysnativeFileCollectionApp output folder. It is located in your Documents folder.
Windows Explorer should open and highlight the zipped folder
Please attach the SysnativeFileCollectionApp.zip to your post and await further instructionsComment
-
Originally posted by jmarketHmm that is very weird indeed.
This may be a bigger problem than we think. Let me have you run a tool to check your hard disk.
[ul]
[li]Click on the Start button and in the search box, type Command Prompt[/li][li]When you see Command Prompt on the list, right-click on it and select Run as administrator[/li][li]When command prompt opens, copy and paste the following command into it, press Enter.[/li]
[ICODE]sfc /scannow[/ICODE]
[li]Wait for this to finish before you continue[/li][li]Copy and paste the following command, press Enter.[/li]
[ICODE]findstr /c:"[SR]" %windir%\logs\cbs\cbs.log > %userprofile%\Desktop\sfc.txt[/ICODE]
[/ul]
That will create sfc.txt on your Desktop. Please attach sfc.txt to your next post:
[ul]
[li]Open Reply window. Click โMore Reply Optionsโ.[/li][li]Go to the end of your text (if any).[/li][li]Under โAttach Filesโ click โChoose Files..โ[/li][li]For โFile nameโ paste this: %userprofile%\Desktop\sfc.txt[/li][li]Click the โAdd to Postโ link which will appear on the right when the file has been uploaded.[/li][li]Click โAdd Replyโ.[/li][/ul]
After the above instructions are complete, please do the below again for me. I will have to do deeper digging into this.
Please download the Sysnative BSOD Dump + System File Collection App - save to Documents folder.
Run the app - Double-click on the downloaded EXE file
Output = new folder created in Documents + a zipped version โ SysnativeFileCollectionApp folder + SysnativeFileCollectionApp.zip.
Please note that the app averages ~3 minutes to run on most systems; other systems - it my take as long as 10-15 minutes to run. Please be patient.
Also note: The app auto-zips the SysnativeFileCollectionApp output folder. It is located in your Documents folder.
Windows Explorer should open and highlight the zipped folder
Please attach the SysnativeFileCollectionApp.zip to your post and await further instructionsComment
-
I got yet another BSOD last night, this one was agin related to the touchpad, so Iโll attach the minidump file. Iโm wondering if the issue is my SSD, becuase I wasnโt getting all of these BSODs until after I installed my SSD. I ordered one off of Amazon it is a WD Blue NAND SATA SSD M.2 2280. Itโs 250 GB.
Okay so I tried to find the minidump file but itโs not there, Iโm assuming thatโs because Windows said it was collecting information but it was stuck on 0% for about 10 minutes, so I just did a hard restart so Iโm assuming since it didnโt collect any info, it didnโt create a minidump file. But it was the same BSOD that I was getting before related to the touchpad.Comment
-
Comment