Solved Bsod on new pc build, may be in connection with USB3

[speedgamer01]

Hi, my issue started a few days ago, I have got 4 blue screens so far the first one was in clear connection with my usb drivers on the z68 chipset, and the computer got a blue screen when I put it in sleep or hibernated it using AMP WinOff software.
Since then I got 3 others (I have uninstalled the new usb 3 drivers previously)

All 4 says: KERNEL_DATA_INPAGE_ERROR
caused by adress :
- 1st: ntoskrnl.exe+dce3c
- other 3: ntoskrnl.exe+def2c

The last one was minutes ago, my wmp froze, and it offered me to kill the microsoft windows process....
After a minute it gave me the bsod :banghead:
(all of my drivers are from the gigabyte website)
minidumps:
View attachment 163429

 

[zigzag3143]

Hi, my issue started a few days ago, I have got 4 blue screens so far the first one was in clear connection with my usb drivers on the z68 chipset, and the computer got a blue screen when I put it in sleep or hibernated it using AMP WinOff software.
Since then I got 3 others (I have uninstalled the new usb 3 drivers previously)

All 4 says: KERNEL_DATA_INPAGE_ERROR
caused by adress :
- 1st: ntoskrnl.exe+dce3c
- other 3: ntoskrnl.exe+def2c

The last one was minutes ago, my wmp froze, and it offered me to kill the microsoft windows process....
After a minute it gave me the bsod :banghead:
(all of my drivers are from the gigabyte website)
minidumps:
View attachment 163429

Caused by memory corruption. Please run these two tests


Download a copy of Memtest86 and burn the ISO to a CD using Iso Recorder or another ISO burning program.

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.



Driver verifier

I'd suggest that you first backup your stuff 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.

Also and essential. You have drivers from as far back as 1999 that need immediate updating. I am frankly surprised they run at all

cvintdrv.SYS    6/25/1999 5:57:43 PM        0x95ffa000    0x95ffaec0    0x00000ec0    0x3773fb57                        
Aspi32.SYS    9/10/1999 7:46:10 PM        0x914aa000    0x914ade40    0x00003e40    0x37d99842                        
pfc.sys    9/27/2002 6:53:07 PM        0x92034000    0x92036680    0x00002680    0x3d94e153                        
Afc.sys    2/23/2005 2:58:55 AM        0x9202c000    0x92034000    0x00008000    0x421c29af                        
RTCore32.sys    5/25/2005 2:39:05 AM        0xa4da8000    0xa4da9200    0x00001200    0x42941d89                        
MarvinBus.sys    9/23/2005 5:17:57 PM        0x932f9000    0x93327000    0x0002e000    0x43347105                        
ssoftnt4.sys    1/24/2007 2:46:37 AM        0xa4cce000    0xa4ce4f80    0x00016f80    0x45b700cd                        
avidXPserial.sys    9/13/2007 12:55:25 PM        0x910d9000    0x910e6e00    0x0000de00    0x46e96b7d                        
GEARAspiWDM.sys    1/29/2008 1:00:57 PM        0x92037000    0x92039500    0x00002500    0x479f5bc9                        
mcdbus.sys    2/24/2009 6:42:13 AM        0x9324f000    0x9326b800    0x0001c800    0x49a3cf05                        
gdrv.sys    3/12/2009 11:17:32 PM        0xa4deb000    0xa4ded6c0    0x000026c0    0x49b9d04c                        
ALSysIO.sys    4/19/2009 3:41:19 PM        0xa4daa000    0xa4db2000    0x00008000    0x49eb7e5f                        
spldr.sys    5/11/2009 12:13:47 PM        0x8cbcd000    0x8cbd5000    0x00008000    0x4a084ebb                        
amdxata.sys    5/19/2009 1:57:35 PM        0x8c540000    0x8c549000    0x00009000    0x4a12f30f                        
nvstor.sys    5/20/2009 2:44:09 AM        0x8c4d4000    0x8c4f9000    0x00025000    0x4a13a6b9                        
HookCentre.sys    6/19/2009 6:27:03 AM        0xa4d9b000    0xa4da8000    0x0000d000    0x4a3b67f7                        
gdwfpcd32.sys    7/6/2009 9:07:28 PM        0x911db000    0x911e8000    0x0000d000    0x4a529fd0

How To Find Drivers:

- search Google for the name of the driver
- compare the Google results with what's installed on your system to figure out which device/program it belongs to
- visit the web site of the manufacturer of the hardware/program to get the latest drivers (DON'T use Windows Update or the Update driver function of Device Manager).
- if there are difficulties in locating them, post back with questions and someone will try and help you locate the appropriate program.

- - The most common drivers are listed on this page: Driver Reference Driver Reference
- - Driver manufacturer links are on this page: Drivers and Downloads

 

[speedgamer01]

Thank you Zigzag!

I could not start my computer for a short while, and I was browsing around from a laptop.
I've managed to find my install disk, I've put it in and waited for the system startup repair to run (which previously did nothing and keeped looping)
Restart...then Windows came back to life and configured itself. : )

You really opened my eyes about those old drivers, which I would never thought about.
Now I'm gonna take care about the drivers, and run the memory tests in the afternoon/at night.
I will let you know about the results.
Thank you very much!

 

[speedgamer01]

I ended up here with the first driver, I don't have such a hardware, and I am not running any RAID configuration..
Here is the second driver's source page, but i have no idea about those softwares, can I remove these old/unused drivers in any way, do i need to?

 

[zigzag3143]

I ended up here with the first driver, I don't have such a hardware, and I am not running any RAID configuration..
Here is the second driver's source page, but i have no idea about those softwares, can I remove these old/unused drivers in any way, do i need to?

If you arent running a RAID then neither of these drivers are necessary. I would rename them (driver name.bak) to prevent them from loading.