Windows 7 Forums

Welcome to Windows 7 Forums. Our forum is dedicated to helping you find support and solutions for any problems regarding your Windows 7 PC be it Dell, HP, Acer, Asus or a custom build. We also provide an extensive Windows 7 tutorial section that covers a wide range of tips and tricks.


Windows 7: BSOD when using Chrome, playing Diablo 3

30 May 2014   #1
zzzaaaa

Windows 7 Home Premium 64bit
 
 
BSOD when using Chrome, playing Diablo 3

Hi all, been getting BSODs more and more frequently these days, most notably when I'm using chrome or playing D3. The error shown is usually either SYSTEM_SERVICE_EXCEPTION or DRIVER_IRQL_NOT_LESS_OR_EQUAL.

Could this be due to bad RAM? I've had this computer for nearly 2 years now.


My System SpecsSystem Spec
.
30 May 2014   #2
koolkat77

Microsoft Community Contributor Award Recipient

Windows 10 Home 64Bit
 
 

Welcome to the forum zzzaaaa,

Reduce items at start-up:Perform a clean boot:
Code:
DAEMON Tools Lite	"e:\program files (x86)\daemon tools lite\dtlite.exe" -autorun	user-PC\user	HKU\S-1-5-21-2596862970-426004402-775072447-1000\SOFTWARE\Microsoft\Windows\CurrentVersion\Run
Daemon Tools/Alchohol is known to cause Blue Screens. Please remove it: Run the System File Checker that scans the of all protected Windows 7 system files and replaces incorrect corrupted, changed/modified, or damaged versions with the correct versions if possible:Scan with Kaspersky TDSSKiller:ESET online scanner: Recommended antivirus software for Windows 7 based on stability compared to others:-
warning   Warning
Do not start the free trial of Malware Bytes; remember to deselect that option when prompted.



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!:-

BIOS64.sys Sun Jun 8 06:12:00 2003 (3EE27F50)
This is probably aBIOSTAR I/O driver file
Driver Reference Table - BIOS64.sys

lmimirr.sys Wed Apr 11 04:32:45 2007 (461C108D)
RemotelyAnywhere Mirror Miniport Driver or LogMeIn Mirror Miniport Driver
Driver Reference Table - lmimirr.sys

Lycosa.sys Fri Jan 18 14:51:42 2008 (4790689E)
Razer Lycosa/Razer Tarantula Keyboard Driver. Older versions have BSOD issues with Win7
Driver Reference Table - Lycosa.sys

BS_I2c64.sys Mon Jun 16 12:45:18 2008 (48560BFE)
Found in BIOSTAR BIOS Flash Utility
Driver Reference Table - BS_I2c64.sys

LMIRfsDriver.sys Mon Jul 14 22:26:56 2008 (487B7E50)
RemotelyAnywhere Mirror Miniport Driver or LogMeIn Mirror Miniport Driver
Driver Reference Table - LMIRfsDriver.sys

hamachi.sys Thu Feb 19 16:36:41 2009 (499D3639)
LogMeIn Hamachi Virtual network interface driver
Driver Reference Table - hamachi.sys

RTKVHD64.sys Tue Oct 5 15:58:40 2010 (4CAAF6D0)
Realtek High Definition Audio Function Driver
Driver Reference Table - RTKVHD64.sys

HECIx64.sys Wed Oct 20 05:33:43 2010 (4CBE2AD7)
Intel Management Engine Interface
Driver Reference Table - HECIx64.sys

nusb3hub.sys Fri Dec 10 10:50:35 2010 (4D01B19B)
NEC Electronics USB 3.0 Host Controller Driver (previous BSOD issues with 2010 and earlier versions)
Driver Reference Table - nusb3hub.sys

nusb3xhc.sys Fri Dec 10 10:50:35 2010 (4D01B19B)
NEC Electronics USB 3.0 Host Controller Driver (previous BSOD issues with 2010 and earlier versions)
Driver Reference Table - nusb3xhc.sys

Rt64win7.sys Wed Jan 26 19:34:03 2011 (4D4022CB)
Realtek RTL8168D/8111D Family PCI-E Gigabit Ethernet NIC
Driver Reference Table - Rt64win7.sys

gfibto.sys Fri Sep 2 07:31:28 2011 (4E6031F0)
Possibly a VIPRE Antivirus driver
Driver Reference Table - gfibto.sys

To perform a clean install of a driver, follow this tutorial:Use Revo Uninstaller to uninstall stubborn software. Opt for Advance Mode while uninstalling which allows you to remove leftover registry:-Post a screenshot of your Hard Drive(s) using Crystal Disk Info software:Run a Hard Drive test:Check for heating issues using Speccy or HWmonitor

Upload a screen shot:
Take memtest. Run for 8 passes and test each stick in a know good slot for an additional 6 passes.
Quote:
The goal is to test all the RAM sticks and all the motherboard slots.

Check your motherboard manual to ensure the RAM sticks are in the recommended motherboard slots. Some motherboards have very specific slots required for the number of RAM sticks installed.

If you get errors, stop the test and continue with the next step.

1. Remove all but one stick of RAM from your computer (this will be RAM stick #1), and run Memtest86 again, for 7 passes.
*Be sure to note the RAM stick, use a piece of tape with a number, and note the motherboard slot.
If this stick passes the test then go to step #3.

2. If RAM stick #1 has errors, repeat the test with RAM stick #2 in the same motherboard slot.
*If RAM stick #2 passes, this indicates that RAM stick #1 may be bad. If you want to be absolutely sure, re-test RAM stick #1 in another known good slot.
*If RAM stick #2 has errors, this indicates another possible bad RAM stick, a possible motherboard slot failure or inadequate settings.
3. Test the next stick of RAM (stick #2) in the next motherboard slot.
*If this RAM stick has errors repeat step #2 using a known good stick if possible, or another stick.
*If this RAM stick has no errors and both sticks failed in slot#1, test RAM stick #1 in this slot.
4. If you find a stick that passes the test, test it in all the other motherboard slots.

If Part 2 testing shows errors, and all tests in Part 3 show errors, you will need to test the RAM sticks in another computer and/or test other RAM in your computer to identify the problem.

In this way, you can identify whether it is a bad stick of RAM, a bad motherboard, or incompatibility between the sticks.
information   Information
Errors are sometimes found after 8 passes.

Tip   Tip
Do this test overnight, before going to bed.

Post back with results.

BUGCHECK SUMMARY
Code:
Built by: 7601.18409.amd64fre.win7sp1_gdr.140303-2144
Debug session time: Fri May 30 13:05:10.115 2014 (UTC + 6:00)
System Uptime: 0 days 0:08:29.927
BugCheck D1, {fffff8800133563c, 2, 8, fffff8800133563c}
Probably caused by : Ntfs.sys ( Ntfs! ?? ::NNGAKEGL::`string'+2ee0 )
BUGCHECK_STR:  0xD1
PROCESS_NAME:  svchost.exe
ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
Built by: 7601.18409.amd64fre.win7sp1_gdr.140303-2144
Debug session time: Fri May 30 12:55:41.518 2014 (UTC + 6:00)
System Uptime: 0 days 1:30:47.720
BugCheck 3B, {c0000005, fffff8000325717d, fffff8800c0a2480, 0}
Probably caused by : memory_corruption ( nt!MiDeletePfnList+1bd )
BUGCHECK_STR:  0x3B
PROCESS_NAME:  chrome.exe
ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
Built by: 7601.18409.amd64fre.win7sp1_gdr.140303-2144
Debug session time: Fri May 30 11:23:39.926 2014 (UTC + 6:00)
System Uptime: 0 days 0:00:52.144
BugCheck 3B, {c0000005, fffff8000329ad67, fffff88009f75af0, 0}
Probably caused by : memory_corruption ( nt!MiPfnShareCountIsZero+77 )
BUGCHECK_STR:  0x3B
PROCESS_NAME:  Steam.exe
ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
Built by: 7601.18409.amd64fre.win7sp1_gdr.140303-2144
Debug session time: Fri May 30 11:22:08.366 2014 (UTC + 6:00)
System Uptime: 0 days 2:57:44.568
BugCheck 1E, {ffffffffc0000005, fffff800032f606b, 0, ffffffffffffffff}
Probably caused by : memory_corruption ( nt!MiMapPageInHyperSpaceWorker+1b )
BUGCHECK_STR:  0x1E_c0000005_R
PROCESS_NAME:  Diablo III.exe
ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
Built by: 7601.18409.amd64fre.win7sp1_gdr.140303-2144
Debug session time: Thu May 29 22:42:15.357 2014 (UTC + 6:00)
System Uptime: 0 days 14:32:29.169
BugCheck 3B, {c0000005, fffff800032a517d, fffff88003c65410, 0}
Probably caused by : memory_corruption ( nt!MiDeletePfnList+1bd )
BUGCHECK_STR:  0x3B
PROCESS_NAME:  atiesrxx.exe
ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
Built by: 7601.18409.amd64fre.win7sp1_gdr.140303-2144
Debug session time: Tue May 27 11:58:13.771 2014 (UTC + 6:00)
System Uptime: 0 days 4:06:22.973
BugCheck 3B, {c0000005, fffff8000329f17d, fffff88005437480, 0}
Probably caused by : memory_corruption ( nt!MiDeletePfnList+1bd )
BUGCHECK_STR:  0x3B
PROCESS_NAME:  atieclxx.exe
ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
Built by: 7601.18409.amd64fre.win7sp1_gdr.140303-2144
Debug session time: Thu May 22 10:44:05.381 2014 (UTC + 6:00)
System Uptime: 0 days 0:24:08.599
BugCheck D1, {fffff8800130a63c, 2, 8, fffff8800130a63c}
Probably caused by : Ntfs.sys ( Ntfs! ?? ::NNGAKEGL::`string'+2ee0 )
BUGCHECK_STR:  0xD1
PROCESS_NAME:  Diablo III.exe
ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
Built by: 7601.18409.amd64fre.win7sp1_gdr.140303-2144
Debug session time: Wed May 21 14:47:25.294 2014 (UTC + 6:00)
System Uptime: 0 days 5:56:09.511
BugCheck 1E, {ffffffffc0000005, fffff800032c106b, 0, ffffffffffffffff}
Probably caused by : memory_corruption ( nt!MiMapPageInHyperSpaceWorker+1b )
BUGCHECK_STR:  0x1E_c0000005_R
PROCESS_NAME:  uTorrent.exe
ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
Built by: 7601.18409.amd64fre.win7sp1_gdr.140303-2144
Debug session time: Mon May 19 11:55:54.838 2014 (UTC + 6:00)
System Uptime: 0 days 2:02:36.041
BugCheck 3B, {c0000005, fffff800032d1d67, fffff8800a7678a0, 0}
Probably caused by : memory_corruption ( nt!MiPfnShareCountIsZero+77 )
BUGCHECK_STR:  0x3B
PROCESS_NAME:  CCC.exe
ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
Built by: 7601.18409.amd64fre.win7sp1_gdr.140303-2144
Debug session time: Sun May 18 11:05:17.928 2014 (UTC + 6:00)
System Uptime: 0 days 2:00:40.130
BugCheck 3B, {c0000005, fffff8000325717d, fffff8800c902410, 0}
Probably caused by : memory_corruption ( nt!MiDeletePfnList+1bd )
BUGCHECK_STR:  0x3B
PROCESS_NAME:  chrome.exe
ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
Built by: 7601.18409.amd64fre.win7sp1_gdr.140303-2144
Debug session time: Sat May 17 23:09:29.267 2014 (UTC + 6:00)
System Uptime: 0 days 11:39:22.469
BugCheck 3B, {c0000005, fffff800032a517d, fffff880062b25f0, 0}
Probably caused by : memory_corruption ( nt!MiDeletePfnList+1bd )
BUGCHECK_STR:  0x3B
PROCESS_NAME:  svchost.exe
ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
Built by: 7601.18409.amd64fre.win7sp1_gdr.140303-2144
Debug session time: Fri May 16 19:11:45.502 2014 (UTC + 6:00)
System Uptime: 0 days 10:50:38.720
BugCheck 3B, {c0000005, fffff800032dbd67, fffff880055fb980, 0}
Probably caused by : memory_corruption ( nt!MiPfnShareCountIsZero+77 )
BUGCHECK_STR:  0x3B
PROCESS_NAME:  atieclxx.exe
ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
Built by: 7601.18409.amd64fre.win7sp1_gdr.140303-2144
Debug session time: Thu May 15 13:07:35.829 2014 (UTC + 6:00)
System Uptime: 0 days 0:02:12.656
BugCheck 3B, {c0000005, fffff80003306bee, fffff8800c35bc90, 0}
Probably caused by : memory_corruption ( nt!MiDeletePteRun+504 )
BUGCHECK_STR:  0x3B
PROCESS_NAME:  Diablo III.exe
ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
Built by: 7601.18409.amd64fre.win7sp1_gdr.140303-2144
Debug session time: Thu May 15 13:04:38.269 2014 (UTC + 6:00)
System Uptime: 0 days 4:05:13.471
BugCheck 1E, {ffffffffc0000005, fffff800032b506b, 0, ffffffffffffffff}
Probably caused by : memory_corruption ( nt!MiMapPageInHyperSpaceWorker+1b )
BUGCHECK_STR:  0x1E_c0000005_R
PROCESS_NAME:  Diablo III.exe
ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
My System SpecsSystem Spec
Reply

 BSOD when using Chrome, playing Diablo 3




Thread Tools Search this Thread
Search this Thread:

Advanced Search




Similar help and support threads
Thread Forum
BSOD Playing Diablo III, also random crashes when playing Diablo III.
Made a new post because I got a different BSOD. Sorry ignore this thread.
BSOD Help and Support
BSOD when playing diablo 3
Hi There I'm having exactly the same issues when playing Diablo 3. So I see the SOLVED part in the thread name and I really would like to know how did you solved it?? Short summary on my activity so far
BSOD Help and Support
BSOD while browsing(Chrome, Firefox) gaming(Diablo 3), plus more.
My BSOD's started 3 weeks ago with a forced OS change, after i went from XP PRO x32 to Win 7 x64. The machine has just had a hardware change(new Motherboard for DDR3 memory, the cooler was replaced). Reason, why i perpetrated this hardware change, was due to the high temperatures and lack of...
BSOD Help and Support
BSOD while playing Diablo 3
i got a BSOD while playing Diablo 3. the error was 'page fault on nonpaged area'. it also happens with world of warcraft Is Windows 7 . . . - 64 bit - retail - What is the age of system (hardware)? year and half - What is the age of OS installation (have you re-installed the OS?) 6 moths
BSOD Help and Support
BSOD often while playing Diablo 3
Hello and thanks in advance for the help. I've reached the peak of my knowhow and it ain't that high. IТve been having plenty of BSOD lately while playing Diablo 3. IТve included the zipped files as attachments as per directed and the parameters of hardware are listed below. Problem(s): ...
BSOD Help and Support


Our Sites

Site Links

About Us

Find Us

Windows 7 Forums is an independent web site and has not been authorized, sponsored, or otherwise approved by Microsoft Corporation. "Windows 7" and related materials are trademarks of Microsoft Corp.

й Designer Media Ltd

All times are GMT -5. The time now is 12:02.

Twitter Facebook Google+



Windows 7 Forums

Seven Forums Android App Seven Forums IOS App