BSOD - Windows 7 64bit

Hi,

I've got another dump file.

Cheers

Code:

BugCheck 24, {1904fb, fffff8800317e078, fffff8800317d8d0, fffff8800124cecd}

Probably caused by : memory_corruption

Code:

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

memory_corruption doesn't necessary mean that a RAM module is faulty, it can also point to a object which corrupted the RAM at the time of the crash, for instance a corrupted driver or program. Paging files and the CPU caches can also be causes.

Code:

CHKIMG_EXTENSION: !chkimg -lo 50 -db !Ntfs
3 errors : !Ntfs (fffff8800124cec3-fffff8800124cedb)
fffff8800124cec0  85  d8  01 *80  00  48  85  c0  74  2f  84 *52  74  2b  48  3b .....H..t/.Rt+H;
fffff8800124ced0  de  7e  26  48  3b  df  48  0f  4f  fb  48 *09  bc  24  e0  00 .~&H;.H.O.H..$..

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

Hi,

I don't think the RAM is corrupted; I ran memtest86+ with multiple passes and it declared that nothing was wrong.

I have also checked my HDD's before using chkdsk and seatools a few months ago, but I'll try again.

Here's the crystaldiskinfo:


Thanks

Your S.M.A.R.T readings seem to be fine, and how many passes did you run MemTest for?

Hi there,

Sorry I haven't replied, I don't remember how many passes but it was for a day or so.

I've upgraded to windows 8 pro (hope that's not a problem) and I've attached some more BSOD dumps.

Cheers,

Jordan

Code:

BugCheck 3B, {c0000005, fffff960000deef2, fffff8801c7dacc0, 0}

Probably caused by : memory_corruption

Code:

Usual causes:  System service, Device driver, graphics driver, memory

Code:

2: kd> !error 00000000c0000005
Error code: (NTSTATUS) 0xc0000005 (3221225477) - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.

Code:

!chkimg -lo 50 -db !win32k
6 errors : !win32k (fffff960000deec3-fffff960000deefb)
fffff960000deec0  8b  5c  24 *d0  8b  c3  bb  01  00  00  00 *cc  3b  5f  08  0f .\$.........;_..
...
fffff960000deee0  20  e9  6f *df  ff  ff  cc  90  90  90  90 *b0  90  90  90  90  .o.............
fffff960000deef0  ff  f3  48 *a3  ec  20  48  83  39  00  48 *ab  d9  75  06  48 ..H.. H.9.H..u.H

The above extension checks for errors with the modules of files and drivers stored within the RAM.

-->Memory:

• RAM - Test with Memtest86+

Run Memtest86+ for least 7-8 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.

-->What are the results of the hard-drive tests?

Hi,

I did as you said, and have no problems with the RAM after 7 passes.

The hdds (using seagate tools) were absolutely fine.

I've also more dumps so hopefully they will help!

Cheers :)

Code:

BugCheck BE, {fffff683fb223d20, 13c000006c229025, fffff8801e0a0850, b}

Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+312a3 )

Code:

Usual causes:  Device driver, Memory

A driver has attempted to write to a virtual memory address.

Run Driver Verifier to scan for any corrupted drivers which may be causing problems, this program works by running various stress tests on drivers, in order to produce a BSOD which will locate the driver; run for least 24 hours:

• Driver Verifier - Enable and Disable

   Information

Additional Help - Using Driver Verifier to identify issues with Drivers

hi,

I've been having some BSODs in the last day or 2, and I've had a couple of different errors, mainly DRIVER_IRQL_NOT_LESS_OR_EQUAL

I have a Clevo w35_37ET with windows 7 ultimate x64, but i'm not very familiar with this type of errors, any help would be welcome. Thanks!

Please start your own thread, - BSOD Help and Support - Windows 7 Help Forums - and then follow these instructions again:
Blue Screen of Death (BSOD) Posting Instructions. Somone will be able to assist you with your problem.

Having different problems from different users just gets confusing.