BSOD after upgrading computer DRIVER_IRQL_NOT_LESS_OR_EQUAL (d1) ntoskrnl.exe


I've just changed motherboard card, memory and CPU to the new one:
gigabyte p67a-d3-b3, intel core i3 2120, Patriot DDR3 2x4096MB 1600MHz CL8.0 Viper Xtreme Divison 2 LLK.

I changed in BIOS memory to 1600MhZ 8-9-8-24 1.5 V (instead of 1.65V (i couldnt find option to get it to 1.65V in BIOS, when i changed to 1.6V system didnt run). After 1 day I got BSOD. But i changed back memory to the orginal state and after about 1 hour system just got shocked. BSOD didn't show up, but computer was frozen and non stop i could hear beeeeeeeeeeeeeeeep sound.

I didn't uninstall drivers from old motherboard (don't know how). I installed new drivers for new motherboard / CPU. I didn't install again graphic card drivers (I was told i don't need to). I didn't make format either (I'd like to avoid that as much as I can).

In attachment everything you want: minidump / Rammon / cpu-z / and seven forums tool logs.

Please help me :)

Best regards,

Arkadiusz Wlodarczyk


I'd like to add that each time computer got frozen was while I was watching something on Youtube (I think not 100% sure).


Last edited:


Fantastic Member
Microsoft Community Contributor
Un-install Apple Charger - it is known to cause BSOD's in some Win7 systems.

Un-install DaemonTools/Alcohol software - it's known to cause BSOD's in some Win7 systems.

Please update these older drivers. Links are included to assist in looking up the source of the drivers. If unable to find an update, please remove (un-install) the program responsible for that driver. DO NOT manually delete/rename the driver as it may make the system unbootable! :
ctac32k.sys Wed Jul 2 04:38:22 2008 (486B3E7E)
Creative Audio Driver

hamachi.sys Thu Feb 19 05:36:41 2009 (499D3639)
LogMeIn Hamachi Virtual network interface driver
Please un-install this one - AFAIK there is no update available.

nvstor64.sys Tue Aug 4 20:31:07 2009 (4A78D2CB)
nVidia Storage Driver (nForce chipset driver)

If these things don't stop the BSOD's, please run Driver Verifier according to these instructions: Driver Verifier Settings

The following is for information purposes only.
[font=lucida console]**************************Thu Sep  6 05:23:44.612 2012 (UTC - 4:00)**************************
Loading Dump File [C:\Users\John\_jcgriff2_\dbug\__Kernel__\090612-24850-01.dmp]
Windows 7 Kernel Version [B]7601 [/B](Service Pack 1) MP (4 procs) Free x64
Built by: [B]7601[/B].17835.amd64fre.win7sp1_gdr.120503-2030
System Uptime:[B]0 days 1:45:40.814[/B]
BugCheck Code: [B]BugCheck D1, {fffff87fe6a4bf2c, 2, 8, fffff87fe6a4bf2c}[/B]
Probably caused by :[B]USBPORT.SYS ( USBPORT+74c1 )[/B]
PROCESS_NAME: [B]thunderbird.ex[/B]
CPUID:        "Intel(R) Core(TM) i3-2120 CPU @ 3.30GHz"
MaxSpeed:     3300
  BIOS Version                  FE
  BIOS Release Date             03/20/2012
  Manufacturer                  Gigabyte Technology Co., Ltd.
  Product Name                  P67A-D3-B3

3rd Party Drivers:The following is for information purposes only. Any drivers in red should be updated.
[font=lucida console]**************************Thu Sep  6 05:23:44.612 2012 (UTC - 4:00)**************************
[COLOR=RED][B]ctac32k.sys                 Wed Jul  2 04:38:22 2008 (486B3E7E)[/B][/COLOR]
[COLOR=RED][B]hamachi.sys                 Thu Feb 19 05:36:41 2009 (499D3639)[/B][/COLOR]
intelppm.sys                Mon Jul 13 19:19:25 2009 (4A5BC0FD)
nvstor64.sys                Tue Aug  4 20:31:07 2009 (4A78D2CB)
amdxata.sys                 Fri Mar 19 12:18:18 2010 (4BA3A3CA)
nvstor.sys                  Fri Mar 19 16:45:11 2010 (4BA3E257)
emupia2k.sys                Wed May  5 08:57:27 2010 (4BE16B37)
ctsfm2k.sys                 Wed May  5 08:57:33 2010 (4BE16B3D)
ctoss2k.sys                 Wed May  5 08:57:46 2010 (4BE16B4A)
ha20x2k.sys                 Wed May  5 08:59:10 2010 (4BE16B9E)
ctaud2k.sys                 Wed May  5 08:59:48 2010 (4BE16BC4)
ctprxy2k.sys                Wed May  5 08:59:51 2010 (4BE16BC7)
CTEXFIFX.SYS                Wed May  5 09:01:21 2010 (4BE16C21)
CT20XUT.SYS                 Wed May  5 09:01:28 2010 (4BE16C28)
CTHWIUT.SYS                 Wed May  5 09:01:32 2010 (4BE16C2C)
SmartDefragDriver.sys       Fri Nov 26 04:29:40 2010 (4CEF7E04)
AppleCharger.sys            Mon Jan 10 04:57:29 2011 (4D2AD809)
dtsoftbus01.sys             Mon Mar 14 09:15:36 2011 (4D7E14F8)
nvBridge.kmd                Fri May 20 23:58:23 2011 (4DD7385F)
Rt64win7.sys                Tue May 31 23:15:51 2011 (4DE5AEE7)
RTKVHD64.sys                Tue Jul 26 05:22:00 2011 (4E2E8738)
HECIx64.sys                 Wed Nov  9 19:52:25 2011 (4EBB2049)
EtronXHCI.sys               Fri Feb  3 06:23:49 2012 (4F2BC3C5)
EtronHub3.sys               Fri Feb  3 06:23:55 2012 (4F2BC3CB)
MpFilter.sys                Fri Mar  9 06:05:26 2012 (4F59E3F6)
nvhda64v.sys                Wed Apr 18 13:07:54 2012 (4F8EF4EA)
nvlddmkm.sys                Thu Jun 28 18:58:00 2012 (4FECE178)

Thank you.

I did everything but I cannot find Apple Charger? What is that? Where is that? ;) I tried search google but nothing about it there.

How to remove this thing :
nVidia Storage Driver (nForce chipset driver)

I'm not sure but this thing looks like remainder of old motherboard (asus m2n-sli deluxe) ?

Best regards :)


Fantastic Member
Microsoft Community Contributor
Apple Charger may be On/Off Charge. It is a utility that allows you to charge through your USB ports even if the computer is hibernating/sleeping. Regardless, any utility that adjusts the USB ports like this must be uninstalled.

I think that nvstor64.sys is leftover from your old motherboard. To remove it safely, please do this:
- create a System Restore point
- create a System Repair Disc (Start...All Programs...Maintenance...Create a System Repair Disc)
- use this free tool to stop any instances of nvstor64.sys from loading (remove the checkmark in the far left column to stop it from loading): Autoruns for Windows
- rename nvstor64.sys to nvstor64.BAD (it's usually located in C:\Windows\System32\drivers )
- reboot and see if the system boots.

If it doesn't boot, boot from the System Repair disc and use System Restore to go back to the restore point that you set earlier
and then use the Command Prompt to re-rename nvstor64.BAD to nvstor64.sys.

This website is not affiliated, owned, or endorsed by Microsoft Corporation. It is a member of the Microsoft Partner Program.