Overclock.net › Forums › Software, Programming and Coding › Operating Systems › Windows › Crash Analysis and Debugging › A Year of BSODs (mostly ntoskrnl.exe)
New Posts  All Forums:Forum Nav:

A Year of BSODs (mostly ntoskrnl.exe)

post #1 of 40
Thread Starter 
Hey folks,

I'm hoping you all can help me solve this confounding BSOD problem I'm having. For the last year, I've had recurring blue screens that Windows reports are mostly triggered by ntoskrnl.exe. You can see what I mean here:



My Troubleshooting Steps
1) Multiple virus scans (both in OS & at boot time)
2) Multiple RAM tests (Using Hirens Boot CD)
3) Multiple HDD tests (Both Windows and 3rd Party)

None of these tests came back with remarkable results.

These BSODs can arise either during very high load or when the PC is just sitting idle. I've woken the PC up from sleep many times, only to see it's "recovered from a serious error."

I'm very new to these forums, but I've tried to follow the BSOD posting instructions to the letter. I've attached my file collection and PERFMON report.

System Specs
OS: Windows 7 Home Premium, 64-bit (Retail)
Age of System: > 2 years
Age of OS install: Installed on 12/9/2011 (1 year)

CPU: Intel Core i5-2500K CPU @ 3.30 GHz
Video Card: EVGA GeForce GTS450
Motherboard: ASUS Sabertooth P67
Power supply: Corsair TX 650W

System Manufacturer: None (Home-built)

Please let me know if there's anything I've missed. Thank you all in advance!

BSODs.zip 3226k .zip file
post #2 of 40
Do you use Daemon Tools? That is known to cause many BSODs. If so, try closing that.

In my experience ntoskrnl BSODs have always been driver-related. Try to update drivers for every little thing you can think of such as Gigabit ethernet, audio, video, etc. I've used this tool before to take care of the problem, maybe it'll work for you. http://www.techsupportforum.com/forums/showpost.php?p=2670109
Gaming Rig
(20 items)
 
  
CPUMotherboardGraphicsRAM
Intel 2500k, 4.6GHz, 1.304v ASRock P67 Extreme4 Gen3 2x Sapphire HD7970 OC with Boost, 1150 MHz/1550... 2x4GB DDR3 1600 Corsair Vengeance 
Hard DriveHard DriveHard DriveOptical Drive
Samsung 840 Pro Samsung 750GB HD753LJ Samsung F3 ASUS 24X DVD Combo Drive 
CoolingOSMonitorKeyboard
Noctua DH14 Windows 8 Professional x64 Crossover 27Q 27" IPS LED, 2560x1440 Logitech G11 
PowerCaseMouseMouse Pad
Corsair TX750 Cooler Master HAF932 Logitech G500 Custom 
AudioAudioAudioAudio
Creative X-Fi Titanium Fatal1ty 2x Dayton B652 Bookshelf Dayton DTA-100A Amplifier Dayton 12" SUB-1200 Subwoofer 
  hide details  
Reply
Gaming Rig
(20 items)
 
  
CPUMotherboardGraphicsRAM
Intel 2500k, 4.6GHz, 1.304v ASRock P67 Extreme4 Gen3 2x Sapphire HD7970 OC with Boost, 1150 MHz/1550... 2x4GB DDR3 1600 Corsair Vengeance 
Hard DriveHard DriveHard DriveOptical Drive
Samsung 840 Pro Samsung 750GB HD753LJ Samsung F3 ASUS 24X DVD Combo Drive 
CoolingOSMonitorKeyboard
Noctua DH14 Windows 8 Professional x64 Crossover 27Q 27" IPS LED, 2560x1440 Logitech G11 
PowerCaseMouseMouse Pad
Corsair TX750 Cooler Master HAF932 Logitech G500 Custom 
AudioAudioAudioAudio
Creative X-Fi Titanium Fatal1ty 2x Dayton B652 Bookshelf Dayton DTA-100A Amplifier Dayton 12" SUB-1200 Subwoofer 
  hide details  
Reply
post #3 of 40
Quote:
Originally Posted by chriscamargo View Post

Hey folks,
I'm hoping you all can help me solve this confounding BSOD problem I'm having. For the last year, I've had recurring blue screens that Windows reports are mostly triggered by ntoskrnl.exe. You can see what I mean here:

My Troubleshooting Steps
1) Multiple virus scans (both in OS & at boot time)
2) Multiple RAM tests (Using Hirens Boot CD)
3) Multiple HDD tests (Both Windows and 3rd Party)
None of these tests came back with remarkable results.
These BSODs can arise either during very high load or when the PC is just sitting idle. I've woken the PC up from sleep many times, only to see it's "recovered from a serious error."
I'm very new to these forums, but I've tried to follow the BSOD posting instructions to the letter. I've attached my file collection and PERFMON report.
System Specs
OS: Windows 7 Home Premium, 64-bit (Retail)
Age of System: > 2 years
Age of OS install: Installed on 12/9/2011 (1 year)
CPU: Intel Core i5-2500K CPU @ 3.30 GHz
Video Card: EVGA GeForce GTS450
Motherboard: ASUS Sabertooth P67
Power supply: Corsair TX 650W
System Manufacturer: None (Home-built)
Please let me know if there's anything I've missed. Thank you all in advance!
BSODs.zip 3226k .zip file

Thanks for following the instructions! smile.gif
I'll take a look through your files - I'm sure we can get this resolved!

--

Your BSODs are all due to memory corruption of some kind. This corruption can come from bad hardware (usually RAM), or a suspect device driver that is not behaving. Because you mentioned you've tested your RAM already, we will skip the hardware possibility for now, but it may be revisited in the future if all other options are exhausted.

OK first things first, we've got some REALLY old stuff from LogMeIn:
Code:
Module Name:       LMIInfo
Display Name:      LogMeIn Kernel Information Provider
Link Date:         1/4/2008 10:57:14 AM

Module Name:       lmimirr
Display Name:      lmimirr
Link Date:         4/10/2007 3:32:45 PM

I recommend to update or remove LogMeIn.

You may also want to check to make sure your wireless drivers are completely up to date:
Code:
Module Name:       netr28x
Display Name:      Ralink 802.11n Extensible Wireless Driver
Link Date:         4/18/2011 8:31:37 PM

I noticed Sandboxie and MagicDisc are installed - could we please remove them for the duration of this issue? smile.gif
Ol' Sandy
(28 items)
 
"Zeus"
(12 items)
 
Elite Preview
(6 items)
 
CPUMotherboardGraphicsRAM
Intel Xeon E3-1230v3 Gigabyte GA-Z97X-UD5H-BK MSI Gaming GTX 980 Kingston 32GB (4x8) 
Hard DriveHard DriveHard DriveHard Drive
Plextor PX-256M5S 256GB Samsung EVO 1TB Hitachi HDS721010CLA332 Hitachi HDS723020BLA642 
Hard DriveHard DriveHard DriveOptical Drive
Hitachi HDS723020BLA642 Hitachi HUA722010CLA330 WDC WD10EARS-00Z5B1 TSSTcorp CDDVDW SH-S223B 
CoolingCoolingOSMonitor
Phanteks PH-TC14PE with TY-140's Lamptron FCv5 (x2) Windows 8 Pro 64-bit Dell U2412M 
MonitorMonitorMonitorKeyboard
Dell U2412M Dell U2212HM Dell U2713HM Topre Realforce 87UB | Ducky DK9087 G2 Pro 
PowerCaseMouseMouse Pad
Corsair AX-750 Corsair Obsidian 650D Logitech G700 XTRAC Ripper XXL 
AudioAudioAudioAudio
Beyerdynamic DT-770 Pro 250ohm Schiit Bifrost DAC Schiit Asgard 2 HiVi Swan M50W 2.1 
CPUMotherboardRAMHard Drive
Intel Xeon E5-2620 Super Micro X9SRL-F-B 128GB 1333MHz LSI 9271-8i 
OSPowerCase
VMware ESXi 5.5 SeaSonic SS-400FL2 Fractal Define R3 
CPUMotherboardGraphicsRAM
Intel Core i5-3437U HP EliteBook Folio 9470m  Intel HD Graphics 4000  16GB DDR3 SDRAM 
Hard DriveOS
256GB SSD Windows 10 Insider Preview 
  hide details  
Reply
Ol' Sandy
(28 items)
 
"Zeus"
(12 items)
 
Elite Preview
(6 items)
 
CPUMotherboardGraphicsRAM
Intel Xeon E3-1230v3 Gigabyte GA-Z97X-UD5H-BK MSI Gaming GTX 980 Kingston 32GB (4x8) 
Hard DriveHard DriveHard DriveHard Drive
Plextor PX-256M5S 256GB Samsung EVO 1TB Hitachi HDS721010CLA332 Hitachi HDS723020BLA642 
Hard DriveHard DriveHard DriveOptical Drive
Hitachi HDS723020BLA642 Hitachi HUA722010CLA330 WDC WD10EARS-00Z5B1 TSSTcorp CDDVDW SH-S223B 
CoolingCoolingOSMonitor
Phanteks PH-TC14PE with TY-140's Lamptron FCv5 (x2) Windows 8 Pro 64-bit Dell U2412M 
MonitorMonitorMonitorKeyboard
Dell U2412M Dell U2212HM Dell U2713HM Topre Realforce 87UB | Ducky DK9087 G2 Pro 
PowerCaseMouseMouse Pad
Corsair AX-750 Corsair Obsidian 650D Logitech G700 XTRAC Ripper XXL 
AudioAudioAudioAudio
Beyerdynamic DT-770 Pro 250ohm Schiit Bifrost DAC Schiit Asgard 2 HiVi Swan M50W 2.1 
CPUMotherboardRAMHard Drive
Intel Xeon E5-2620 Super Micro X9SRL-F-B 128GB 1333MHz LSI 9271-8i 
OSPowerCase
VMware ESXi 5.5 SeaSonic SS-400FL2 Fractal Define R3 
CPUMotherboardGraphicsRAM
Intel Core i5-3437U HP EliteBook Folio 9470m  Intel HD Graphics 4000  16GB DDR3 SDRAM 
Hard DriveOS
256GB SSD Windows 10 Insider Preview 
  hide details  
Reply
post #4 of 40
Thread Starter 
Gentlemen,

Thank you both for the excellent responses!

I've uninstalled Sandboxie, MagicDisc and Daemon Tools. I've also updated my NVIDIA device drivers for my GTS 450, as well as the Intel chipset drivers for my motherboard. I located the most recent drivers for my ASUS PCE-N15 wireless network card, but I'm not sure if Windows accepted them as "new," even though their creation date was more recent than that of the installed driver. It told me I already had the best drivers for my device, but I manually installed them anyway using the "Have disk..." process.

In any case, I'll keep the system running and see if we can produce another blue screen. What's the process if another BSOD occurs? Will there be any files I can attach to give the best insights into the next crash?

Again, thank you both!
post #5 of 40
Quote:
Originally Posted by chriscamargo View Post

Gentlemen,
Thank you both for the excellent responses!
I've uninstalled Sandboxie, MagicDisc and Daemon Tools. I've also updated my NVIDIA device drivers for my GTS 450, as well as the Intel chipset drivers for my motherboard. I located the most recent drivers for my ASUS PCE-N15 wireless network card, but I'm not sure if Windows accepted them as "new," even though their creation date was more recent than that of the installed driver. It told me I already had the best drivers for my device, but I manually installed them anyway using the "Have disk..." process.
In any case, I'll keep the system running and see if we can produce another blue screen. What's the process if another BSOD occurs? Will there be any files I can attach to give the best insights into the next crash?
Again, thank you both!

Just post back and I'll go through the next stage with you smile.gif
Ol' Sandy
(28 items)
 
"Zeus"
(12 items)
 
Elite Preview
(6 items)
 
CPUMotherboardGraphicsRAM
Intel Xeon E3-1230v3 Gigabyte GA-Z97X-UD5H-BK MSI Gaming GTX 980 Kingston 32GB (4x8) 
Hard DriveHard DriveHard DriveHard Drive
Plextor PX-256M5S 256GB Samsung EVO 1TB Hitachi HDS721010CLA332 Hitachi HDS723020BLA642 
Hard DriveHard DriveHard DriveOptical Drive
Hitachi HDS723020BLA642 Hitachi HUA722010CLA330 WDC WD10EARS-00Z5B1 TSSTcorp CDDVDW SH-S223B 
CoolingCoolingOSMonitor
Phanteks PH-TC14PE with TY-140's Lamptron FCv5 (x2) Windows 8 Pro 64-bit Dell U2412M 
MonitorMonitorMonitorKeyboard
Dell U2412M Dell U2212HM Dell U2713HM Topre Realforce 87UB | Ducky DK9087 G2 Pro 
PowerCaseMouseMouse Pad
Corsair AX-750 Corsair Obsidian 650D Logitech G700 XTRAC Ripper XXL 
AudioAudioAudioAudio
Beyerdynamic DT-770 Pro 250ohm Schiit Bifrost DAC Schiit Asgard 2 HiVi Swan M50W 2.1 
CPUMotherboardRAMHard Drive
Intel Xeon E5-2620 Super Micro X9SRL-F-B 128GB 1333MHz LSI 9271-8i 
OSPowerCase
VMware ESXi 5.5 SeaSonic SS-400FL2 Fractal Define R3 
CPUMotherboardGraphicsRAM
Intel Core i5-3437U HP EliteBook Folio 9470m  Intel HD Graphics 4000  16GB DDR3 SDRAM 
Hard DriveOS
256GB SSD Windows 10 Insider Preview 
  hide details  
Reply
Ol' Sandy
(28 items)
 
"Zeus"
(12 items)
 
Elite Preview
(6 items)
 
CPUMotherboardGraphicsRAM
Intel Xeon E3-1230v3 Gigabyte GA-Z97X-UD5H-BK MSI Gaming GTX 980 Kingston 32GB (4x8) 
Hard DriveHard DriveHard DriveHard Drive
Plextor PX-256M5S 256GB Samsung EVO 1TB Hitachi HDS721010CLA332 Hitachi HDS723020BLA642 
Hard DriveHard DriveHard DriveOptical Drive
Hitachi HDS723020BLA642 Hitachi HUA722010CLA330 WDC WD10EARS-00Z5B1 TSSTcorp CDDVDW SH-S223B 
CoolingCoolingOSMonitor
Phanteks PH-TC14PE with TY-140's Lamptron FCv5 (x2) Windows 8 Pro 64-bit Dell U2412M 
MonitorMonitorMonitorKeyboard
Dell U2412M Dell U2212HM Dell U2713HM Topre Realforce 87UB | Ducky DK9087 G2 Pro 
PowerCaseMouseMouse Pad
Corsair AX-750 Corsair Obsidian 650D Logitech G700 XTRAC Ripper XXL 
AudioAudioAudioAudio
Beyerdynamic DT-770 Pro 250ohm Schiit Bifrost DAC Schiit Asgard 2 HiVi Swan M50W 2.1 
CPUMotherboardRAMHard Drive
Intel Xeon E5-2620 Super Micro X9SRL-F-B 128GB 1333MHz LSI 9271-8i 
OSPowerCase
VMware ESXi 5.5 SeaSonic SS-400FL2 Fractal Define R3 
CPUMotherboardGraphicsRAM
Intel Core i5-3437U HP EliteBook Folio 9470m  Intel HD Graphics 4000  16GB DDR3 SDRAM 
Hard DriveOS
256GB SSD Windows 10 Insider Preview 
  hide details  
Reply
post #6 of 40
Thread Starter 
Got a fresh one! Well, sorta fresh. It happened to me right before vacation, so I'm posting it now that I'm back.

post #7 of 40
Quote:
Originally Posted by chriscamargo View Post

Got a fresh one! Well, sorta fresh. It happened to me right before vacation, so I'm posting it now that I'm back.
Looks to me like memory corruption. Have you tried running memtest?
Jay
(13 items)
 
  
CPUMotherboardGraphicsRAM
FX 8350 4.4Ghz at 1.36v GA 78LMT USB3 Rev 5.0 Sapphire R9 285 OC 16GB Kingston Savage Ram 
Hard DriveHard DriveCoolingOS
1TB Western Digital 500GB Seagate Barracuda Noctua NH-D15S Windows 8.1 
MonitorPowerMouseMouse Pad
Asus MG279Q Fressync OCZ ZS 650 Watt PSU Dragonwar ELE-G9 Dragonwar 
  hide details  
Reply
Jay
(13 items)
 
  
CPUMotherboardGraphicsRAM
FX 8350 4.4Ghz at 1.36v GA 78LMT USB3 Rev 5.0 Sapphire R9 285 OC 16GB Kingston Savage Ram 
Hard DriveHard DriveCoolingOS
1TB Western Digital 500GB Seagate Barracuda Noctua NH-D15S Windows 8.1 
MonitorPowerMouseMouse Pad
Asus MG279Q Fressync OCZ ZS 650 Watt PSU Dragonwar ELE-G9 Dragonwar 
  hide details  
Reply
post #8 of 40
Never seen one actually say MEMORY_MANAGEMENT, it seems to be power-related more than memory-related (I say this because OP did mention they ran memory tests). I would suggest manually setting your memory voltage in BIOS to the exact level your memory is rated for. Usually 1.6v for Sandy Bridge. Your memory slots could be faulty, perhaps try using different ones if setting the voltage doesn't fix it and see if you still get a BSOD. And actually I'm surprised no one has asked: did you overclock your RAM or change timings? If so try running it at factory specs to narrow down the possible factors.
Edited by Stealth Pyros - 12/31/12 at 6:03am
Gaming Rig
(20 items)
 
  
CPUMotherboardGraphicsRAM
Intel 2500k, 4.6GHz, 1.304v ASRock P67 Extreme4 Gen3 2x Sapphire HD7970 OC with Boost, 1150 MHz/1550... 2x4GB DDR3 1600 Corsair Vengeance 
Hard DriveHard DriveHard DriveOptical Drive
Samsung 840 Pro Samsung 750GB HD753LJ Samsung F3 ASUS 24X DVD Combo Drive 
CoolingOSMonitorKeyboard
Noctua DH14 Windows 8 Professional x64 Crossover 27Q 27" IPS LED, 2560x1440 Logitech G11 
PowerCaseMouseMouse Pad
Corsair TX750 Cooler Master HAF932 Logitech G500 Custom 
AudioAudioAudioAudio
Creative X-Fi Titanium Fatal1ty 2x Dayton B652 Bookshelf Dayton DTA-100A Amplifier Dayton 12" SUB-1200 Subwoofer 
  hide details  
Reply
Gaming Rig
(20 items)
 
  
CPUMotherboardGraphicsRAM
Intel 2500k, 4.6GHz, 1.304v ASRock P67 Extreme4 Gen3 2x Sapphire HD7970 OC with Boost, 1150 MHz/1550... 2x4GB DDR3 1600 Corsair Vengeance 
Hard DriveHard DriveHard DriveOptical Drive
Samsung 840 Pro Samsung 750GB HD753LJ Samsung F3 ASUS 24X DVD Combo Drive 
CoolingOSMonitorKeyboard
Noctua DH14 Windows 8 Professional x64 Crossover 27Q 27" IPS LED, 2560x1440 Logitech G11 
PowerCaseMouseMouse Pad
Corsair TX750 Cooler Master HAF932 Logitech G500 Custom 
AudioAudioAudioAudio
Creative X-Fi Titanium Fatal1ty 2x Dayton B652 Bookshelf Dayton DTA-100A Amplifier Dayton 12" SUB-1200 Subwoofer 
  hide details  
Reply
post #9 of 40
Let's give the driver verifier a whirl - I'm not convinced the issue is hardware yet.

Driver Verifier

IMPORTANT
You may wish to print out these instructions in order to refer to recovery steps if your computer fails to restart after enabling the Driver Verifier (thus rendering this page inaccessible)


The Driver Verifier is a component of Windows starting with Windows Server 2003 (8, 7, Vista, XP, 2008/R2) which is used to promote stability and reliability. Drivers are kernel-mode components that if do not behave correctly can cause system corruption, failures and other crashes.

If a non-Microsoft driver is running around in bad territory and causing your computer to blue-screen, turning on the Driver Verifier will help to pinpoint which driver is at fault, after which it then can be updated or removed from the system.

How to enable the Driver Verifier

Create a System Restore point

This section does NOT apply to Windows XP, Windows Server 2003 or 2008/R2

1. Click Start
2. In the search box, type sysdm.cpl and then press ENTER.
3. Verify that the system disk is selected and click the Create button.
4. Type a description for the restore point.
5. Click the Create button. A status bar will appear as Vista saves your files. When the process is complete, a message box will appear indicating that the restore point was created.

Configure Driver Verifier

1. Click Start
2. In the search box, type verifier and then press ENTER.
3. Ensure that Create custom settings (for code developers) is selected and then click Next.
4. Select Select individual settings from a full list and then click Next.
5. Place a check mark next to the following boxes:
  • Special Pool
  • Pool Tracking
  • Force IRQL Checking
  • Deadlock Detection
  • Security Checks (Windows 7 and Windows 8)
  • DDI compliance checking (Windows 8)
  • Miscellaneous Checks

6. Click Next and then choose Select driver names from a list.
7. Click the Provider column to sort drivers by their provider.
8. Place a check mark next to each item that is NOT provided by Microsoft or Microsoft Corporation.
9. Click Finish and restart your computer.

What you should know about the Driver Verifier

The Driver Verifier works by monitoring the drivers you selected and then if a violation is detected, it will immediately cause a blue-screen

Sometimes after the Driver Verifier is enabled and you restart your computer, you may blue-screen before being able to log on to Windows. This happens when the Driver Verifier detects a violation from a driver that is set to load at boot time. This is no cause for concern - to resume normal operation, follow the below steps:

1. Restart the computer in Safe Mode by selecting it from the F8 boot menu (press F8 repeatedly after the system restarts).
2. Once in Safe Mode, do the following:

If you created a restore point and are NOT running Windows XP, Windows Server 2003 or 2008/R2:
  • Click Start, type system restore in the search box, and then press ENTER.
  • Restore your computer to the point you created beforehand.

If you are running Windows XP, Windows Server 2003 or 2008/R2, or could not create a restore point beforehand:
  • Click Start, type cmd in the search box, and then press ENTER.
  • At the command prompt, type verifier /reset and then press ENTER.
  • Restart your computer

How long do I leave the Driver Verifier enabled?

Keep the Driver Verifier enabled for around 24-48 hours - don't worry too much about getting the timing perfect. If your computer does not blue-screen during that time, you can disable the Driver Verifier by following the steps above.

A blue-screen occurred, what should I do?

The minidumps generated by your blue-screen will now have more information in them due to Driver Verifier being enabled. They will be located at %windir%\Minidump. Save these and attach them to your next reply for analysis.
Ol' Sandy
(28 items)
 
"Zeus"
(12 items)
 
Elite Preview
(6 items)
 
CPUMotherboardGraphicsRAM
Intel Xeon E3-1230v3 Gigabyte GA-Z97X-UD5H-BK MSI Gaming GTX 980 Kingston 32GB (4x8) 
Hard DriveHard DriveHard DriveHard Drive
Plextor PX-256M5S 256GB Samsung EVO 1TB Hitachi HDS721010CLA332 Hitachi HDS723020BLA642 
Hard DriveHard DriveHard DriveOptical Drive
Hitachi HDS723020BLA642 Hitachi HUA722010CLA330 WDC WD10EARS-00Z5B1 TSSTcorp CDDVDW SH-S223B 
CoolingCoolingOSMonitor
Phanteks PH-TC14PE with TY-140's Lamptron FCv5 (x2) Windows 8 Pro 64-bit Dell U2412M 
MonitorMonitorMonitorKeyboard
Dell U2412M Dell U2212HM Dell U2713HM Topre Realforce 87UB | Ducky DK9087 G2 Pro 
PowerCaseMouseMouse Pad
Corsair AX-750 Corsair Obsidian 650D Logitech G700 XTRAC Ripper XXL 
AudioAudioAudioAudio
Beyerdynamic DT-770 Pro 250ohm Schiit Bifrost DAC Schiit Asgard 2 HiVi Swan M50W 2.1 
CPUMotherboardRAMHard Drive
Intel Xeon E5-2620 Super Micro X9SRL-F-B 128GB 1333MHz LSI 9271-8i 
OSPowerCase
VMware ESXi 5.5 SeaSonic SS-400FL2 Fractal Define R3 
CPUMotherboardGraphicsRAM
Intel Core i5-3437U HP EliteBook Folio 9470m  Intel HD Graphics 4000  16GB DDR3 SDRAM 
Hard DriveOS
256GB SSD Windows 10 Insider Preview 
  hide details  
Reply
Ol' Sandy
(28 items)
 
"Zeus"
(12 items)
 
Elite Preview
(6 items)
 
CPUMotherboardGraphicsRAM
Intel Xeon E3-1230v3 Gigabyte GA-Z97X-UD5H-BK MSI Gaming GTX 980 Kingston 32GB (4x8) 
Hard DriveHard DriveHard DriveHard Drive
Plextor PX-256M5S 256GB Samsung EVO 1TB Hitachi HDS721010CLA332 Hitachi HDS723020BLA642 
Hard DriveHard DriveHard DriveOptical Drive
Hitachi HDS723020BLA642 Hitachi HUA722010CLA330 WDC WD10EARS-00Z5B1 TSSTcorp CDDVDW SH-S223B 
CoolingCoolingOSMonitor
Phanteks PH-TC14PE with TY-140's Lamptron FCv5 (x2) Windows 8 Pro 64-bit Dell U2412M 
MonitorMonitorMonitorKeyboard
Dell U2412M Dell U2212HM Dell U2713HM Topre Realforce 87UB | Ducky DK9087 G2 Pro 
PowerCaseMouseMouse Pad
Corsair AX-750 Corsair Obsidian 650D Logitech G700 XTRAC Ripper XXL 
AudioAudioAudioAudio
Beyerdynamic DT-770 Pro 250ohm Schiit Bifrost DAC Schiit Asgard 2 HiVi Swan M50W 2.1 
CPUMotherboardRAMHard Drive
Intel Xeon E5-2620 Super Micro X9SRL-F-B 128GB 1333MHz LSI 9271-8i 
OSPowerCase
VMware ESXi 5.5 SeaSonic SS-400FL2 Fractal Define R3 
CPUMotherboardGraphicsRAM
Intel Core i5-3437U HP EliteBook Folio 9470m  Intel HD Graphics 4000  16GB DDR3 SDRAM 
Hard DriveOS
256GB SSD Windows 10 Insider Preview 
  hide details  
Reply
post #10 of 40
Thread Starter 
Happy New Year, everyone! I'm home fighting the flu so it was the perfect time to give the Driver Verifier a shot. smile.gif

Sure enough, I received a BSOD a few milliseconds into Windows 7 start up animation. It was incredibly brief. There was almost no animation to speak of, except for those little morphing dots appearing on the screen.

There's only one problem: the blue screen didn't create anything new in the Minidump folder. The last file I see is the one dated 12/25, which is the MEMORY_MANAGEMENT error I posted last. I even let the system blue screen twice before I got it into safe mode. Both times it happened at the exact same point.

I did a System Restore, got the machine back on its feet, and now it's like it didn't even happen.

I take it this isn't supposed to happen without creating a dmp file, right?
New Posts  All Forums:Forum Nav:
  Return Home
  Back to Forum: Crash Analysis and Debugging
Overclock.net › Forums › Software, Programming and Coding › Operating Systems › Windows › Crash Analysis and Debugging › A Year of BSODs (mostly ntoskrnl.exe)