Windows 7 Need Help With fixing Blue screen of death in windows 7 (SYSTEM_SERVICE_EXCEPTION)

[GamingGringo]

so i got a BSOD the other day while playing battlefield hardline on my new custom made desktop.
I installed some software (bluescreenview) to view it in my dumpfile and it said that the BSOD was caused by the Driver pacer.sys. (driver adress is pacer.sys+1199)
what should i do at this point? I know the problem but i dont know that much about computers to resolve the issue. PLEASE HELP. blue screens of death scare me :'(



More Info:
Bug check string: SYSTEM_SERVICE_EXCEPTION
Bug check code: 0x0000003b
Parameter 1: 00000000`c0000005
Parameter 2: fffff800`01aa947b
Parameter 3: fffff880`0bab8d00
Parameter 4: 00000000`00000000
Caused by driver: pacer.sys
Caused by adress: pacer.sys+1199
Processor: x64
Crash adress: ntoskrnl.exe+75bc0
Full path: C:\Windows\Minidump\061814-21855-01.dmp
Processor Count: 8
Major Version: 15
Minor Version: 7601
Dump file size 291,472
Dump File time: 6/18/2014 10:48:22 PM

(in the dumpfile there is also a list of files and 2 of them are highlighted red.
One is
ntoskrnl.exe ntoskrnl.exe+75169 fffff800`01a5f000 fffff800`02044000 0x005e5000 0x531590fb 3/4/2014 3:38:19 AM Microsoft® Windows® Operating System NT Kernel & System 6.1.7601.18409 (win7sp1_gdr.140303-2144) Microsoft Corporation C:\Windows\system32\ntoskrnl.exe

Second is
pacer.sys pacer.sys+1199 fffff880`02d7f000 fffff880`02da5000 0x00026000 0x4ce7a862 11/20/2010 5:52:18 AM


Again... PLEASE HELP!!!

 

[kemical]

Hi Gringo,
to effectively debug your dump files we need to see them. Please read this thread and post the results:
Link Removed

 

[GamingGringo]

oh right. Here are my MiniDump Files.

 

[GamingGringo]

here is also the blue screen viewer i used.

 

[kemical]

*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 3B, {c0000005, fffff80001aa947b, fffff8800bab8d00, 0}

Probably caused by : ntkrnlmp.exe ( nt!ExQueryPoolUsage+e0 )

Followup: MachineOwner

Hi,
The above bugcheck can often appear for a number of reasons:
A process within Windows is corrupt, out of date drivers/bios and/or bad RAM modules. I know your system is brand new but it's not unknown for brand new RAM to have faults.
Pacer.sys is a Windows driver and part of the network so either that driver or data within windows is corrupt or something else is causing Pacer.sys to crash. Looking through the dump file for clues is the best way to go and the more you have the better. As we have only one I'll try and cover a broad range of possibilities although we usually do this anyway unless it's something very obvious.

Update Bios:
BiosVersion = P1.00
BiosReleaseDate = 04/28/2014
BaseBoardManufacturer = ASRock
BaseBoardProduct = Z97 Killer
There has been several updates since the board (very nice board by the way) was released. You'll need a USB stick which you'll have to format so it's FAT32 on which you'll store the new bios download on. Just follow the instructions given on the web page under the red plus sign:
http://www.asrock.com/mb/Intel/Fatal1ty Z97 Killer/?cat=Download&os=BIOS

Norton AV:
I see your running Norton AV. Norton is well known in debugging circles for causing issues and sadly it's not the app it once was circa 2002. Please uninstall using this tool:
https://support.norton.com/sp/en/uk/home/current/solutions/kb20080710133834EN_EndUserProfile_en_us
Please use MSE as it's extremely stable:
Link Removed

Drivers:
athrx.sys Wed Feb 22 06:29:09 2012: Atheros network adapter driver please update using download off MoBo website:
http://www.asrock.com/mb/Intel/Fatal1ty Z97 Killer/?cat=Download&os=Win764
In fact please go through the above webpage and apply all those latest drivers as I see your missing at least one.

Windows corruption
To ensure Windows is corrupt please run the System file checker. To do this look for command prompt in the start menu, right click on it and run as admin. Type:
sfc /scannow
Press enter and await results.

If after completing the above changes your still getting a bsod then download the latest version of Memtest86 here:
http://www.memtest.org/
This guide although a little old explains how best to use it:
http://www.techspot.com/community/topics/tutorial-how-to-use-memtest.62524/

Post any new dump files.