BSOD while playing Battlefield 3

Sillymon

New member
Local time
8:45 AM
Messages
6
Hi all, I just built a new computer a week ago. It has been running fine for a week, and I've played Battlefield for a week with no problems. However, now I can only play for ~5 minutes before I get a BSOD.

The error code is 3b, and when I use BlueScreenView, it says that it is caused by "ntoskrnl.exe"

I've run Memtest and sfc /scannow, both giving me the all clear. Also I just ran chkdsk without a problem.

Everything's been running smoothly until now, and I am starting to get really worried about this. I have also put in around 20 hours of BF3 without a hitch.

System specs:
i7 990X - 3.47 ghz
Asus Sabertooth X58 mobo
Asus GTX 560 1 GB graphics card
3x4 GB Kingston RAM
1 TB Western Digital Caviar Blue HDD
Windows 7 Professional 64-bit
750 watt Antec PSU


==================================================
Dump File : 112011-23805-01.dmp
Crash Time : 11/20/2011 9:11:56 AM
Bug Check String : SYSTEM_SERVICE_EXCEPTION
Bug Check Code : 0x0000003b
Parameter 1 : 00000000`c0000005
Parameter 2 : fffff800`0338c20a
Parameter 3 : fffff880`0553cbf0
Parameter 4 : 00000000`00000000
Caused By Driver : ntoskrnl.exe
Caused By Address : ntoskrnl.exe+7cc40
File Description : NT Kernel & System
Product Name : Microsoft® Windows® Operating System
Company : Microsoft Corporation
File Version : 6.1.7601.17640 (win7sp1_gdr.110622-1506)
Processor : x64
Crash Address : ntoskrnl.exe+7cc40
Stack Address 1 :
Stack Address 2 :
Stack Address 3 :
Computer Name :
Full Path : C:\Windows\Minidump\112011-23805-01.dmp
Processors Count : 12
Major Version : 15
Minor Version : 7601
Dump File Size : 290,736
==================================================

==================================================
Dump File : 111911-40669-01.dmp
Crash Time : 11/19/2011 11:29:21 PM
Bug Check String : SYSTEM_SERVICE_EXCEPTION
Bug Check Code : 0x0000003b
Parameter 1 : 00000000`c0000005
Parameter 2 : fffff800`0339e399
Parameter 3 : fffff880`096a4a30
Parameter 4 : 00000000`00000000
Caused By Driver : ntoskrnl.exe
Caused By Address : ntoskrnl.exe+7cc40
File Description : NT Kernel & System
Product Name : Microsoft® Windows® Operating System
Company : Microsoft Corporation
File Version : 6.1.7601.17640 (win7sp1_gdr.110622-1506)
Processor : x64
Crash Address : ntoskrnl.exe+7cc40
Stack Address 1 :
Stack Address 2 :
Stack Address 3 :
Computer Name :
Full Path : C:\Windows\Minidump\111911-40669-01.dmp
Processors Count : 12
Major Version : 15
Minor Version : 7601
Dump File Size : 285,600
==================================================



Please help! Zip file attached.

EDIT: Yet again another 3B, during Just Cause 2 after running fine for over an hour. Need help urgently!
 
Last edited:

My Computer

OS
Windows 7 Professional 64 bit
Hi all, I just built a new computer a week ago. It has been running fine for a week, and I've played Battlefield for a week with no problems. However, now I can only play for ~5 minutes before I get a BSOD.

The error code is 3b, and when I use BlueScreenView, it says that it is caused by "ntoskrnl.exe"

I've run Memtest and sfc /scannow, both giving me the all clear. Also I just ran chkdsk without a problem.

Everything's been running smoothly until now, and I am starting to get really worried about this. I have also put in around 20 hours of BF3 without a hitch.

System specs:
i7 990X - 3.47 ghz
Asus Sabertooth X58 mobo
Asus GTX 560 1 GB graphics card
3x4 GB Kingston RAM
1 TB Western Digital Caviar Blue HDD
Windows 7 Professional 64-bit
750 watt Antec PSU


==================================================
Dump File : 112011-23805-01.dmp
Crash Time : 11/20/2011 9:11:56 AM
Bug Check String : SYSTEM_SERVICE_EXCEPTION
Bug Check Code : 0x0000003b
Parameter 1 : 00000000`c0000005
Parameter 2 : fffff800`0338c20a
Parameter 3 : fffff880`0553cbf0
Parameter 4 : 00000000`00000000
Caused By Driver : ntoskrnl.exe
Caused By Address : ntoskrnl.exe+7cc40
File Description : NT Kernel & System
Product Name : Microsoft® Windows® Operating System
Company : Microsoft Corporation
File Version : 6.1.7601.17640 (win7sp1_gdr.110622-1506)
Processor : x64
Crash Address : ntoskrnl.exe+7cc40
Stack Address 1 :
Stack Address 2 :
Stack Address 3 :
Computer Name :
Full Path : C:\Windows\Minidump\112011-23805-01.dmp
Processors Count : 12
Major Version : 15
Minor Version : 7601
Dump File Size : 290,736
==================================================

==================================================
Dump File : 111911-40669-01.dmp
Crash Time : 11/19/2011 11:29:21 PM
Bug Check String : SYSTEM_SERVICE_EXCEPTION
Bug Check Code : 0x0000003b
Parameter 1 : 00000000`c0000005
Parameter 2 : fffff800`0339e399
Parameter 3 : fffff880`096a4a30
Parameter 4 : 00000000`00000000
Caused By Driver : ntoskrnl.exe
Caused By Address : ntoskrnl.exe+7cc40
File Description : NT Kernel & System
Product Name : Microsoft® Windows® Operating System
Company : Microsoft Corporation
File Version : 6.1.7601.17640 (win7sp1_gdr.110622-1506)
Processor : x64
Crash Address : ntoskrnl.exe+7cc40
Stack Address 1 :
Stack Address 2 :
Stack Address 3 :
Computer Name :
Full Path : C:\Windows\Minidump\111911-40669-01.dmp
Processors Count : 12
Major Version : 15
Minor Version : 7601
Dump File Size : 285,600
==================================================



Please help! Zip file attached.

These crashes were caused by memory corruption. Please run these two tests to verify your memory and find which driver is causing the problem.


1-Memtest.
*Download a copy of Memtest86 and burn the ISO to a CD using Iso Recorder or another ISO burning program. Memtest86+ - Advanced Memory Diagnostic Tool

*Boot from the CD, and leave it running for at least 5 or 6 passes.

Just remember, any time Memtest reports errors, it can be either bad RAM or a bad motherboard slot.

Test the sticks individually, and if you find a good one, test it in all slots.

Any errors are indicative of a memory problem.

If a known good stick fails in a motherboard slot it is probably the slot.
http://www.sevenforums.com/tutorials/105647-ram-test-memtest86.html



2-Driver verifier

I'd suggest that you first backup your data and then make sure you've got access to another computer so you can contact us if problems arise. Then make a System Restore point (so you can restore the system using the Vista/Win7 Startup Repair feature).

In Windows 7 you can make a Startup Repair disk by going to Start....All Programs...Maintenance...Create a System Repair Disc - with Windows Vista you'll have to use your installation disk or the "Repair your computer" option at the top of the Safe Mode menu .

Then, here's the procedure:
- Go to Start and type in "verifier" (without the quotes) and press Enter
- Select "Create custom settings (for code developers)" and click "Next"
- Select "Select individual settings from a full list" and click "Next"
- Select everything EXCEPT FOR "Low Resource Simulation" and click "Next"
- Select "Select driver names from a list" and click "Next"
Then select all drivers NOT provided by Microsoft and click "Next"
- Select "Finish" on the next page.

Reboot the system and wait for it to crash to the Blue Screen. Continue to use your system normally, and if you know what causes the crash, do that repeatedly. The objective here is to get the system to crash because Driver Verifier is stressing the drivers out. If it doesn't crash for you, then let it run for at least 36 hours of continuous operation (an estimate on my part).

If you can't get into Windows because it crashes too soon, try it in Safe Mode.
If you can't get into Safe Mode, try using System Restore from your installation DVD to set the system back to the previous restore point that you created.

http://www.sevenforums.com/tutorials/101379-driver-verifier-enable-disable.html

 

My Computer

Computer Manufacturer/Model Number
HP Pavillion dv-7 1005 Tx
OS
Win 8 Release candidate 8400
CPU
[email protected]
Memory
4 gigs
Graphics Card(s)
Nvidia 9600M
Sound Card
HD built-in
Monitor(s) Displays
17" Wxga
Screen Resolution
1440x900
Cooling
none
Internet Speed
45Mb down 5Mb up
Thanks for the reply ZigZag, I have already run Memtest and it came up all clear. I will try driver verifier and will get back to you.

EDIT: I am starting in safe mode now. With the driver verifier turned on, I BSOD'd right at the login screen because of "portcls.sys" blue screen error d6.


==================================================
Dump File : 112011-33618-01.dmp
Crash Time : 11/20/2011 12:44:33 PM
Bug Check String : DRIVER_PAGE_FAULT_BEYOND_END_OF_ALLOCATION
Bug Check Code : 0x000000d6
Parameter 1 : fffff980`0492f018
Parameter 2 : 00000000`00000000
Parameter 3 : fffff880`049bdb15
Parameter 4 : 00000000`00000000
Caused By Driver : ntoskrnl.exe
Caused By Address : ntoskrnl.exe+7cc40
File Description : NT Kernel & System
Product Name : Microsoft® Windows® Operating System
Company : Microsoft Corporation
File Version : 6.1.7601.17640 (win7sp1_gdr.110622-1506)
Processor : x64
Crash Address : ntoskrnl.exe+7cc40
Stack Address 1 :
Stack Address 2 :
Stack Address 3 :
Computer Name :
Full Path : C:\Windows\Minidump\112011-33618-01.dmp
Processors Count : 12
Major Version : 15
Minor Version : 7601
Dump File Size : 283,480
==================================================


EDIT 2: I think it might have worked now that I've installed a beta driver for Nvidia and a new Realtek sound driver...will report back later today. Thanks for the driver verifier suggestion Zig.
 
Last edited:

My Computer

OS
Windows 7 Professional 64 bit
Ugh, here it goes again. This time they are different errors. This was right after I installed MalwareBytes, only this time BF3 ran fine.


==================================================
Dump File : 112011-25209-01.dmp
Crash Time : 11/20/2011 2:02:24 PM
Bug Check String : KMODE_EXCEPTION_NOT_HANDLED
Bug Check Code : 0x0000001e
Parameter 1 : ffffffff`c0000005
Parameter 2 : fffff800`03375ac0
Parameter 3 : 00000000`00000000
Parameter 4 : ffffffff`ffffffff
Caused By Driver : fltmgr.sys
Caused By Address : fltmgr.sys+13a01
File Description :
Product Name :
Company :
File Version :
Processor : x64
Crash Address : ntoskrnl.exe+7cc40
Stack Address 1 :
Stack Address 2 :
Stack Address 3 :
Computer Name :
Full Path : C:\Windows\Minidump\112011-25209-01.dmp
Processors Count : 12
Major Version : 15
Minor Version : 7601
Dump File Size : 284,880
==================================================

==================================================
Dump File : 112011-29374-01.dmp
Crash Time : 11/20/2011 1:53:01 PM
Bug Check String : MEMORY_MANAGEMENT
Bug Check Code : 0x0000001a
Parameter 1 : 00000000`00041284
Parameter 2 : 00000000`09838001
Parameter 3 : 00000000`00004777
Parameter 4 : fffff700`01080000
Caused By Driver : ntoskrnl.exe
Caused By Address : ntoskrnl.exe+7cc40
File Description : NT Kernel & System
Product Name : Microsoft® Windows® Operating System
Company : Microsoft Corporation
File Version : 6.1.7601.17640 (win7sp1_gdr.110622-1506)
Processor : x64
Crash Address : ntoskrnl.exe+7cc40
Stack Address 1 :
Stack Address 2 :
Stack Address 3 :
Computer Name :
Full Path : C:\Windows\Minidump\112011-29374-01.dmp
Processors Count : 12
Major Version : 15
Minor Version : 7601
Dump File Size : 292,648
==================================================
 

My Computer

OS
Windows 7 Professional 64 bit
Nothing is working, and now I am getting constant Memory_Management BSOD's. Reinstalling Windows 7 right now and hopefully it will work.
 

My Computer

OS
Windows 7 Professional 64 bit
Nothing is working, and now I am getting constant Memory_Management BSOD's. Reinstalling Windows 7 right now and hopefully it will work.


Good luck
 

My Computer

Computer Manufacturer/Model Number
HP Pavillion dv-7 1005 Tx
OS
Win 8 Release candidate 8400
CPU
[email protected]
Memory
4 gigs
Graphics Card(s)
Nvidia 9600M
Sound Card
HD built-in
Monitor(s) Displays
17" Wxga
Screen Resolution
1440x900
Cooling
none
Internet Speed
45Mb down 5Mb up
I am back again on a different computer. Windows installs to 28% and gives me a "ntfs.sys" BSOD (Tried 6 times). I am almost certain it's a corrupted hard drive now, even though I've run fine for a week.

My dad is taking it in to work and having a friend with spare parts check it out for me.
 

My Computer

OS
Windows 7 Professional 64 bit
Hi guys,

My dad took it in to Intel for testing today on their test rig, and the i7 was at fault. They installed a new i7 for me and it has worked for a couple hours now. I will leave it overnight to see if any more BSOD's occur.

Thanks for all the help!
 

My Computer

OS
Windows 7 Professional 64 bit
Back
Top