📎 AI Summary:
The user experienced BSOD errors while gaming, with analysis indicating issues related to the ntkrnlmp.exe and potential driver conflicts, particularly involving the jraid.sys driver. The suggested solution was to update the JMicron RAID driver, which the user followed successfully, resulting in the resolution of the crashes. Overall, the thread is positive, with the user expressing gratitude for the helpful advice.
J

jcheung87

New Member
Joined
Mar 3, 2011
Messages
12
Thread Author #1
Hey guys I seem to be getting a BSOD whenever I play video games. I thought it was the memory so I ran memtest86 for countless hours each stick at a time and they all tested out fine. I also tested my HD through chkdisk and everything tested out fine. I also seem to get 2 different crashes each time so I attached the minidump for both. This has been really frustrating to me because I really cannot pinpoint the problem. Thanks for reading!
 

Attachments

Sort by date Sort by votes
cybercore

cybercore

New Member
Joined
Jul 7, 2009
Messages
15,626
#2

BugCheck 50, {fffffa8066623980, 0, fffff800033ffdd3, 5}
Probably caused by : ntkrnlmp.exe ( nt!ExFreePoolWithTag+43 )

BugCheck A, {fffffa80240c6bb0, 2, 1, fffff800032c4d24}
Probably caused by : ntkrnlmp.exe ( nt!KiInsertQueueApc+74 )
Click to expand...



Update JMicron RAID driver
jraid.sys Mon Nov 03 21:20:09 2008





Crash Dumps:

Code: 
Loading Dump File [F:\a\Minidump\D M P\DMP\031311-15880-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Mini Kernel Dump does not have process information
Symbol search path is: SRV*c:\websymbols*http://msdl.microsoft.com/download/symbols
Executable search path is: 
Windows 7 Kernel Version 7601 (Service Pack 1) MP (8 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7601.17514.amd64fre.win7sp1_rtm.101119-1850
Machine Name:
Kernel base = 0xfffff800`03252000 PsLoadedModuleList = 0xfffff800`03497e90
Debug session time: Sun Mar 13 12:12:41.624 2011 (UTC - 5:00)
System Uptime: 0 days 0:15:47.608
Loading Kernel Symbols
.................................................
Loading User Symbols
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck A, {fffffa80240c6bb0, 2, 1, fffff800032c4d24}

Probably caused by : ntkrnlmp.exe ( nt!KiInsertQueueApc+74 )

Followup: MachineOwner
---------

7: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

IRQL_NOT_LESS_OR_EQUAL (a)
An attempt was made to access a pageable (or completely invalid) address at an
interrupt request level (IRQL) that is too high.  This is usually
caused by drivers using improper addresses.
If a kernel debugger is available get the stack backtrace.
Arguments:
Arg1: fffffa80240c6bb0, memory referenced
Arg2: 0000000000000002, IRQL
Arg3: 0000000000000001, bitfield :
	bit 0 : value 0 = read operation, 1 = write operation
	bit 3 : value 0 = not an execute operation, 1 = execute operation (only on chips which support this level of status)
Arg4: fffff800032c4d24, address which referenced memory

Debugging Details:
------------------


WRITE_ADDRESS: GetPointerFromAddress: unable to read from fffff800035030e8
 fffffa80240c6bb0 

CURRENT_IRQL:  2

FAULTING_IP: 
nt!KiInsertQueueApc+74
fffff800`032c4d24 488910          mov     qword ptr [rax],rdx

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

BUGCHECK_STR:  0xA

TRAP_FRAME:  fffff88008fec960 -- (.trap 0xfffff88008fec960)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=fffffa80240c6bb0 rbx=0000000000000000 rcx=fffffa80040c6bb0
rdx=fffffa80040c6df0 rsi=0000000000000000 rdi=0000000000000000
rip=fffff800032c4d24 rsp=fffff88008fecaf0 rbp=fffff88003383180
 r8=fffff8a00d746000  r9=fffffa80040c6bb0 r10=fffffa800396fc01
r11=0000000000000800 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei ng nz na pe nc
nt!KiInsertQueueApc+0x74:
fffff800`032c4d24 488910          mov     qword ptr [rax],rdx ds:fffffa80`240c6bb0=????????????????
Resetting default scope

LAST_CONTROL_TRANSFER:  from fffff800032d1be9 to fffff800032d2640

STACK_TEXT:  
fffff880`08fec818 fffff800`032d1be9 : 00000000`0000000a fffffa80`240c6bb0 00000000`00000002 00000000`00000001 : nt!KeBugCheckEx
fffff880`08fec820 fffff800`032d0860 : 00000000`000004d8 fffff8a0`0d5e7060 ffffed82`b281e754 fffffa80`040c6b60 : nt!KiBugCheckDispatch+0x69
fffff880`08fec960 fffff800`032c4d24 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiPageFault+0x260
fffff880`08fecaf0 fffff800`032c5961 : fffffa80`040c6b60 00000000`00000002 fffffa80`040c6b60 fffff880`03383180 : nt!KiInsertQueueApc+0x74
fffff880`08fecb20 fffff800`03521a55 : 00000000`0038f8a8 fffff880`08fecca0 fffffa80`040c6b60 00000000`00000000 : nt!KeSuspendThread+0xa1
fffff880`08fecb60 fffff800`035219b2 : fffffa80`040c6b60 fffff880`08fecc30 fffffa80`03d0c6d0 00000000`0019e801 : nt!PsSuspendThread+0x71
fffff880`08fecbd0 fffff800`032d18d3 : fffffa80`03d0c6d0 00000000`0024002c fffffa80`03f44b30 fffffa80`040c6b60 : nt!NtSuspendThread+0x82
fffff880`08fecc20 00000000`749d2e09 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
00000000`0019e7e8 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x749d2e09


STACK_COMMAND:  kb

FOLLOWUP_IP: 
nt!KiInsertQueueApc+74
fffff800`032c4d24 488910          mov     qword ptr [rax],rdx

SYMBOL_STACK_INDEX:  3

SYMBOL_NAME:  nt!KiInsertQueueApc+74

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nt

IMAGE_NAME:  ntkrnlmp.exe

DEBUG_FLR_IMAGE_TIMESTAMP:  4ce7951a

FAILURE_BUCKET_ID:  X64_0xA_nt!KiInsertQueueApc+74

BUCKET_ID:  X64_0xA_nt!KiInsertQueueApc+74

Followup: MachineOwner
---------

























Loading Dump File [F:\a\Minidump\D M P\DMP\031211-16988-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*c:\websymbols*http://msdl.microsoft.com/download/symbols
Executable search path is: 
Windows 7 Kernel Version 7601 (Service Pack 1) MP (8 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7601.17514.amd64fre.win7sp1_rtm.101119-1850
Machine Name:
Kernel base = 0xfffff800`03254000 PsLoadedModuleList = 0xfffff800`03499e90
Debug session time: Sat Mar 12 12:06:39.795 2011 (UTC - 5:00)
System Uptime: 0 days 1:01:37.966
Loading Kernel Symbols
.................................................
Loading User Symbols
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 50, {fffffa8066623980, 0, fffff800033ffdd3, 5}


Could not read faulting driver name
Probably caused by : ntkrnlmp.exe ( nt!ExFreePoolWithTag+43 )

Followup: MachineOwner
---------

0: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

PAGE_FAULT_IN_NONPAGED_AREA (50)
Invalid system memory was referenced.  This cannot be protected by try-except,
it must be protected by a Probe.  Typically the address is just plain bad or it
is pointing at freed memory.
Arguments:
Arg1: fffffa8066623980, memory referenced.
Arg2: 0000000000000000, value 0 = read operation, 1 = write operation.
Arg3: fffff800033ffdd3, If non-zero, the instruction address which referenced the bad memory
	address.
Arg4: 0000000000000005, (reserved)

Debugging Details:
------------------


Could not read faulting driver name

READ_ADDRESS: GetPointerFromAddress: unable to read from fffff800035050e8
 fffffa8066623980 

FAULTING_IP: 
nt!ExFreePoolWithTag+43
fffff800`033ffdd3 418b45f0        mov     eax,dword ptr [r13-10h]

MM_INTERNAL_CODE:  5

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

BUGCHECK_STR:  0x50

PROCESS_NAME:  System

CURRENT_IRQL:  0

LAST_CONTROL_TRANSFER:  from fffff800032ddf09 to fffff88002d619c2

STACK_TEXT:  
fffff800`00b9cc98 fffff800`032ddf09 : 00000000`0027b58e fffffa80`053c10a8 fffff800`03454cc0 00000000`00000001 : 0xfffff880`02d619c2
fffff800`00b9cca0 fffff800`032cc33c : fffff800`03446e80 fffff800`00000000 00000000`00000000 fffff800`033ebe00 : nt!PoIdle+0x52a
fffff800`00b9cd80 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiIdleLoop+0x2c


STACK_COMMAND:  .bugcheck ; kb

FOLLOWUP_IP: 
nt!ExFreePoolWithTag+43
fffff800`033ffdd3 418b45f0        mov     eax,dword ptr [r13-10h]

SYMBOL_NAME:  nt!ExFreePoolWithTag+43

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nt

IMAGE_NAME:  ntkrnlmp.exe

DEBUG_FLR_IMAGE_TIMESTAMP:  4ce7951a

FAILURE_BUCKET_ID:  X64_0x50_nt!ExFreePoolWithTag+43

BUCKET_ID:  X64_0x50_nt!ExFreePoolWithTag+43

Followup: MachineOwner
---------




Drivers:

Code: 
fffff880`00e00000 fffff880`00e57000   ACPI     ACPI.sys     Sat Nov 20 04:19:16 2010 (4CE79294)
fffff880`011d1000 fffff880`011dc000   amdxata  amdxata.sys  Fri Mar 19 12:18:18 2010 (4BA3A3CA)
fffff880`01154000 fffff880`0115d000   atapi    atapi.sys    Mon Jul 13 19:19:47 2009 (4A5BC113)
fffff880`0115d000 fffff880`01187000   ataport  ataport.SYS  Sat Nov 20 04:19:15 2010 (4CE79293)
fffff880`00cfc000 fffff880`00dbc000   CI       CI.dll       Sat Nov 20 08:12:36 2010 (4CE7C944)
fffff880`01bbb000 fffff880`01beb000   CLASSPNP CLASSPNP.SYS Sat Nov 20 04:19:23 2010 (4CE7929B)
fffff880`00c9e000 fffff880`00cfc000   CLFS     CLFS.SYS     Mon Jul 13 19:19:57 2009 (4A5BC11D)
fffff880`0156d000 fffff880`015df000   cng      cng.sys      Sat Nov 20 05:08:45 2010 (4CE79E2D)
fffff880`01ba5000 fffff880`01bbb000   disk     disk.sys     Mon Jul 13 19:19:57 2009 (4A5BC11D)
fffff880`0104c000 fffff880`01060000   fileinfo fileinfo.sys Mon Jul 13 19:34:25 2009 (4A5BC481)
fffff880`01000000 fffff880`0104c000   fltmgr   fltmgr.sys   Sat Nov 20 04:19:24 2010 (4CE7929C)
fffff880`015f0000 fffff880`015fa000   Fs_Rec   Fs_Rec.sys   Mon Jul 13 19:19:45 2009 (4A5BC111)
fffff880`01b6b000 fffff880`01ba5000   fvevol   fvevol.sys   Sat Nov 20 04:24:06 2010 (4CE793B6)
fffff880`01a68000 fffff880`01ab2000   fwpkclnt fwpkclnt.sys Sat Nov 20 04:21:37 2010 (4CE79321)
fffff800`03209000 fffff800`03252000   hal      hal.dll      Sat Nov 20 08:00:25 2010 (4CE7C669)
fffff880`01b62000 fffff880`01b6b000   hwpolicy hwpolicy.sys Sat Nov 20 04:18:54 2010 (4CE7927E)
fffff880`01187000 fffff880`011a2000   jraid    jraid.sys    Mon Nov 03 21:20:09 2008 (490FB159)
fffff800`00bbf000 fffff800`00bc9000   kdcom    kdcom.dll    Mon Jul 13 21:31:07 2009 (4A5BDFDB)
fffff880`01552000 fffff880`0156d000   ksecdd   ksecdd.sys   Sat Nov 20 04:21:15 2010 (4CE7930B)
fffff880`01679000 fffff880`016a4000   ksecpkg  ksecpkg.sys  Sat Nov 20 05:10:34 2010 (4CE79E9A)
fffff880`00c3b000 fffff880`00c8a000   mcupdate_GenuineIntel mcupdate_GenuineIntel.dll Sat Nov 20 08:03:51 2010 (4CE7C737)
fffff880`010ea000 fffff880`01104000   mountmgr mountmgr.sys Sat Nov 20 04:19:21 2010 (4CE79299)
fffff880`00e60000 fffff880`00e6a000   msisadrv msisadrv.sys Mon Jul 13 19:19:26 2009 (4A5BC0FE)
fffff880`014f4000 fffff880`01552000   msrpc    msrpc.sys    Sat Nov 20 04:21:56 2010 (4CE79334)
fffff880`01b50000 fffff880`01b62000   mup      mup.sys      Mon Jul 13 19:23:45 2009 (4A5BC201)
fffff880`01400000 fffff880`014f3000   ndis     ndis.sys     Sat Nov 20 04:23:30 2010 (4CE79392)
fffff880`01619000 fffff880`01679000   NETIO    NETIO.SYS    Sat Nov 20 04:23:13 2010 (4CE79381)
fffff800`03252000 fffff800`0383c000   nt       ntkrnlmp.exe Sat Nov 20 04:30:02 2010 (4CE7951A)
fffff880`01214000 fffff880`013b7000   Ntfs     Ntfs.sys     Sat Nov 20 04:20:57 2010 (4CE792F9)
fffff880`00eaa000 fffff880`00ebf000   partmgr  partmgr.sys  Sat Nov 20 04:20:00 2010 (4CE792C0)
fffff880`00e6a000 fffff880`00e9d000   pci      pci.sys      Sat Nov 20 04:19:11 2010 (4CE7928F)
fffff880`010d3000 fffff880`010da000   pciide   pciide.sys   Mon Jul 13 19:19:49 2009 (4A5BC115)
fffff880`010da000 fffff880`010ea000   PCIIDEX  PCIIDEX.SYS  Mon Jul 13 19:19:48 2009 (4A5BC114)
fffff880`015df000 fffff880`015f0000   pcw      pcw.sys      Mon Jul 13 19:19:27 2009 (4A5BC0FF)
fffff880`00c8a000 fffff880`00c9e000   PSHED    PSHED.dll    Mon Jul 13 21:32:23 2009 (4A5BE027)
fffff880`01b16000 fffff880`01b50000   rdyboost rdyboost.sys Sat Nov 20 04:43:10 2010 (4CE7982E)
fffff880`011a2000 fffff880`011d1000   SCSIPORT SCSIPORT.SYS Sat Nov 20 05:34:01 2010 (4CE7A419)
fffff880`01b0e000 fffff880`01b16000   spldr    spldr.sys    Mon May 11 12:56:27 2009 (4A0858BB)
fffff880`01864000 fffff880`01a68000   tcpip    tcpip.sys    Sat Nov 20 04:25:52 2010 (4CE79420)
bfc5feff`df7012e3 bfc5ff00`3ac10c12   Unknown_Module_bfc5feff_df7012e3 Unknown_Module_bfc5feff`df7012e3 unavailable (00000000)
fffff880`00e9d000 fffff880`00eaa000   vdrvroot vdrvroot.sys Mon Jul 13 20:01:31 2009 (4A5BCADB)
fffff880`01104000 fffff880`01140000   vmbus    vmbus.sys    Sat Nov 20 04:57:29 2010 (4CE79B89)
fffff880`01ab2000 fffff880`01ac2000   vmstorfl vmstorfl.sys Sat Nov 20 04:57:30 2010 (4CE79B8A)
fffff880`00ebf000 fffff880`00ed4000   volmgr   volmgr.sys   Sat Nov 20 04:19:28 2010 (4CE792A0)
fffff880`01077000 fffff880`010d3000   volmgrx  volmgrx.sys  Sat Nov 20 04:20:43 2010 (4CE792EB)
fffff880`01ac2000 fffff880`01b0e000   volsnap  volsnap.sys  Sat Nov 20 04:20:08 2010 (4CE792C8)
fffff880`00efc000 fffff880`00fa0000   Wdf01000 Wdf01000.sys Mon Jul 13 19:22:07 2009 (4A5BC19F)
fffff880`00fa0000 fffff880`00faf000   WDFLDR   WDFLDR.SYS   Mon Jul 13 19:19:54 2009 (4A5BC11A)
fffff880`01140000 fffff880`01154000   winhv    winhv.sys    Sat Nov 20 04:20:02 2010 (4CE792C2)
fffff880`00e57000 fffff880`00e60000   WMILIB   WMILIB.SYS   Mon Jul 13 19:19:51 2009 (4A5BC117)
 

Upvote 0 Downvote
J

jcheung87

New Member
Joined
Mar 3, 2011
Messages
12
Thread Author #3
Hi thanks for responding! I'm not sure what I should do to update that driver. I tried googling it but I couldn't find any definitive answers.
 

Upvote 0 Downvote
You must log in or register to reply here.

Similar threads

M
  • Solved
Windows 7 Frequent Blue Screen Errors During Gaming: Possible RAM Issues or Other Causes?
Replies
1
Views
2K
kemical
kemical
S
  • Solved
Windows 7 Troubleshooting Random BSOD Issues on Recently Acquired PC During Gaming Sessions
Replies
8
Views
3K
kemical
kemical
W
  • Solved
Windows 7 Troubleshooting Frequent BSOD Errors During Gaming Sessions
Replies
9
Views
5K
widebodymr2619
W
B
  • Solved
Windows 7 Troubleshooting Random BSOD Errors During Gaming and Idling on New Build
Replies
1
Views
1K
WindowsForum AI
WindowsForum AI