BSOD - is it drivers?

baaablacksheep

Honorable
Jan 8, 2014
15
0
10,520
I have an HP compaq pro 6300 MT, win 7 64-bit that is getting BSOD's during the startup process. It will start, begin configuring updates, fail, start reverting then itll toss the bluescreen. Im wondering if its driver related and if so, could someone possibly point at which component is causing it? Here is the info on it:

==================================================
Dump File : 111915-22276-01.dmp
Crash Time : 11/19/2015 12:04:31 PM
Bug Check String : IRQL_NOT_LESS_OR_EQUAL
Bug Check Code : 0x0000000a
Parameter 1 : 00000000`00000000
Parameter 2 : 00000000`00000002
Parameter 3 : 00000000`00000001
Parameter 4 : fffff800`0389296f
Caused By Driver : ntoskrnl.exe
Caused By Address : ntoskrnl.exe+748c0
File Description : NT Kernel & System
Product Name : Microsoft® Windows® Operating System
Company : Microsoft Corporation
File Version : 6.1.7601.18869 (win7sp1_gdr.150525-0603)
Processor : x64
Crash Address : ntoskrnl.exe+748c0
Stack Address 1 :
Stack Address 2 :
Stack Address 3 :
Computer Name :
Full Path : C:\Windows\Minidump\111915-22276-01.dmp
Processors Count : 4
Major Version : 15
Minor Version : 7601
Dump File Size : 280,880
Dump File Time : 11/19/2015 12:05:31 PM
==================================================

Any info that could be provided on this error would be much appreciated!

Thanks!
 
Hello... Avoid any hardware updates from Microsoft... A typical windows 7 Sp1 install will not need any updates... Not all updates may be needed for your hardware and OS, for your PC needs.

1) If a re-install is impossible... you will need "safe mode" or Windows manual boot device control skills.
2) Pickup a small black Friday ssd/hd and install new OS on it for further testing with your hardware... and keeping your existing files/data intact.
 
This PC was already wiped about 3-6 months ago with similar issues. I dont think reinstalling the OS is the right answer. Im going to try and update all of the drivers while in safe mode but if anyone know what component it may be based on the BSOD info that would really be a huge time saver... Thank you for answering tho!