ntoskrnl.exe/ntkrnlmp.exe BSOD Whilst Gaming (0xC000001D)

Could you please upload the new BSODs?

I can indeed. Havent bluescreen'd *yet*. New minidumps are attached!

Update: Just had another one whilst playing Battlefield 3 again (this time on Windows 8)

Its attached below.

Im starting to get real sad now - First my Macbook breaks and the main computer is going crazy too lol!

Thanks in advance for all of your help!

Code:

BugCheck 24, {b50019060b, fffff88002bde328, fffff88002bddb60, fffff803a2773cbe}

Probably caused by : ntkrnlmp.exe ( nt!CcAcquireByteRangeForWrite+56e )

Code:

Usual causes:  Disk corruption, insufficient physical memory, Device driver, Indexing, Resident antivirus, backup, defrag programs, Disk/Drive failing/failure

This bugcheck is caused when a problem is detected within the ntfs.sys driver, which is used to read and write to hard-drives formatted with the NTFS file system. There seems to be quite a few mishandled page faults, and access violations within the dump files in general.

Code:

EXCEPTION_RECORD:  fffff88002bde328 -- (.exr 0xfffff88002bde328)
ExceptionAddress: fffff803a2773cbe (nt!CcAcquireByteRangeForWrite+0x000000000000056e)
   ExceptionCode: c0000005 (Access violation)
  ExceptionFlags: 00000000
NumberParameters: 2
   Parameter[0]: 0000000000000000
   Parameter[1]: 0000000000000100 <-- Non-Paged Pool
Attempt to read from address 0000000000000100

Code:

CONTEXT:  fffff88002bddb60 -- (.cxr 0xfffff88002bddb60)
rax=0000000000000000 rbx=fffffa8003d73120 rcx=0000000000000c2b
rdx=0000000000000c2b rsi=0000000000000000 rdi=0000000000000400
rip=fffff803a2773cbe rsp=fffff88002bde560 rbp=fffff88002bde701
 r8=0000000000000100  r9=0000000000000c2a r10=fffffa8009044194
r11=fffffa8006d926f8 r12=fffff88002bde6f0 r13=fffffa8003d73150
r14=fffffa8009044194 r15=fffff88002bde6a0
iopl=0         nv up ei pl nz na po cy
cs=0010  ss=0018  ds=002b  es=002b  fs=0053  gs=002b             efl=00010207
nt!CcAcquireByteRangeForWrite+0x56e:
fffff803`a2773cbe 418b07          mov     eax,dword ptr [r15] ds:002b:fffff880`02bde6a0=00000000

The instruction in which the exception seems to be caused by is nt!CcAcquireByteRangeForWrite, I'm guessing this instruction queries the size of the data which is going to be written with the I/O stream.

Run some hard-drive diagnostics and follow these steps:

• Hard Drive Diagnostic Procedure

Find your hard-drive manufacturer and run their tests.

Additional Tests:

• SeaTools for DOS | Seagate
• CrystalDiskInfo - Software - Crystal Dew World

Post a screenshot of Crystal Disk Info summary:

• Screenshots and Files - Upload and Post in Seven Forums

writhziden said:

If you have an SSD, make sure the following are up to date:

• SSD firmware
• BIOS Version
• Chipset Drivers
• Hard disk controller drivers/SATA drivers
• If you have a Marvell IDE ATA/ATAPI device, make sure the drivers are up to date from the Intel site or Marvell site and not from your motherboard/vendor support site.

Check for any file system errors and bad sectors using Option #2 of:

• Disk Check

Use this command with Disk Check:

Code:

chkdsk C: /f /r

Here are the Western Digital Tests + Crystal Disk Benchmarks. I dont know much about CrystalDisk but it doesn't look good if I'm honest lol!
I have another drive, a 250gb but its older than the drive I'm using now and I was using it as a backup drive aka old pictures old music etc etc.

I will run the tests that take longer overnight since theyll take a while!

Okay thanks, and the Crystal Disk Info just gives the S.M.A.R.T values.

Do we have any ideas then about these new BSODs? I ran a chkdsk /r /f last night. Not sure where it says the outcome of it though. Unless it only says it when its just finished it. In that case I missed it!

Which ones are you referring to? It could be bad RAM or a bad motherboard DIMM slot, since the instruction was reading from a non-paged pool address.

Read Option #2:

Check Disk (chkdsk) - Read Event Viewer Log

I mean the recent ones. I think I tried the other ram slots before but I will try it again when I get home tonight. And will also check the chkdsk results. Will report back in about 2 hours or so! Thanks :)

The steps I provided are general to all the recent crashes, I just wrote about the Stop 0x24, since that was the dump which provided the most information.

Usual RAM testing procedure -

• RAM - Test with Memtest86+

Run Memtest86+ for least 9-10 passes, and preferably overnight as it can take a while to fully complete.

Test each RAM stick individually, if an error is found then move the same RAM stick into the next DIMM slot and test again, if errors are found for the same RAM stick in every available slot then you have a faulty RAM module. On the other hand, if no errors are found in the next slot or the other slots for the same RAM module, then you have a faulty DIMM slot.

Test each RAM stick and every motherboard DIMM slot available.

Arc said:

No code has to be inserted here. It is a RAM, a bad RAM.

But if you have got a result like that:
No code has to be inserted here. It is a motherboard issue. The particular slot is bad.

Welcome :)